80DMR
Uploaded by
parashar150580DMR
Uploaded by
parashar1505Siebel Data Model
Reference
Version 8.0
December 2006
Copyright 2005, 2006, Oracle. All rights reserved.
The Programs (which include both the software and documentation) contain proprietary information;
they are provided under a license agreement containing restrictions on use and disclosure and are also
protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering,
disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability
with other independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems
in the documentation, please report them to us in writing. This document is not warranted to be errorfree. Except as may be expressly permitted in your license agreement for these Programs, no part of
these Programs may be reproduced or transmitted in any form or by any means, electronic or
mechanical, for any purpose.
PRODUCT MODULES AND OPTIONS. This guide contains descriptions of modules that are optional and
for which you may not have purchased a license. Siebels Sample Database also includes data related to
these optional modules. As a result, your software implementation may differ from descriptions in this
guide. To find out more about the modules your organization has purchased, see your corporate
purchasing agent or your Siebel sales representative.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs
on behalf of the United States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS. Programs, software, databases, and related documentation and technical
data delivered to U.S. Government customers are "commercial computer software" or "commercial
technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific
supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the
Programs, including documentation and technical data, shall be subject to the licensing restrictions set
forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set
forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle USA,
Inc., 500 Oracle Parkway, Redwood City, CA 94065.
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently
dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup,
redundancy and other measures to ensure the safe use of such applications if the Programs are used for
such purposes, and we disclaim liability for any damages caused by such use of the Programs.
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from third
parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites.
You bear all risks associated with the use of such content. If you choose to purchase any products or
services from a third party, the relationship is directly between you and the third party. Oracle is not
responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of
the agreement with the third party, including delivery of products or services and warranty obligations
related to purchased products or services. Oracle is not responsible for any loss or damage of any sort
that you may incur from dealing with any third party.
Contents
Siebel Data Model Reference 1
Chapter 1: Whats New in This Release
Chapter 2: Data Model Overview
Chapter 3: Understanding the Logical Model
Entity Relationship Diagram Conventions
11
General Entities 12
Exclusive Arc Relationship 12
Recursive Relationship 13
Entity Relationship Diagrams and Descriptions
Account 17
Adjustment Group 20
Asset Management 22
Auction 24
Auto Email Response Generator 26
CG Promotion Planning
28
Compensation Planning Administration
Compensation Planning Execution 33
Competency Management System 35
Content Management 37
Contract Conditions 39
Contracts 41
Data Visibility 43
Dun & Bradstreet Integration 46
Employee KPI 48
Expense Reports 50
Field Service Inventory 52
Field Service Scheduler 54
Forecasts 56
High Tech Marketing Development Fund
Invoiceable Charges 60
Invoices 62
Marketing Budget Request 64
Marketing Campaign
66
Marketing Collaboration 68
14
31
58
Siebel Data Model Reference Version 8.0
Contents
Marketing Encyclopedia 70
Marketing Events 72
Marketing Plans 75
Marketing Program 77
Marketing Resource Management: Document
Opportunity Management 82
Order Life Cycle 84
Orders 86
Partner Collaboration 88
Partner Program Registration 90
Party Model 92
Payments 94
Performance Review 96
Personal Account 99
Personal Financial Review 101
Pricing Comparison 103
Pricing 105
Product Promotion 107
Product Quality Tracking 109
Product Recommendation 111
Products or Services 113
Professional Services 115
Revenue 117
Sales Hierarchy and Credit Assignment 119
Sales Portfolio Management 121
Service Agreement 123
Service Calendars and Work Shifts 125
Service Request 127
Shipment 129
Siebel Assistant 131
Territory Management 133
Territory Quota Rollup 135
Textile, Apparel, and Footwear 137
Time Sheet 139
Trade Promotions 141
Training Curriculum Course 143
Training Test Engine 145
Versioned Object Definition 147
Warranty 149
80
Chapter 4: Understanding the Physical Model
Data Model Naming Conventions
4
151
Siebel Data Model Reference Version 8.0
Contents
Table Naming Conventions 151
Index Naming Conventions 153
Column Naming Conventions 153
Abbreviations Used in the Physical Model Listings
Data Model Type Definitions
154
154
Table Type Definitions 155
Table Status Definitions 156
Column Type Definitions 157
Domain Type Definitions 157
Columns of Numeric Physical Type
Siebel System Fields
158
158
INTEGRATION_ID Columns
Include Only Field
159
Siebel Repository
159
Database Schema Version
159
160
Limit Checking for Data Types
Validating the Siebel Schema
160
160
Party Model Unifies Access to Data
161
Chapter 5: Schema Changes
Table Changes in This Version
163
Tables That Are New in this Version
Tables That Changed in this Version
163
169
Table Column Changes in This Version
169
Table Columns That Are New in This Version 169
System Columns That Are New in This Version 182
Table Columns That Changed in This Version 182
Table Index Changes in This Version
183
Table Indexes That Are New in This Version 183
Table Indexes That Changed in This Version 185
Table Indexes That Are Deprecated in This Version
188
Index
Siebel Data Model Reference Version 8.0
Contents
Siebel Data Model Reference Version 8.0
Whats New in This Release
Whats New in Siebel Data Model Reference, Version 8.0
Table 1 lists changes described in this version of the documentation to support release 8.0 of the
software.
Table 1.
Whats New in Siebel Data Model Reference, Version 8.0
Topic
Description
Column changes
A listing of column changes in this schema including new
columns, deprecated columns, and changes to existing column
definitions.
See Table Column Changes in
This Version on page 169.
Marketing Budget Request ERD
A new entity-relationship diagram.
See Marketing Budget Request
on page 64.
This ERD illustrates the Marketing Resource Management
budget request process.
Marketing Program ERD
This entity-relationship diagram has been modified.
See Marketing Program on
page 77.
A new entity Offer has been added and campaign targeting is
now performed at the offer level.
Marketing Resource
Management: Document ERD
A new entity-relationship diagram.
See Marketing Resource
Management: Document on
page 80.
This ERD illustrates the Marketing Resource Management
marketing content process.
Sales Portfolio Management ERD
A new entity-relationship diagram.
See Sales Portfolio
Management on page 121.
The Portfolio Management Process allows portfolio managers to
manage a group of strategic accounts by:
Table changes
See Table Changes in This
Version on page 163.
Assessing the potential of their assigned accounts
Engaging the high-potential accounts within their portfolio
Directing and managing the resources at their disposal
Managing ongoing relationships with customers and
partners
A listing of table changes in this schema including new tables,
deprecated tables, and changes to existing table definitions.
Siebel Data Model Reference Version 8.0
Whats New in This Release
Table 1.
Whats New in Siebel Data Model Reference, Version 8.0
Topic
Description
Table index changes
A listing of index changes in this schema including new indexes,
deprecated indexes, and changes to existing index definitions.
See Table Index Changes in This
Version on page 183.
Territory Management ERD
See Territory Management on
page 133.
The relationship from Territory to Territory Hierarchy has been
changed from mandatory to optional and moved out of the
Territory user key. Territory is now multi-org enabled.
Territory Quota Rollup
A new entity-relationship diagram.
See Territory Quota Rollup on
page 135.
This data model supports quota assignment and quota rollup to
a territory. Users can define quotas, spread them over several
periods, and assign them to contacts, accounts, regions, and
ZIP codes.
Siebel Data Model Reference Version 8.0
Data Model Overview
Oracles Siebel Data Model defines how the data used by Siebel Business Applications is stored in a
standard third-party relational DBMS such as DB2, Microsoft SQL Server, or Oracle. The Siebel Data
Model also defines some of the data integrity constraints validated by Siebel Business Applications.
NOTE: The terms and conditions of your license agreement with Oracle permits use only of those
portions of the Siebel Data Model that correspond to the Siebel products you have purchased. You
are not entitled to use any portion of the Siebel Data Model to support Siebel products for which you
have not purchased the required licenses.
The Siebel Data Model is designed for speed and performance in data entry, running limited scope
queries, and managing processes like call scripting. These tasks are considered transactions, and the
database used is called an online transaction processing (OLTP) database.
Optimizing a database used for these purposes requires a design, or schema, that puts each unit of
information in a single location in the database. This allows you to update the data efficiently, since
you do not have to update the same unit of data in several different locations. Most tables in an OLTP
database have links, or join paths, to other tables, sometimes to many other tables.
The database design used in an OLTP database is usually normalized. There are several levels of
database normalization, ranging from first to fifth normal form. The Siebel database is in third
normal form.
The information in this reference is intended as an aid in configuring and using Siebel Business
Applications.
CAUTION: Do not attempt to insert or update data in the Siebel Business Applications tables
through non-Siebel application products. Doing so can render your Siebel database unusable;
additionally, you limit the ability of Oracle to provide you with quality support.
To learn how to configure an application to insert, update, and delete data interactively, read the
Siebel Developers Reference. To learn how to insert, update, and delete data in large quantities,
read the Siebel Enterprise Integration Manager Administration Guide.
Siebel Data Model Reference Version 8.0
Data Model Overview
10
Siebel Data Model Reference Version 8.0
Understanding the Logical
Model
The Siebel logical model represents the following in Siebel Business Applications:
Entities
Relationships between entities
This information is represented in entity relationship diagrams (ERDs).
Oracle has made and continues to make a significant investment in modeling the business functions
of sales, marketing, and service organizations. The entity relationship diagrams included in this
chapter represent the logical model for the current release of Siebel Business Applications. In some
areas, the model extends beyond the current implementation. Published entities, therefore, might
appear in the logical model that may not be implemented in the physical model at the present time.
The ERDs included in this publication are those that are the most useful to individuals involved in
implementing or integrating Siebel Business Applications. These diagrams cover the application
areas that are most relevant to a functional understanding of the application.
The information on ERDs is organized as follows:
Entity Relationship Diagram Conventions
Entity Relationship Diagrams and Descriptions on page 14
Entity Relationship Diagram
Conventions
This topic describes entity relationship diagram conventions, as follows:
General Entities on page 12
Exclusive Arc Relationship on page 12
Recursive Relationship on page 13
Siebel Data Model Reference Version 8.0
11
Understanding the Logical Model Entity Relationship Diagram Conventions
General Entities
Figure 1 shows the diagram conventions for general entities used in this publication.
Figure 1.
General Entity Relationship Diagram Conventions
Exclusive Arc Relationship
Figure 2 illustrates an example of the exclusive arc relationship. An exclusive arc is an arc across two
or more relationship ends; you can read each exclusive arc relationship as follows:
12
Siebel Data Model Reference Version 8.0
Understanding the Logical Model Entity Relationship Diagram Conventions
Each [entity] must be [relationship name] either to one and only one [entity] or [relationship name]
to one and only one [entity]. For example, each Product Comparison must be to either one and only
one Product Internal or to one and only one Product External as shown in Figure 2.
Figure 2.
Exclusive Arc Relationship Diagram Convention Example
Recursive Relationship
Figure 3 illustrates an example of the recursive relationship. A recursive relationship is one in which
an entity has a relationship to itself. For example, each activity might be part of one and only one
activity, or each activity might be made up of one or more activities, as shown in Figure 3.
Recursive relationships are almost always optional, and either one-to-many or many-to-many.
Part of
Activity
Made up of
Entity Relationship Example:
1) Each activity may by made up of one or more activities.
2) Each activity may be part of one and only one activity.
Figure 3.
Recursive Relationship Diagram Convention Example
Siebel Data Model Reference Version 8.0
13
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Entity Relationship Diagrams and
Descriptions
ERDs represent the significant entities and relevant relationships in a functional area. To enhance
their readability, the diagrams do not include every relationship and subtype. Some many-to-many
relationships have also been preserved instead of showing them as one-to-many relationships
around intersection tables in the logical model.
Table 2 provides a list of ERDs in alphabetic order.
Table 2.
Entity Relationship Diagrams
ERD Name
Figure Num.
and Page
Functional Area
Account
Figure 4 on
page 19
General
Adjustment Group
Figure 5 on
page 21
General
Asset Management
Figure 6 on
page 23
General
Auction
Figure 7 on
page 25
General
Auto Email Response Generator
Figure 8 on
page 27
General
CG Promotion Planning
Figure 9 on
page 30
Marketing
Compensation Planning Administration
Figure 10 on
page 32
ERM
Compensation Planning Execution
Figure 11 on
page 34
ERM
Competency Management System
Figure 12 on
page 36
ERM
Content Management
Figure 13 on
page 38
General
Contract Conditions
Figure 14 on
page 40
General
Contracts
Figure 15 on
page 42
General
Data Visibility
Figure 16 on
page 45
General
Dun & Bradstreet Integration
Figure 17 on
page 47
Sales/Marketing
14
Siebel Data Model Reference Version 8.0
Revised
in 8.0
New
in 8.0
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Table 2.
Entity Relationship Diagrams
ERD Name
Figure Num.
and Page
Functional Area
Employee KPI
Figure 18 on
page 49
ERM
Expense Reports
Figure 19 on
page 51
General
Field Service Inventory
Figure 20 on
page 53
Service
Field Service Scheduler
Figure 21 on
page 55
Service
Forecasts
Figure 22 on
page 57
Sales/Marketing
High Tech Marketing Development Fund
Figure 23 on
page 59
Marketing
Invoiceable Charges
Figure 24 on
page 61
Service
Invoices
Figure 25 on
page 63
Service
Marketing Budget Request
Figure 26 on
page 65
Marketing
Marketing Campaign
Figure 27 on
page 67
Marketing
Marketing Collaboration
Figure 28 on
page 69
Marketing
Marketing Encyclopedia
Figure 29 on
page 71
Sales/Marketing
Marketing Events
Figure 30 on
page 74
General
Marketing Plans
Figure 31 on
page 76
Marketing
Marketing Program
Figure 32 on
page 79
Marketing
Marketing Resource Management:
Document
Figure 33 on
page 81
Marketing
Opportunity Management
Figure 34 on
page 83
Sales
Order Life Cycle
Figure 35 on
page 85
General
Revised
in 8.0
New
in 8.0
Yes
Yes
Yes
Siebel Data Model Reference Version 8.0
15
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Table 2.
Entity Relationship Diagrams
ERD Name
Figure Num.
and Page
Functional Area
Orders
Figure 36 on
page 87
General
Partner Collaboration
Figure 37 on
page 89
General
Partner Program Registration
Figure 38 on
page 91
General
Party Model
Figure 39 on
page 93
General
Payments
Figure 40 on
page 95
General
Performance Review
Figure 41 on
page 98
ERM
Personal Account
Figure 42 on
page 100
Industry-Specific
Personal Financial Review
Figure 43 on
page 102
Industry-Specific
Pricing Comparison
Figure 44 on
page 104
Energy
Pricing
Figure 45 on
page 106
General
Product Promotion
Figure 46 on
page 108
General
Product Quality Tracking
Figure 47 on
page 110
General
Product Recommendation
Figure 48 on
page 112
General
Products or Services
Figure 49 on
page 114
Service
Professional Services
Figure 50 on
page 116
General
Revenue
Figure 51 on
page 118
General
Sales Hierarchy and Credit Assignment
Figure 52 on
page 120
Sales
Sales Portfolio Management
Figure 53 on
page 122
Sales
16
Siebel Data Model Reference Version 8.0
Revised
in 8.0
New
in 8.0
Yes
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Table 2.
Entity Relationship Diagrams
ERD Name
Figure Num.
and Page
Functional Area
Service Agreement
Figure 54 on
page 124
Service
Service Calendars and Work Shifts
Figure 55 on
page 126
Service
Service Request
Figure 56 on
page 128
Service
Shipment
Figure 57 on
page 130
General
Siebel Assistant
Figure 58 on
page 132
General
Territory Management
Figure 59 on
page 134
Sales
Territory Quota Rollup
Figure 60 on
page 136
Sales
Textile, Apparel, and Footwear
Figure 61 on
page 138
Industry-Specific
Time Sheet
Figure 62 on
page 140
General
Trade Promotions
Figure 63 on
page 142
General
Training Curriculum Course
Figure 64 on
page 144
General
Training Test Engine
Figure 65 on
page 146
General
Versioned Object Definition
Figure 66 on
page 148
General
Warranty
Figure 67 on
page 150
Service
Revised
in 8.0
New
in 8.0
Yes
Yes
Account
Figure 4 shows the Account ERD. The account entity is a key entity in the Siebel Data Model. The
account entity appears in many diagrams in this publication, and is often referred to as an
organization unit.
Siebel Data Model Reference Version 8.0
17
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
The account entity is a subtype of party composed of one or more people or contacts. An account is
any organization or subset of an organization that can be sold to or serviced. An account might
represent a company, a site, a subsidiary, a division, or any other subset of an organization. An
account might also represent a governmental agency, club, or other formal or informal group of
individuals. Each account might be accessible at one or more addresses.
The account entity supports Global Account Views and Dynamic Hierarchy. This allows a universal
view of all customer interactions. The Global Account Views present accounts in the context of a
customizable hierarchy, allowing navigation to parent and child accounts. Roll-up and roll-down
functionality gives users access to account-specific information, and aggregate information including
child accounts, activities, contacts, opportunities, and the account team.
Dynamic Hierarchy allows the Global Account Views to display a different hierarchy depending on the
business unit of the user. Each custom account hierarchy is represented completely in a relationship
table. The relationships are then denormalized into a separate table to be used for roll-up support.
Table 3 lists the entities in this ERD and their corresponding tables.
Table 3.
Account ERD Entities and Tables
Entity
Tables
Account
S_ORG_EXT, S_PARTY
Account Synonym
S_ORG_SYN
Activity
S_EVT_ACT
Address
S_ADDR_ORG
Assignment Group (Territory)
S_ASGN_GRP
Business Unit
S_BU, S_ORG_EXT, S_PARTY
Characteristics
S_CHRCTR
Dynamic Account Hierarchy
S_DYN_HRCHY
Dynamic Account Hierarchy Node
S_DYN_HRCHY_REL
Employee/Agent
S_EMP_PER, S_CONTACT, S_PARTY
Industry
S_INDUST
Market Segment
S_MKT_SEG
Party
S_PARTY
Payment Term
S_PAYMENT_TERM
Person
S_CONTACT, S_PARTY
Position
S_POSTN, S_PARTY
Price List
S_PRI_LST
Sales or Service Team Member
S_ACCNT_POSTN
18
Siebel Data Model Reference Version 8.0
part of
PAYMENT TERM
default payment term for
for
OTHER PERSON
PERSON
contact of
composed of
a parent of
user of
applicable to
a report to
POSITION
held by
responsibility of
access to
EMPLOYEE / AGENT
target of
current price
list for
holders
of
SALES OR SERVICE
TEAM MEMBER
responsible for
PRICE LIST
participant in
ASSIGNMENT
GROUP
(TERRITORY)
user characteristics for
described in
belong to
pay or payed by
target of
participate in
action for
MARKET
SEGMENT
addressed to
CORRESPONDENCE
ACTIVITY
type of
OTHER
PARTY
for
DECISION
ISSUES
another name for
responsibility of
constrained to use
responsible for
ACCOUNT
known as
for
ADDRESS
located at
acessible to
NAMED HIERARCHY
made up of
of
a parent of
BUSINESS UNIT
PARTY
made visible through
for
NAMED HIERARCHY
ACCOUNT
a report to
classification for
CHARACTERISTIC
Figure 4.
ACCOUNT SYNONYM
INDUSTRY
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Account
Siebel Data Model Reference Version 8.0
19
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Adjustment Group
Figure 5 shows the Adjustment Group ERD. This ERD illustrates the system for managing the various
matrices for pricing, compatibility, eligibility, product promotions, and so on. It allows the user to
define a matrix, its dimensions, and all of its rules. This new infrastructure allows the adjustment to
be any value, not just a price amount.
Table 4 lists the entities in this ERD and their corresponding tables.
Table 4.
Adjustment Group ERD Entities and Tables
Entity
Tables
Adjustment Group
S_ADJ_GROUP
Adjustment Group Dimension
S_ADJ_GROUP_DIM
Product Compatibility Matrix Rule
S_PRODCOMP_MTRX
Product Eligibility Matrix Rule
S_PRODELIG_MTRX
Product Promotion Pricing Matrix Rule
S_PROM_PMTRX
Standard Entitlement Pricing Matrix Rule
S_STDENTL_PMTRX
Standard Product Pricing Matrix Rule
S_STDPROD_PMTRX
Standard Training Pricing Matrix Rule
S_STDTRNG_PMTRX
20
Siebel Data Model Reference Version 8.0
for
# MTRX_RULE_NUM
STANDARD TRAINING PRICING MATRIX RULE
# MTRX_RULE_NUM
STANDARD PRODUCT PRICING MATRIX RULE
# MTRX_RULE_NUM
STANDARD ENTITLEMENT PRICING MATRIX
RULE
# MTRX_RULE_NUM
for
for
for
PRODUCT PROMOTION PRICING MATRIX RULE for
# MTRX_RULE_NUM
for
contain
contain
contain
contain
contain
contain
# FIELD_NAME
ADJUSTMENT GROUP
DIMENSION
for
contain
# ADJ_GROUP_NAME
Figure 5.
PRODUCT ELIGIBILITY MATRIX RULE
# MTRX_RULE_NUM
PRODUCT COMPATABILITY MATRIX RULE
ADJUSTMENT GROUP
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Adjustment Group
Siebel Data Model Reference Version 8.0
21
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Asset Management
Figure 6 shows the Asset Management ERD. This ERD illustrates how Siebel Business Applications
track instances of assets. Moving counter-clockwise from the lower-right corner, the diagram shows
how internal products can be made into assets and associated with an account or a contact to register
ownership. Additional relationships between assets and accounts, contacts, and employees are
illustrated in the upper-right corner. Additional information such as the related opportunities, the
current business or personal address location of the asset, notes, and related assets are shown
across the top of the diagram. The left side of the diagram shows the relationships with service
requests, activities, and related part movements.
Table 5 lists the entities in this ERD and their corresponding tables.
Table 5.
Asset Management ERD Entities and Tables
Entity
Tables
Activity
S_EVT_ACT
Activity Part Movement
S_ACTPART_MVMT
Asset Contact Relationship
S_ASSET_CON
Asset Employee Relationship
S_ASSET_EMP
Asset External Organization
S_ASSET_ACCNT
Asset Feature
S_ASSET_FEA
Asset Modification
S_ASSET_TXN
Asset Relationship
S_ASSET_REL
Business Address
S_ADDR_ORG
Competitive Metric
S_CMPT_MTRC
Competitive Product Feature
S_CMPT_PROD_FEA
Contact
S_CONTACT, S_PARTY
Employee
S_EMP_PER, S_CONTACT, S_PARTY
External Product
S_PROD_EXT
Internal Product
S_PROD_INT
Opportunity
S_OPTY
Opportunity Asset
S_OPTY_ASSET
Person
S_CONTACT, S_PARTY
Personal Address
S_ADDR_PER
Product Instance (Asset)
S_ASSET
Service Request
S_SRV_REQ
22
Siebel Data Model Reference Version 8.0
initiated by
for problems with
SERVICE
REQUEST
for
of
ASSET
RELATIONSHIP
ACTIVITY PART
MOVEMENT
of
moved by
ASSET
FEATURE
of
COMPETITIVE
PRODUCT
FEATURE
a component of
an assembly of
of
of
subject of
subject of
moved by
use of
NON-SERIALIZABLE
PRODUCT
INTERNAL PRODUCT
PRODUCT
involved in
parent of
EXTERNAL
PRODUCT
child of
vendor of
VENDOR
OTHER EXTERNAL
ORGANIZATION
ACCOUNT
SERIALIZABLE
PRODUCT
made into
produced by
owner of
EXTERNAL
ORGANIZATION
associated with
associated with
associated with
EMPLOYEE
currently possessed by
possessor of
owner of
currently owned by
use of
to
to
to
OPPORTUNITY
currently owned byCONTACT
PERSON
ASSET CONTACT RELATIONSHIP
instance of
involved in
ASSET
MODIFICATION
for
modified by
initiated by
ASSET EMPLOYEE RELATIONSHIP
ASSET EXTERNAL ORGANIZATION
for
of
subject
of
subject of
located at
subject of
initiator of
subject of
subject of
for
NOTE
for
of
classification for
COMPETITIVE
of
METRIC
classification for
of
for
subject of
for
PRODUCT INSTANCE (ASSET)
associated with
associated with
subject of
subject of
defined for
for problems with
subject of
initiator of
made up of
defined for
part of
performed on
made up of
BUSINESS
ADDRESS
OPPORTUNITY
ASSET
Figure 6.
ACTIVITY
part of
PERSONAL
ADDRESS
ADDRESS
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Asset Management
Siebel Data Model Reference Version 8.0
23
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Auction
Figure 7 shows the Auction ERD. This ERD illustrates how the Siebel Data Model represents the
auctioning of goods or services to bidders. An auction item may be a stand-alone offering, or may
be a specific instance of an offering of a quantity of product or of a particular asset for sale. An
auction item must be listed by a corporate or individual user, but that user may be either internal to
or external to the Siebel-owning company. Auction items are displayed to bidders through one or
more categories in a catalog. Fulfillment of an auction item to the winning bidders may be tracked
through one or more order items. Finally, users may set up watched items, may define alerts, and
may rate fellow listers or bidders.
Table 6 lists the entities in this ERD and their corresponding tables.
Table 6.
Auction ERD Entities and Tables
Entity
Tables
Asset
S_ASSET
Auction Alert Definition
S_AUC_ALRT_DEF
Auction Item
S_AUC_ITEM
Auction Item Bid
S_AUC_BID
Auction Item Promotion
S_AUC_ITM_PROMO
Auction Item Watch
S_AUC_WATCH
Auction Lister/Bidder Rating
S_AUC_RATING
Catalog
S_CTLG
Catalog Category
S_CTLG_CAT
Catalog Category Item
S_CTLG_CAT_PROD, S_CTLGCAT_ASSET, S_CTLG_CAT_AUC
Order
S_ORDER
Order Item
S_ORDER_ITEM
Party
S_PARTY
Person
S_CONTACT
Product
S_PROD_INT
Triggered Auction Alert Item
S_AUC_ALRT
User
S_USER, S_CONTACT, S_PARTY
24
Siebel Data Model Reference Version 8.0
OTHER PARTY
PARTY
OTHER PERSON
USER
lister of
listed by
AUCTION ITEM
placer of
subject of
featured in
PERSON
for
for
fulfilled as
fulfillment of
placed by
AUCTION ITEM BID
AUCTION ITEM
PROMOTION
ORDER
composed of
part of
ORDER ITEM
for
for
subject of
subject of
pricing
mechanism
for
ASSET
creator of
for
AUCTION ITEM WATCH
alerted by
for
represented by
TRIGGERED AUCTION ITEM ALERT
priced by
displayed as
PRODUCT
displayed as
represented by
priced by
pricing
mechanism
for
created from
for
creator of
subject of
made by
applicable to
made up of
rating of
creator of
created by
AUCTION ALERT
DEFINITION
subject of
AUCTION LISTER/BIDDER
RATING
genesis of
created
from
CATALOG
owner of
owner of
CATALOG CATEGORY
part of
Figure 7.
represented as
CATALOG CATEGORY ITEM
accessed
via
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Auction
Siebel Data Model Reference Version 8.0
25
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Auto Email Response Generator
Figure 8 shows the Auto Email Response Generator ERD. This ERD illustrates the data model for the
automatic generation of a response to an inbound communication. Incoming messages (inbound
communications) are compared against a database of previously categorized messages to categorize
them in one or more categories. The categories are associated with predefined template
communication responses, used to generate a default response to each category of message. A
notification mechanism can be defined to alert a person whenever the usage of a category or
template exceeds a predefined limit.
Table 7 lists the entities in this ERD and their corresponding tables.
Table 7.
Auto Email Response Generator ERD Entities and Tables
Entity
Tables
Activity
S_EVT_ACT
Catalog
S_CTLG
Catalog Category
S_CTLG_CAT
Category Usage Notification
S_COMM_CTG_NTFY
Communication Template Usage Notification
S_COMMTMPL_NTFY
Person
S_CONTACT, S_PARTY
Problem Resolution Document
S_RESITEM
Template Communication Response
S_DMND_CRTN_PRG
26
Siebel Data Model Reference Version 8.0
subject of
for usage of
PERSON
target of
COMMUNICATION TMPL USAGE
NOTIFICATION
OUTBOUND RESPONSE
INBOUND COMMUNICATION
PROBLEM
RESOLUTION
DOCUMENT
to notify
categorized within
target of
to notify
CATEGORY
USAGE
NOTIFICATION
classification of
default response for
subject of
for usage of
classification for
categorized under
classification for
made up
part of
CATALOG
made up of
CATALOG CATEGORY
part of
Figure 8.
TEMPLATE COMMUNICATION RESPONSE
ACTIVITY
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Auto Email Response Generator
Siebel Data Model Reference Version 8.0
27
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
CG Promotion Planning
Figure 9 shows the CG Promotion Planning ERD. This ERD illustrates how Siebel Business Applications
support the funding of trade promotions in channel management and the Consumer Goods (CG)
industry. Marketing development funds (MDFs) are defined for an account, for a product line or
product category, and for an accounting period. An MDF can be a fixed sum of money, an accrual
fund, or a mixture of the two. The value of the accrual fund is typically determined based on an
accrual rate multiplied by either the number of units sold, or the revenue in a given period from one
or more specific products that are representative of the product line or category of the fund. Planned
expenses for the various tactics involved in the planning and execution of product promotions can
be allocated to one or more MDFs. Allocations that have not yet been approved are considered fund
requests. One or more such MDF allocations may be covered by a single payment to the partner
account.
Advanced Planning is a feature designed to address the process used by CG organizations to plan
sales volume and sales revenue at key accounts. Advanced Planning is part of a broader process
called Trade Marketing. Trade Marketing includes planning, executing, and analyzing sales.
Table 8 lists the entities in this ERD and their corresponding tables.
Table 8.
CG Promotion Planning ERD Entities and Tables
Entity
Tables
Account
S_ORG_EXT, S_PARTY
Authorized Product
S_ORG_PROD
Fund Allocation
S_MDF_ALLOC
Marketing Development Fund
S_MDF
Marketing Event or Activity
S_SRC
MDF Accrual
S_MDF_ACCRUAL
Payment
S_SRC_PAYMENT
Period
S_PERIOD
Person
S_CONTACT, S_PARTY
Position
S_POSTN, S_PARTY
Price List
S_PRI_LST
Price List Item
S_PRI_LST_ITEM
Product Internal
S_PROD_INT
Product Line
S_PROD_LN
Product Structure
S_PROD_REL or S_PROD_ITEM
Promotion Plan
S_SRC
Promotion
S_SRC
Promotion Account
S_SRC
28
Siebel Data Model Reference Version 8.0
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Table 8.
CG Promotion Planning ERD Entities and Tables
Entity
Tables
Promotion Product
S_SRC
Promotion Category
S_SRC
Promotion Account Product
S_SRC
Siebel Data Model Reference Version 8.0
29
30
of
subject of
Siebel Data Model Reference Version 8.0
MIXED FUND
FIXED FUND
ACCRUAL
FUND
MARKETING
part of DEVELOPMENT
FUND
made up of
sub allocated to
defined for
for
funded through
for promotion of
for promotion of
AUTHORIZED
PRODUCT
designated to
responsible for
assigned to
responsible for
assigned to
approved by
requested by
to
covered by
earned in
earned by
earned by
PRICE LIST ITEM
subject of
relation of
earner of
subject of
of
for
ACCOUNT
OTHER PERSON
EMPLOYEE / AGENT
PERSON
target of
related to
MDF ACCRUAL
of
at
POSITION
approver of
requestor of
for
OTHER PAYMENT
PROMOTION PAYMENT
PAYMENT
subject of
subject of
subject of
PRODUCT LINE
PERIOD
earner of
part of
subject of
subject of
subject of
of
of
hierarchy child of
hierarchy parent of
INTERNAL PRODUCT OR
SERVICE
a component of
promoted via
an assembly of
subject of
basis for
for
PRODUCT
STRUCTURE
defined for
OTHER MARKETING EVENT OR
ACTIVITY
PROMOTION ACCOUNT PRODUCT
PROMOTION PRODUCT
PROMOTION CATEGORY
PROMOTION ACCOUNT
PROMOTION
user of
composed of
based on
PRICE LIST
used by
available to
defined for
part of
made of
recipient of
applicable to
subject to
target of
subject of
composed of
for
PROMOTION PLAN
MARKETING EVENT OR ACTIVITY
Figure 9.
sub allocation of
FUND
ALLOCATION
Oracle
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
CG Promotion Planning
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Compensation Planning Administration
Figure 10 shows the Compensation Planning Administration ERD. The administration activities of
compensation planning involve setting up salary structures such as salary plan, salary grades, and
job codes. In addition to salary structures, an organization sets up compensation budgets,
compensation types such as merit increase, bonus, promotion, and stock options, planning periods,
budget calculation and eligibility rules, guidelines and calculation of budget allocations for
employees.
Table 9 lists the entities in this ERD and their corresponding tables.
Table 9.
Compensation Planning Administration ERD Entities and Tables
Entity
Tables
Business Unit
S_BU
Compensation Budget Definition
S_CP_BDGT
Compensation Budget Item
S_CP_BDGT_ITEM
Compensation Budget Item For Employee
S_CP_BDGT_EMP
Compensation Cycle Planning Period
S_CP_PD_BDGTITM
Compensation Guideline Definition
S_CP_GDLN
Compensation Guideline Factor
LOV
Compensation Guideline Set
S_CP_GDLN_SET
Compensation Guideline Table
S_CP_GDLN_TBL
Compensation Planning Period
S_CP_PERIOD
Compensation Region
S_CP_REGN
Compensation Type
LOV
Compensation Valid Effectivity Date
S_CP_EFF_DATE
Employee Eligibility
S_APP_QUERY (PDQ)
Employee/Agent
S_EMP_PER
Job Category
LOV
Job Code
S_JOB
Job Family
S_JOB_FAMILY
Job Profile
S_JOB_PRFL
Period
S_PERIOD
Salary Grade
S_SALARY_GRADE, S_SALPLAN_GRADE
Salary Plan
S_SALARY_PLAN
Siebel Data Model Reference Version 8.0
31
32
used by
Siebel Data Model Reference Version 8.0
BUSINESS UNIT
have
budget for
COMPENSATION BUDGET DEFINITION
container for
used by
EMPLOYEE ELIGIBILITY
(PDQ)
type for
defined for
constrained by
COMPENSATION TYPE
type for
defined for
subject of type of
valid date for
container for
used in
defined for
QUARTERLY PERIOD
ANNUAL PERIOD
PERIOD
used in
defined for
used in
2 factor
defined
in
have
defined in
SALARY GRADE
composed of
sub-org of
for
JOB
FAMILY
support
POSITION
defined for
employer of
for
JOB
CATEGORY
category for
employed by
salary
grade
defined
in
part of
grouping for
categorized
in
manage by
salary plan for
have
has
job code for
JOB CODE
salary plan
grade defined
in
SALARY PLAN FOR
SALARY GRADE
salary grades for
component of
period for
have
for
SALARY PLAN
component of
1 factor
defined
in
defined defined
for
for
COMPENSATION
REGION
COMPENSATION
GUIDELINE
FACTOR
used in
subject of
COMPENSATION PLANNING PERIOD
container for
have
compensation location for
values for
salary
defined
in
located in
EMPLOYEE / AGENT
COMPENSATION GUIDELINE
DEFINITION
has
COMPENSATION GUIDELINE TABLE
defined for
COMPENSATION
GUIDELINE SET
user of
subject of
type of
defined for
defined for constrained by
COMPENSATION BUDGET ITEM
has
have
COMPENSATION
CHANGE EFFECTIVITY
DATE
allocated for
COMPENSATION CYCLE PLANNING PERIOD
budget allocation for
COMPENSATION BUDGET
ITEM FOR EMPLOYEE
Title : Compensation Planning Administration
Author : Oracle, Confidential
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 10. Compensation Planning Administration
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Compensation Planning Execution
Figure 11 shows the Compensation Planning Execution ERD. In the execution phase of compensation
planning, a workbook is created for each of the authorized managers with the list of employees who
report to them. The manager goes through the planning process and decides on the merit, bonus,
promotion, and stock option changes that he may grant to his employees. Authorized persons such
as managers, or HR personnel approve the plans. Totals are maintained for each manager and
organization.
Table 10 lists the entities in this ERD and their corresponding tables.
Table 10.
Compensation Planning Execution ERD Entities and Tables
Entity
Tables
Business Unit
S_BU
Compensation Budget Definition
S_CP_BDGT
Compensation Budget Item
S_CP_BDGT_ITEM
Compensation Budget Item For Employee
S_CP_BDGT_EMP
Compensation Cycle Planning Period
S_CP_PD_BDGTITM
Compensation Guideline Definition
S_CP_GDLN
Compensation Guideline Set
S_CP_GDLN_SET
Compensation Guideline Table
S_CP_GDLN_TBL
Compensation Plan
S_CP_PLAN
Compensation Plan Comments
S_NOTE_CP_PLAN
Compensation Plan For Employee
S_CP_PLAN_EMP
Compensation Plan Item Detail
S_CP_PLNITM_DTL
Compensation Plan Item For Employee
S_CP_PLAN_ITEM
Compensation Plan Total
S_CP_PLNITM_TOT
Compensation Planning Period
S_CP_PERIOD
Compensation Type
LOV
Compensation Valid Effectivity Date
S_CP_EFF_DATE
Plan Approval
S_CP_APPROVAL
Proxy Access To Plan
S_USER_PROXY
Siebel Data Model Reference Version 8.0
33
34
Siebel Data Model Reference Version 8.0
" $% $
& !' $.'
2
2
" $% $
& !' $
!* $ $
1
14
3
" $% $
'$ '
13
2
2
14
14
" $% $
.&!
!* $ $
13
14
1
6
2
.&% $%%
&$
313
" ' +0
$
3
!
" $% $
.&!
"*
" ' +
21
613
513
2
1
6
313
213
113
" $% $
'$
" $% $ '$* " ' +
" $% $ '$$ $
!
" $% $
.&!
"
3
3
" $% $+
" $% $
& !' $%
2
" $% $
'$ ""$%
3
14
" $% $
+ ' '$$ $
!
3
" $% $ '$ "* " ' +
Oracle
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 11. Compensation Planning Execution
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Competency Management System
Figure 12 shows the Competency Management System ERD. An organization can define a set of
competencies that employees can have or acquire over a period of time and an evaluation of
employees' skill levels in those competencies, In addition, information about an employee's past
work experience, merits, honors, professional memberships and education qualifications can be
maintained. An organization can also define a list of courses and related skills which can be
associated with an employee when they complete those courses.
Table 11 lists the entities in this ERD and their corresponding tables.
Table 11.
Competency Management System ERD Entities and Tables
Entity
Tables
Career Path
S_JOB_PRFL_TRNS
Competency, Competency Category, Root Competency
Category
S_CMPTNCY
Educational Qualification
S_PER_EDU_QUAL
Employee Competency
S_EMP_CMPTNCY
Employee Competency Change
S_EMP_CMPT_CHG
Employee/Agent
S_EMP_PER
Honors And Awards
S_PER_AWARD
Job Code
S_JOB
Job Profile
S_JOB_PROFILE, S_JOBPRFL_CMPT
Past Work Experience
S_PER_WRK_EXP
Person
S_USER, S_CONTACT
Professional Membership
S_PER_PROF_MBR
Professional Qualification
S_PER_PROF_CERT
Review Rating
S_PERF_RATING
Review Rating Scale
S_PERF_RTNG_SCL
Team Competency
S_TEAM_CMPTNCY
Training Course
S_PROD_INT_CRSE
Siebel Data Model Reference Version 8.0
35
36
Siebel Data Model Reference Version 8.0
= . * '
?
13
2
9
2
313
13
= . !
26
14
14
13
3
6 5 6
3
2613
> ; $
% '
> ; $
" ' + " $ +
9$
513
" " $ +
%; <8 $
*%% $'"". %9
" ' + & $ " $ +
@
" $ +
+
3
9 $ %$!; !%
!& $'7&' * $
*%% $' * $
7&' * $ 8 $
" $ +
+
?
$ $
& %
?
" $ +
3"%3
Oracle
" ' +
0
$
% $
9
% $
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 12. Competency Management System
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Content Management
Figure 13 shows the Content Management ERD. This ERD illustrates how the Siebel Data Model
supports the process of creating and maintaining content through projects. A content project is made
up of one or more content project items that represent an item of master data, such as a product
definition or an item of literature. Each content project item is an instance of a content item type
that is part of a content object. A content object is based on a business object and is published to
the production system through an EAI integration object. A workflow process governs the flow of the
items in a content project from conception through publication. Each item may be the responsibility
of, reviewed by, or approved by one or more Positions.
Table 12 lists the entities in this ERD and their corresponding tables.
Table 12.
Content Management ERD Entities and Tables
Entity
Tables
Content Item Type
S_CONTENT_TYPE
Content Object
S_CONTENT_OBJ
Content Project
S_CONTENT_PROJ
Content Project Item
S_CONTENT_ITEM
Literature
S_LIT
Person
S_CONTACT, S_PARTY
Position
S_POSTN, S_PARTY
Product
S_PROD_INT
Siebel Data Model Reference Version 8.0
37
38
CONTENT
PROJECT
ITEM
Siebel Data Model Reference Version 8.0
picked via
picked via
owned by
used by
owner of
responsible
for
responsibility
of
managed by
for managing
changes to
an example of
Title : Content Management
Author : Oracle, Confidential
OTHER MASTER
DATA ITEM
holder of
followed by
controlled by
producer of
produced by
held by
generally
controlled
by
used by
WORKFLOW PROCESS
generally followed
by
PERSON
generally the responsibility of
generally responsible for
PICK APPLET
CONTENT
PROJECT
POSITION
PRODUCT
LITERATURE
MASTER DATA ITEM
type for
VIEW
used by
based on
used by
picked via
used by
used by
published via
EAI
INTEGRATION
OBJECT
used by
BUSINESS
OBJECT
basis for
picked via
CONTENT OBJECT
viewed via
used by
made
up of
part of
used by
viewed via
picked via
picked via
CONTENT ITEM
TYPE
PICK LIST
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 13. Content Management
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Contract Conditions
Figure 14 shows the Contract Conditions ERD. This ERD illustrates the usage of templates to create
agreements. An agreement could comprise one or more entitlements. A contracts administrator may
define template entitlements, template benefits and template conditions in addition to template
terms. Template benefits and conditions could be for a specific product or product line or product
class or category. An entitlement could be created using the entitlement template and this would
create the corresponding benefits and conditions based on the corresponding template benefits and
conditions. The terms governing the agreement could be based on template terms.
Table 13 lists the entities in this ERD and their corresponding tables.
Table 13.
Contract Conditions ERD Entities and Tables
Entity
Tables
Agreement
S_DOC_AGREE
Benefit
S_AGREE_BNFT
Category
S_CTLG_CAT
Condition
S_AGREE_COND
Condition Compliance
S_AGR_COND_CMPL
Contract
S_DOC_AGREE
Entitlement
S_ENTLMNT
Entitlement Template
S_ENTL_TMPL
Object Class
S_VOD, S_VOD_VER
Product
S_PROD_INT
Product Line
S_PROD_LN
Template Benefit
S_ENTL_BNFTTMPL
Template Condition
S_ENTL_CONDTMPL
Template Term
S_AGR_TERM_TMPL
Term
S_AGR_TERM_DESC
Siebel Data Model Reference Version 8.0
39
40
Siebel Data Model Reference Version 8.0
AGREEMENT
used by
correspond to
comprise
applicable to
ENTITLEMENT
# NAME
governed by
in reference to
comprise
used by
OTHER
CONTRACT
TEMPLATE TERM
# TERM_NUM
dependent upon
used by
in reference to
belong to
basis for
subject of
subject of
subject of
subject of
subject of
in reference to
comprise
in reference to
ENTITLEMENT TEMPLATE
# NAME
composed of
TEMPLATE BENEFIT
# SEQ_NUM
in context of
TEMPLATE CONDITION
# SEQ_NUM
used in
composed of
in reference to
based on
applicable to
based on
BENEFIT
# SEQ_NUM
governed by
applicable to
applicable to
CONDITION
# SEQ_NUM
subject of
in reference to
applicable to
based on
in reference to
CONDITION COMPLIANCE
# COMPL_NUM
subject of
CONTRACT
subject of
applicable to
TERM
Title : Contract Lifecycle Management
Author : Oracle, Confidential
CATEGORY
OBJECT CLASS
PRODUCT LINE
PRODUCT
CONTRACT CONDITION
OBJECT
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 14. Contract Conditions
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Contracts
Figure 15 shows the Contracts ERD. This ERD illustrates the significant entities related to general
business contracts (quotes, orders, agreements, and others). A contract is an agreement between
two parties, usually to deliver goods or services in exchange for payment. For example, a quote is
an agreement between a company and a customer to guarantee a price for a particular set of items
if acted on within a specified timeframe. The customer is usually an account, but may be a person.
The party on the other side of the contract is an internal or partner organization (or business unit).
A contract is composed of contract line items that specify the internal products, services, or assets
to be covered under the terms of the contract.
Table 14 lists the entities in this ERD and their corresponding tables.
Table 14.
Contracts ERD Entities and Tables
Entity
Tables
Account
S_ORG_EXT, S_PARTY
Asset
S_ASSET
Business Unit
S_BU, S_ORG_EXT, S_PARTY
Contract
S_DOC_AGREE, S_DOC_QUOTE, S_ORDER
Contract Line Item
S_AGREE_ITEM, S_QUOTE_ITEM, S_ORDER_ITEM
Internal Product or Service
S_PROD_INT
Payment Term
S_PAYMENT_TERM
Person
S_CONTACT, S_PARTY
Position
S_POSTN, S_PARTY
Price List
S_PRI_LST
Siebel Data Model Reference Version 8.0
41
42
Siebel Data Model Reference Version 8.0
BUSINESS UNIT
responsible for
ORDER
PERSON
primary contact for
responsibility of
POSITION
responsible for
responsibility of
OTHER CONTRACT
AGREEMENT
CONTRACT
composed of
part of
for
priced by
priced by
for
for
involved by
composed of
QUOTE
ORDER LINE ITEM
QUOTE LINE ITEM
part of
OTHER CONTRACT LINE ITEM
AGREEMENT LINE
ITEM
CONTRACT LINE ITEM
Title : Contracts
Author : Oracle, Confidential
subject of
default pricing for
pricing for
subject of
employed at
ACCOUNT
subject to
employer of
applicable to
for
subject to
PAYMENT
TERM
for
subject to
priced by
INTERNAL
PRODUCT OR
SERVICE
pricing
method for
subject of
made into
an instance of
composed of
PRICE LIST
ASSET
part of
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 15. Contracts
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Data Visibility
The main business entities represented (shown in Figure 16) in the Siebel Data Model fall into one of
two super-types: Master Data Item or Customer Data Item. A Master Data Item represents data set
up and administered by the company using Siebel Business Applications such as products, literature,
and price Lists. Master Data Items are often categorized to make information more accessible. A user
gains visibility to this data either through the person's association with a business unit (multiple
organization visibility) or through the person's access to items in a catalog (access control). Access
to items in a catalog is provided by making the category public, or by granting access to the category
to one or more access groups. Each access group may be made up of smaller access groups and may
be made up of one or more groups of users. Categories granted to a parent access group are
automatically granted to all of its child access groups, but categories granted to a child are not
granted to its parents.
A Customer Data Item represents transactional data collected during the normal course of doing
business such as opportunities, quotes, orders, agreements, service requests, and activities. A user
gains visibility to this data either through the person's association with a business unit (multiple
organization visibility) or more commonly through a direct assignment of the person or the person's
position to the item. A Customer Data Item is usually accessible to one business unit, but is
occasionally accessible to two or more business units. Each business unit may be made up of smaller
business units. A given type of customer data item is usually assigned to employees through position
or directly to the employee, but rarely both. Managers can be granted access to customer data items
assigned to their subordinates.
Table 15 lists the entities in this ERD and their corresponding tables.
Table 15.
Data Visibility ERD Entities and Tables
Entity
Tables
Access Group
S_PARTY
Account
S_ORG_EXT
Activity
S_EVT_ACT
Agreement
S_DOC_AGREE
Business Unit
S_BU, S_ORG_EXT, S_PARTY
Catalog
S_CTLG
Category
S_CTLG_CAT
Dynamic Account Hierarchy
S_DYN_HRCHY
Dynamic Account Hierarchy Node
S_DYN_HRCHY_REL
Employee/Agent
S_EMP_PER, S_CONTACT, S_PARTY
Group
S_PARTY
Internal/Partner Organization Unit
S_ORG_EXT
Literature Item
S_LIT
Opportunity
S_OPTY
Siebel Data Model Reference Version 8.0
43
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Table 15.
Data Visibility ERD Entities and Tables
Entity
Tables
Order
S_ORDER
Organization Unit
S_ORG_EXT, S_PARTY
Party
S_PARTY
Position
S_POSTN, S_PARTY
Price List
S_PRI_LST
Product
S_PROD_INT
Quote
S_DOC_QUOTE
Service Request
S_SRV_REQ
44
Siebel Data Model Reference Version 8.0
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 16. Data Visibility
!>13
Oracle
"% ! "
&% " ! "
@
' %
&$ +
7&
% >
7&%
> +
!
"$
+
' & "
1
9 "%
! "
'
613
13
13
!&
9 &% "
! "
+
% $
" ' +0
$
%%
&
9 % $
1
9 +
1
&
$ [ $&$
% $
9
$ [ $&$
$ $'0 $
$ [ $&$
6
6
6
9
$ $'0 $
$ [ $&$
.&% $%%&$
9
&
@
@6
Siebel Data Model Reference Version 8.0
45
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Dun & Bradstreet Integration
This ERD (shown in Figure 17) illustrates how Siebel Business Applications integrate with Dun &
Bradstreet Organization information. A D & B organization may be classified as doing business in one
or more industries, may provide information about contacts at the organization and their
management responsibilities. In addition, a D & B organization may indicate its direct parent
organization, its ultimate domestic parent, and its ultimate global parent. A Siebel organization unit
(for example, an account) can be related to its equivalent D & B organization and its associated
parent organizations. Contact information from one or more D & B organizations can be used to
create one or more call lists.
Table 16 lists the entities in this ERD and their corresponding tables.
Table 16.
Dun & Bradstreet Integration ERD Entities and Tables
Entity
Tables
Call List
S_CALL_LST
Call List D & B Organization
S_DNB_ORG_LST
D & B Contact Responsibility
S_DNB_CON_MRC
D & B Management Responsibility Type
S_DNB_MRC
D & B Organization
S_DNB_ORG
D & B Organization Industry Classification
S_DNB_ORG_SIC
D & B Standard Industry Classification
S_DNB_SIC
Industry
S_INDUST
Organization Industry Classification
S_ORG_INDUST
Organization Unit
S_ORG_EXT, S_PARTY
Prospect
S_PRSP_CONTACT
46
Siebel Data Model Reference Version 8.0
CALL LIST
created from
for
CALL LIST D&B
ORGANIZATION
ORGANIZATION UNIT
classified within
classifier of
composed of
of
global parent of
domestic parent of
parent of
equivalent to
INDUSTRY
ORGANIZATION INDUSTRY CLASSIFICATION
Title : Dun & Bradstreet Integration
Author : Oracle, Confidential
member in
source of
global child of
domestic child of
child of
equivalent to
direct
child of
classification for
specifier of
OTHER
PROSPECT
PROSPECT
affiliated with
domestic
child of
domestic
parent of
global
parent of
primarily a
banking
customer of
D&B CONTACT
composed of
classified
within
D&B ORGANIZATION
direct
parent of
classifier of
bearer of
D&B STANDARD INDUSTRY
CLASSIFICATION
classification for
specifier of
for
D&B MANAGEMENT
RESPONSIBILITY TYPE
assigned to
of
D&B CONTACT RESPONSIBILITY
global child
of
a bank for
D&B ORGANIZATION INDUSTRY CLASSIFICATION
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 17. Dun & Bradstreet Integration
Siebel Data Model Reference Version 8.0
47
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Employee KPI
This ERD (shown in Figure 18) illustrates that Key Performance Indicators (KPI) can be defined and
associated with the objectives of an employee so that the employee and the manager of the
employee manager can measure achievement or current values against the goals set in the
objectives of the employee.
Table 17 lists the entities in this ERD and their corresponding tables.
Table 17.
Employee KPI ERD Entities and Tables
Entity
Tables
BUSINESS UNIT
S_BU
EMPLOYEE PERFORMANCE
MEASUREMENT
S_EMP_PERF_MEAS
GROUP, ACCESS GROUP
S_PARTY
KEY PERFORMANCE INDICATOR
DEFINITION
S_KPI, S_KPI_AGRP
KPI VALUE FOR EMPLOYEE
S_EMP_KPI
KPI VALUE FOR OBJECTIVE
S_PERF_MITM_KPI
KPI VALUE HISTORY
S_EMPKPI_SNPSHT
ORGANIZATION UNIT, DIVISION
S_ORG_EXT
PERFORMANCE MEASUREMENT ITEM
S_PERF_MEAS_ITM
PERSON, EMPLOYEE/AGENT, OTHER
PERSON
S_CONTACT, S_EMP_PER, S_USER
48
Siebel Data Model Reference Version 8.0
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 18. Employee KPI
Title : Employee KPI
Author : Oracle, Confidential
KPI VALUE
FOR
OBJECTIVE
PERFORMANCE
MEASUREMENT
ITEM
contain value for
measured in
contain value for
objective for
KPI VALUE FOR EMPLOYEE
user of
defined for
KPI VALUE HISTORY
used to
generate value
for
source for
history for
subject of
history for
has
EMPLOYEE
PERFORMANCE
MEASUREMENT
KEY PERFORMANCE INDICATOR DEFINITION
measurement
of
approved by
accessed by
approver of
parent visibility node of
PARTY
child visibility node of
ORGANIZATION UNIT
PERSON
GROUP
have access to
has
have
subject of
EMPLOYEE / AGENT
DIVISION
OTHER
PARTY
ACCESS GROUP
OTHER PERSON
Siebel Data Model Reference Version 8.0
49
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Expense Reports
This ERD (shown in Figure 19) illustrates how Siebel Business Applications track employee expense
reports. Employees (for example, sales representatives, field service engineers, and professional
services personnel) can track expense items incurred for business purposes. These expenses can be
associated with an account, an opportunity, or a project, and may be related to an activity. Other
employees or contacts involved in the expense can be associated with the expense. The expenses in
a specified reporting period can then be reported on an expense report for reimbursement.
Table 18 lists the entities in this ERD and their corresponding tables.
Table 18.
Expense Reports ERD Entities and Tables
Entity
Tables
Activity
S_EVT_ACT
Employee
S_EMP_PER, S_CONTACT, S_PARTY
Expense Item
S_EXP_ITEM
Expense Item Type
S_EXP_ITM_TYPE
Expense Report
S_EXP_RPT
Expense Report Approval
S_EXP_RPT_APPR
Opportunity
S_OPTY
Organization Unit
S_ORG_EXT, S_PARTY
Party
S_PARTY
Person
S_CONTACT, S_PARTY
Project
S_PROJ
50
Siebel Data Model Reference Version 8.0
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 19. Expense Reports
Title : Expense Reports
Author : Oracle, Confidential
EXPENSE ITEM
incurred for
PROJECT
subject of
incurred for
OPPORTUNITY
for
ACTIVITY
subject of
source of
incurred during
for
source of
subject of
EXPENSE ITEM TYPE
of
classification for
made up of
PARTY
part of
incurred for
ORGANIZATION UNIT
subject of
involver of
involved in
PERSON
OTHER
ORGANIZATION UNIT
incurred by
incurrer of
EMPLOYEE /
AGENT
OTHER
PERSON
EXPENSE REPORT
APPROVAL
by
reported on
provider of
of
composed
of
subject of
INTERNAL
ORGANIZATION /
PARTNER
reported for
EXPENSE REPORT
the reporting period for
PERIOD
reported by
accounting approval by
reporter of
approver of
charged to
charged with
Siebel Data Model Reference Version 8.0
51
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Field Service Inventory
This ERD (shown in Figure 20) illustrates how Siebel Business Applications track field service parts
inventory. Parts may be tracked in inventory as serialized assets or as nonserialized quantities of
products. An instance of product inventory defines a quantity of product in a given location with a
given status and availability. Inventory quantities cannot be modified directly. Instead, they are
modified through inventory transactions that reflect each movement of parts between locations,
statuses, and availabilities. Inventory locations may be located at a third-party provider, as well as
within the internal organization. They may also be related to other inventory locations for the
purposes of replenishment or fulfillment.
Table 19 lists the entities in this ERD and their corresponding tables.
Table 19.
Field Service Inventory ERD Entities and Tables
Entity
Tables
Address
S_ADDR_ORG
Asset
S_ASSET
Business Unit
S_BU, S_ORG_EXT, S_PARTY
Inventory Location
S_INVLOC
Inventory Transaction
S_INV_TXN
Organization Unit
S_ORG_EXT, S_PARTY
Party
S_PARTY
Person
S_CONTACT, S_PARTY
Position
S_POSTN, S_PARTY
Product Inventory
S_PROD_INV
Product Inventory Category
S_PROD_INV_CAT
Product Inventory Location
S_PROD_INVLOC
Product or Service
S_PROD_INT
52
Siebel Data Model Reference Version 8.0
currently in
inventory at
stored in
NON-SERIALIZABLE
PRODUCT
PRODUCT INTERNAL
PRODUCT OR SERVICE
is made into
a component of
an assembly of
PRODUCT
INVENTORY
CATEGORY
for
are counted via
located at
type of
INVENTORY
LOCATION TYPE
SERIALIZABLE
PRODUCT
of
at
composed of
for
INTERNAL/PARTNER
ORGANIZATION
ORGANIZATION UNIT
composed
of
OTHER
ORGANIZATION
located at
supplier
of
for
from
visible
to
part of
composed of
sub-org
of
BUSINESS
UNIT
accessor of
responsibility
of
OTHER INVENTORY
LOCATION
VIRTUAL INVENTORY
LOCATION
made up
responsible
for
located
at
replenished
ADDRESS
for
accessed by
responsibility of
PERSONAL (TRUNK)
INVENTORY LOCATION
WAREHOUSE
INVENTORY LOCATION
replenishment
source for
INVENTORY
TRANSACTION TYPE
responsible responsible
for
for
POSITION
held by
for
replenished from
of
holder of
type of
affiliated
with
PERSON
for
stores
defines movement
from
NON-SERIALIZED
TRANSACTION
is affected by
counts product for
PRODUCT INVENTORY
LOCATION
type of
for
SERIALIZED
TRANSACTION
INVENTORY TRANSACTION
defines
is affected movement to
by
participates in
PRODUCT INVENTORY
status of
is a
ASSET (PRODUCT
INSTANCE)
Title : Field Service Inventory
Author : Oracle, Confidential
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 20. Field Service Inventory
Siebel Data Model Reference Version 8.0
53
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Field Service Scheduler
This ERD (shown in Figure 21) illustrates how the Siebel Data Model supports the scheduling of
employees to perform service activities within configured service regions. A service region
corresponds to one or more ZIP codes or other geographical representation, but may only be
associated with a single time zone. The service region defines a number of parameters, time duration
maps, cost functions, and rule sets that constrain the scheduling of resources within the region. A
given service request or activity is assigned to a service region and then to an employee, based on
the employee's working hours and current schedule.
Table 20 lists the entities in this ERD and their corresponding tables.
Table 20.
Field Service Scheduler ERD Entities and Tables
Entity
Tables
Address
S_ADDR_ORG
Employee
S_EMP_PER, S_CONTACT, S_PARTY
Employee Exceptional Work Hours
S_EMP_EXCPT_HRS
Scheduler Cost Function
S_SCH_CSTFN
Scheduler Cost Function Variable
S_SCH_CSTFN_VAR
Scheduler Parameter
S_SCH_PARAM
Scheduler Parameter Set
S_SCH_PARAM_SET
Scheduler Rule
S_SCH_RULE
Scheduler Rule Node
S_SCH_RULENODE
Scheduler Rule Set
S_SCH_RLST
Scheduler Time Map
S_SCH_TMMAP
Scheduler Time Map Duration
S_SCH_TMMAP_DUR
Service Activity
S_EVT_ACT
Service Region
S_SRV_REGN
Service Request
S_SRV_REQ
Timezone
S_TIMEZONE
Work Shift
S_SCHED_CAL
Work Shift Exception
S_EXCPT_CAL
Work Shift Exception Hour
S_EXCPT_CAL_HRS
Work Shift Hour
S_SCHED_CAL_HRS
Zipcode
S_ZIPCODE
54
Siebel Data Model Reference Version 8.0
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 21. Field Service Scheduler
Title : Field Service Scheduler
Author : Oracle, Confidential
above
under
within
for
made up of
subject of
SERVICE
ACTIVITY
SERVICE
REQUEST
for
SCHEDULER
RULE SET
SCHEDULER RULE
SCHEDULER RULE NODE
user of
SERVICE REGION
in
used by
for
subject of
SCHEDULER COST
FUNCTION
VARIABLE
assigned to
owner of
assigned to
defined for
EMPLOYEE
assigned with
subject of
user of
used by
EMPLOYEE
EXCEPTIONAL
WORK HOURS
for
SCHEDULER COST
FUNCTION
at
with
for
starting
SCHEDULER TIME
MAP DURATION
in
for
for
WORK SHIFT
EXCEPTION HOUR
ending at
defined for
subject of
ADDRESS
user of
used by
defined for
in
in
for
in
SCHEDULER
TIME MAP
user of
for
defined for
WORK SHIFT HOUR
defined by
defined by
SCHEDULER
PARAMETER
WORK SHIFT
with
with
in
within
for
WORK SHIFT EXCEPTION
for
for
TIMEZONE
for
for
ZIPCODE
used by
made up of
SCHEDULER PARAMETER SET
Siebel Data Model Reference Version 8.0
55
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Forecasts
This ERD (shown in Figure 22) illustrates the process of generating forecasts. A forecast series
defines a set of forecast periods in which forecasts must be submitted, and describes the appropriate
number of periods to forecast into the future for each forecast period. One or more positions are then
assigned to submit forecasts under the defined forecast series. When a forecast series is accessible
to the public, it means the forecast series can be shared across organizations. Each participant
submits a forecast each period that is made up of forecast items. Each forecast item may be
attributed to different kinds of business transactions, and may be defined at any of a number of levels
based on business rules. These forecast items may be generated based on known revenue items.
Forecasts that managers make can contain items from the forecasts of their subordinates.
Table 21 lists the entities in this ERD and their corresponding tables.
Table 21.
Forecasts ERD Entities and Tables
Entity
Tables
Agreement
S_DOC_AGREE
Forecast
S_FCST
Forecast Item Detail
S_FCST_ITEM_DTL
Forecast Period
S_FCSTSER_DATE
Forecast Series
S_FCSTSER
Forecasted Item
S_FCST_ITEM
Marketing Event
S_SRC
Opportunity
S_OPTY
Organization Unit
S_ORG_EXT, S_PARTY
Person
S_CONTACT, S_PARTY
Position
S_POSTN, S_PARTY
Product Line
S_PROD_LN
Product or Service
S_PROD_INT
Project
S_PROJ
Quote
S_DOC_QUOTE
Revenue Item
S_REVN
Service Request
S_SRV_REQ
56
Siebel Data Model Reference Version 8.0
OPPORTUNITY
attributed to
for
for
for
PROJECT
attributed to
AGREEMENT
attributed to
for
REVENUE ITEM
summary of
SERVICE REQUEST
attributed to
MARKETING
EVENT OR
ACTIVITY
attributed to
for
FORECASTED ITEM
member of
Title : Forecasts
Author : Oracle, Confidential
QUOTE
FORECAST SERIES
aggregated by
applicable to
a report to
governed by
INTERNAL
ORGANIZATION
UNIT
OTHER
ORGANIZATION
UNIT
defined for
AGGREGATE
DIMENSION
attributed to
for
manager of
POSITION
for
owner of
submitted by
submitter of
subject of
original forecast of
subject of
valid period for
FORECAST PERIOD
period for
participant of
owned by
submitted for
manager's forecast of
FORECAST
subordinator's forecast of
ORGANIZATION UNIT
partner attributed to
OTHER PERSON
EMPLOYEE /
AGENT
PERSON
account attributed to
for
for
author of
defined by
for
member of
PRODUCT OR
SERVICE
PRODUCT LINE
for
for
FORECAST ITEM DETAIL
subject of
attributed to
attributed to
for
forecasted via
generated for
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 22. Forecasts
Siebel Data Model Reference Version 8.0
57
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
High Tech Marketing Development Fund
This ERD (shown in Figure 23) illustrates how Siebel Business Applications support the funding of
trade promotions in the high technology industry. Marketing Development Fund (MDF) is a pool of
money made available to partners for the organization of marketing activities (campaigns, events,
and so on). An MDF may be a partner-specific fund or general fund. MDFs (Programs) provide the
brand owner with the ability to make marketing funds available to partners in a programmatic way.
Partner Specific funds are child funds of Programs. Within each Partner Specific fund, the partner
accrues funds under the given program. The partner creates a partner event activity (pre-approval)
with several associated event items. Event Items add granularity to the partner event activity.
Partners create claims to redeem the money in their partner-specific funds for marketing activities
that were pre-approved by the brand owner.
Table 22 lists the entities in this ERD and their corresponding tables.
Table 22.
High Tech Marketing Development Fund ERD Entities and Tables
Entity
Tables
Account, Partner, Other Account
S_ORG_EXT
Claim Item
S_SRC_PAYITM
Claim, Payment, Other Payment
S_SRC_PAYMENT
Event Item
S_SRC_COST
Fund Allocation
S_MDF_ALLOC
General Fund
S_MDF
Internal Product or Service
S_PROD_INT
Market Segment
S_MKT_SEG
Marketing Development Fund
S_MDF
Marketing Event or Activity
S_SRC
MDF Snapshot
S_MDF_PERIOD
MDF Transaction
S_MDF_TXN
Partner Event Activity
S_SRC
Partner Program
S_PRTNR_PROG
Partner Program Application
S_PRTNRPRG_APPL
Partner Specific Fund
S_MDF
Position
S_POSTN
58
Siebel Data Model Reference Version 8.0
for
has
MDF
SNAPSHOT
for
PARTNER
PROGRAM
belongs to
for
for
MARKET
SEGMENT
belongs to
PARTNER
for
PROGRAM
APPLICATION
belongs to
POSITION
has
to
to
GENERAL
FUND
PARTNER
SPECIFIC
FUND
for promotion of
for promotion of
for
funded through
DEBIT
defined for
subject of
belongs to
subject of
part of
CREDIT
OTHER PAYMENT
.
MDF TRANSACTION
EVENT ITEM
OTHER
ACCOUNT
target of
belongs
for
has
CLAIM
PAYMENT
subject of
target of
PARTNER
ACCOUNT
MARKETING
DEVELOPMENT
FUND
designated to
subject of
of
FUND ALLOCATION
Title : High Tech Marketing Development Fund
Author : Oracle, Confidential
earned by
part of
subject of
earner of
earned by
has
CLAIM ITEM
PRODUCT
LINE
for
subject of
part of
hierarchy child of
hierarchy parent of
INTERNAL PRODUCT OR
SERVICE
of
OTHER MARKETING
EVENT OR ACTIVITY
promoted via
composed of
earner of
basis for
PARTNER EVENT
ACTIVITY
MARKETING EVENT OR
ACTIVITY
has
available to
defined for
recipient of
part of
made of
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 23. High Tech Marketing Development Fund
Siebel Data Model Reference Version 8.0
59
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Invoiceable Charges
This ERD (shown in Figure 24) illustrates how financial transactions, such as charges and credits, are
handled. Any charge or credit that could be invoiced is added to this table. This is based on defined
consolidation plan rules to consolidate charges and credits into invoice and invoice items.
Table 23 lists the entities in this ERD and their corresponding tables.
Table 23.
Invoiceable Charges ERD Entities and Tables
Entity
Tables
Activity
S_EVT_ACT
Address
S_ADDR_ORG
Agreement
S_DOC_AGREE
Agreement Entitlement
S_ENTLMNT
Agreement Line Item
S_AGREE_ITEM
Asset
S_ASSET
Auction Item
S_AUC_ITEM
Expense Item
S_EXP_ITEM
Invoiceable Charge
S_INVOICE_CHRG
Invoice
S_INVOICE
Invoice Item
S_INVOICE_ITEM
Invoice Item Reconciliation Entry
S_INVC_ITM_DTL
Order
S_ORDER
Order Line Item
S_ORDER_ITEM
Part Movement
S_ACTPART_MVMT, S_ORDPART_MVMT
Part Repair
S_PART_RPR
Party
S_PARTY, S_ORG_EXT, S_CONTACT, S_USER, S_BU
Payment
S_SRC_PAYMENT
Payment Term
S_PAYMENT_TERM
Product or Service
S_PROD_INT
Project Item
S_PROJITEM
Project Team Role
S_PROJ_RSRC
Service Request
S_SRV_REQ
Shipment
S_SHIPMENT
Time Sheet Item
S_TMSHT_ITEM
60
Siebel Data Model Reference Version 8.0
for
INVOICE
made up of
part of
Siebel Data Model Reference Version 8.0
for
ADDRESS
billed to
for
made for
fulfilled by
PAYMENT
INVOICE ITEM
subject of
invoiced into
for
INVOICE ITEM for
INVOICABLE
subject of
CHARGE
INVOICE ITEM
DETAIL
INVOICE ITEM
RECONCILIATION ENTRY
Title : Invoicable Charges
Author : Oracle, Confidential
subject of
for
ACCOUNT
contact of
OTHER
ORGANIZATION
UNIT
charged via
PARTY
for
ORGANIZATION UNIT
billed to
located at
for
billed to
INVOICABLE CHARGE
for
for
for
for
for
for
for
PERSON
primary billing contact of
for
AGREEMENT
charged via
ORDER
PRODUCT OR
SERVICE
object for
composed of
SHIPMENT
AUCTION ITEM
part of
composed of
ordered on
part of
of
charged via
of
ORDER
PART
MOVEMENT
PAYMENT TERM
ORDER LINE
ITEM
fulfilled by
for
ACTIVITY
PART
MOVEMENT
made up of
part of
charged via
AGREEMENT
LINE ITEM
based on
made up of
part of
SERVICE
REQUEST
EXPENSE ITEM
charged via
charged via
AGREEMENT
ENTITLEMENT
basis for
charged via
TIME SHEET ITEM
PART REPAIR
charged via
PART MOVEMENT
PROJECT
TEAM ROLE
charged via
based on
for
for
charged via
for
PROJECT
ITEM
charged via
charged via
ASSET
ACTIVITY
basis of
charged via
charged via
charged via
based on
for
for
for
for
composed of
for
charged via
OTHER
PARTY
billed to
part of
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 24. Invoiceable Charges
61
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Invoices
This ERD (shown in Figure 25) illustrates the invoicing and payment processes. An invoice may be
considered a receivable or a payable for the company. It may be generated to bill for an order, a
project, a part repair, an agreement, a service request, an activity, or a period of time for products
or services delivered within a specific period of time. Items on the invoice may be reconciled with
one or more other entities as well. A payment may be made for one or more Invoices, and an invoice
may be paid through one or more payments.
Table 24 lists the entities in this ERD and their corresponding tables.
Table 24.
Invoices ERD Entities and Tables
Entity
Tables
Activity
S_EVT_ACT
Agreement
S_DOC_AGREE
Expense
S_EXP_ITEM
Invoice
S_INVOICE
Invoice Attachment
S_INVOICE_ATT
Invoice Item
S_INVOICE_ITEM
Order
S_ORDER
Order Item
S_ORDER_ITEM
Part Movement
S_ORDPART_MVMT
Part Repair
S_PART_RPR
Payment
S_SRC_PAYMENT
Period
S_PERIOD
Product
S_PROD_INT
Project
S_PROJ
Service Request
S_SRV_REQ
Shipment
S_SHIPMENT
62
Siebel Data Model Reference Version 8.0
composed
of
for
for
for
for
for
for
for
for
for
for
for
billed via
OTHER INVOICE
INVOICE ITEM
part of
INVOICE
Title : Invoices
Author : Oracle, Confidential
billed via
billed via
PRODUCT
billed via
fulfillment for
fulfilled by
part of
billed via
reason for
generated
for
object for
SHIPPED PART
for
billed via
part of
ORDER
composed
of
composed of
PART MOVEMENT
billed via
reason for
PART REPAIR
reason for
generated
for
PERIOD
generated
for
PAYABLE INVOICE
fulfilled by
made for
PAYMENT
SERVICE REQUEST
reason for
generated
for
ACTIVITY
ordered on
of
ORDER ITEM
EXPENSE
billed via
detail for
for
reason for
generated
for
AGREEMENT
UNIT OF
LABOR
billed via
billed via
billed via
PROJECT
reason for
generated for
RECEIVABLE INVOICE
source for
for
INVOICE ATTACHMENT
for
based on
SHIPMENT
reason for
PAYMENT
TERM
generated
for
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 25. Invoices
Siebel Data Model Reference Version 8.0
63
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Marketing Budget Request
This ERD (shown in Figure 26) covers the Marketing Resource Management: budget request process.
It illustrates the relationships between budget requests and marketing tactics, marketing funds, and
purchase orders. A budget request can be managed by a team and defined against a dedicated
marketing fund for a period and a region. It can be associated with one or more industries, products,
and product lines.
Table 25 lists the entities in this ERD and their corresponding tables.
Table 25.
Marketing Budget Request ERD Entities and Tables
Entity
Table(s)
Budget Request
S_MKTG_BDGT_REQ
Purchase Request
S_ORDER
Marketing Development Fund
S_MDF
Marketing Plan
S_SRC
Marketing Fund
S_MDF
Marketing Tactics
S_SRC
Tactics Expense
S_SRC_COST
Purchase Request Line Item
S_ORDER_ITEM
64
Siebel Data Model Reference Version 8.0
14
.&% $%%&$
14
13
14
" < $
%
1
& 9% 7&%
& 9%
7&%' $
"
$>
14
%8 $%
1
2
2
1
!& ' $
14
!
2
" < $
!>' "$*&$!
!&
14
$!&% +
14
% $
" < $
*&$!
14
1 13
13
" < $
'$
14
13
.&!
7&%
" 5. ?
Oracle
$
1
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 26. Marketing Budget Request
Siebel Data Model Reference Version 8.0
65
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Marketing Campaign
This ERD (shown in Figure 27) illustrates campaign management, execution, and evolution.
Campaign management may involve the focus of the campaign on a territory, as well as the
responsibility of the various internal divisions and teams for successful execution. Execution may
include the production and distribution of literature to the appropriate campaign contacts. Campaign
evolution tracks the usage of call lists to identify campaign contacts and generate leads. Campaign
contacts may include prospective contacts purchased on a call list. If a prospective contact is not
promoted to a customer before the call list that names them expires, they are typically deleted from
the database.
Table 26 lists the entities in this ERD and their corresponding tables.
Table 26.
Marketing Campaign ERD Entities and Tables
Entity
Tables
Activity
S_EVT_ACT
Call List
S_CALL_LST
Call List Member
S_CALL_LST_CON
Campaign Call List
S_CAMP_CALL_LST
Campaign Contact
S_CAMP_CON
Fulfillment Recipient
S_FUL_RECIP
Fulfillment Request
S_EVT_FUL_REQ
Fulfillment Request Item
S_FUL_REQ_ITEM
Literature Item
S_LIT
Marketing Event
S_SRC
Opportunity
S_OPTY
Opportunity Contact
S_OPTY_CON
Order
S_ORDER
Organization Unit
S_ORG_EXT, S_PARTY
Person
S_CONTACT, S_PARTY
Position
S_POSTN, S_PARTY
Prospective Contact
S_PRSP_CONTACT
Response
S_COMMUNICATION
Territory
S_ASGN_GRP
66
Siebel Data Model Reference Version 8.0
OTHER PERSON
recipient of
PERSON
POSITION
for
for
subject of
made up
of
ORDER
composed of
for
initiator of
originator of
originator of
originator of
associated with
generated by
made
of
part of
used in
subject
of
PURCHASED
LIST
CAMPAIGN CALL LIST
for
user of
MARKETING
SEGMENT
CALL LIST
in
of
of
of
subject
of
of
subject of
subject
of
of
subject of
CALL LIST
MEMBER
primarily from
source of
made up of
targeted at
PROSPECTIVE CONTACT
a parent
to
a report to
OTHER
MARKETING
EVENT OR
ACTIVITY
responsibility of
MARKETING CAMPAIGN
introduction to
for
CAMPAIGN CONTACT
MARKETING EVENT OR ACTIVITY
responsible for
made up of
part of
managed within
subject of
promoted via
subject of
conducted as
focus of
relevant to
part of
RESPONSE
generated by
ORGANIZATION UNIT
assigned to
TERRITORY
NOTE
LITERATURE
ITEM
FULFILLMENT
REQUEST
initiated by
generated by
assigned to sell in
assigned to
assigned to
role played by
assigned to
CAMPAIGN
TEAM MEMBER
of
for
OPPORTUNITY CONTACT
OPPORTUNITY
targeted at
part of
of
part of
FULFILLMENT
REQUEST ITEM
addressed to
FULFILLMENT
RECIPIENT
ACTIVITY
Title : Marketing Campaign
Author :Oracle, Confidential
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 27. Marketing Campaign
Siebel Data Model Reference Version 8.0
67
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Marketing Collaboration
Collaborative marketing (shown in Figure 28) assists marketers in maintaining the balance between
the need for consistent customer management among partners and effective brand building with
local expertise. It consists of two features. Marketing program collaboration allows companies to
develop marketing programs in a more collaborative environment, resulting in reduced costs. It
encourages collaboration on programs through the sharing of information with key action groups
(internal and external). Partner marketing enhancements provides the ability to associate and track
partner participation in marketing programs and campaigns to measure and report on opportunities,
orders, and ROI. It also closes the loop by providing the ability to track partner sources for
responses/opportunities orders.
Table 27 lists the entities in this ERD and their corresponding tables.
Table 27.
Marketing Collaboration ERD Entities and Tables
Entity
Tables
Internal Partner/Organization
S_ORG_EXT, S_PARTY
Marketing Event or Activity
S_SRC
Opportunity
S_OPTY
Order
S_ORDER
Organization Unit, Other Organization Unit
S_ORG_EXT, S_PARTY
Partner Organization
S_BU, S_PARTY
Party, Other Party
S_PARTY
Quote
S_DOC_QUOTE
Response
S_COMMUNICATION
68
Siebel Data Model Reference Version 8.0
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 28. Marketing Collaboration
Title : Marketing Collaboration
Author : Oracle, Confidential
PARTY
ORGANIZATION UNIT
responsible for
ORDER
responsibility of
collaborating on
PARTNER
ORGANIZATION
INTERNAL /
PARTNER
ORGANIZATION
item of collaboration for
generated from
based on
basis for
responsible for
QUOTE
responsibility of
collaborating on
item of collaboration for
generated from
lead to
responsible for
OPPORTUNITY
responsibility of
collaborating on
item of collaboration for
generated from
item of collaboration for
RESPONSE
responsibility of
collaborating on
responsible for
created for
source of
source of
source of
item of collaboration for
MARKETING EVENT OR ACTIVITY
responsibility of
collaborating on
responsible for
OTHER ORGANIZATION UNIT
OTHER PARTY
Siebel Data Model Reference Version 8.0
69
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Marketing Encyclopedia
This ERD (shown in Figure 29) illustrates how Siebel Business Applications track competitive
information about products and companies. A standard set of metrics may be defined against which
competitive organizations and their products can be rated in comparison with the internal
organization and products, respectively. Detailed product specifications can be recorded. In addition,
competitive literature may be associated both with organizations and with products. The relevance
of key decision issues to the various competitive metrics may be defined.
Table 28 lists the entities in this ERD and their corresponding tables.
Table 28.
Marketing Encyclopedia ERD Entities and Tables
Entity
Tables
Company Literature
S_CO_LIT
Competitive Company Feature
S_CMPT_CO_FEA
Competitive Metric
S_CMPT_MTRC
Competitive Product Feature
S_CMPT_PROD_FEA
Issue
S_ISS
Literature Item
S_LIT
Organization Unit
S_ORG_EXT, S_PARTY
Product Comparison
S_PROD_CMP
Product Detail
S_PROD_SPEC
Product External
S_PROD_EXT
Product Internal
S_PROD_INT
Product Literature
S_PROD_LIT
70
Siebel Data Model Reference Version 8.0
for
characterized by
PRODUCT
DETAIL
INTERNAL PRODUCT
OR SERVICE
of
to
produced by
subject of
COMPETITIVE COMPANY METRIC
INTERNAL / PARTNER
ORGANIZATION UNIT
reference to
usage of
about
subject of subject of
usage of
COMPANY
LITERATURE
for
COMPETITIVE
COMPANY
FEATURE
classification for
EXTERNAL ORGANIZATION UNIT
LITERATURE ITEM
reference to
about
PRODUCT
LITERATURE
ORGANIZATION UNIT
vendor of
EXTERNAL
PRODUCT
competitor of
PRODUCT COMPARISON
competitor of
subject of
COMPETITIVE PRODUCT METRIC
COMPETITIVE METRIC
classification for
of
relevant to
DECISION
ISSUE
PRODUCT OR SERVICE
subject of
of
COMPETITIVE
PRODUCT
FEATURE
Title : Marketing Encyclopedia
Author : Oracle, Confidential
of
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 29. Marketing Encyclopedia
Siebel Data Model Reference Version 8.0
71
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Marketing Events
This ERD (shown in Figure 30) illustrates how Siebel Business Applications support marketing events
and activities planning. A marketing event may be composed of one or more sessions, held at one
or more venues such as a hotel or convention center. The room for each session of an event may be
chosen based on the size and equipment requirements of the session matched to the size and
available equipment of each room. Users can also create travel plans for customers attending the
events. Event vendors and sponsors can be tracked as well as the various offers or services they
provide. The event staff can be planned and attendees invited. Attendees may then register for the
event or even for specific sessions. Attendees may be quoted registration prices through a quote and
purchase tickets to the event through an order.
Table 29 lists the entities in this ERD and their corresponding tables.
Table 29.
Marketing Events ERD Entities and Tables
Entity
Tables
Activity
S_EVT_ACT
Contract Line Item
S_ORDER_ITEM, S_QUOTE_ITEM
Equipment Requirement
S_SRC_REQ_EQUIP
Event
S_SRC_EVT, S_SRC
Event Cost
S_SRC_COST
Event Location
S_EVTLOC
Event Registration
S_SRC_EVT_REG
Event Session
S_SRC_EVT, S_SRC
Event Vendor
S_SRC_ORG
Event Venue
S_SRC_VENUE
Literature Item
S_LIT
Location Room
S_EVTLOC_ROOM
Marketing Event or Activity
S_SRC
Order
S_ORDER
Organization Unit
S_ORG_EXT, S_PARTY
Parent Event
S_SRC_EVT, S_SRC
Position
S_POSTN, S_PARTY
Product or Service
S_PROD_INT
Quote
S_DOC_QUOTE
Room Avail Equipment
S_EVTLOC_RM_EQP
Travel Participant
S_EVT_TRVL_PER
Travel Plan
S_EVT_TRVL_PLAN
72
Siebel Data Model Reference Version 8.0
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Table 29.
Marketing Events ERD Entities and Tables
Entity
Tables
Vendor Offer
S_EVT_VNDR_OFR
Vendor Review
S_EVT_VNDR_RVW
Vendor Service
S_EVT_VNDR_SVC
Venue
S_ORG_EXT, S_PARTY
Venue Offer
S_EVT_VENUE_OFR
Venue Review
S_EVT_VENUE_RVW
Venue Service
S_EVT_VENUE_SVC
Siebel Data Model Reference Version 8.0
73
74
Siebel Data Model Reference Version 8.0
>$&
>$' $
13
$ [ $
&$
3
>$>$&
14
14
14
9 '
>$
% $
2
14
>$ !&
9 !&
% >
% $
9
$
7&
!
$
14
2
26
$ ''!
% $
; ' %
$!
>$
% $
13
14
2
13
26
>'
$ 1
$ ' $ "
14
$
>$
2
2
!& % >
' &
"
2
13
? 13
13
>' '$
6
2 13
7& "$
7& "$
1
>$%%% $
' $ "
?6
21
"7& "$
> '. ' +
9 " < $
>$ > +
> +
2
2613
>$ %
2613 13
" < $
>$ > +
14
>$&
> ;
13
>$&
% >
>$!
> ;
14
13
>$!
% >
2
13
>$!
**
2
2
>$&
**
1
>$>$!
" 52
Oracle
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 30. Marketing Events
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Marketing Plans
This ERD (shown in Figure 31) illustrates how marketing plans are used in conjunction with the
financial modeler for the purposes of financial planning. Marketing plans are multilevel groupings of
plan elements (campaigns) or sub-plans. Financial goals and costs can be forecasted for each level
of the plan, tracked against actual achievement after campaign execution, and rolled up to the toplevel plan. Funds can also be allocated for different plans in different periods and used as inputs for
accounting purposes or in financial calculations.
Table 30 lists the entities in this ERD and their corresponding tables.
Table 30.
Marketing Plans ERD Entities and Tables
Entity
Tables
Call List
S_CALL_LST
Marketing Development Fund
S_MDF
Marketing Event Cost
S_SRC_COST
Marketing Event or Activity, Marketing Plan, Other Marketing Plan
or Activity
S_SRC
Marketing Goal
S_SRC_GOAL
Period
S_PERIOD
Planned Marketing Development Fund Allocation
S_MDF_ALLOC
Product or Service, Product Line, Other Product or Service
S_PROD_INT, S_PROD_LN
Product Promotion
S_PROD_INT_SRC
Siebel Data Model Reference Version 8.0
75
76
Siebel Data Model Reference Version 8.0
used for
for
defined for
valid in
reserved from
MARKETING
DEVELOPMENT
FUND
source of
defined for
GOAL
uses
BUDGET
REQUEST
defined for
PERIOD
part of
INVOICE
made up of
INVOICE ITEM
estimated for
valid in
PLANNED
attributed to
MARKETING
DEVELOPMENT
MARKETING
FUND ALLOC
Title : Marketing Plans
Author : Oracle, Confidential
source of
created from
CALL LIST
FOR
belong to
type of
SUBJECT OF
valid in
user of
requirer of
created for
owner for
compose of
defined for the budget of
CAMPAIGN
CALL LIST
launched in
PRODUCT OR SERVICE
created for
incur
consists of
source of
created from
attributed to
PRODUCT
PROMOTION
promotion item for
basis of
defined for launch of
has
based on
MARKETING
EVENT COST
has
OTHER
MARKETING
EVENT OR
ACTIVITY
MARKETING
PLAN
MARKETING EVENT
OR ACTIVITY
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 31. Marketing Plans
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Marketing Program
This ERD (shown in Figure 32) illustrates how Siebel Business Applications support the more complex
program planning and execution used for Database Marketing. Marketing segments are dynamic lists
of people defined by a set of database criteria and available to marketing programs. These criteria
may be defined on measures and attributes based on complex mathematical scores, ratios, and
formulas applied to customer demographics or behavior data sourced from the Siebel database or
from external applications such as a data warehouse.
After a data dictionary describing the external data store has been defined, segment definitions can
be created and attached to one or more campaigns, together with purchased lists. Filters allow the
exclusion of segment members based on predefined clauses. Segment prioritization and
deduplication make sure that individuals qualified for more than one segment do not receive
conflicting messages from more than one campaign. Waves can be generated as a subset of the
qualifying people within the targeted segments.
Recurring marketing programs can be defined in which each stage may be based on customer
response behavior or any other event. Marketers can define customer hierarchies, so that campaigns
can be driven by data summarized from any level of the hierarchy (for example household level and
customer level). People to be contacted are listed as campaign contacts for a specific campaign or
wave.
Each campaign may be presented with one or more offers. An offer is a type of demand creation
program that is directly presented to a target audience. It is intended to generate awareness of or
demand for one or more products. Responses are tracked through Communications.
Table 31 lists the entities in this ERD and their corresponding tables.
Table 31.
Marketing Program ERD Entities and Tables
Entity
Tables
Assignment Rule Group
S_ASGN_RULE_GRP
Call List
S_CALL_LST
Campaign Allocation
S_CAMP_CALL_LST
Campaign Contact
S_CAMP_CON
Campaign Load
S_CAMP_LD_WAVE
Campaign Wave
S_DD_CAMP_WAVE
Contact
S_CONTACT, S_PARTY
Contact Status
S_ SRCDCP_CONSTA
Deal
S_DEAL
Filter
S_DD_FILTER
Filter Clause
S_DD_FILTER_DTL
Load Wave
S_CAMP_LD_WAVE
Marketing Activity
S_SRC
Siebel Data Model Reference Version 8.0
77
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Table 31.
Marketing Program ERD Entities and Tables
Entity
Tables
Marketing Segment
S_CALL_LST
Offer
S_DMND_CRTN_PRG
Offer Campaign
S_CAMP_WAVE_DCP
Offer Campaign
S_SRC_DCP
Program Segment
S_CAMP_CALL_LST
Prospective Contact
S_PRSP_CONTACT
Purchased List
S_CALL_LST
Response
S_COMMUNICATION
78
Siebel Data Model Reference Version 8.0
**
2
6
1
2
.&% $%%&$
14
"
$
;>
!& % >
13
"
$' %
! % .& $
'
"
$ **
** "! <
3
"
$' !
' !;>
"
$ $
%
"$
& 9%!
' %
''' %
" < $
%
" < $
'$
" < $
"
+
14
% & !
* "
% & !
'"$
" 5
Oracle
$ [ $
&$
% >
$
9
% $
% $
% $
14
1 2
14
2
14
14
1
14
2
2
" < $
>$
" < $
"
$
'!% &
14
"
%
"$
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 32. Marketing Program
Siebel Data Model Reference Version 8.0
79
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Marketing Resource Management: Document
This ERD (shown in Figure 33) illustrates the marketing content processing of the enhanced
Marketing Resource Management module. It shows the relationship between the content and various
entities such as project, offer media package, and lead source. It also illustrates the process of
managing content inventory by region and location, and shows how fulfillment requests are
completed through vendor bidding.
Table 32 lists the entities in this ERD and their corresponding tables.
Table 32.
Marketing Resource Management: Document ERD Entities and Tables
Entity
Tables
Marketing Material
S_CB_ASSET
Material Inventory by Location
S_MKTG_DOC_INVT
Event Location
S_EVTLOC
Region
S_REGION
Material Fulfillment Request
S_EVT_FUL_REQ
Material Fulfillment Item
S_FUL_REQ_ITEM
Mat Fulfill Request Attachment
S_NOTE_FUL_REQ
Vendor Bidding
S_FUL_REQ_BID
Vendor Bidding Item
S_FR_BID_LITM
External Organization
S_ORG_EXT
Offer Media Package
S_DMND_CRTN_PRG
Offer Document
S_OFFR_CBAST
Lead Source
S_SRC
Lead Source Document
S_SRC_CBAST
Project
S_PROJ
Project Document
S_PROJ_CBAST
80
Siebel Data Model Reference Version 8.0
** "!
<
2
**
! &"$
2
'!% &
2
"*&'* ''
7&%
9"$
=
2
=
! &"$
3
14
" '
*&'* ''"$ "
14
" '*&'*IL'"$ 7&%
13
'!% & ! &"$
1
13
>$! . !! $
2
>$! . !! $
"
8 $'
$ [ $
3 3
** "
$
1
>$
' $
6
3
" < $
" '
$
2
1
" ' $>$ +.+' $
" "!
"
Oracle
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 33. Marketing Resource Management: Document
Siebel Data Model Reference Version 8.0
81
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Opportunity Management
This ERD (shown in Figure 34) illustrates the significant entities related to an opportunity (or lead),
including relationships to contacts, employees (generally sales representatives), products, accounts,
and so on.
Table 33 lists the entities in this ERD and their corresponding tables.
Table 33.
Opportunity Management ERD Entities and Tables
Entity
Tables
Address
S_ADDR_ORG
Agreement
S_DOC_AGREE
Contact
S_CONTACT, S_PARTY
Employee
S_EMP_PER, S_CONTACT, S_PARTY
Event
S_EVT_ACT
External Organization Unit
S_ORG_EXT, S_PARTY
Issue
S_ISS
Opportunity
S_OPTY
Opportunity Relationship
S_OPTY_REL
Organization Unit
S_ORG_EXT, S_PARTY
Person
S_CONTACT, S_PARTY
Product
S_PROD_INT
Quote
S_DOC_QUOTE
Sales Stage
S_STG
Source
S_SRC
Territory
S_ASGN_GRP
82
Siebel Data Model Reference Version 8.0
driver of
OPPORTUNITY
for
classified in
for
part of
considered on
PRODUCT OR
SERVICE
consideration of
ADDRESS
source of
basis for
based on
ISSUE
relevant as
relevant to
subject to
within
subject to
made up of
TERRITORY
consideration on
relevance of
part of
affiliated with
part of
for
OPPORTUNITY
RELATIONSHIP
collection of
of
responsible for
owned by
performer of
performed by
subject of
targeted at
resource for
CORRESPONDENCE
EVENT ACTIVITY
AGREEMENT
composed of
owned by
located at
for
OPPORTUNITY ISSUE
subject of
for
QUOTE
SALES DOCUMENT
vendor of
a collection of
produced by
of
PRODUCT
STRUCTURE
made up of
SALES
STAGE
a parent to
OTHER ORGANIZATION UNIT
a report to
a component of
composed of
classification of
driven by
SALES
METHODOLOGY
initiator of
initiated by
nvolver of
a partner to
MARKETING EVENT OR
ACTIVITY
involved on
INTERNAL / PARTNER
ORGANIZATION UNIT
ORGANIZATION UNIT
in partnership with
Title : Opportunity Management
Author : Oracle, Confidential
on
a report to
EMPLOYEE /
AGENT
manager of
involver of
OTHER
PERSON
PERSON
located at
for
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 34. Opportunity Management
Siebel Data Model Reference Version 8.0
83
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Order Life Cycle
This ERD (shown in Figure 35) illustrates how orders are tracked through their full life cycle by Siebel
Business Applications. The cycle starts with an opportunity that tracks the consideration of purchase
of one or more products. This opportunity leads to one or more quotes, composed of one or more
quoted product items. A quote may then lead to one or more orders. An order is composed of one
or more ordered product items. Fulfillment of the order can be tracked through a set of part
movements of various types, culminating in a shipment of products to the customer, and the
invoicing for shipped goods.
Table 34 lists the entities in this ERD and their corresponding tables.
Table 34.
Order Life Cycle ERD Entities and Tables
Entity
Tables
Account
S_ORG_EXT, S_PARTY
Invoice
S_INVOICE
Invoice Item
S_INVOICE_ITEM
Opportunity
S_OPTY
Opportunity Product
S_REVN
Order
S_ORDER
Order Item
S_ORDER_ITEM
Order Part Movement
S_ORDPART_MVMT
Product or Service
S_PROD_INT
Quote
S_DOC_QUOTE
Quote Item
S_QUOTE_ITEM
Shipment
S_SHIPMENT
84
Siebel Data Model Reference Version 8.0
target of
part of
for
lead to
PRODUCT OR SERVICE
part of
of
ORDER
taken for
composed of
ordered on
part of
of
billed via
billed via
for
for
for
part of
of
from
ALLOCATION
RECEIPT
MVMT
SHIP
MVMT
preceded by followed by
OTHER PART
MOVEMENT
ORDER PART MOVEMENT
on
subject of
SHIPMENT
made up of
vehicle for fulfillment of
delivered by
a step toward the
fulfillment of
billed via
for
INVOICE
billed via
composed of
generated for
reason for
INVOICE ITEM
fulfilled by
for
billed via
for
composed of
target of
ORDER ITEM
part of
created from
composed of
composed of
for
lead to
receiver of
QUOTE ITEM
for
QUOTE
prepared for
quoted for purchase on
for
composed of
considered for purchase on
of
OPPORTUNITY
PRODUCT
for
lead to
lead to
consideration of purchase of
OPPORTUNITY
of
ACCOUNT
Title : Order Life Cycle
Author : Oracle, Confidential
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 35. Order Life Cycle
Siebel Data Model Reference Version 8.0
85
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Orders
This ERD (shown in Figure 36) illustrates the relationships between orders and significant entities
related to orders such as assets, products, inventory locations, part movements, inventory
transactions, activities, and parties. Orders include sales orders, service orders, purchase orders,
and return material authorizations (RMAs) among others. The fulfillment of an order results in one
or more part movements according to the instructions of the order. Each part movement results in
one or more inventory transactions. Each order is usually the responsibility of a single internal or
partner organization, but sometimes two or more. An order may be assigned or credited to one or
more positions.
Table 35 lists the entities in this ERD and their corresponding tables.
Table 35.
Orders ERD Entities and Tables
Entity
Tables
Activity
S_EVT_ACT
Asset
S_ASSET
Inventory Location
S_INVLOC
Inventory Transaction
S_INV_TXN
Inventory Transaction Type
S_INV_TXN_TYPE
Order
S_ORDER
Order Item
S_ORDER_ITEM
Order Type
S_ORDER_TYPE
Part Movement
S_ACTPART_MVMT, S_ORDPART_MVMT
Part Movement Type
S_PARTMVMT_TYPE
Party
S_PARTY, S_ORG_EXT, S_POSTN, S_CONTACT
Product
S_PROD_INT
86
Siebel Data Model Reference Version 8.0
ORDER
composed of
SALES ORDER
part of
composed of
part of
result of
OTHER ORDER
RMA
for
composed of
part of
for
for
proceded by
for
for
PARTY
primary contact for
of
source of
related to
ORGANIZATION UNIT
PERSON
POSITION
responsible for
destination of
ACTIVITY
subject of
for
ACTIVITY PART
MOVEMENT
to
source of
OTHER ORGANIZATION
OTHER
PARTY
from
OTHER PART
MOVEMENT
INTERNAL/PARTNER ORGANIZATION
INVENTORY LOCATION
related to
PART
MOVEMENT
TYPE
for
destination of
ORDER TYPE
responsible for
customer of
responsibility of
for
responsibility of
to
from
of
subject of
of
followed by
an instance of
moved on
PRODUCT
ASSET
made into
subject of
subject to
of
ORDER PART MOVEMENT
PART MOVEMENT
ORDER ITEM
fulfilled by
cause of
PURCHASE ORDER
SERVICE ORDER
INVENTORY
TRANSACTION
TYPE
for
of
INVENTORY
TRANSACTION
Title : Orders
Author : Oracle, Confidential
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 36. Orders
Siebel Data Model Reference Version 8.0
87
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Partner Collaboration
Partner collaboration (shown in Figure 37) allows the brand owner's partner companies to give other
partners visibility to their data. With this functionality, partners can more easily collaborate with
other partners, without any required intervention from the brand owner company. Partner companies
can start collaborations and invite other partners of the brand owner to join their collaborations.
Once the invitation is accepted, individual partner companies who are now part of the collaboration
can pledge resources (Positions) to the collaboration, making the resources available to all partners
in the collaboration who may want to add the resource to a project or an opportunity.
Table 36 lists the entities in this ERD and their corresponding tables.
Table 36.
Partner Collaboration ERD Entities and Tables
Entity
Tables
Business Unit
S_BU
Collaboration
S_PARTY_GROUP
Collaboration Resource
S_PARTY_PER
Collaboration Invitation
S_BRDCST_MSG
Party
S_PARTY
Position
S_POSTN
88
Siebel Data Model Reference Version 8.0
"%%
9 "%%
''. $ $> $
13
%9 !
$ [ $* ''. $
%9 ! % $* ''. $
1
14
313
9 +
1
9
$ [ O$
&$
$ $'0 $
$ [ $
3
$ [ $&$
313
.&% $%% $%^ % $% .'
$ [ $
''. $
% $
+
3
.&% $%% $%^ % $% .'
% $
.&% $%% $% $""".
''. $%9 ! % &
.&% $%% $% $
1
Oracle,
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 37. Partner Collaboration
Siebel Data Model Reference Version 8.0
89
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Partner Program Registration
Partner Program Registration (shown in Figure 38) provides a system for the process of configuration
and deployment of registration of partner programs. Partner Program Registration consists of three
smaller and more manageable processes: a user registration process, a company registration
process, and a partner program registration process.
Table 37 lists the entities in this ERD and their corresponding tables.
Table 37.
Partner Program Registration ERD Entities and Tables
Entity
Tables
Application Approval Team
S_PRG_APPL_PSTN
Application Attachment
S_PRG_APPL_ATT
Application Question Answer
S_PRG_APPL_QA
Approval List
S_PRTNRPRG_PRTN
Eligibility List
S_PRTNRPRG_PRTN
Partner
S_ORG_EXT
Partner Program
S_PRTNR_PROG
Partner Program Application
S_PRTNRPRG_APPL
Partner Program Group
S_PRTNRPRG_GRP
Partner Program Membership
S_PRTNRPRG_MBR
Program Team
S_PRTNRPRG_PSTN
Renew List
S_PRTNRPRG_PRTN
90
Siebel Data Model Reference Version 8.0
2
''
% &$
2
' $
9"$
% $
6
' $
>'"
2
13
$
.&% $%%&$
$;' %
'
. ' +' %
>'' %
''% 9
" <
%
"$
!& ' $
' & "
'$
&
$
""". %9
113
3 1
1
$
" ' $
' $
7&% $
$%;
Oracle,
14
14
14
14
14
6
6
14
14
""
1
'
+
6
'
$
"
&
'
+
"
d
.%
"
!!$!
"
$
"
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 38. Partner Program Registration
Siebel Data Model Reference Version 8.0
91
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Party Model
This ERD (shown in Figure 39) illustrates the structure of the party entity, its significant subtypes,
and relationships. A party is either a person or some grouping of people such as an organization, a
household, a position or a list of users. A person may be an employee or agent of the company using
Siebel Business Applications. A person may also be considered a user if he or she has been granted
user login credentials. An access group is a type of party that is made up of one or more groups.
Addresses may be tracked for a person, a household, or an organization.
Table 38 lists the entities in this ERD and their corresponding tables.
Table 38.
Party Model ERD Entities and Tables
Entity
Tables
Access Group
S_PARTY
Account
S_ORG_EXT, S_PARTY
Business Address
S_ADDR_ORG
Employee/Agent
S_EMP_PER, S_CONTACT, S_PARTY
Group
S_PARTY
Household
S_ORG_GROUP, S_PARTY
Organization Relationship
S_ORG_REL
Organization Unit
S_ORG_EXT, S_PARTY
Party
S_PARTY
Party Relationship
S_PARTY_REL
Person
S_CONTACT, S_PARTY
Person Relationship
S_PARTY_REL or S_CONTACT_REL
Personal Address
S_ADDR_PER
Position
S_POSTN, S_PARTY
User List
S_PARTY
User Login
S_USER
92
Siebel Data Model Reference Version 8.0
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 39. Party Model
3"
Oracle
+ ' $%9
% $ ' $%9
!! %%
% $'!! %%
.&% $%%!! %%
$ [ $ ' $%9
9 ' $%9
6
+
&
% $
9 &%9 '!
" ' +0
$
%%
&
&% ' %
1
% $
9
&
1
$ [ $&$
9
% $
&$
9 +
9
$ [ $&$
&% '
$
Siebel Data Model Reference Version 8.0
93
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Payments
This ERD (shown in Figure 40) illustrates the support for payments provided in the Siebel Data Model.
The payment entity supports payments made by customers to the company, as well as payments
made by the company to customers, vendors, or others. A payment may be made to directly settle
an order or to settle one or more Invoices. An invoice may be paid through one or more payments.
A payment may be taken as a deduction from a prepayment balance available to the paying party.
Table 39 lists the entities in this ERD and their corresponding tables.
Table 39.
Payments ERD Entities and Tables
Entity
Tables
Address
S_ADDR_ORG
Invoice
S_INVOICE
Order
S_ORDER
Organization Unit
S_ORG_EXT, S_PARTY
Party
S_PARTY
Payment
S_SRC_PAYMENT
Person
S_CONTACT, S_PARTY
Prepayment Balance
S_PREPAY_BAL
94
Siebel Data Model Reference Version 8.0
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 40. Payments
Title : Payments
Author :Oracle, Confidential
INVOICE
PAYMENT
in settlement of
paid by
generated for
INBOUND PAYMENT
billed via
in settlement of
ORDER
paid by
received from
debited from
source of
OUTBOUND PAYMENT
PREPAYMENT
BALANCE
ADDRESS
addressed to
available to
used in
paid to
addressed to
for
located at
receiver of
PARTY
entitled to
PERSON
source for
receiver of
ORGANIZATION UNIT
OTHER
ORGANIZATION
ACCOUNT
Siebel Data Model Reference Version 8.0
95
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Performance Review
This ERD (shown in Figure 41) illustrates how the Siebel Data Model supports employee performance
reviews. Review templates of various types (such as annual review, periodic review, customer
satisfaction, MBO, KSO, and service level) can be specified to contain one or more Components (such
as shared objectives, training plan, rollup, 360-degree evaluation, individual objectives, and skills).
Components may be made up of standard review metrics. The performance review can then be
created for a given employee and employee-specific objectives can be defined. At the end of the
review period, the performance review can be completed and ratings given for assigned objectives
and for the standard review metrics. Different rating scales can be defined and used for different
types of reviews. Review templates can be specified for different job families and internal
organizations. An employee may optionally be separately reviewed for performance in each of his or
her assigned Positions.
This diagram also illustrates how the Siebel Data Model supports employee performance review by
other employees within an organization. These employees can be employees at the same level, a
higher level, or a lower level who may provide performance reviews for an employee to the manager
of that employee. A set of evaluation questions can be defined and associated with different sets of
employees. The reviewers answer the questions to evaluate the performance of the employee.
Table 40 lists the entities in this ERD and their corresponding tables.
Table 40.
Performance Review ERD Entities and Tables
Entity
Tables
360 Evaluation
S_PERF_360_EVAL
Competency
S_CMPTNCY
Employee Criteria (PDQ)
S_APP_VER, S_RVW_360_CS
Employee/Agent
S_EMP_PER, S_CONTACT, S_PARTY
Evaluation Script
S_CS_PATH, S_CS_PATH_SCPT
Evaluation Script Answer
S_CS_RUN, S_CS_RUN_ANSWR
Job Family
S_JOB_FAMILY
Organization Unit
S_ORG_EXT, S_PARTY
Party
S_PARTY
Performance Measurement Item
S_PERF_MEAS_ITM
Performance Review
S_EMP_PERF_MEAS
Period
S_PERIOD
Person
S_CONTACT, S_PARTY
Position
S_POSTN, S_PARTY
Review Component
S_PERF_RVW_CMP
Review Component Language
S_RVW_COMP_LANG
Review For Skill Item
S_PERF_CMPTNCY
96
Siebel Data Model Reference Version 8.0
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Table 40.
Performance Review ERD Entities and Tables
Entity
Tables
Review Metric
S_PERF_RVW_MTRC
Review Rating
S_PERF_RATING
Review Rating Scale
S_PERF_RATING_SCL
Review Template
S_PERF_RVW_TMPL
Review Template Component
S_PERF_RVW_COMP
Siebel Data Model Reference Version 8.0
97
98
Siebel Data Model Reference Version 8.0
14
14
13
313
9 % $
2
3
!
3
1
.&% $%%&$
$ [ $&$
1
9
$ [ $
$ $'0 $
$ [ $
1
9 > ;+
! > ;
1
" $$
+
> ; " $$
> ;
" $$
'$
&
= .*" '+
1
* "$
> ;"
2
$$&' > ;
!+
".
1
* "$
.= >
> ;"
> ; $
% '
> ;" '
> ;" ' " $$
" $ +
26
> ;* %< '' "
14
> ;
$
14
1
1
% $
14
2
" ' + &% "
% %* $%
9 " ' +
* "$
"%& "$
" ' +
* "$ > ;
" ' + * "$
"%& "$
3
14 2
* "$ "%& "$ "
1 313
" ' +
` !7{
>'& $%
" ' +0
$
2
% $
+
6
213
?
|}~>'& $
2
>'& $%
$%;
26
Oracle
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 41. Performance Review
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Personal Account
This ERD (shown in Figure 42) illustrates how personal accounts (such as financial accounts or
insurance policies) are accessible by contacts and associated with accounts, and how addresses are
relevant for each of these. Also supported are associations between contacts and the membership of
contacts in groups. Opportunities are associated with personal accounts to track the source of
existing business.
Table 41 lists the entities in this ERD and their corresponding tables.
Table 41.
Personal Account ERD Entities and Tables
Entity
Tables
Account
S_ORG_EXT, S_PARTY
Activity
S_EVT_ACT
Contact
S_CONTACT, S_PARTY
Opportunity
S_OPTY
Organization Unit
S_ORG_EXT, S_PARTY
Personal Account
S_ASSET
Personal Account Contact
S_ASSET_CON
Personal Address
S_ADDR_PER
Product
S_PROD_INT
Service Request
S_SRV_REQ
Siebel Data Model Reference Version 8.0
99
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 42. Personal Account
Title : Personal Account
Author : Oracle, Confidential
PERSONAL
ADDRESS
PERSONAL ACCOUNT CONTACT
user of
used by
for
party on
ACTIVITY
for
OPPORTUNITY
SERVICE REQUEST
source of
defined for
accessed by
subject of
applicable to
source of
subject of
derived from
PERSONAL ACCOUNT
user of
used by
part of
of
parent of
subject of
PRODUCT OR SERVICE
named as
ORGANIZATION UNIT
CONTACT
member of
GROUP
made up of
by
ADDRESS
USAGE
owner of
user of
defined for
ACCOUNT
by
of
user of
subject of
100
Siebel Data Model Reference Version 8.0
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Personal Financial Review
This ERD (shown in Figure 43) illustrates the information captured during the process of reviewing
the financial status of an individual customer. The financial review process itself is tracked as an
activity and becomes the source of the rest of the personal financial information of the contact,
including assets, liabilities, income, expenses, and financial needs (such as retirement savings).
When the financial needs of the contact are not fully addressed by his or her current financial product
holdings, assets, or liabilities, the salesperson makes one or more financial recommendations. When
a financial recommendation leads to a purchased product, such as a savings account or mortgage,
the product instance can be associated with the recommendation that led to it. Assets may be located
at a personal address and may be a source of income. Similarly, a liability, such as a mortgage, may
be secured by an associated asset and may have periodic expenses associated with the liability.
Table 42 lists the entities in this ERD and their corresponding tables.
Table 42.
Personal Financial Review ERD Entities and Tables
Entity
Tables
Activity
S_EVT_ACT
Activity Product Instance
S_ACT_ASSET
Asset (Liability)
S_FN_ASSET_LIAB
Asset (Liability) Contact
S_FN_ASSET_LIAB_CON
Contact
S_CONTACT, S_PARTY
Contact Relationship
S_CONTACT_REL
Financial Need
S_FN_NEED
Financial Recommendation
S_FN_RCMD
Household/Account
S_ORG_GROUP, S_PARTY
Income (Expense)
S_FN_INCM_EXP
Income (Expense) Contact
S_FN_INCM_EXP_CON
Need Contact
S_FN_NEED_CON
Opportunity
S_OPTY
Organization Unit
S_ORG_EXT, S_PARTY
Product
S_PROD_INT
Product Instance
S_ASSET
Product Instance Contact
S_ASSET_CON
Received Product Instance
S_FN_RCMD_ASSET
Recommendation Contact
S_FN_RCMD_CON
Siebel Data Model Reference Version 8.0
10 1
102
Siebel Data Model Reference Version 8.0
source of
for
with
of
affects
made of
from
is addressed by
subject of
of
owned by
for
of
is a
subject of
is a
ASSET LIAB.
CONTACT
NEED CONTACT
PROD. INST.
CONTACT
on
has a
ASSET (LIABILITY)
with
source of
for
regarding
to understand
to review
reported during
to review
ACTIVITY
incurred by
FINANCIAL
REVIEW
PROCESS
part of
location of
reported during
INCOME (EXPENSE)
located at
has
CONTACT
is primarily incurred by
associated to
owns
has
primary subject of
jointly has
associated to
from
of
ORG MEMBER
member of
in
owns
made up of
because of
source of
with
with
with
source of
of
managed by
owned by
associated with
RECOMMENDATION CONTACT
of
of
of
of
vendor of
ORGANIZATION UNIT
associated with
owned by
owns
vendor of
ACTIVITY PROD.
INST.
with
subject of
recommended during
ADDRESSED NEED
of
of
subject of
addresses
communicated during
of
of
subject of
produced by
PRODUCT INSTANCE
made up of
part of
FINANCIAL NEED
part of
because of
RCIVD PROD. INST.
source of
OPPORTUNITY
consideration of
considered on
FINANCIAL RECOMMENDATION
for
subject of
PRODUCT OR SERVICE
Title : Personal Financial Review
Author : Oracle, Confidential
INC. EXP.
CONTACT
involves
in
made up of
has
for
located at
to
ACTIVITY CONTACT
PERSONAL ADDRESS
of
with
has
has
of
CONTACT
RELATIONSHIP
member of
made up of
in
participates in
head of
defined for
HOUSEHOLD/
ACCOUNT
subject of
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 43. Personal Financial Review
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Pricing Comparison
This ERD (shown in Figure 44) illustrates the pricing comparison feature. A competitor's customer is
viewed as an opportunity and by creating a quote using that competitor's price list the size of the
opportunity can be quantified. Comparison quotes are generated using products and services from
the internal price list that are similar to the competitor's offerings, to calculate the savings the
customer could achieve by switching from the competitor.
Products and services provided by companies have complex pricing structures including tier-based
pricing. Pricing also varies by region, payment method, service type, credit risk, and so on. The tier
prices are associated with the attributes of the product or service that is provided.
Table 43 lists the entities in this ERD and their corresponding tables.
Table 43.
Pricing Comparison ERD Entities and Tables
Entity
Tables
Object Class
S_VOD, S_VOD_VER
Object Class Extended Attribute
S_XA_ATTR
Opportunity
S_OPPTY
Price List
S_PRI_LST
Price List Item
S_PRI_LST_ITEM
Pricing Matrix
S_PRI_MTRX
Pricing Matrix Item
S_PRI_MTRX_ITEM
Product Extended Attribute
S_PROD_INT_XA
Product or Service
S_PROD_INT
Product or Service Structure
S_PROD_ITEM
Quote
S_DOC_QUOTE
Quote Item
S_QUOTE_ITEM
Quote Item Extended Attribute
S_QUOTE_ITEM_XA
Tier Price Value
S_VDISCNT_ITEM
Tier Pricing
S_VOL_DISCNT
Siebel Data Model Reference Version 8.0
10 3
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 44. Pricing Comparison
Title : Pricing Comparison
Author : Oracle, Confidential
for
PRICE LIST ITEM
subject of
part of
COMPETITOR
ITEM
PRODUCT OR
SERVICE
composed of
QUOTE ITEM
EXTENDED
ATTRIBUTE
QUOTE ITEM
for
quotation for
described
by
subject of
comparison for
for
compared to
composed of
INTERNAL
ITEM
QUOTE
OPPORTUNITY
COMPETITOR
COMPARISON
for
subject
of
priced via
priced via
for
for
PRODUCT OR
SERVICE
STRUCTURE
used by
composed of
PRICE LIST
of
INTERNAL PRICE
LIST
COMPETITOR
PRICE LIST
assembly
of
component
of
PRODUCT
EXTENDED
ATTRIBUTE
TIER PRICE VALUE
for
described by
subject of
for
based on
classified as
TIER PRICING
subclass of
basis of
subject of
for
OBJECT CLASS
EXTENDED
ATTRIBUTE
PRICING MATRIX ITEM
for
PRICING MATRIX
for
for
have types
of
104
Siebel Data Model Reference Version 8.0
classification
for
OBJECT CLASS
described
by
based on
used by
parent class of
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Pricing
This ERD (shown in Figure 45) illustrates the pricing capabilities of Siebel Business Applications,
including price lists, pricing matrices, and pricing models, and how they are related to simple and
complex products or services to be priced. A price list is made up of price list items, each of which
tracks the price for a given product or service. The list prices may be adjusted for certain extended
attributes as defined in a specified pricing matrix. They may be adjusted based on changes to a
customizable product through component price adjustments. They may also be modified through a
specified pricing model made up of pricing factors.
Table 44 lists the entities in this ERD and their corresponding tables.
Table 44.
Pricing ERD Entities and Tables
Entity
Tables
Component Price Adjustment
S_PRI_CFG_ITEM
Object Class
S_VOD, S_VOD_VER
Object Class Extended Attribute
S_XA_ATTR
Price List
S_PRI_LST
Price List Item
S_PRI_LST_ITEM
Pricing Factor Item
S_PRIFCTR_ITM
Pricing Factor Item Attrib
S_PRIFCTITM_ATR
Pricing Matrix
S_PRI_MTRX
Pricing Matrix Attribute
S_PRI_ATTR
Pricing Matrix Item
S_PRI_MTRX_ITEM
Pricing Matrix Value
S_PRI_MTRX_VAL
Pricing Model
S_PRIMDL
Pricing Model Factor
S_PRIMDL_FCTR
Product Extended Attribute
S_PROD_INT_XA
Product or Service
S_PROD_INT
Product or Service Structure
S_PROD_ITEM
Siebel Data Model Reference Version 8.0
10 5
106
Siebel Data Model Reference Version 8.0
used by
PRICING MATRIX
made up of
part of
PRICING MATRIX
ITEM
configured via
based on
for
constraint for
made up of
for
PRICING MODEL
FACTOR
made up of
for
PRICING FACTOR ITEM
constrained by
of
for
basis of
the subject of
OBJECT CLASS
EXTENDED
ATTRIBUTE
have types
OBJECT CLASS
classification for
classified as
INTERNAL
PRODUCT OR
SERVICE
subclass of
described by
for
parent class of
described by
for
referenced by
subject of
a component of
an assembly of
based on
PRODUCT
EXTENDED
ATTRIBUTE
defined for
PRODUCT OR
SERVICE
STRUCTURE
PRICING FACTOR
ITEM ATTRIB
PRICING MODEL
of object class
used by
PRICING MATRIX
ATTRIBUTE
subject of
for
PRICING MATRIX
VALUE
PRICE LIST
an adjustment for
composed of
for
of
adjusted via
priced via
PRICE LIST
ITEM
for
COMPONENT PRICE
ADJUSTMENT
Title : Pricing
Author : Oracle, Confidential
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 45. Pricing
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Product Promotion
Product Promotion (shown in Figure 46) provides a system for managing product promotions.
Production Promotion allows the user to fully define the promotion based on products, product
templates, product attributes, and so on. Product Promotion also allows the user to specify other
information for the promotion including the terms, charges, and pricing rules.
Table 45 lists the entities in this ERD and their corresponding tables.
Table 45.
Product Promotion ERD Entities and Tables
Entity
Tables
Conditional Charge Prorate Plan
S_AGR_PR_PLAN
Product Promotion
S_PROD_INT
Product Promotion Charge
S_PROM_CHRG
Product Promotion Item
S_PROM_ITEM
Product Promotion Item Attribute
S_PROM_ITEM_XA
Product Promotion Item Attribute Value
S_PROMITM_VAL
Product Promotion Pricing Matrix Rule
S_PROM_PMTRX
Product Promotion Term
S_PROMITM_TRMS
Product Promotion Term Description
S_PROD_TRM_DESC
Siebel Data Model Reference Version 8.0
10 7
108
child of
has
parent of
Siebel Data Model Reference Version 8.0
contain
PRODUCT PROMOTION
PRODUCT
made up
PRODUCT PROMOTION ITEM
root of
define for
PRODUCT PROMOTION ITEM ATTRIBUTE
has
define for
PRODUCT PROMOTION ITEM ATTRIBUTE
VALUE
Title : PRODUCT PROMOTION
Author : Oracle, Confidential
child of
has
has
has
define for
PRODUCT PROMOTION TERM
define for
PRODUCT PROMOTION CHARGE
define for
contain
associate by
associate to
PRODUCT PROMOTION PRICING MATRIX RULE for
has
define for
PRODUCT PROMOTION TERM
DESCRIPTION
CONDITIONAL CHARGE
PRORATA PLAN
ADJUSTMENT GROUP
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 46. Product Promotion
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Product Quality Tracking
This ERD (shown in Figure 47) illustrates the significant entities related to product defect tracking.
Defects can be associated with service requests and may have associated activities defined to fix the
defect. Associations may be defined with various product or product versions to record which are
affected by the defect, which are planned to fix the defect, and which actually fix the defect.
Additional relevant associations with external products may be recorded. Defects may be associated
with other, related defects.
Table 46 lists the entities in this ERD and their corresponding tables.
Table 46.
Product Quality Tracking ERD Entities and Tables
Entity
Tables
Activity
S_EVT_ACT
Defect Symptom
S_PRDFCT_SYMP
Employee/Agent
S_EMP_PER, S_CONTACT, S_PARTY
Organization Unit
S_ORG_EXT, S_PARTY
Product or Service
S_PROD_INT, S_PROD_EXT
Product Quality Item
S_PROD_DEFECT
Project
S_PROJ
Project Item
S_PROJITEM
Resolution Item
S_RESITEM
Service Request
S_SRV_REQ
Siebel Data Model Reference Version 8.0
10 9
110
Siebel Data Model Reference Version 8.0
handled via
INTERNAL PRODUCT VERSION
INTERNAL PRODUCT OR SERVICE
actual fix for
OTHER PERSON
produced in
version of
EXTERNAL PRODUCT
part of
primarily by
reported by
relation
of
owner of
owned by
primary of
owner of
owned by
reported via
solution to
resolved by
defined for
INTERNAL PRODUCT
OTHER ACTIVITY
made up of
OTHER INTERNAL PRODUCT
OR SERVICE
an assembly of
owner of
owned by
a component of
OTHER
ORGANIZATION
UNIT
INTERNAL /
PARTNER
ORGANIZATION
UNIT
ORGANIZATION UNIT
caused by
part of
part of
reporter of
reported by
SERVICE REQUEST
made up of
resolved by
solution to
SERVICE REQUEST ACTIVITY
RESOLUTION ITEM
QUALITY ENHANCEMENT
ACTIVITY
ACTIVITY
EMPLOYEE / AGENT
fixed via
PRODUCT
RELEASE
PROJECT
OTHER
PROJECTS
PROJECT
PERSON
reporter of
in environment of
actually fixed in
reported for planned to
be fixed in
related to
based on
includes
belong to
PRODUCT PATCH /
ENHANCEMENT
REQUEST
basis for
REQUIRED
FEATURE
OTHER PRODUCT QUALITY ITEM
PRODUCT DEFECT
exhibition of
PRODUCT QUALITY ITEM
defined for
QA TEST
PROJECT ITEM
PRODUCT OR SERVICE
target
afflicted
fix for
with
duplicate
of
duplicated
as
observed for
DEFECT
SYMPTOM
Title : Product Quality Tracking
Author : Oracle, Confidential
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 47. Product Quality Tracking
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Product Recommendation
Product Recommendation (shown in Figure 48) provides a system for managing product
recommendations for up-sell or cross-sell. Product Recommendation allows the user to clearly define
the messages, the set of possible responses, and the recommendation itself.
Table 47 lists the entities in this ERD and their corresponding tables.
Table 47.
Product Recommendation ERD Entities and Tables
Entity
Tables
Communication
S_COMMUNICATION
Product Message
S_PROD_MSG
Product Message Response
S_PROD_MSG_RESP
Product Message Variable
S_PROD_MSG_VAR
Product or Service
S_PROD_INT
Product Recommendation
S_PROD_RECMNDTN
Siebel Data Model Reference Version 8.0
11 1
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 48. Product Recommendation
Title : Product Recommendation
Author : Oracle, Confidential
PRODUCT
recommendation for
RECOMMENDATION
PRODUCT OR SERVICE
recommended via
for
subject of
displayed via
PRODUCT MESSAGE
template for
PRODUCT MESSAGE
VARIABLE
defined for
utilize
have
for
COMMUNICATION
have
actual response for
112
Siebel Data Model Reference Version 8.0
PRODUCT MESSAGE
RESPONSE
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Products or Services
This ERD (shown in Figure 49) illustrates the significant entities related to a product including product
components (product structure), substitute or competitive products (product comparison), the
product's vendor, the product line or lines to which the product belongs, and so on. In addition, this
diagram illustrates the relationship between products and product prices, as well as the language
translations for some of these entities.
Table 48 lists the entities in this ERD and their corresponding tables.
Table 48.
Products or Services ERD Entities and Tables
Entity
Tables
Catalog
S_CTLG
Catalog Category
S_CTLG_CAT
Class Attribute
S_XA_ATTR
Class of Product or Service
S_VOD, S_VOD_VER
Language
S_LANG
Price List
S_PRI_LST
Price List Item
S_PRI_LST_ITEM
Product Assembly Port
S_PROD_ITEM
Product Line
S_PROD_LN
Product or Service
S_PROD_INT or S_PROD_EXT
Product or Service Attribute
S_PROD_INT_XA
Product Structure
S_PROD_ITEM
Vendor
S_ORG_EXT, S_PARTY
Siebel Data Model Reference Version 8.0
11 3
114
a collection of
Siebel Data Model Reference Version 8.0
CATALOG
made up of
for
EXTERNAL PRODUCT OR SERVICE
INTERNAL PRODUCT OR SERVICE
categorized in
PRODUCT OR SERVICE
part of
child of
translation for
parent to
a
component
of
for
described
via
of
constrained
by
PRODUCT
STRUCTURE
valid for
translation for
subject
of
for
of
translated
into
translated
into
translation
for
VENDOR
a report to
a parent to
CLASS OF PRODUCT OR
SERVICE
producer of
produced by
classified in
a classification for
subject of
of
translation for
CLASS ATTRIBUTE
basis for
based on
PRODUCT OR SERVICE
ATTRIBUTE
subject
of
PRICE
LIST
composed of
of
PRICE LIST ITEM
defined for
PRODUCT ASSEMBLY
PORT
translated into
translation for
an
assembly
of
translated into
part of
CATALOG CATEGORY
translated into
composed of
PRODUCT
LINE
part of
LANGUAGE
Title : Products or Services
Author : Oracle, Confidential
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 49. Products or Services
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Professional Services
This ERD (shown in Figure 50) illustrates how Siebel Business Applications support the planning and
execution of Professional Services projects. Projects can be defined for an external or internal client,
as the responsibility of one or more internal organizations, subcontracted to one or more partners,
associated with a required skill set, and made accessible to one or more positions. The definition of
required project team roles allows project billings to be estimated based on the billing rate and the
number of hours required from the resource. An employee, a sub-contractor employee or a contact
can ultimately fill a team role from the client, but until then, a list of potential project resources can
be stored for the project or a specific project team role. Positions and project team roles can be
associated with a service billing product to define the billing rate for that entity from a billing rate
list. Project issues can be tracked for a project, assigned to a project team role, and detailed as a
series of activities. Receivable Invoices billed to the client or payable invoices from subcontractors
can be associated with the project.
Table 49 lists the entities in this ERD and their corresponding tables.
Table 49.
Professional Services ERD Entities and Tables
Entity
Tables
Activity
S_EVT_ACT
Address
S_ADDR_ORG
Billing Rate List
S_PRI_LST
Employee/Agent
S_EMP_PER, S_CONTACT, S_PARTY
Internal/Partner Organization
S_ORG_EXT, S_PARTY
Invoice
S_INVOICE
Lead Source
S_SRC
Opportunity
S_OPTY
Organization Unit
S_ORG_EXT, S_PARTY
Person
S_CONTACT, S_PARTY
Position
S_POSTN, S_PARTY
Potential Project Resource
S_PROJ_PTL_RSRC
Project
S_PROJ
Project Contact
S_PROJ_CON
Project Issue
S_PROJ_ISS
Project Team Role
S_PROJ_RSRC
Skill
S_PROJRSRC_SKL
Siebel Data Model Reference Version 8.0
11 5
116
Siebel Data Model Reference Version 8.0
to track work on
the outcome of
for
assigned to
for
for
of
for
sent to
accessible to
responsible for
a partner for
responsibility of
located at
for
billed for
composed of
EMPLOYEE /
AGENT
OTHER
PERSON
INTERNAL/PARTNER
ORGANIZATION
ORGANIZATION UNIT
billed in
involved in
the client of
ADDRESS
for
of
for
filled by
PERSON
assigned to fill
BILLING RATE
LIST
defined as
subcontracted to
for
for
required by
located at
billed by
billed for
INVOICE
PROJECT CONTACT
targeted at
subject of
because of
source of
LEAD
SOURCE
requirer of
subject of
requirer of
POTENTIAL PROJECT
RESOURCE
defined for
PROJECT TEAM ROLE
assigned to
PROJECT ISSUE
subject of
subject of
PROFESSIONAL SERVICE PROJECT
requirer of
subject of
source of
OPPORTUNITY
subject of
for the resolution of
defined by
ACTIVITY
required by
SKILL
Title : Professional Services
Author : Oracle, Confidential
accessor of
OTHER
ORGANIZATION
UNIT
employed by
SERVICE
BILLING
POSITION
TYPE
POSITION
billed as
billing type for
held by
occupant of
billing type for
billed as
billed via
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 50. Professional Services
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Revenue
This ERD (shown in Figure 51) illustrates how revenue items are tracked and analyzed in Siebel
Business Applications. Revenue Items may be defined for any number of confirmed or likely business
transactions such as opportunities, accounts, projects, marketing events or activities, agreements,
invoices, and so on. Revenue is generally attributed to a product, service, product line, or some
description of the product or service offering. Credit for the revenue can be spread across sales team
members by breaking the revenue into a line for each sales team member with their credit amounts.
Recurring or incoming revenues over a period of time (weeks, months, or years) can be shown by
using the revenue schedule capabilities. A revenue template with detailed items can be created for
this purpose.
Table 50 lists the entities in this ERD and their corresponding tables.
Table 50.
Revenue ERD Entities and Tables
Entity
Tables
Agreement
S_DOC_AGREE
Agreement Item
S_AGREE_ITEM
Invoice
S_INVOICE
Invoice Item
S_INVC_ITEM
Marketing Event
S_SRC
Opportunity
S_OPTY
Organization Unit
S_ORG_EXT, S_PARTY
Person
S_CONTACT, S_PARTY
Position
S_POSTN, S_PARTY
Product Line
S_PROD_LN
Product or Service
S_PROD_INT
Project
S_PROJ
Revenue Item
S_REVN
Revenue Template
S_REVN_TMPL
Revenue Template Item
S_REVN_TMPL_ITM
Service Request
S_SRV_REQ
Siebel Data Model Reference Version 8.0
11 7
118
detailed item of
REVENUE ITEM
revenue plan for
Title : Revenue
Author : Oracle, Confidential
Siebel Data Model Reference Version 8.0
subject of
part of
REVENUE TEMPLATE
ITEM
details of
consist of
template for
part of
subject of
attributed to
subject of
made up of
subject of
attributed to
attributed to
attributed to
REVENUE TEMPLATE
PRODUCT OR SERVICE
OPPORTUNITY
AGREEMENT
INVOICE
MARKETING EVENT OR
ACTIVITY
SERVICE REQUEST
attributed to
EMPLOYEE / AGENT
PERSON
PROJECT
attributed to
occupant of
attributed to
held by
belongs to
manager of
composed of
CONTRACT ITEM
PRODUCT LINE
attributed to
INVOICE ITEM
owner of
attributed to
template item for
based on
based on
for
for
for
for
for
for
for
for
for
for
for
for
for
POSITION
a report to
OTHER
ORGANIZATION
UNIT
INTERNAL /
PARTNER
ORGANIZATION
UNIT
ORGANIZATION UNIT
OTHER PERSON
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 51. Revenue
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Sales Hierarchy and Credit Assignment
The Sales Hierarchy Module allows organizations to build sales hierarchies on top of sales territories
and to assign sales credits to territories and positions accordingly. A sales hierarchy (shown in
Figure 52) consists of sales territories, which are made up of positions and crediting rules. The sales
hierarchy can be versioned to accommodate ongoing changes without losing track of its history. A
position can be assigned to different territories or the same territory with different start date and
end date. A crediting rule can be applied to positions with allocation percentage defined. For a given
hierarchy version, the credit assignment engine is able to identify all the positions assigned to the
territories and all the applicable crediting rules by effective start date and end date. The crediting
rules, their criteria and values are read by Siebel Assignment Manager, which performs the
assignments appropriately. The sales hierarchy needs to be approved and validated before taking
effect.
Table 51 lists the entities in this ERD and their corresponding tables.
Table 51.
Sales Hierarchy and Credit Assignment ERD Entities and Tables
Entity
Tables
Credit Allocation
S_SLSCR_RL_PSTN
Credit Assignment Rule
S_SLSCRDT_RULE
Credit Rule Criteria
S_SLSCRDT_CRIT
Credit Rule Criteria Value
S_SLSCRDT_VAL
Hierarchy Version
S_SLS_HIER_VER
Hierarchy Version Territory
S_SLS_HIER_TERR
Position
S_POSTN, S_PARTY
Position Territory Assignment
S_SLSTERR_POSTN
Sales Hierarchy
S_SLS_HIER
Sales Territory
S_SLS_TERR
Siebel Data Model Reference Version 8.0
11 9
120
Siebel Data Model Reference Version 8.0
validated by
SALES HIERARCHY
RULE TYPE
subject of
categoried by
VALIDATION RULE
CREDIT RULE CRITERIA
characterized by
subject of
parent of
version of
recipient of
recipient of
recipient of
approve
approved by
approve
assigned to
approve
assigned territory
OTHER PARTY
POSITION
PARTY
approved by approve
approved by
HIERARCHY
VERSION
versioned by
composed of
part of
assignment of
POSITION TERRITORY ASSIGNMENT
HIERARCHY VERSION
TERRITORY
assigned to
transfer to
rollup to
allocated to
approved
consists of
applicable to
version of
belongs to
subordinate to
consists of
allocation of
CREDIT ASSIGNMENT
RULE
subject of
CREDIT ALLOCATION
SALES TERRITORY
characterized by
defined for
applied to
defined for
CREDIT RULE CRITERIA
VALUE
Title : Sales Hierarchy and Credit Assignment
Author : Oracle, Confidential
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 52. Sales Hierarchy and Credit Assignment
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Sales Portfolio Management
This ERD (shown in Figure 53) illustrates the process of creating and managing sales portfolios for
employees in sales positions within the sales organization. It shows the process for creating a sale
portfolio, setting target accounts for a given portfolio, and defining the business or service units for
each associated account as well as their business drivers and initiatives. Also illustrated are partners
and partner's competitors associated with the portfolio accounts. In addition, this ERD covers the
marketing campaigns which are targeted at the accounts in the portfolios.
Table 52 lists the entities in this ERD and their corresponding tables.
Table 52.
Sales Portfolio Management ERD Entities and Tables
Entity
Tables
Sales Portfolio
S_SLS_PORTFOLIO
Portfolio Category
S_PRTFL_CTGRY
Portfolio Account
S_PRTFL_ACCNT
Product Offering
S_ENT_SOLN
Portfolio Partner
S_PRTFL_PRTNR
Portfolio Attachment
S_PRTFL_ATT
Portfolio Product Offering
S_PRTFL_ENTSOLN
Account Prod Offering
S_PRTFL_ACCSOLN
Portfolio Sub_Account
S_PRTFL_SUBACC
Portfolio Account Attachment
S_PRTFL_ACC_ATT
Portfolio Business Driver
S_PRTFL_BU_DRVR
Portfolio Business Initiative
S_PRTFL_BU_INTV
Campaign
S_SRC
Portfolio Account Campaign
S_PRTFL_CAMP
Portfolio Partner Competitor
S_PRTFL_CMPTR
Organization Unit
S_ORG_EXT
Siebel Data Model Reference Version 8.0
12 1
122
Siebel Data Model Reference Version 8.0
!&
** $
14
14
2
1
* '
+
@
* '
$
"
14
13
9
&$
$
$ [ $
"
$ [ $
&$
$ [ $&$
14
* ' .&% $%%
! >
* ' %&. &$
14
* '
$
* '
&$
9"$
* ' .&% $%%
$ >
* ' &$
14
2
6
* '
9"$
%'% * '
* ' !&
** $
&$ !
** $
"
$
2 2
* ' &$ "
$
%
"
Oracle
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 53. Sales Portfolio Management
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Service Agreement
This ERD (shown in Figure 54) illustrates how Siebel Business Applications support service
agreements. A service agreement is a contract that entitles one or more contacts at one or more
organizations to service or support on one or more items through entitlements. Entitlement items
define coverage of products or specified instances of a product. The entitlement can be constrained
by a service calendar (to indicate 24x7 coverage, for example), and may be subject to one or more
metrics (that describe a guaranteed two-hour response, for example).
Table 53 lists the entities in this ERD and their corresponding tables.
Table 53.
Service Agreement ERD Entities and Tables
Entity
Tables
Account
S_ORG_EXT, S_PARTY
Agreement
S_DOC_AGREE
Agreement Entitlement
S_ENTLMNT
Agreement Item
S_AGREE_ITEM
Asset
S_ASSET
Contact
S_CONTACT, S_PARTY
Entitled Product or Asset
S_ENTLMNT_ITEM
Entitled Service
S_ENTL_ACT_TYPE
Expense Type
S_EXP_ITEM_TYPE
Material
S_PROD_INT
Order
S_ORDER
Preventive Maintenance
S_PM_PLNITM
Price Adjustment
S_ENTL_PRDPRI
Product
S_PROD_INT
Service Calendar
S_SCHED_CAL
Service Metric
S_SVC_METRIC
Service Request
S_SRV_REQ
Work Type
S_PROJ
Siebel Data Model Reference Version 8.0
12 3
124
Siebel Data Model Reference Version 8.0
basis for
entitled by
basis for
entitled by
basis for
based on
for
of
basis for
ACTION
TYPE
for
basis
for
covered by
used by
constrained by
for
for
made up of
part of
covered by
with
subject of
made
into
an
instance
of
subject of
for
subject of
ACCOUNT
subject of
employer of
employed at
for
for
ASSET
subject of
subject of
for
SERVICE
CALENDER
CONTACT
AGREEMENT
part of
AGREEMENT
ITEM
AGREEMENT
ITEM RENEWAL
TERM
made up of
basis for
based on
based on
ENTITLED PRODUCT OR ASSET
based on
PRICE ADJUSTMENT
AGREEMENT ENTITLEMENT
defined for
ENTITLED
SERVICE
suject of
basis for
based on
billable as
billable for
billable as
billable for
billable as
billable for
PREVENTIVE
MAINTENANCE
SERVICE
METRIC
ORDER
SERVICE
REQUEST
MATERIAL
WORK
TYPE
EXPENSE
TYPE
Title : Agreement Entitlement
Author : Oracle, Confidential
PRODUCT
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 54. Service Agreement
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Service Calendars and Work Shifts
This ERD (shown in Figure 55) illustrates the structure of service calendars and work shifts. Both are
made up of a set of working hours for each day of the week with a single exception calendar defining
planned holidays and other exceptional working days. An employee can be assigned to a work shift
to define his or her normal working hours with exceptional working or non-working hours expressed
as employee exception hours.
Table 54 lists the entities in this ERD and their corresponding tables.
Table 54.
Service Calendars and Work Shifts ERD Entities and Tables
Entity
Tables
Employee
S_CONTACT, S_EMP_PER, S_PARTY
Employee Exception Hours
S_EXCPT_CAL_HRS
Exception Calendar
S_EXCPT_CAL
Exception Calendar Hours
S_EXCPT_CAL_HRS
Person
S_CONTACT, S_PARTY
Schedule Calendar
S_SCHED_CAL
Schedule Calendar Hours
S_SCHED_CAL_HRS
Service Calendar
S_SCHED_CAL
Work Shift
S_SCHED_CAL
Siebel Data Model Reference Version 8.0
12 5
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 55. Service Calendars and Work Shifts
Title : Service Calendars and Work Shifts
Author : Oracle, Confidential
SCHEDULE
CALENDAR
HOURS
EXCEPTION
CALENDAR
HOURS
EMPLOYEE
EXCEPTION
HOURS
worked by
for
for
of
of
contributor of
SCHEDULE CALENDAR
PERSON
OTHER PERSON
SERVICE CALENDAR
EMPLOYEE /
AGENT
assigned to
WORK SHIFT
worked by
manager of
126
EXCEPTION
CALENDAR
a report to
Siebel Data Model Reference Version 8.0
for
of
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Service Request
This ERD (shown in Figure 56) illustrates how service requests are handled as a series of activities,
each owned by a specific employee. Relevant information includes the contact who reported the
service request, the product with which assistance is requested along with the customer's
environment or profile, and specifically which third-party products are in use and relevant to the
service request.
Table 55 lists the entities in this ERD and their corresponding tables.
Table 55.
Service Request ERD Entities and Tables
Entity
Tables
Activity
S_EVT_ACT
Asset (Product Instance)
S_ASSET
External Product Instance
S_ORG_PRDEXT
Party
S_PARTY, S_ORG_EXT, S_CONTACT, S_USER
Product or Service
S_PROD_INT, S_PROD_EXT
Service Region
S_SRV_REGN
Siebel Data Model Reference Version 8.0
12 7
128
Siebel Data Model Reference Version 8.0
EXTERNAL
PRODUCT
PRESENCE
part of
profile of
at
in
environment
of
made up of
EXTERNAL
PRODUCT OR
SERVICE
PRODUCT OR SERVICE
part of
profile of
subject of
of
in
environment
of
SERVICE REQUEST
part of
Title : Service Request
Author : Oracle, Confidential
for
manufactured into
INTERNAL PRODUCT OR SERVICE
subject of
an instance of
ASSET (PRODUCT
INSTANCE)
subject of
for problems
with
OTHER PERSON
OTHER ORGANIZATION
UNIT
INTERNAL / PARTNER
ORGANIZATION UNIT
ORGANIZATION UNIT
OTHER PARTY
responsible for
subject of
responsibility of
EMPLOYEE / AGENT
responsible for
PERSON
PARTY
responsible for
owner of
part of
OTHER ACTIVITY
responsibility of
reporter of
SERVICE
REGION
responsible for
responsible for
owned by
responsibility of
reported by
responsibility of
responsibility of
SERVICE REQUEST ACTIVITY
for problems
with
subject of
ACTIVITY
made up of
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 56. Service Request
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Shipment
This ERD (shown in Figure 57) illustrates the relationship between orders, quote, products, inventory
locations, and shipment related to orders. Delivery requests and delivery promises (date of delivery,
delivery quantity) can be associated with order items and quote items.
Table 56 lists the entities in this ERD and their corresponding tables.
Table 56.
Shipment ERD Entities and Tables
Entity
Tables
Inventory Location
S_INVLOC
Order
S_ORDER, S_ORDER_SHIP
Order Item Delivery Request
S_ORDPART_REQ
Order Line Item
S_ORDER_ITEM
Order Part Movement
S_ORDPART_MVMT, S_SHIPMENT_MVMT
Part Movement Type
S_PARTMVMT_TYPE
Product Internal
S_PROD_INT
Quote
S_DOC_QUOTE, S_DOC_ORDER
Quote Item Delivery Promise
S_QTE_ITM_DLVRQ
Quote Item Delivery Request
S_QTE_ITM_DLVRQ
Quote Line Item
S_QUOTE_ITEM
Shipment
S_SHIPMENT
Siebel Data Model Reference Version 8.0
12 9
130
Siebel Data Model Reference Version 8.0
13
1
3
1
1
1
7&
7& ' $ "
7& "
!' > +
" %
" >"$
+
7& "
!' > + 7&%
3
613
! "
!' > + 7&%
! ' $ "
13
9 " >"$
! "!' > + " %
2 32
$>$ +' $
!
2 13
%9 "$
%9 "$' $ "
! " >"$
%
Oracle
!&
$ $'
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 57. Shipment
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Siebel Assistant
This ERD (shown in Figure 58) illustrates how Siebel Business Applications support the Siebel
Assistant functionality. Personal or corporate sales planning items can be defined to serve as
template assessments or template activity plans. Both types of sales planning items can be defined
as relevant to one or more sales stages within one or more sales methodologies. A template
assessment contains one or more attributes, optionally validated by a set of valid values. Actual
Assessments are created from a template assessment during a specific sales stage to assess an
opportunity, an account, or a contact. A template activity plan is made up of one or more template
activities. Actual activity plans are created from a template activity plan during a specific sales stage
to prompt the user to plan certain activities copied from the template activities.
Table 57 lists the entities in this ERD and their corresponding tables.
Table 57.
Siebel Assistant ERD Entities and Tables
Entity
Tables
Account
S_ORG_EXT, S_PARTY
Activity
S_EVT_ACT
Activity Plan
S_EVT_ACT
Activity Plan Template
S_TMPL_PLANITEM
Assessment Template
S_TMPL_PLANITEM
Assessment
S_ASSESS
Assessment Attribute
S_ASSESS_ATTRIB
Assessment Attribute Valid Value
S_ASSESS_ATTVAL
Assessment Value
S_ASSESS_VAL
Employee/Agent
S_EMP_PER, S_CONTACT, S_PARTY
Opportunity
S_OPTY
Opportunity Stage
S_OPTY_STG
Person
S_CONTACT, S_PARTY
Sales Methodology
S_SALES_METHOD
Sales Stage
S_STG
Stage Plan Item
S_STG_PLANITEM
Stage Recommendation
S_STG_RECOMMEND
Template Activity
S_EVT_ACT
Siebel Data Model Reference Version 8.0
13 1
132
Siebel Data Model Reference Version 8.0
subject of
ACCOUNT
subject of
of
ASSESSMENT
a component of
for
of
OTHER
PERSON
OPPORTUNITY
for
EMPLOYEE /
AGENT
for
ASSESSMENT
TEMPLATE
planned by
created during
PERSON
of
for
SALES PLANNING ITEM
container of
ASSESSMENT ATTRIBUTE
validated via
defined for
made up of
for
of
OPPORTUNITY STAGE
ACTIVITY PLAN TEMPLATE
of
of
at
for
SALES
METHODOLOGY
composed of
for
STAGE
RECOMMENDATION
SALES STAGE
of
for
governor of
for
for
for
governed by
currently at
for
STAGE PLAN ITEM
instance of
ACTIVITY
PLAN
instantiated as
for
TEMPLATE
ACTIVITY
OTHER ACTIVITY
ACTIVITY
part of
made up of
ASSESSMENT ATTRIBUTE
VALID VALUE
defined for
created from
assesed via
subject of
ASSESSMENT VALUE
Title : Siebel Assistant
Author : Oracle, Confidential
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 58. Siebel Assistant
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Territory Management
This ERD (shown in Figure 59) illustrates that sales territories can be defined geographically,
explicitly (using named accounts, contacts, or assets), or a combination of both. Flexible territory
hierarchies can be defined to capture the relationship between territories. Multiple positions can be
assigned to a given territory and multiple territories can be assigned to a given position. Accounts,
contacts, and assets can be assigned to sales representatives within a sales force.
Table 58 lists the entities in this ERD and their corresponding tables.
Table 58.
Territory Management ERD Entities and Tables
Entity
Tables
Account
S_ORG_EXT
Account Team Member
S_ACCNT_POSTN
Account/Terr Mapping
S_TERR_ACCNT
Asset
S_ASSET
Asset Team Member
S_ASSET_POSTN
Asset/Terr Mapping
S_TERR_ASSET
Business Unit
S_BU
Contact
S_CONTACT
Contact/Terr Mapping
S_TERR_CON
Contact Team Member
S_POSTN_CON
Division
S_ORG_EXT
Geo/Terr Mapping
S_TERR_ZIP, S_TERR_REGION
Position
S_POSTN
Position Territory Assignment
S_TERR_POSITION
Region
S_REGION
Territory
S_TERRITORY
Territory Hierarchy
S_TERR_HIER
Territory Version
S_TERRHIER_NODE
Zipcode
(None)
Siebel Data Model Reference Version 8.0
13 3
134
Siebel Data Model Reference Version 8.0
% $
13
%%
$
13
&$
13
13
%%"
"".
&$""".
$ 0
" $
+" $
$ """.
% $ +
%%
$"$
3"
Oracle
! > % $
$
9 ! > % $
13
1
%'%*
.&% $%%&$
+
9 9+
2
@13
9 '
[ !
+
> % $
0
" $
%%0
" $
&$0
" $
13
+
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 59. Territory Management
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Territory Quota Rollup
This ERD (shown in Figure 60) covers sales quotas setup and quota rollup in the territory
management system. It illustrates assigning sales quotas to periods, contacts, accounts, regions,
and ZIP codes. These assignments can be spread over different periods. As each territory consists
of a set of contacts, accounts, regions, and ZIP codes assigned with quotas; the quotas can be rolled
up to each territory or each territory per period.
Table 59 lists the entities in this ERD and their corresponding tables.
Table 59.
Territory Quota Rollup ERD Entities and Tables
Entity
Tables
Sales Quota
S_SLS_QUOTA
Territory
S_TERRITORY
Territory Quota
S_TERR_QUOTA
Account/Quota
S_QUOTA_ACCNT
Contact/Quota
S_QUOTA_CON
Geo/Quota
S_QUOTA_REGN, S_QUOTA_ZIP
Quota Assignment Breakdown
S_QTA_ACC_PD, S_QTA_CON_PD,
S_QTA_REGN_PD, S_QTA_ZIP_PD
Contact /Terr Mapping
S_TERR_CON
Account / Terr Mapping
S_TERR_ACCNT
Geo/Terr Mapping
S_TERR_REGION, S_TERR_ZIP
Terr/Qta/Geo
S_TERR_QTA_REGN, S_TERR_QTA_ZIP
Terr/Qta/Con
S_TERR_QTA_CON
Terr/Qta/Accnt
S_TERR_QTA_ACCT
Accnt Quota Credit
S_TRQT_ACC_CRDT
Contact Quota Credit
S_TRQT_CON_CRDT
Geo Quota Credit
S_TRQT_REGNCRDT, S_TRQT_ZIP_CRDT
Period Quota
S_QTA_PD_BRKDN
Terr Quota Breakdown
S_TRQT_PD_BRKDN
Siebel Data Model Reference Version 8.0
13 5
136
Siebel Data Model Reference Version 8.0
2
!
7&
1
%'%7&
14
1
!
2
14
6
&$07&
&$
&$0
" $
+" $
7& %%
$"$
14
$
$
0
" $
0
" $
07&
[ !
+
37
Oracle
$
070
7&
!
9 '
070 $
$ 7&
!
$ 07&
070 $
1 5 6
7& %%
$"$
. <! ;$
3
2
2
$7&
!
+7& " $
7& " $
. <! ;$
1 5 6
2 13
7&
. <! ;$
+7&
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 60. Territory Quota Rollup
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Textile, Apparel, and Footwear
This ERD (shown in Figure 61) illustrates how Siebel Business Applications support the assortment
planning process in the textile, apparel, and footwear industries. A retailer can define the products
that are sold in each season, then associate each product with one or more market segments to
define recommended product assortments. Rather than complicating the assortment by specifying
product entries for each combination of one or two attributes in which a style is manufactured (such
as size or color), the attributes can be specified through a seasonal or nonseasonal product option
range (for example, a shirt size range of S, M, L, and XL). The retailer can then further specify
recommended product option mixes that indicate the proportion of each product option attribute
value to deliver when ordering a style (for example, a mix preference of 20% S, 30% M, 30% L, and
20% XL), or each retail customer can create its own mix preferences. When creating an assortment
plan for a season, the retail customer chooses the styles from the recommended product assortment
for the season, modifies the assortment to fit its customers, and chooses the desired product option
mix for each product option. The total ordered quantity of each style is then further broken down
into the quantity to be delivered in each subperiod within the season (for example, each week in the
season). This assortment plan can then serve as a guideline for ordering throughout the season or
even facilitate the generation of orders in each delivery period in the season.
The shaded subtypes in this diagram indicate examples of the types of data that may be found within
a supertype. They are not intended to indicate strict subtypes.
Table 60 lists the entities in this ERD and their corresponding tables.
Table 60.
Textile, Apparel, and Footwear ERD Entities and Tables
Entity
Tables
Marketing Segment
S_MKT_SEG
Order
S_ORDER
Order Item
S_ORDER_ITEM
Organization External
S_ORG_EXT
Period
S_PERIOD
Period Relationship
S_PERIOD_REL
Product Attribute Type
S_LST_OF_VAL
Product Attribute Value
S_LST_OF_VAL
Product Option Mix Preference
S_PROD_OPT_MIX
Product Option Mix Proportion
S_PROD_OPT_PCT
Product Option Range
S_PROD_OPTION
Product Option Range Member
S_PROD_OPT_VAL
Quote
S_DOC_QUOTE
Quote Item
S_QUOTE_ITEM
Siebel Data Model Reference Version 8.0
13 7
138
Siebel Data Model Reference Version 8.0
primarily composed of
lead to
defined for
ASSORTMENT
PLAN
PERIOD RELATIONSHIP
delivery period for
defined
for
for
of
for
composed
of
billed to
for
delivery period for
to
of
MARKETING
the target of
SEGMENT
part of
made up
of
WEEK
subject of
PERIOD
subject of
scope of
specific to
items within
a collection of
subject of
LINE OF BUSINESS
composed of
defined for
OTHER PERIOD TYPES
SEASON
composed
of
defined for
CATEGORY
applicable
to
in
secondary
domain for
COLOR PALETTE
SEASONAL
SIZE RUN
NON-SEASONAL
PRODUCT OPTION RANGE
primarily
defined by secondarily
defined by
primary
domain
for
PRODUCT
ATTRIBUTE
TYPE
the domain
for
a value
of
includer
of
Title : Textile, Apparel and Footwear
Author : Oracle, Confidential
defined for
secondarily
manufactured in
in
defined for
primarily
manufactured in
parent to
collection
of
for
PRODUCT OPTION
RANGE MEMBER
secondarily
of
collection of
subject of
secondary defined by
primarilly
of
subject
of
COLOR
FAMILY
relevant to
collection of
STYLE/COLOR/DIMENSION
launched
in
COLOR
OTHER ATTRIBUTE VALUE
SHOE SIZE
PRODUCT ATTRIBUTE VALUE
primary defined by
subject of
subject of
subject of
PRODUCT INTERNAL
recommended to be ordered in
debut season for
targetted at
for
the
default
mix for
RECOMMENDED
MIX
ordered on belonging to
specific to
ACCOUNT
SPECIFIC
MIX
OTHER
ORGANIZATION
STORE
ACCOUNT
ORGANIZATION
EXTERNAL
subject of
subject of
for
secondarily of
primarily of
PRODUCT OPTION MIX PREFERENCE
(SPREAD)
subject of
applicable to
PRODUCT OPTION
MIX PROPORTION
definer of
primarily specified
on
ASSORTMENT specify
PLAN ITEM
secondarily specified
specify
on
for
scheduled
by
of
ASSORTMENT PLAN ITEM
SCHEDULED DELIVERY
QUOTE ITEM
secondarily composed of
created from
of
QUOTE
defined
for
ORDER
composed
of
for
ORDERED
ASSORTMENT
PLAN ITEM
of
split into
ORDERED
ASSORTMENT
PLAN ITEM
PROPORTION
ORDER ITEM
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 61. Textile, Apparel, and Footwear
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Time Sheet
This ERD (shown in Figure 62) illustrates how Siebel Business Applications track employee time
sheets. Employees can track time spent for client billing or for other purposes. Time can be entered
for projects, activities, service requests, and so on. These time units can then be aggregated into
time sheets through time sheet lines. A time sheet is reported for a specified reporting period and
lists time spent on specific project or nonproject work such as vacation, sick leave, training, and so
on. Each time sheet line is specific to a given day within the reporting period.
Table 61 lists the entities in this ERD and their corresponding tables.
Table 61.
Time Sheet ERD Entities and Tables
Entity
Tables
Activity
S_EVT_ACT
Organization Unit
S_ORG_EXT, S_PARTY
Period
S_PERIOD
Person
S_CONTACT, S_PARTY
Project
S_PROJ
Project Team Role
S_PROJ_RSRC
Service Request
S_SRV_REQ
Time Unit
S_TMSHT_ITEM
Timesheet
S_TMSHT
Timesheet Approval
S_TMSHT_APPR
Timesheet Line
S_TMSHT_LN
Work Type
S_PROJ
Siebel Data Model Reference Version 8.0
13 9
140
Siebel Data Model Reference Version 8.0
TIME SHEET
made up of
for
approved
reported by
for
reported for
PERIOD
NON-PROJECT
WORK TYPE
WORK TYPE
report of time
worked on
PROJECT TASK
for
reported by
belongs to
PROJECT
require
PERSON
reporter of
based
basis for
affiliated with
owner of
EMPLOYEE/AGENT
OTHER PERSON
approver
reporter of
composed of
targeted at
OTHER
ORGANIZATION
UNIT
subject of
owned by
ACTIVITY
INTERNAL
ORGANIZATION UNIT
ORGANIZATION UNIT
have ownership of
OPPORTUNITY
subject of
for
referenced by
defined for
PROJECT TEAM ROLE
subject of
made up
classification for
classified as
WORK TIME UNIT
subject of
submitted for
SERVICE
REQUEST
subject of
reported via
part of
adjustment
TIME ADJUSTMENT
TIME SHEET LINE
made up of
TIME UNIT
adjusted
Title : Time Sheet
Author : Oracle, Confidential
contact for
owned by associated with
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 62. Time Sheet
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Trade Promotions
This ERD (shown in Figure 63) illustrates the planning and execution of a consumer goods promotion,
including definition of promotion-products, promotion-accounts, and promotion-account-products.
Also supported are promotion payments, promotion agreements, and observations of store
conditions.
Table 62 lists the entities in this ERD and their corresponding tables.
Table 62.
Trade Promotions ERD Entities and Tables
Entity
Tables
Account
S_ORG_EXT, S_PARTY
Contract
S_D0C_AGREE, S_DOC_QUOTE, S_ORDER
Contract Item
S_AGREE_ITEM, S_QUOTE_ITEM, S_ORDER_ITEM
Fund Allocation
S_MDF_ALLOC
Internal Product Presence
S_ORG_PROD
Marketing Development Fund
S_MDF
Marketing Event or Activity
S_SRC, S_SRC_CHNL
Note
S_NOTE_SRC
Order
S_ORDER
Other Contract
S_DOC_AGREE, S_DOC_QUOTE
Person
S_CONTACT, S_PARTY
Product
S_PROD_INT, S_PROD_EXT
Siebel Data Model Reference Version 8.0
14 1
142
Siebel Data Model Reference Version 8.0
?13
14
14
!& $ $'
!&
9 " < $
>$ > +
" $ &$
" $
&$ !&
" $ '$
14
2 13
2
2
!& 8 $'
" $
" $
!&
13
?
" < $
!>' "$*&$!
" < $
>$ > +
*&$!
'' $
13
! "
Oracle
$
% $
14
6
&$
14
9
$
!
$
3
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 63. Trade Promotions
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Training Curriculum Course
This ERD (shown in Figure 64) illustrates the entities and relationships relevant to the training
business function. A training curriculum is made up of one or more training courses, which are
offered through one or more course offerings. Both courses and curriculums target one or more
audience types and have literature associated with them. A person can be registered for one or more
course offerings. Tests that may be defined for one or more course offerings, including test questions
and possible answers. Tests taken by an Individual contain the answer given by that person to each
question and the score achieved by that person for each question.
Table 63 lists the entities in this ERD and their corresponding tables.
Table 63.
Training Curriculum Course ERD Entities and Tables
Entity
Tables
Catalog Category
S_CTLG_CAT
Access Group
S_PARTY
Employee Course
S_EMP_CRSE
Employee Course Status
S_EMP_CRSE_STAT
Siebel Data Model Reference Version 8.0
14 3
144
Siebel Data Model Reference Version 8.0
composed of
offered in
categorized into
OTHER PRODUCT OR SERVICE
TRAINING COURSE
path
for
provide training for
for
for
belongs to
for
CURRICULUM
CATEGORY
basis of
based on
PERSON
instructor of
instructed by
in need of
enrolled in
registered by
TRAINING COURSE OFFERING
OTHER MARKETING EVENT OR
ACTIVITY
for
subject of
certification of
CURRICULUM
PERSON
certified for
subject of
granted access to
ACCESS GROUP
accessed by
MARKETING EVENT OR ACTIVITY
needed by
EMPLOYEE COURSE
tracked by
of
EMPLOYEE COURSE STATUS
subject of
LITERATURE
for
subject of
satisfied by
JOB PROFILE
satisfied by
categorized into
target of
CURRICULUM
TARGET AUDIENCE
targeted at
provide training for
composed of
part of
TRAINING
CURRICULUM STEP
TRAINING CURRICULUM
composed of
CATALOG CATEGORY
available for
COURSE
AVAILABLE
LANGUAGE
part of
part of
PRODUCT OR SERVICE
subject of
of
TRAINING
CURRICULUM
STEP COURSE
Title : Training Curriculum Course
Author : Oracle, Confidential
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 64. Training Curriculum Course
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Training Test Engine
This ERD (shown in Figure 65) illustrates the entities and relationships relevant to the training test
engine business function. Tests may be defined for one or more course offerings, or for one or more
courses, including test questions and possible answers, and may be available in one or more
languages. Each test question can be either determined in advance or pulled from a question pool at
run time. Tests taken by an Individual contain the exact question presented to the individual, the
individual's answer to each question, and the score achieved by that person for each question. It also
keeps track whether the question has been attempted.
Table 64 lists the entities in this ERD and their corresponding tables.
Table 64.
Training Test Engine ERD Entities and Tables
Entity
Tables
Course/Course Offering Test
S_CRSE_OFFR_TST
Event Location
S_EVTLOC
Individuals Test
S_CRSE_TSTRUN
Individuals Test Answer
S_CRSE_TSTRUN_A
Individuals Test Category
S_TSTRUN_CATSTS
Individuals Test Question
S_CRSE_TSTRUN_Q
Marketing Event or Activity
S_SRC
Pool Question
S_POOL_QUES
Product or Service
S_PROD_INT
Question/Possible Answer
S_CRSE_TST_ANSR
Question/Question Pool, Question Pool, Question
S_TST_QUES
Question Category
LOV
Test Available Language
S_CRSE_TST_LANG
Test Question
S_CRSE_TST_QUES
Topic/Objective
S_CRSE_TOPIC
Training Course
S_PROD_INT_CRSE, S_PROD_INT
Training Course Offering
S_SRC_EVT, S_SRC
Training Test
S_CRSE_TST
Siebel Data Model Reference Version 8.0
14 5
146
Siebel Data Model Reference Version 8.0
13
2
9 " < $
>$ > +
$ $
& % ** $
>$' $
3
" < $
>$ > +
14
213
$! > !&'%%
+
$! > !&'%%
$! > !&'%%
7&% $
14
$! > !&'%
%$%;
Oracle
14
13
1
6
1
& %0 & % ** $
%
14
6
7&% $
+
9 !& % >
$ $
& %
1
0 .= >
@
!& % >
14
21
7&% $
7&% $
'
14
7&% $07&% $ '
14
13
14
%> '.'
'$
&
6
$ $
%
%7&% $
7&% $0 %% .'$%;
'7&% $
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 65. Training Test Engine
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Versioned Object Definition
Versioned Object Definition (shown in Figure 66) provides a system for managing the versioned
objects in the system including Products, Product Templates (Classes), Attributes, Context Variables,
and so on. Versioned Object Definition replaces the Product Configurator infrastructure tables in all
previous releases.
Table 65 lists the entities in this ERD and their corresponding tables.
Table 65.
Versioned Object Definition ERD Entities and Tables
Entity
Tables
Attribute Definition
S_ISS_ATTR_DEF
Attribute Value
S_ISS_ATTR_VAL
Joint Workspace
S_ISS_JWS
Joint Workspace Item
S_ISS_JWS_ITEM
Object Attribute
S_ISS_OBJ_ATTR
Object Attribute Value
S_ISS_OBATR_VAL
Object Definition
S_ISS_OBJ_DEF
Object Definition
S_VOD
Versioned Object Definition Version
S_VOD_VER
Siebel Data Model Reference Version 8.0
14 7
148
locally
defined
for
for
Siebel Data Model Reference Version 8.0
have
have
PRODUCT DEFINITION
for
OBJECT DEFINITION
child for
parent of
PRODUCT HEADER
DEFINITION
have
VERSIONED OBJECT DEFINITION
PRODUCT
ATTRIBUTE
OBJECT ATTRIBUTE
have
for
PRODUCT ATTRIBUTE VALUE
OBJECT ATTRIBUTE VALUE
Title : Versioned Object Definition
Author : Oracle, Confidential
have
for
PRODUCT TEMPLATE
DEFINITION
have
for
PRODUCT TEMPLATE HEADER
DEFINITION
have
locally
defined
for
PRODUCT TEMPLATE
ATTRIBUTE
have
for
PRODUCT TEMPLATE
ATTRIBUTE VALUE
ATTRIBUTE DEFINITION
for
have
have
grouped in
for
VERSIONED OBJECT
DEFINITION VERSION
for
have
OTHER VERSIONED OBJECT HEADER
DEFINITION
ATTRIBUTE VALUE
for
ATTRIBUTE HEADER DEFINITION
for
globally defined via
JOINT WORKSPACE
ITEM
for
have
JOINT WORKSPACE
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 66. Versioned Object Definition
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Warranty
This ERD (shown in Figure 67) illustrates how Siebel Business Applications tracks product warranty
coverages. Warranty coverage is provided by an organization (often the vendor of the product) and
covers one or more products that are part of a covered product line. The products covered under the
warranty coverage may be specified directly through product warranty coverage entries or indirectly
through product line warranty coverages (which specifies coverage for the products that compose
the product line). Warranty service may be provided by one or more authorized service providers.
The various warranty coverages applicable to an asset throughout its life are tracked, and may be
applied to fully or partially compensate the service provider for service requested in a service order.
Table 66 lists the entities in this ERD and their corresponding tables.
Table 66.
Warranty ERD Entities and Tables
Entity
Tables
Asset
S_ASSET
Asset Warranty Coverage
S_ASSET_WRNTY
Order
S_ORDER
Order Item
S_ORDER_ITEM
Organization Unit
S_ORG_EXT, S_PARTY
Product
S_PROD_INT
Product Line
S_PROD_LN
Product Line Warranty Coverage
S_PRDLN_WRNTY
Product Warranty Coverage
S_PROD_WRNTY
Warranty Coverage
S_WRNTY_CVRG
Warranty Service Provider
S_WRNTY_SRV_ORG
Siebel Data Model Reference Version 8.0
14 9
150
Siebel Data Model Reference Version 8.0
part of
provided by
subject of
role played by
of
OTHER ORDER
ORGANIZATION UNIT
by
PRODUCT
WARRANTY
COVERAGE
subject of
made up of
of
WARRANTY COVERAGE
by
ASSET
WARRANTY
COVERAGE
made up of
applied to
claimed against
SERVICE ORDER
WARRANTY SERVICE
PROVIDER
ORDER
composed of
ORDER ITEM
Title : Warranty
Author : Oracle, Confidential
by
warrantor of
provided by
of
subject of
made into
PRODUCT LINE
WARRANTY
COVERAGE
an instance of
made up of
of
ASSET
subject of
part of
made up of
PRODUCT
LINE
composed of
PRODUCT
a part of
vendor of
vended by
Understanding the Logical Model Entity Relationship Diagrams and Descriptions
Figure 67. Warranty
Understanding the Physical
Model
The Siebel physical model encompasses the tables, their columns, and their indexes. This chapter
covers the following topics.
Data Model Naming Conventions on page 151
Data Model Type Definitions on page 154
Siebel System Fields on page 158
INTEGRATION_ID Columns on page 159
Include Only Field on page 159
Siebel Repository on page 159
Database Schema Version on page 160
Limit Checking for Data Types on page 160
Party Model Unifies Access to Data on page 161
Data Model Naming Conventions
This topic describes:
Table Naming Conventions
Index Naming Conventions on page 153
Column Naming Conventions on page 153
Abbreviations Used in the Physical Model Listings on page 154
Table Naming Conventions
Tables in the Siebel database use a three-part naming convention. The syntax is:
PREFIX_NAME_SUFFIX.
PREFIX
Table names in Siebel Business Applications have a one- to three-letter prefix (EIM_,
S_, W_, and so on) to distinguish them from other tables in your application.
NAME
A unique table name that is generally an abbreviation of the entity supertype name.
SUFFIX
A supertype name may be followed by the entity subtype. For example, the supertype
EVT (event) has ACT (activity) as one of its subtypes. Thus, the name becomes
S_EVT_ACT.
Siebel Data Model Reference Version 8.0
15 1
Understanding the Physical Model Data Model Naming Conventions
The prefix indicates the part of the Siebel schema to which a table belongs. Table 67 provides some
of the prefixes and their descriptions.
Table 67.
Table Prefixes
Prefix
Meaning
EIM_
Interface tables for Siebel Enterprise Integration Manager.
S_
Siebel base table. (Exception: Tables with names of the form S_<name>_IF are
obsolete interface tables.)
W_
Oracle Business Analytics Warehouse table, described in Oracle Business Analytics
Warehouse Data Model Reference.
The suffix indicates a table type. Table 68 provides some of the suffixes and their descriptions.
Table 68.
Base Table Suffixes
Suffix
Meaning
_ATT
File attachment table.
_REL
A table that supports a many-to-many relationship from an entity back to itself.
_SS
A table that stores Siebel-to-Siebel integration information.
_V
A table that represents a database view.
_X
One-to-one extension table, available for customers to add attributes to the Siebel
database.
_XA
A table that stores extended attributes associated with an object class.
_XM
One-to-many extension table, available for customers to add attributes to the Siebel
database.
152
Siebel Data Model Reference Version 8.0
Understanding the Physical Model Data Model Naming Conventions
Index Naming Conventions
Indexes are named the same as the table on which they are created plus a one- to four-character
suffix as shown in Table 69.
Table 69.
Standard Index Suffixes
Suffix
Value
Unique or
Not Unique
_F#
Foreign key index.
Not unique
_P#
Primary key index.
Unique
_U#
Primary key index of the user.
Unique
_V#
Special routing visibility rule index; usually on primary child
foreign key and system foreign key columns not ordinarily
indexed (for example, primary address, primary contact, creator,
and so on).
Not unique
_M#
Miscellaneous index. Any index that does not fit into one of the
above categories.
Not unique
CAUTION: Consult Siebel Technical Support before modifying or deleting indexes. Modifying or
deleting indexes can negatively affect the performance of Siebel Business Applications and may
render it unusable.
Column Naming Conventions
Suffixes are used to indicate columns that must contain specific values. Table 70 shows the standard
suffixes for column names and their possible values.
Table 70.
Standard Column Suffixes
Suffix
Value
_AMT
This column contains a currency amount.
_CD
The column value is based on the contents of the List of Values (LOV).
_DT
This column contains a date or datetime value.
_FLG
This column contains a Boolean value where Y indicates Yes or True; N indicates No
or False.
_ID
This column contains ROW_ID values.
_NUM
This column contains a number or an identifying alphanumeric value.
_TEXT
This column contains text data.
Siebel Data Model Reference Version 8.0
15 3
Understanding the Physical Model Data Model Type Definitions
Table 70.
Standard Column Suffixes
Suffix
Value
_TM
This column contains a time value.
_TS
This column contains a timestamp value.
Abbreviations Used in the Physical Model Listings
Descriptions that appear in the physical model listings may use the abbreviations shown in Table 71.
Table 71.
Physical Model Listing Abbreviations
Abbreviation or Phrase
Meaning
fk
Foreign key; a column that references a primary key of another table.
pk
Primary key; the unique row identifier of a table.
SEA
Siebel Enterprise Applications.
Siebel System Field
One of the Siebel Enterprise Applications system fields described in
Table 76 on page 158.
Data Model Type Definitions
This topic contains the following type definitions:
Table Type Definitions on page 155
Table Status Definitions on page 156
Column Type Definitions on page 157
Domain Type Definitions on page 157
154
Siebel Data Model Reference Version 8.0
Understanding the Physical Model Data Model Type Definitions
Table Type Definitions
Table 72 provides descriptions of the types of tables in the Siebel database.
Table 72.
Table Types 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.
Siebel Data Model Reference Version 8.0
15 5
Understanding the Physical Model Data Model Type Definitions
Table 72.
Table Types in the Siebel Database
Table Type
Description
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 has
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 may get compiled into the SRF files.
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 by Oracle Business Analytics in the Oracle
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, as shown in Table 73.
Table Status Definitions
Table 73 provides descriptions of the types of table status in the Siebel database.
Table 73.
Table Status Definitions
Table Status
Description
Active
Actively used and supported in Siebel Business Applications.
Inactive
Dropped or removed from Siebel Data Model and no longer supported.
Customers must remove every reference to these tables or columns in their
configurations.
EOL
End of Life. Supported as is in this release but will be dropped in a future release
of Siebel Business Applications. Use alternate active tables or columns.
Not Used
Not currently used by Siebel Business Applications, but may be used by
customers.
156
Siebel Data Model Reference Version 8.0
Understanding the Physical Model Data Model Type Definitions
Column Type Definitions
Table 74 provides descriptions for the types of columns in the Siebel database.
Table 74.
Column Types in the Siebel Database
Column Type
Description
Data (Public)
This is the general type for most columns.
Denormalized
This is the type for a column that holds a value denormalized from another
column. Denormalized columns are only supported in special situations and
cannot be added as part of customization.
Extension
These are columns that belong to an extension table or extension columns in
a base table. Those columns are used to define customized fields in a
business component.
System
This is the type for System Fields, which are described in Table 76 on
page 158.
Domain Type Definitions
Table 75 provides descriptions for the domain types of certain columns in the Siebel database.
Table 75.
Domain Types
Domain
Type
Meaning
Domain Contains
FK
Foreign Key column
The name of the table referenced by this Foreign Key column.
PC
Primary Child
The name of the table in which the Primary Child is found. For
example, an account (S_ORG_EXT) may be associated to
multiple industries (S_INDUST) through the intersection table
S_ORG_INDUST. One of these industries is the primary industry
of the account: column S_ORG_EXT.PR_INDUST_ID points to
the foreign key column INDUST_ID of the primary child table
S_ORG_INDUST (the column S_ORG_INDUST.INDUST_ID is a
foreign key to the base table S_INDUST and so it points to
S_INDUST.ROW_ID).
LOV
List of Values
The intended List of Values type for this column. List of values
types are defined in the table S_LST_OF_VAL accessible
through Siebel Tools: Screens>System Administration>List of
Values.
LOVB
List of Values
Bounded
The List of Values type against which this column is validated.
In the LOVB case, end users must specify a value from the list,
whereas in the LOV case, the user can enter a value not
contained in the list.
Siebel Data Model Reference Version 8.0
15 7
Understanding the Physical Model Columns of Numeric Physical Type
Table 75.
Domain
Type
Domain Types
Meaning
Domain Contains
MLOV
Multilingual List of
Values
The List of Values type against which this column is validated,
in multiple languages. End users must specify a value from the
list, but see the values in their preferred language.
MLS
Multiple Language
Support
The name of the table in which the translation in an alternate
language can be found.
DNRM
Denormalized
The path to the original column, used by the Object Manager to
synchronize the values, in the form of [foreign key
column].[original column]. For example, the ACCNT_NAME
column of table S_ACCNT_POSTN is denormalized; its domain
is [OU_EXT_ID].[NAME]. In other words, the contents of
column NAME of the table referenced by OU_EXT_ID
(S_ORG_EXT) are replicated into column ACCNT_NAME of table
S_ACCNT_POSTN. Denormalization is used to improve query
performance.
(blank)
There is no domain specified for this column.
Columns of Numeric Physical Type
Columns of a numeric physical type must have the properties Precision and Scale set, for example:
Number (22, 7), or Number (10, 0). The first value (22 and 10, in these examples) represents the
precision, which is the total length of the column including the decimal places. The second number
(7 and 0, in these examples) represents the scale, which are the decimal places after the decimal
point. Siebel Tools sets the Length property to 22 by default; Length is a required column in Siebel
Tools, but this property does not play any role in columns of a numeric physical type.
Siebel System Fields
Every Siebel table contains the system fields described in Table 76. Do not alter the contents of these
fields.
Table 76.
Siebel System Fields
Column Name
Description
CONFLICT_ID
Unique value used to resolve Siebel remote routing conflicts if
necessary; otherwise, value is zero.
CREATED
Date the record was entered.
CREATED_BY
User who entered the record (foreign key to S_USER).
DCKING_NUM
No longer used.
158
Siebel Data Model Reference Version 8.0
Understanding the Physical Model INTEGRATION_ID Columns
Table 76.
Siebel System Fields
Column Name
Description
LAST_UPD
Date and time the record was last changed.
LAST_UPD_BY
User who last changed record (foreign key to S_USER).
MODIFICATION_NUM
Internally incremented number used for locking and to identify
records for incremental updates of the Siebel Business Data
Warehouse.
ROW_ID
Unique row identifier.
INTEGRATION_ID Columns
Many tables contain a column called INTEGRATION_ID for back office integration. Normally,
customers use this column to store the unique reference identifiers for corresponding records in the
back office application. These columns are currently used by the Siebel Connector for Oracle
Applications and the Siebel SAP R/3 Connector.
The S_ADDR_ORG.INTEGRATION2_ID and INTEGRATION3_ID columns have been created for
integration with Oracle back office applications. The INTEGRATION2_ID column is used to store the
Oracle BILL TO SITE ID, and the INTEGRATION3_ID column is used to store the Oracle SHIP TO SITE
ID.
Include Only Field
Include Only is an index column field, and is either blank or checked. It applies only to DB2. When
checked, it adds the column into the leaf pages of the unique index. This avoids access to table pages
when the column is the only other piece of data retrieved from the table other than the indexed
columns. Included columns do not contribute to the unique constraint.
Siebel Repository
Siebel Business Applications includes a set of tables referred to as the Siebel repository tables. These
tables store the full definition of a given configuration of Siebel Business Applications, including the
database schema and the client configuration. As with other Siebel tables, do not manipulate
information in the Siebel repository tables directly. Instead, use Siebel Tools. For more information
on how to use Siebel Tools, see Using Siebel Tools. To learn more about the information stored in
the repository, see Siebel Object Types Reference.
Siebel Data Model Reference Version 8.0
15 9
Understanding the Physical Model Database Schema Version
Database Schema Version
Each Siebel Business Applications database installation is stamped with a database schema version.
You can learn the schema version of a Siebel installation by choosing Help > Technical Support from
your Siebel client. The schema version is listed in the format 41.XX.YY.ZZ, where XX, YY, and ZZ are
one or two digit integers.
Limit Checking for Data Types
The Object Manager imposes limit checking on data of specific types to make sure that every input,
regardless of its source, is within specified limits (shown in Table 77). Sources of inputs include the
Siebel application, EIM, and connectors. For example, if you do a bulk import using EIM, you must
make sure the dates are within the specified range, otherwise the Object Manager returns an SQL
error for each out-of-range date.
Table 77.
Input Limits on Data Types
Data Type
Limit Checking
Dates
Dates must be in the range of January 1, 1753 to December 31, 4712.
Long
Maximum size of 16K
Text
Maximum size of 16K
CLOB
Maximum size of 128K
Validating the Siebel Schema
To make sure that there are no inconsistencies between the Siebel Database Server and the physical
database schema, use the Siebel Server utility dbchck.exe (Windows) or dbchck (UNIX). You can use
the dbchck utility to validate data relationships, including foreign keys and the list of values. You can
also use the DICTUTL utility to verify that all doc objects and rule definitions are correct. For more
information about how to use these utilities, see Siebel Enterprise Integration Manager
Administration Guide.
160
Siebel Data Model Reference Version 8.0
Understanding the Physical Model Party Model Unifies Access to Data
Party Model Unifies Access to Data
The party model is a means of unifying all access to data about relationships. This covers
relationships between your company and people (contacts, employees, partner employees, users)
and other businesses (accounts, divisions, organizations, partners). The base table for all such
access is S_PARTY. Related tables are implicitly joined as extension tables. Table 78 lists the
extension tables and their corresponding EIM interface tables.
Table 78.
S_PARTY Extension Tables and Corresponding EIM Interface Tables
Data Type
Extension Table to S_PARTY
EIM Interface Table
Accounts
S_ORG_EXT
EIM_ACCOUNT
Business Units
S_BU
EIM_BU
Contacts
S_CONTACT
EIM_CONTACT
Employees
S_CONTACT
EIM_EMPLOYEE
Groups
S_ORG_GROUP
EIM_GROUP
Organizations
S_ORG_BU
EIM_ORG_BU
Parties
N/A
EIM_PARTY
Positions
S_POSTN
EIM_POSITION
Users
S_USER
EIM_USER
Because the extension tables are implicitly joined to S_PARTY, you do not need to configure anything
to access them through S_PARTY. Some data types have a many-to-many relationship. For example,
any contact can be associated with multiple accounts or partners. To model these relationships there
are preconfigured intersection tables: S_PARTY_PER and S_PARTY_REL. Use S_PARTY_REL to
implement relationships between parties in the S_PARTY table. In this case, records in S_PARTY are
both parent (PARTY_ID) and child (PERSON_ID).
Use S_PARTY_PER to implement relationships between members:
Access groups and members
Accounts and contacts
Employees and positions
User lists and users
Siebel Data Model Reference Version 8.0
16 1
Understanding the Physical Model Party Model Unifies Access to Data
162
Siebel Data Model Reference Version 8.0
Schema Changes
This chapter includes the following topics:
Table Changes in This Version on page 163
Table Column Changes in This Version on page 169
Table Index Changes in This Version on page 183
Table Changes in This Version
This topic lists the following changes to tables that have been implemented in this version of the
schema:
Tables That Are New in this Version on page 163
Tables That Changed in this Version on page 169
Tables That Are New in this Version
Table 79 lists tables that are new in this version.
Table 79.
New Tables in This Version
Table
Type
Active
S_AGREE_BNFT
Data (Public)
Yes
S_AGREE_COND
Data (Public)
Yes
S_AGR_COND_CMPL
Data (Public)
Yes
S_ALGN_IND_TMP
Data (Private)
Yes
S_ALGN_POSTN
Data (Intersection)
Yes
S_ALGN_POS_OPTY
Data (Intersection)
Yes
S_ALGN_PROD_TMP
Data (Private)
Yes
S_ALGN_QTA_ACCT
Data (Intersection)
Yes
S_ALGN_QTA_AFFL
Data (Intersection)
Yes
S_ALGN_QTA_CON
Data (Intersection)
Yes
S_ALGN_QTA_REGN
Data (Intersection)
Yes
S_ALGN_QTA_TERR
Data (Intersection)
Yes
Siebel Data Model Reference Version 8.0
16 3
Schema Changes Table Changes in This Version
Table 79.
New Tables in This Version
Table
Type
Active
S_ALGN_QTA_ZIP
Data (Intersection)
Yes
S_ALGN_QT_BRKDN
Data (Intersection)
Yes
S_ALGN_TERR_POS
Data (Intersection)
Yes
S_APP_VER_ATT
Data (Private)
Yes
S_AUDIT_JOIN
Data (Private)
Yes
S_AUDIT_LINK
Data (Private)
Yes
S_AUDIT_READ
Data (Private)
Yes
S_AUDIT_VERSION
Data (Private)
Yes
S_BDGTREQ_ORDER
Data (Intersection)
Yes
S_BR_CONCEPT
Data (Private)
Yes
S_BR_GBL_BINARY
Data (Private)
Yes
S_BR_GBL_PARM
Data (Private)
Yes
S_BR_KNWLDGBASE
Data (Private)
Yes
S_BR_MDL_BC_FLD
Data (Private)
Yes
S_BR_MDL_BC_REL
Data (Private)
Yes
S_BR_MODULE
Data (Private)
Yes
S_BR_MODULE_BIN
Data (Private)
Yes
S_BR_MOD_BC_REL
Data (Private)
Yes
S_DCP_CALL_LST
Data (Intersection)
Yes
S_DOCK_DL_MGR
Data (Private)
Yes
S_DOCK_TXN_SKIP
Data (Private)
Yes
S_DQ_BC_FLD_MAP
Data (Private)
Yes
S_DQ_BUSCOMP
Data (Private)
Yes
S_DQ_CON_KEY
Data (Public)
Yes
S_DQ_ORG_KEY
Data (Public)
Yes
S_DQ_PRSP_KEY
Data (Public)
Yes
S_DQ_RULE
Data (Private)
Yes
S_DQ_RULE_PARAM
Data (Public)
Yes
S_DQ_SYST
Data (Private)
Yes
S_DQ_SYST_PARM
Data (Private)
Yes
S_EMT_DPLYPKG
Data (Public)
Yes
164
Siebel Data Model Reference Version 8.0
Schema Changes Table Changes in This Version
Table 79.
New Tables in This Version
Table
Type
Active
S_EMT_DPLYUNIT
Data (Public)
Yes
S_ENTL_BNFTTMPL
Data (Public)
Yes
S_ENTL_CONDTMPL
Data (Public)
Yes
S_ENT_SOLN
Data (Public)
Yes
S_FCSTSER_AGFLD
Data (Public)
Yes
S_FR_BID_LITM
Data (Public)
Yes
S_FUL_REQ_BID
Data (Intersection)
Yes
S_INST_UPG_HIST
Data (Private)
Yes
S_MKTGOFFR_BU
Data (Intersection)
Yes
S_MKTGOFFR_PROD
Data (Intersection)
Yes
S_MKTG_DOC_INVT
Data (Intersection)
Yes
S_MKTG_OFFR
Data (Public)
Yes
S_NODE_PREF
Data (Private)
Yes
S_NOTE_FUL_REQ
Data (Public)
Yes
S_NOTE_MDF
Data (Public)
Yes
S_OFFR_CBAST
Data (Intersection)
Yes
S_PROD_ACCNT
Data (Public)
Yes
S_PROD_CON
Data (Intersection)
Yes
S_PROJ_CBAST
Data (Intersection)
Yes
S_PRTFL_ACCNT
Data (Intersection)
Yes
S_PRTFL_ACCSOLN
Data (Intersection)
Yes
S_PRTFL_ACC_ATT
Data (Public)
Yes
S_PRTFL_ATT
Data (Public)
Yes
S_PRTFL_BU_DRVR
Data (Public)
Yes
S_PRTFL_BU_INTV
Data (Public)
Yes
S_PRTFL_CAMP
Data (Intersection)
Yes
S_PRTFL_CMPTR
Data (Intersection)
Yes
S_PRTFL_CTGRY
Data (Public)
Yes
S_PRTFL_ENTSOLN
Data (Intersection)
Yes
S_PRTFL_POSTN
Data (Intersection)
Yes
S_PRTFL_PRTNR
Data (Intersection)
Yes
Siebel Data Model Reference Version 8.0
16 5
Schema Changes Table Changes in This Version
Table 79.
New Tables in This Version
Table
Type
Active
S_PRTFL_SUBACC
Data (Intersection)
Yes
S_QTA_ACC_PD
Data (Intersection)
Yes
S_QTA_CON_PD
Data (Intersection)
Yes
S_QTA_PARTYAFFL
Data (Public)
Yes
S_QTA_PD_BRKDN
Data (Intersection)
Yes
S_QTA_REGN_PD
Data (Intersection)
Yes
S_QTA_ZIP_PD
Data (Intersection)
Yes
S_QUOTA_ACCNT
Data (Intersection)
Yes
S_QUOTA_CON
Data (Intersection)
Yes
S_QUOTA_REGN
Data (Intersection)
Yes
S_QUOTA_ZIP
Data (Intersection)
Yes
S_RTS_BIG_ATT
Data (Public)
Yes
S_RTS_CFG
Data (Public)
Yes
S_RTS_LOG
Data (Public)
Yes
S_RTS_MSG_HSTRY
Data (Public)
Yes
S_RTS_STATE
Data (Public)
Yes
S_RTS_SUBSCRN
Data (Public)
Yes
S_RTS_TIMEOUT
Data (Public)
Yes
S_RTS_TMOUT_VAL
Data (Public)
Yes
S_RTS_WQ
Data (Public)
Yes
S_RTS_WQ_USER
Data (Public)
Yes
S_SD_ATTENDEE
Data (Private)
Yes
S_SLS_PORTFOLIO
Data (Public)
Yes
S_SLS_QUOTA
Data (Public)
Yes
S_SRCH_CHG_TXN
Data (Private)
Yes
S_SRCH_CTGRY
Data (Private)
Yes
S_SRCH_CTG_FLD
Data (Private)
Yes
S_SRCH_CTG_REL
Data (Private)
Yes
S_SRCH_OPERATOR
Data (Private)
Yes
S_SRCH_SAVED
Data (Private)
Yes
S_SRCH_USR_PREF
Data (Private)
Yes
166
Siebel Data Model Reference Version 8.0
Schema Changes Table Changes in This Version
Table 79.
New Tables in This Version
Table
Type
Active
S_SRC_BDGT_REQ
Data (Intersection)
Yes
S_SRC_CBAST
Data (Intersection)
Yes
S_SRC_OFFR
Data (Intersection)
Yes
S_SRC_ORDER
Data (Intersection)
Yes
S_SRM_TASK_HIST
Data (Public)
Yes
S_TASK_DEFN_REL
Data (Public)
Yes
S_TEAMSPACEARCH
Data (Public)
Yes
S_TERRALGN_BU
Data (Intersection)
Yes
S_TERRALGN_IND
Data (Intersection)
Yes
S_TERRALGN_PROD
Data (Intersection)
Yes
S_TERRALGN_QTA
Data (Intersection)
Yes
S_TERRITORY_BU
Data (Intersection)
Yes
S_TERR_IND
Data (Intersection)
Yes
S_TERR_PROD
Data (Intersection)
Yes
S_TERR_QTA_ACCT
Data (Intersection)
Yes
S_TERR_QTA_AFFL
Data (Intersection)
Yes
S_TERR_QTA_CON
Data (Intersection)
Yes
S_TERR_QTA_REGN
Data (Intersection)
Yes
S_TERR_QTA_ZIP
Data (Intersection)
Yes
S_TERR_QUOTA
Data (Intersection)
Yes
S_TQ_AFFL_CRDT
Data (Intersection)
Yes
S_TRQT_ACCT_PD
Data (Intersection)
Yes
S_TRQT_ACC_CRDT
Data (Intersection)
Yes
S_TRQT_AFFL_PD
Data (Intersection)
Yes
S_TRQT_CON_CRDT
Data (Intersection)
Yes
S_TRQT_CON_PD
Data (Intersection)
Yes
S_TRQT_PD_BRKDN
Data (Intersection)
Yes
S_TRQT_REGNCRDT
Data (Intersection)
Yes
S_TRQT_REGN_PD
Data (Intersection)
Yes
S_TRQT_ZIP_CRDT
Data (Intersection)
Yes
S_TRQT_ZIP_PD
Data (Intersection)
Yes
Siebel Data Model Reference Version 8.0
16 7
Schema Changes Table Changes in This Version
Table 79.
New Tables in This Version
Table
Type
Active
S_TU_INST
Data (Public)
Yes
S_TU_LOG
Data (Private)
Yes
S_TU_LOG_MAP
Data (Private)
Yes
S_TU_LOG_X_01
Extension
Yes
S_TU_LOG_X_02
Extension
Yes
S_TU_LOG_X_03
Extension
Yes
S_TU_LOG_X_04
Extension
Yes
S_TU_LOG_X_05
Extension
Yes
S_TU_LOG_X_06
Extension
Yes
S_TU_LOG_X_07
Extension
Yes
S_TU_LOG_X_08
Extension
Yes
S_TU_LOG_X_09
Extension
Yes
S_TU_LOG_X_10
Extension
Yes
S_UIC_APLT_GRP
Data (Public)
Yes
S_UIC_APLT_LANG
Data (Public)
Yes
S_UIC_APPLET
Data (Public)
Yes
S_UIC_ATAB_GRP
Data (Public)
Yes
S_UIC_ATAB_ITEM
Data (Public)
Yes
S_UIC_VIEW
Data (Public)
Yes
S_UIF_WEB_FILE
Data (Private)
Yes
S_USR_PREF_UOM
Data (Public)
Yes
S_WEBCHNL_SES
Data (Public)
Yes
S_WEBCHNL_SNSVC
Data (Public)
Yes
S_WEBCHNL_USR
Data (Public)
Yes
S_WFA_ANLY_INFO
Data (Public)
Yes
S_WFA_ANLY_PROP
Data (Public)
Yes
S_WFA_ANLY_TS
Data (Public)
Yes
S_WFA_INST_PRM
Data (Public)
Yes
S_WFA_INTL
Data (Private)
Yes
168
Siebel Data Model Reference Version 8.0
Schema Changes Table Column Changes in This Version
Tables That Changed in this Version
Table 80 lists tables whose type has changed in this version.
Table 80.
Tables with Changed Type
Table
Previous Type
New Type
S_AUDIT_CHILDBC
Data (Public)
Data (Private)
T_MASTER_DTL2_X
Extension (Siebel)
Extension
Table Column Changes in This Version
This topic lists the following changes to columns that have been implemented in this version of the
schema:
Table Columns That Are New in This Version on page 169
System Columns That Are New in This Version on page 182
Table Columns That Changed in This Version on page 182
Table Columns That Are New in This Version
Table 81 lists table columns that are new in this version. Some column headings are abbreviated as
follows.
Optional = Opt
Length = Len
Precision = Prec
LOV Bound = LOV Bnd
Siebel Data Model Reference Version 8.0
16 9
New Table Columns in This Version
Siebel Data Model Reference Version 8.0
Table Name
Column
Opt
Data
Type
S_AC_RSRC_RESP
PERM_FLAG_VAL
Number
22
S_ADDR_ORG
ALIGNMENT_FLG
Char
S_ADDR_PER
ALIGNMENT_FLG
Char
S_ADJ_GROUP
INTEGRATION_ID
Varchar
30
S_ALGN_ACCT_TMP
AFFL_OBJECT_CD
Varchar
30
S_ALGN_CON_TMP
AFFL_OBJECT_CD
Varchar
30
S_ALGN_REGN_TMP
AFFL_OBJECT_CD
Varchar
30
S_ALGN_REGN_TMP
ASGN_OBJECT_CD
Varchar
30
S_ALGN_ZIP_TMP
AFFL_OBJECT_CD
Varchar
30
S_ALGN_ZIP_TMP
ASGN_OBJECT_CD
Varchar
30
S_ALGN_ZIP_TMP
GEO_TYPE_CD
Varchar
30
S_APP_QUERY
OWNER_ID
Varchar
15
S_APP_VER
AUDIT_ADMIN_VER
Varchar
30
S_AUDIT_BUSCOMP
BASE_TBL_NAME
Varchar
30
S_AUDIT_BUSCOMP
DESC_TEXT
Varchar
250
S_AUDIT_BUSCOMP
EXPORT_FLG
Char
S_AUDIT_BUSCOMP
SYS_AUDIT_FLG
Char
S_AUDIT_FIELD
COL_NAME
Varchar
30
S_AUDIT_FIELD
JOIN_NAME
Varchar
75
S_AUDIT_FIELD
READ_FLG
Char
S_AUDIT_FIELD
READ_FV_FLG
Char
S_AUDIT_FIELD
SPECIAL_JOINED_FLG
Char
S_AUDIT_FIELD
TBL_NAME
Varchar
30
S_AUDIT_ITEM
AUDIT_LOG
CLOB
137625
6
S_AUDIT_ITEM
AUDIT_SOURCE_CD
Varchar
50
Len
Prec
10
Scale
Default
LOV Type
LOV
Bnd
Schema Changes Table Column Changes in This Version
1 70
Table 81.
Table 81.
New Table Columns in This Version
171
Column
Opt
Data
Type
S_AUDIT_ITEM
BC_BASE_TBL
Varchar
30
S_AUDIT_ITEM
CHILD_BC_BASE_TBL
Varchar
30
S_AUDIT_ITEM
CHILD_RECORD_ID
Varchar
15
S_AUDIT_ITEM
GROUP_NUM
Varchar
15
S_AUDIT_ITEM
ITEM_IDEN_NUM
Number
22
S_AUDIT_ITEM
LINK_NAME
Varchar
175
S_AUDIT_ITEM
NODE_NAME
Varchar
50
S_AUDIT_ITEM
SRC_DEST_ID
Varchar
15
S_AUDIT_ITEM
SYNC_DT
UTC
DateTime
S_AUDIT_ITEM
TBL_NAME
Varchar
30
S_AUDIT_ITEM
TBL_RECORD_ID
Varchar
15
S_CAMP_CALL_LST
FLOWCHART_CNCTR
Varchar
1999
S_CAMP_CON
DCP_ID
Varchar
15
S_CB_ASSET
MKTG_ASSET_FLG
Char
S_CM_CNCTR
SRCH_ENGINE_ID
Varchar
15
S_COMMUNICATION
DCP_ID
Varchar
15
S_CONTACT
PRESENCE_URI
Varchar
100
S_CON_ADDR
ALIGNMENT_FLG
Char
S_CON_SYNC_SCHD
CALL_LST_ID
Varchar
15
S_CS_PATH
DEPLOY_READY_FLG
Char
S_DMND_CRTN_PRG
DPLY_INSTRT_TEXT
Varchar
250
S_DMND_CRTN_PRG
LAST_SYNC_DT
UTC
DateTime
S_DMND_CRTN_PRG
MKTG_OFFR_ID
Varchar
15
S_DMND_CRTN_PRG
NEED_TO_SYNC_FLG
Char
S_DMND_CRTN_PRG
OFFR_GROUP_CD
Varchar
30
Len
Prec
15
Scale
Default
LOV Type
LOV
Bnd
RTD_OFFER_GROUP
Yes
Schema Changes Table Column Changes in This Version
Siebel Data Model Reference Version 8.0
Table Name
New Table Columns in This Version
Siebel Data Model Reference Version 8.0
Table Name
Column
Opt
Data
Type
S_DMND_CRTN_PRG
PR_CAMPAIGN_ID
Varchar
15
S_DMND_CRTN_PRG
RTD_STATUS_CD
Varchar
30
S_DMND_CRTN_PRG
VERSION_NUM
Number
22
S_DOCK_TXN_LOG
LOG_DATA_CLOB
CLOB
131072
0
S_DOCK_TXN_LOG
LOG_DATA_CLOB_LEN
Number
22
S_DYN_HRCHY
HIER_LAST_UPD
UTC
DateTime
S_EMT_DSET_ITEM
DEPLOY_MODE_CD
Varchar
30
S_EMT_DSET_ITEM
PDQ_ID
Varchar
15
S_EMT_OBJECT
EXPORT_BS_NAME
Varchar
75
S_EMT_OBJECT
EXPORT_MTHD_NAME
Varchar
75
S_EMT_OBJECT
IMPORT_BS_NAME
Varchar
75
S_EMT_OBJECT
IMPORT_MTHD_NAME
Varchar
75
S_EMT_OBJECT
PRVW_SP_BS_NAME
Varchar
75
S_EMT_OBJECT
PRVW_SP_MTHD_NAME
Varchar
75
S_EMT_OBJECT
XPT_VLD_BS_NAME
Varchar
75
S_EMT_OBJECT
XPT_VLD_MTHD_NAME
Varchar
75
S_EMT_SESSN_ITM
DEPLOY_MODE_CD
Varchar
30
S_EMT_SESSN_ITM
PDQ_ID
Varchar
15
S_ENTL_PRDPRI
AGREE_BNFT_ID
Varchar
15
S_ENTL_PRDPRI
CTLG_CAT_ID
Varchar
15
S_ENTL_PRDPRI
XA_CLASS_ID
Varchar
15
S_ENTMPL_PRDPRI
BNFT_TMPL_ID
Varchar
15
S_ENTMPL_PRDPRI
CTLG_CAT_ID
Varchar
15
S_ENTMPL_PRDPRI
XA_CLASS_ID
Varchar
15
S_EVT_FUL_REQ
COMMENTS
Varchar
30
Len
Prec
Scale
10
10
LOV Type
LOV
Bnd
RTD_OFFER_STATUS
Yes
Upsert
EMT_OPERATION
Yes
Upsert
EMT_OPERATION
Yes
Default
Schema Changes Table Column Changes in This Version
1 72
Table 81.
Table 81.
New Table Columns in This Version
173
Column
Opt
Data
Type
S_EVT_FUL_REQ
EVTLOC_ID
Varchar
15
S_EVT_FUL_REQ
MKTG_ASSET_STAT_CD
Varchar
30
S_EVT_MKTG
CALL_REASON_CD
Varchar
30
S_EVT_MKTG
EVT_FUL_REQ_ID
Varchar
15
S_EVT_MKTG
PORTFOLIO_ID
Varchar
15
S_EVT_MKTG
PRTFL_ACCNT_ID
Varchar
15
S_EVT_MKTG
PRTFL_CTGRY_ID
Varchar
15
S_EVT_MKTG
STRTGY_CMPNT_CD
Varchar
30
S_FCST
MGR_UPD_FLG
Char
S_FCSTSER
QTY_AGFLD_ID
Varchar
15
S_FCSTSER_POSTN
AGGR_LVL_NUM
Number
22
S_FCSTSER_POSTN
FCSTSER_AGFLD_ID
Varchar
15
S_FCST_ITEM_DTL
ADJ_AMT
Number
22
S_FCST_ITEM_DTL
AGGR_DIM_NAME_1
Varchar
50
S_FCST_ITEM_DTL
AGGR_DIM_NAME_2
Varchar
50
S_FCST_ITEM_DTL
AGGR_DIM_NAME_3
Varchar
50
S_FCST_ITEM_DTL
AGGR_DIM_NAME_4
Varchar
50
S_FCST_ITEM_DTL
AGGR_DIM_NAME_5
Varchar
50
S_FCST_ITEM_DTL
AGGR_DIM_NAME_6
Varchar
50
S_FCST_ITEM_DTL
AGGR_FIELD_CD
Varchar
30
S_FCST_ITEM_DTL
CONV_QTY
Number
22
S_FCST_ITEM_DTL
CONV_UOM_CD
Varchar
30
S_FCST_ITEM_DTL
EXPECT_AMT
Number
22
S_FCST_ITEM_DTL
PAR_FCST_ITMDTL_ID
Varchar
15
S_FCST_ITEM_DTL
PERIOD_NAME
Varchar
50
S_FCST_ITEM_DTL
SEQ_NUM
Number
22
Len
Prec
Scale
Default
10
22
22
22
10
LOV Type
LOV
Bnd
TODO_TYPE
Yes
PMP_STATEGY_COMP
Yes
Schema Changes Table Column Changes in This Version
Siebel Data Model Reference Version 8.0
Table Name
New Table Columns in This Version
Siebel Data Model Reference Version 8.0
Table Name
Column
Opt
Data
Type
S_FCST_ITEM_DTL
UOM_CONV_FCTR
Number
22
S_FUL_REQ_ITEM
CB_ASSET_ID
Varchar
15
S_FUL_REQ_ITEM
COLOR_SPEC
Varchar
50
S_FUL_REQ_ITEM
NUM_SAMPLES
Number
22
S_FUL_REQ_ITEM
PAPER_TYPE
Varchar
50
S_FUL_REQ_ITEM
RQMNT_DESC_TEXT
Varchar
250
S_HH_SYNC_SESSN
BATCH_SESSION_FLG
Char
S_HH_SYNC_SESSN
DBXTRACT_CMPLT_TS
UTC
DateTime
S_HH_SYNC_SESSN
DBXTRACT_SCHLD_TS
UTC
DateTime
S_HH_SYNC_SESSN
DBXTRACT_STAT_CD
Varchar
30
S_HH_SYNC_SESSN
TXN_PROC_CMPLT_TS
UTC
DateTime
S_HH_SYNC_SESSN
TXN_PROC_STAT_CD
Varchar
30
S_HH_SYNC_SESSN
TXN_RECEIVED_TS
UTC
DateTime
S_HH_SYNC_SUM
BATCH_SESSION_FLG
Char
S_HH_SYNC_SUM
BO_FILTER_STRING_1
Varchar
1999
S_HH_SYNC_SUM
BO_FILTER_STRING_2
Varchar
1999
S_HH_SYNC_SUM
BO_FILTER_STRING_3
Varchar
1999
S_HH_SYNC_SUM
DBXTRACT_CMPLT_TS
UTC
DateTime
S_HH_SYNC_SUM
DBXTRACT_SCHLD_TS
UTC
DateTime
S_HH_SYNC_SUM
DBXTRACT_STAT_CD
Varchar
30
S_HH_SYNC_SUM
TARGET_CLIENT_TYPE
Varchar
30
S_HH_SYNC_SUM
TXN_PROC_CMPLT_TS
UTC
DateTime
S_HH_SYNC_SUM
TXN_PROC_STAT_CD
Varchar
30
Len
Prec
Scale
22
10
Default
LOV Type
LOV
Bnd
BATCHSYNC_EXTRACT_STATUS
Yes
BATCHSYNC_TXN_STATUS
Yes
BATCHSYNC_EXTRACT_STATUS
Yes
BATCHSYNC_TXN_STATUS
Yes
Schema Changes Table Column Changes in This Version
1 74
Table 81.
Table 81.
New Table Columns in This Version
Data
Type
175
Column
Opt
Len
S_HH_SYNC_SUM
TXN_RECEIVED_TS
UTC
DateTime
S_INVOICE
AGREE_BNFT_ID
Varchar
15
S_MDF
APPR_STATUS_CD
Varchar
30
S_MDF
INIT_FUND_AMT
Number
22
S_MDF
OWNER_ID
Varchar
15
S_MDF
REGION_ID
Varchar
15
S_MKTG_BDGT_REQ
MKTG_FUND_ID
Varchar
15
S_NODE
NODE_AUDIT_VER_NUM
Varchar
30
S_NODE
REAL_TM_SYNC_FLG
Char
S_OPTY_POSTN
ASGN_RULE_GRP_ID
Varchar
15
S_OPTY_POSTN
ASGN_TERR_ID
Varchar
15
S_OPTY_SRC
DCP_ID
Varchar
15
S_ORDER
AGREE_BNFT_ID
Varchar
15
S_ORDER
DCP_ID
Varchar
15
S_ORDER
INIT_APRV_AMT
Number
22
S_ORDER
PURCH_ORD_EXP_TS
TimeStamp
S_ORDER
TOTAL_AMT
Number
22
S_PRTNRPRG_APPL
AGREE_ITEM_ID
Varchar
15
S_PRTNRPRG_APPL
AGR_IT_DT_USED_FLG
Char
S_PRTNRPRG_APPL
PRTNRPRG_MBR_ID
Varchar
15
S_PRTNRPRG_MBR
AGREE_ITEM_ID
Varchar
15
S_PRTNRPRG_MBR
MEMBERSHIP_NUM
Varchar
30
S_PRTNR_PROG
PROD_INT_ID
Varchar
15
S_REVN
ENT_SOLN_ID
Varchar
15
S_REVN
EXPECT_AMT
Number
22
S_REVN
REVN_TYPE_CD
Varchar
30
Prec
22
Scale
Default
LOV Type
LOV
Bnd
MKTG_PLAN_APPR_TYPE
Yes
PMP_REVENUE_TYPE
Yes
22
22
22
Schema Changes Table Column Changes in This Version
Siebel Data Model Reference Version 8.0
Table Name
New Table Columns in This Version
Siebel Data Model Reference Version 8.0
Table Name
Column
Opt
Data
Type
S_RT_SVC
STATE_MGMT_TYPE_CD
Varchar
30
S_SD_PIM_ROW
OWNER_APPT_ID
Varchar
15
S_SMQ_ADDR
SECTKN_ENCRPKY_REF
Number
22
S_SMQ_HISTORY
MSG_ID_IDEN
Varchar
50
S_SMQ_HISTORY
SOURCE_OBJ_TYPE
Varchar
100
S_SMQ_HISTORY
SOURCE_OID
Varchar
50
S_SMQ_HISTORY
TYPE_CD
Varchar
30
S_SRC
BDGT_ALLOC_PCT
Number
22
S_SRC
FLOWCHART_CNCTR
Varchar
1999
S_SRC
MEDIA_SUBTYPE_CD
Varchar
30
S_SRC
PR_MKTG_OFFR_ID
Varchar
15
S_SRC
SPONSOR_EMP_ID
Varchar
15
S_SRC_COST
BDGT_REQ_ID
Varchar
15
S_SRC_COST
EVT_FUL_REQ_ID
Varchar
15
S_SRC_COST
PURCH_ORDER_ID
Varchar
15
S_SRC_EVT_REG
AWARE_CHNL_CD
Varchar
30
ATTENDEE_AWARENESS
Yes
S_SRC_EVT_REG
MEAL_PREF_CD
Varchar
30
ATTENDEE_MEAL_PREF
Yes
S_SRC_EVT_REG
NUM_GUESTS
Number
22
S_SRC_PAYMENT
AGREE_BNFT_ID
Varchar
15
S_SRC_REL
FLOWCHART_CNCTR
Varchar
1999
S_SRM_REQUEST
SRVR_FLOW_ID_VAL
Varchar
40
S_SRV_REQ
ENTLMNT_MTRC_ID
Varchar
15
S_SRV_REQ
RECOMMENDATION_CD
Varchar
30
SR_RECOMMENDATION_TYPE
Yes
S_STDENTL_PMTRX
DYN_PMTRX_ID
Varchar
15
S_STDENTL_PMTRX
VOL_DISCNT_ID
Varchar
15
S_STDTRNG_PMTRX
DIST_CHANNEL_CD
Varchar
30
SAP_DISTRIBUTION_CHANNEL
Yes
Len
Prec
10
22
Scale
LOV
Bnd
Default
LOV Type
STATEFUL
REPOSITORY_SVC_STATEMGM
T_CD
Yes
SMQ_MSG_TYPE
Yes
OFFER_MEDIA
10
Schema Changes Table Column Changes in This Version
1 76
Table 81.
Table 81.
New Table Columns in This Version
177
Column
Opt
Data
Type
S_STDTRNG_PMTRX
DIVN_CD
Varchar
30
S_STDTRNG_PMTRX
DYN_PMTRX_ID
Varchar
15
S_STDTRNG_PMTRX
SALES_ORG_CD
Varchar
30
S_STDTRNG_PMTRX
VOL_DISCNT_ID
Varchar
15
S_TASK_DEFN
HELP_URL_TEXT
Varchar
250
S_TASK_DEFN
REL_TU_TASK_NAME
Varchar
100
S_TERRALGN
BU_ID
Varchar
15
S_TERRALGN
COMBINE_ALGN_ID
Varchar
15
S_TERRALGN
EXPIRATION_DT
UTC
DateTime
S_TERRALGN
LOCKED_BY_USER_ID
Varchar
15
S_TERRALGN
LOCKED_DT
UTC
DateTime
S_TERRALGN
LOCKED_FLG
Char
S_TERRALGN
PR_POSTN_ID
Varchar
15
S_TERRALGN
ROLL_UP_AMT
Number
22
S_TERRALGN_ACCT
ACTIVATION_DT
UTC
DateTime
S_TERRALGN_ACCT
AFFL_OBJECT_CD
Varchar
30
S_TERRALGN_ACCT
APPR_PER_ID
Varchar
15
S_TERRALGN_ACCT
APPR_STATUS_CD
Varchar
30
S_TERRALGN_ACCT
EXPIRATION_DT
UTC
DateTime
S_TERRALGN_ACCT
FROM_TERR_ID
Varchar
15
S_TERRALGN_ACCT
REP_ACTION_CD
Varchar
30
S_TERRALGN_ACCT
REQ_PER_ID
Varchar
15
S_TERRALGN_AST
ACTIVATION_DT
UTC
DateTime
S_TERRALGN_AST
APPR_PER_ID
Varchar
15
Len
Prec
Scale
Default
LOV Type
LOV
Bnd
SAP_DIVN_CD
Yes
SAP_SALES_ORG
Yes
TM_AFFL_OBJECT_TYPE
Yes
ALGN_APPR_STATUS_CD
Yes
APPTM_REP_ACTION_TYPE
Yes
0-R9NH
22
Schema Changes Table Column Changes in This Version
Siebel Data Model Reference Version 8.0
Table Name
New Table Columns in This Version
Siebel Data Model Reference Version 8.0
Table Name
Column
Opt
Data
Type
LOV Type
LOV
Bnd
S_TERRALGN_AST
APPR_STATUS_CD
Varchar
30
ALGN_APPR_STATUS_CD
Yes
S_TERRALGN_AST
EXPIRATION_DT
UTC
DateTime
S_TERRALGN_AST
REP_ACTION_CD
Varchar
30
APPTM_REP_ACTION_TYPE
Yes
S_TERRALGN_AST
REQ_PER_ID
Varchar
15
S_TERRALGN_CON
ACTIVATION_DT
UTC
DateTime
S_TERRALGN_CON
AFFL_OBJECT_CD
Varchar
30
TM_AFFL_OBJECT_TYPE
Yes
S_TERRALGN_CON
APPR_PER_ID
Varchar
15
S_TERRALGN_CON
APPR_STATUS_CD
Varchar
30
ALGN_APPR_STATUS_CD
Yes
S_TERRALGN_CON
EXPIRATION_DT
UTC
DateTime
S_TERRALGN_CON
FROM_TERR_ID
Varchar
15
S_TERRALGN_CON
REP_ACTION_CD
Varchar
30
APPTM_REP_ACTION_TYPE
Yes
S_TERRALGN_CON
REQ_PER_ID
Varchar
15
S_TERRALGN_COND
DIVISION_ID
Varchar
15
S_TERRALGN_PSTN
ACTIVATION_DT
UTC
DateTime
S_TERRALGN_PSTN
EXPIRATION_DT
UTC
DateTime
S_TERRALGN_REGN
ACTIVATION_DT
UTC
DateTime
S_TERRALGN_REGN
AFFL_OBJECT_CD
Varchar
30
TM_AFFL_OBJECT_TYPE
Yes
S_TERRALGN_REGN
APPR_PER_ID
Varchar
15
S_TERRALGN_REGN
APPR_STATUS_CD
Varchar
30
ALGN_APPR_STATUS_CD
Yes
S_TERRALGN_REGN
ASGN_OBJECT_CD
Varchar
30
TM_ASSIGN_OBJECT_TYPE
Yes
S_TERRALGN_REGN
EXPIRATION_DT
UTC
DateTime
S_TERRALGN_REGN
FROM_TERR_ID
Varchar
15
S_TERRALGN_REGN
REP_ACTION_CD
Varchar
30
APPTM_REP_ACTION_TYPE
Yes
Len
Prec
Scale
Default
Schema Changes Table Column Changes in This Version
1 78
Table 81.
Table 81.
New Table Columns in This Version
Column
Opt
Data
Type
Siebel Data Model Reference Version 8.0
179
LOV Type
LOV
Bnd
S_TERRALGN_REGN
REQ_PER_ID
Varchar
15
S_TERRALGN_ZIP
ACTIVATION_DT
UTC
DateTime
S_TERRALGN_ZIP
AFFL_OBJECT_CD
Varchar
30
TM_AFFL_OBJECT_TYPE
Yes
S_TERRALGN_ZIP
APPR_PER_ID
Varchar
15
S_TERRALGN_ZIP
APPR_STATUS_CD
Varchar
30
ALGN_APPR_STATUS_CD
Yes
S_TERRALGN_ZIP
ASGN_OBJECT_CD
Varchar
30
TM_ASSIGN_OBJECT_TYPE
Yes
S_TERRALGN_ZIP
EXPIRATION_DT
UTC
DateTime
S_TERRALGN_ZIP
FROM_TERR_ID
Varchar
15
S_TERRALGN_ZIP
GEO_TYPE_CD
Varchar
30
TM_GEO_TYPE
Yes
S_TERRALGN_ZIP
REP_ACTION_CD
Varchar
30
APPTM_REP_ACTION_TYPE
Yes
S_TERRALGN_ZIP
REQ_PER_ID
Varchar
15
S_TERRITORY
BU_ID
Varchar
15
S_TERRITORY
ROLL_UP_AMT
Number
22
S_TERR_ACCNT
AFFL_OBJECT_CD
Varchar
30
TM_AFFL_OBJECT_TYPE
Yes
S_TERR_ACCNT
CREATED_BY_ALGN_ID
Varchar
15
S_TERR_ACCNT
EXPIRED_BY_ALGN_ID
Varchar
15
S_TERR_ACCNT
FROM_TERR_ID
Varchar
15
S_TERR_ASSET
CREATED_BY_ALGN_ID
Varchar
15
S_TERR_ASSET
EXPIRED_BY_ALGN_ID
Varchar
15
S_TERR_CON
AFFL_OBJECT_CD
Varchar
30
TM_AFFL_OBJECT_TYPE
Yes
S_TERR_CON
CREATED_BY_ALGN_ID
Varchar
15
S_TERR_CON
EXPIRED_BY_ALGN_ID
Varchar
15
S_TERR_CON
FROM_TERR_ID
Varchar
15
S_TERR_HIER
ORIG_HIER_ID
Varchar
15
S_TERR_POSITION
CREATED_BY_ALGN_ID
Varchar
15
Len
Prec
Scale
Default
0-R9NH
22
Schema Changes Table Column Changes in This Version
Table Name
New Table Columns in This Version
Siebel Data Model Reference Version 8.0
Table Name
Column
Opt
Data
Type
LOV Type
LOV
Bnd
S_TERR_POSITION
EXPIRED_BY_ALGN_ID
Varchar
15
S_TERR_REGION
AFFL_OBJECT_CD
Varchar
30
TM_AFFL_OBJECT_TYPE
Yes
S_TERR_REGION
ASGN_OBJECT_CD
Varchar
30
TM_ASSIGN_OBJECT_TYPE
Yes
S_TERR_REGION
CREATED_BY_ALGN_ID
Varchar
15
S_TERR_REGION
EXPIRED_BY_ALGN_ID
Varchar
15
S_TERR_REGION
FROM_TERR_ID
Varchar
15
S_TERR_ZIP
AFFL_OBJECT_CD
Varchar
30
TM_AFFL_OBJECT_TYPE
Yes
S_TERR_ZIP
ASGN_OBJECT_CD
Varchar
30
TM_ASSIGN_OBJECT_TYPE
Yes
S_TERR_ZIP
CREATED_BY_ALGN_ID
Varchar
15
S_TERR_ZIP
EXPIRED_BY_ALGN_ID
Varchar
15
S_TERR_ZIP
FROM_TERR_ID
Varchar
15
S_TERR_ZIP
GEO_TYPE_CD
Varchar
30
TM_GEO_TYPE
Yes
S_UNVBX_ITEM
CONTEXT
Varchar
250
S_UNVBX_ITMTASK
REMOTE_EXEC_CD
Varchar
200
S_UNVBX_ITMTASK
TERR_ID
Varchar
15
S_UNVBX_ITMTYPE
TRNSFR_APPLET_NAME
Varchar
75
S_UOM_CONV_FCTR
CONV_TYPE_CD
Varchar
30
S_WFA_DATA
STRING_DATA_VAL
Varchar
1999
S_WFA_DPLOY_DEF
ANALY_LVL_CD
Varchar
30
NONE
WF_ANLY_LVL_CD
Yes
S_WFA_DPLOY_DEF
DEL_EVT_HANDLE_FLG
Char
S_WFA_DPLOY_DEF
DESCRIPTION
Varchar
250
S_WFA_DPLOY_DEF
DISPNAME_OVERRIDE
Varchar
250
S_WFA_DPLOY_DEF
DISPNAME_REF
Varchar
75
S_WFA_DPLOY_DEF
REPOSITORY_VERSION
Number
22
S_WFA_DPLOY_DEF
SUB_TASK_FLG
Char
S_WFA_DPLOY_DEF
TYPE_CD
Varchar
30
PROCESS
WF_TYPE_CD
Yes
Len
Prec
10
Scale
Default
Schema Changes Table Column Changes in This Version
1 80
Table 81.
Table 81.
New Table Columns in This Version
Column
Opt
Data
Type
S_WFA_INSTANCE
ANALY_DEF_FLG
Char
S_WFA_INSTANCE
ANALY_LVL_CD
Varchar
30
NONE
S_WFA_INSTANCE
DISPNAME_OVERRIDE
Varchar
100
S_WFA_INSTANCE
INTERNAL_STAT_VAL
Number
22
S_WFA_INSTANCE
LAST_SVPT_VAL
Varchar
15
S_WFA_INSTANCE
ROOT_DEF_ID_VAL
Varchar
15
S_WFA_INST_PROP
LONG_VAL
Text
S_WS_PORT
ATT_PROTOCOL_CD
Varchar
30
T_DETAIL
ENCRPTD_COL
Varchar
50
T_DETAIL
ENCRPTD_HASH_VAL
Varchar
30
T_DETAIL
ENCRPTN_KEY_INDEX
Varchar
10
T_DETAIL
NAME_CI
Varchar
75
T_MASTER_POSTN
MASTER_NAME_CI
Varchar
75
T_MASTER_X
ATTRIB_08
CLOB
131072
V_SA_SBLSRVR
GROUP_NAME
Varchar
45
Len
Prec
10
Scale
Default
LOV Type
LOV
Bnd
WF_ANLY_LVL_CD
Yes
WS_ATT_PROTOCOL_CD
Yes
181
Schema Changes Table Column Changes in This Version
Siebel Data Model Reference Version 8.0
Table Name
Schema Changes Table Column Changes in This Version
System Columns That Are New in This Version
Two new system columns, shown in Table 82, have been added to almost all of the Siebel tables.
These columns may not be present in some tables that are used by Siebel server applications as
temporary tables or log tables. These columns are maintained by the ObjectManager and Oracles
Siebel server applications.
Table 82.
New System Columns in This Version
Column Name
Description
Data Type
DB_LAST_UPD
Last Updated - This Database
UTC Datetime
DB_LAST_UPD_SRC
Source of Last Update - This Database
varchar (50)
Table Columns That Changed in This Version
Table 83 lists table columns that have changed in this version.
Table 83.
Table Columns That Have Changed in This Version
Table
Column
Type of
Change
Previous
Value
New Value
S_AUDIT_ITEM
FIELD_NAME
Optional
No
Yes
S_CON_PRDINT_M
CON_CD
LOV Type
CONTACT_
TYPE
None
S_DISCNT
DISCNT_CD
LOV Type
DISCOUNT
_TYPE
None
S_EMT_DSET_ITEM
POST_PROC_WF_NAME
Optional
No
Yes
S_ESCL_REQ
REQ_ID
Prec
15
S_LST_OF_VAL
ACTIVE_FLG
Optional
Yes
No
S_LST_OF_VAL
MULTI_LINGUAL_FLG
Optional
Yes
No
S_MDF_TXN
TYPE_CD
LOV Bnd
Yes
No
S_MERGE_LOG_ATTR
NEW_STD_VALUE
Length
128
500
S_MERGE_LOG_ATTR
OLD_CUST_VALUE
Length
128
500
S_MERGE_LOG_ATTR
OLD_STD_VALUE
Length
128
500
S_ORDER
CCNUM_ENCRPKEY_REF
Length
30
150
S_PRI_LST_ITEM
PRI_CD
LOV Type
Price Type
None
S_PTY_PAY_PRFL
CCNUM_ENCRPKEY_REF
Length
30
150
S_PTY_PAY_PRFL
CCVNUM_ENCRPKY_REF
Length
30
60
S_SMQ_ADDR
SECURITY_TOKEN
Length
100
210
182
Siebel Data Model Reference Version 8.0
Schema Changes Table Index Changes in This Version
Table 83.
Table Columns That Have Changed in This Version
Table
Column
Type of
Change
Previous
Value
S_SRC
LOAD_BEHAVIOR_CD
LOV Type
None
CAMPAIGN_LOAD_
BEHAVIOR
S_SRC_PAYMENT
CCNUM_ENCRPKEY_REF
Length
30
150
S_SSO_SYS_USER
PWD_ENCRPKEY_REF
Length
30
150
S_TERRASGN_INFO
ASGN_OBJECT_CD
LOV Type
None
TM_ASSIGN_OBJECT_
TYPE
S_TERRASGN_INFO
SEARCH_SPEC
Length
250
1999
S_TERRITORY
TERR_HIER_ID
Optional
No
Yes
S_VOD
LOCKED_BY
Length
15
50
New Value
Table Index Changes in This Version
This topic lists the following changes to table indexes that have been implemented in this version of
the schema:
Table Indexes That Are New in This Version on page 183
Table Indexes That Changed in This Version on page 185
Table Indexes That Are Deprecated in This Version on page 188
Table Indexes That Are New in This Version
Table 84 lists table indexes that are new in this version.
Table 84.
Table Indexes That Are New in This Version
Table Name
Index
Columns
S_AUDIT_ITEM
S_AUDIT_ITEM_M4
(OPERATION_DT)
S_BRDCST_MSG
S_BRDCST_MSG_M5
(UNIVERSAL_MSG_FLG)
S_CAMP_CON
S_CAMP_CON_F19
(DCP_ID)
S_CM_CNCTR
S_CM_CNCTR_F1
(SRCH_ENGINE_ID)
S_COMMUNICATION
S_COMMUNICATN_F18
(DCP_ID)
S_CON_SYNC_SCHD
S_CON_SYNC_SCHD_F3
(CALL_LST_ID)
S_DMND_CRTN_PRG
S_DMND_CRTNPRG_F17
(MKTG_OFFR_ID)
S_EMT_DSET_ITEM
S_EMT_DSET_ITEM_F3
(PDQ_ID)
S_EMT_SESSN_ITM
S_EMT_SESSN_ITM_F3
(PDQ_ID)
Siebel Data Model Reference Version 8.0
18 3
Schema Changes Table Index Changes in This Version
Table 84.
Table Indexes That Are New in This Version
Table Name
Index
Columns
S_ENTL_PRDPRI
S_ENTL_PRDPRI_F50
(AGREE_BNFT_ID)
S_ENTL_PRDPRI
S_ENTL_PRDPRI_F51
(CTLG_CAT_ID)
S_ENTL_PRDPRI
S_ENTL_PRDPRI_F52
(XA_CLASS_ID)
S_ENTMPL_PRDPRI
S_ENTMPLPRDPRI_F50
(BNFT_TMPL_ID)
S_ENTMPL_PRDPRI
S_ENTMPLPRDPRI_F51
(CTLG_CAT_ID)
S_ENTMPL_PRDPRI
S_ENTMPLPRDPRI_F52
(XA_CLASS_ID)
S_EVT_MKTG
S_EVT_MKTG_F4
(EVT_FUL_REQ_ID)
S_EVT_MKTG
S_EVT_MKTG_F5
(PORTFOLIO_ID)
S_EVT_MKTG
S_EVT_MKTG_F6
(PRTFL_ACCNT_ID)
S_EVT_MKTG
S_EVT_MKTG_F7
(PRTFL_CTGRY_ID)
S_FCSTSER
S_FCSTSER_F2
(QTY_AGFLD_ID)
S_FCSTSER_POSTN
S_FCSTSER_POSTN_F2
(FCSTSER_AGFLD_ID)
S_INVOICE
S_INVOICE_F52
(AGREE_BNFT_ID)
S_NODE
S_NODE_F4
(ROUTE_ID)
S_OPTY_POSTN
S_OPTY_POSTN_F2
(ASGN_TERR_ID)
S_OPTY_SRC
S_OPTY_SRC_F4
(DCP_ID)
S_ORDER
S_ORDER_F43
(DCP_ID)
S_ORDER
S_ORDER_F57
(AGREE_BNFT_ID)
S_PRTNRPRG_APPL
S_PRTNRPRG_APPL_F5
(AGREE_ITEM_ID)
S_PRTNRPRG_APPL
S_PRTNRPRG_APPL_F6
(PRTNRPRG_MBR_ID)
S_PRTNRPRG_MBR
S_PRTNRPRG_MBR_F1
(AGREE_ITEM_ID)
S_PRTNRPRG_MBR
S_PRTNRPRG_MBR_U2
(MEMBERSHIP_NUM,CONFLICT_ID)
S_PRTNR_PROG
S_PRTNR_PROG_F7
(PROD_INT_ID)
S_REVN
S_REVN_F19
(ENT_SOLN_ID)
S_SMQ_HISTORY
S_SMQ_HISTORY_M1
(TRANSPORT_IDEN)
S_SMQ_HISTORY
S_SMQ_HISTORY_M2
(OID_IDEN)
S_SORT_CHAR
S_SORT_CHAR_U1
(CHAR_VAL)
S_SRC_PAYMENT
S_SRC_PAYMENT_F65
(AGREE_BNFT_ID)
S_TERR_ASSET
S_TERR_ASSET_F2
(CREATED_BY_ALGN_ID)
S_TERR_ASSET
S_TERR_ASSET_F3
(EXPIRED_BY_ALGN_ID)
S_TERR_CON
S_TERR_CON_F2
(CREATED_BY_ALGN_ID)
184
Siebel Data Model Reference Version 8.0
Schema Changes Table Index Changes in This Version
Table 84.
Table Indexes That Are New in This Version
Table Name
Index
Columns
S_TERR_CON
S_TERR_CON_F3
(EXPIRED_BY_ALGN_ID)
S_TERR_CON
S_TERR_CON_F4
(FROM_TERR_ID)
S_TERR_POSITION
S_TERR_POSITION_F3
(CREATED_BY_ALGN_ID)
S_TERR_POSITION
S_TERR_POSITION_F4
(EXPIRED_BY_ALGN_ID)
S_TERR_REGION
S_TERR_REGION_F2
(CREATED_BY_ALGN_ID)
S_TERR_REGION
S_TERR_REGION_F3
(EXPIRED_BY_ALGN_ID)
S_TERR_REGION
S_TERR_REGION_F4
(FROM_TERR_ID)
S_TERR_ZIP
S_TERR_ZIP_F1
(CREATED_BY_ALGN_ID)
S_TERR_ZIP
S_TERR_ZIP_F2
(EXPIRED_BY_ALGN_ID)
S_TERR_ZIP
S_TERR_ZIP_F3
(FROM_TERR_ID)
S_TMSHT_ITEM
S_TMSHT_ITEM_V1
(CREATED_BY)
S_UNVBX_ITEM
S_UNVBX_ITEM_M2
(REQUESTOR_ID,RQSTD_TS)
S_UNVBX_ITMTASK
S_UNVBX_ITMTASK_F2
(TERR_ID)
S_UNVBX_ITMTASK
S_UNVBX_ITMTASK_M1
(APPROVER_ID,ACTIVE_FLG,START_TS)
T_DETAIL
T_DETAIL_U1_C1
(RUN_NUM,NAME_CI,CONFLICT_ID)
T_MASTER_POSTN
T_MASTER_POSTN_C1
(MASTER_NAME_CI)
Table Indexes That Changed in This Version
Table 85 lists table indexes that are now active in this version.
Table 85.
Table Indexes That Are Now Active in This Version
Table Name
Index
Columns
S_ADDR_ORG
S_ADDR_ORG_M7
(DB_LAST_UPD,ROW_ID)
S_ADDR_PER
S_ADDR_PER_M6
(DB_LAST_UPD,ROW_ID)
Siebel Data Model Reference Version 8.0
18 5
Schema Changes Table Index Changes in This Version
Table 86 lists table indexes that have changed in this version.
Table 86.
Table Indexes That Have Changed Definition in This Version
Table Name
Index
Previous Columns
New Columns
S_APP_QUERY
S_APP_QUERY_U1
NAME
DESC_TEXT
CREATED_BY
LANG_ID
CONFLICT_ID
PRIV_FLG
NAME
DESC_TEXT
OWNER_ID
LANG_ID
CONFLICT_ID
PRIV_FLG
S_APP_QUERY
S_APP_QUERY_V1
CREATED_BY
OWNER_ID
S_FCST_ITEM_DTL
S_FCST_ITEM_DTL_U1
FCST_ITEM_ID
DETAIL_DT
ORIG_FCST_ID
CONFLICT_ID
FCST_ITEM_ID
DETAIL_DT
ORIG_FCST_ID
SEQ_NUM
CONFLICT_ID
S_POSTN
S_POSTN_M4
DB_LAST_UPD
PAR_ROW_ID
DB_LAST_UPD
ROW_ID
PAR_ROW_ID
S_QUOTE_POSTN
S_QUOTE_POSTN_M1
POSTN_ID
QUOTE_NUM
REV_NUM
POSTN_ID
QUOTE_NUM
REV_NUM
QUOTE_ID
S_REVN
S_REVN_M3
EFFECTIVE_DT
PROD_ID
PROD_ID
EFFECTIVE_DT
S_SRM_REQUEST
S_SRM_REQUEST_M6
STATUS
TGT_DELETE_TS
SRVR_FLOW_ID_VAL
ROW_ID
STATUS
TGT_DELETE_TS
S_TERRALGN
S_TERRALGN_U1
TERR_HIER_ID
NAME
CONFLICT_ID
TERR_HIER_ID
BU_ID
NAME
CONFLICT_ID
S_TERRALGN_ACCT
S_TERRALGN_ACCT_U1
TERR_ALGN_ID
TERR_ID
ACCNT_ID
CONFLICT_ID
TERR_ALGN_ID
TERR_ID
ACCNT_ID
AFFL_OBJECT_CD
CONFLICT_ID
186
Siebel Data Model Reference Version 8.0
Schema Changes Table Index Changes in This Version
Table 86.
Table Indexes That Have Changed Definition in This Version
Table Name
Index
Previous Columns
New Columns
S_TERRALGN_CON
S_TERRALGN_CON_U1
TERR_ALGN_ID
TERR_ID
CON_ID
CONFLICT_ID
TERR_ALGN_ID
TERR_ID
CON_ID
AFFL_OBJECT_CD
CONFLICT_ID
S_TERRALGN_REGN
S_TERRALGN_REGN_U1
TERR_ALGN_ID
TERR_ID
REGION_ID
CONFLICT_ID
TERR_ALGN_ID
TERR_ID
REGION_ID
ASGN_OBJECT_CD
AFFL_OBJECT_CD
CONFLICT_ID
S_TERRALGN_ZIP
S_TERRALGN_ZIP_U1
TERR_ALGN_ID
TERR_ID
ZIPCODE
CONFLICT_ID
TERR_ALGN_ID
TERR_ID
ZIPCODE
ASGN_OBJECT_CD
AFFL_OBJECT_CD
GEO_TYPE_CD
CONFLICT_ID
S_TERRITORY
S_TERRITORY_U1
TERR_HIER_ID
NAME
CONFLICT_ID
NAME
BU_ID
CONFLICT_ID
S_TERR_ACCNT
S_TERR_ACCNT_U1
TERR_ID
ACCNT_ID
EFF_START_DT
CONFLICT_ID
TERR_ID
ACCNT_ID
EFF_START_DT
AFFL_OBJECT_CD
CONFLICT_ID
S_TERR_CON
S_TERR_CON_U1
TERR_ID
CON_ID
EFF_START_DT
CONFLICT_ID
TERR_ID
CON_ID
EFF_START_DT
AFFL_OBJECT_CD
CONFLICT_ID
S_TERR_REGION
S_TERR_REGION_U1
TERR_ID
REGION_ID
EFF_START_DT
CONFLICT_ID
TERR_ID
REGION_ID
EFF_START_DT
ASGN_OBJECT_CD
AFFL_OBJECT_CD
CONFLICT_ID
Siebel Data Model Reference Version 8.0
18 7
Schema Changes Table Index Changes in This Version
Table 86.
Table Indexes That Have Changed Definition in This Version
Table Name
Index
Previous Columns
New Columns
S_TERR_ZIP
S_TERR_ZIP_U1
TERR_ID
ZIPCODE
EFF_START_DT
CONFLICT_ID
TERR_ID
ZIPCODE
EFF_START_DT
ASGN_OBJECT_CD
AFFL_OBJECT_CD
GEO_TYPE_CD
CONFLICT_ID
S_UNVBX_ITEM
S_UNVBX_ITEM_F1
REQUESTOR_ID
OBJECT_VAL
S_WFA_DPLOY_DEF
S_WFA_DPLOY_DEF_U1
NAME
VERSION
CONFLICT_ID
TYPE_CD
NAME VERSION
CONFLICT_ID
Table Indexes That Are Deprecated in This Version
Table 87 lists table indexes that have been deprecated in this version.
Table 87.
Deprecated Table Indexes
Table Name
Index
Columns
S_UNVBX_ITEM_F1
S_UNVBX_ITEM_F1
REQUESTOR_ID
S_VOD
S_VOD_F1
LOCKED_BY
188
Siebel Data Model Reference Version 8.0
Index
compensation planning administration ERD
about
31
diagram
32
tables
31
compensation planning execution ERD
about
33
diagram
34
tables
33
competency management system ERD
about
35
diagram
36
tables
35
Consumer Goods
CG promotion planning ERD
28
content management ERD
about
37
diagram
38
tables
37
content object
See content management ERD
content process
See content management ERD
contract conditions ERD
about
39
diagram
40
tables
39
contracts ERD
about
41
diagram
42
tables
41
Customer Data Item, about
43
account ERD
about
17
diagram
19
support for Dynamic Hierarchy
18
support for Global Account Views
18
tables
18
adjustment group ERD
about
20
diagram
21
tables
20
apparel
See textile, apparel, and footwear ERD
asset management ERD
about
22
diagram
23
tables
22
tracking asset instances
22
auction ERD
about
24
diagram
25
tables
24
auto email response generator ERD
about
26
diagram
27
tables
26
B
banking
See commercial banking ERD
C
campaign management
See marketing campaign ERD
CG promotion planning ERD
about
28
diagram
30
tables
28
columns
domain type definitions
157
INTEGRATION_ID columns, about
naming conventions
153
numeric physical type
158
type definitions
157
commercial banking ERD
about
31
159
data (intersection) table type
about
155
obsolete, table marked as
155
data (private) table type, about
155
data (public) table type
about
155
obsolete, table marked as
155
data types
limit checking
160
data visibility ERD
about
43
diagram
45
tables
43
Database Marketing, marketing program
Siebel Data Model Reference Version 8.0
18 9
Index E
ERD
77
database schema version number, finding
and format
160
defect tracking
See product quality tracking ERD
design
See schema
domain type definitions
157
Dun & Bradstreet integration ERD
about
46
diagram
47
tables
46
Dynamic Hierarchy, support by account
entity
18
E
employee KPI ERD
about
48
diagram
49
tables
48
employees
field service scheduler ERD
54
time sheet ERD
139
entitlement items, service agreement
ERD
123
ERDs
account, diagram
19
account, tables
18
adjustment group, diagram
21
adjustment group, tables
20
asset management, diagram
23
asset management, tables
22
auction, diagram
25
auction, tables
24
auto email response generator,
diagram
27
auto email response generator, tables
CG promotion planning, diagram
30
CG promotion planning, tables
28
compensation planning administration,
diagram
32
compensation planning administration,
tables
31
compensation planning execution,
diagram
34
compensation planning execution,
tables
33
competency management system,
diagram
36
competency management system,
tables
35
content management, diagram
38
content management, tables
37
190
26
contract conditions, diagram
40
contract conditions, tables
39
contracts, diagram
42
contracts, tables
41
data visibility, diagram
45
data visibility, tables
43
Dun & Bradstreet integration, diagram
47
Dun & Bradstreet integration, tables
46
employee KPI, diagram
49
employee KPI, tables
48
exclusive arc relationship, diagram
conventions
12
expense reports, diagram
51
expense reports, tables
50
field service inventory, diagram
53
field service inventory, tables
52
field service scheduler, diagram
55
field service scheduler, tables
54
forecasts, diagram
57
forecasts, tables
56
general diagram conventions
12
high tech marketing development fund,
diagram
59
high tech marketing development fund,
tables
58
invoiceable charges, diagram
61
invoiceable charges, tables
60
invoices, diagram
63
invoices, tables
62
marketing campaign, diagram
65, 67
marketing campaign, tables
66
marketing collaboration, diagram
69
marketing collaboration, tables
68
marketing encyclopedia, diagram
71
marketing encyclopedia, tables
70
marketing events, diagram
74
marketing events, tables
72
marketing plans, diagram
76
marketing plans, tables
75
marketing program, diagram
79
marketing program, tables
77
marketing resource management: document,
diagram
81
marketing resource management: document,
tables
80
opportunity management, diagram
83
opportunity management, tables
82
order life cycle, diagram
85
order life cycle, tables
84
orders, diagram
87
orders, tables
86
partner collaboration, diagram
89
partner collaboration, tables
88
partner program registration, diagram
91
Siebel Data Model Reference Version 8.0
Index F
partner program registration, tables
90
party model, diagram
93
party model, tables
92
payments, diagram
95
payments, tables
94
performance review, diagram
98
performance review, tables
96
personal account, diagram
100
personal account, tables
99
personal financial review, diagram
102
personal financial review, tables
101
pricing comparison, diagram
104
pricing comparison, tables
103
pricing, diagram
106
pricing, tables
105
product promotion, diagram
108
product promotion, tables
107
product quality tracking, diagram
110
product quality tracking, tables
109
product recommendation, diagram
112
product recommendation, tables
111
products or services, diagram
114
products or services, tables
113
professional services, diagram
116
professional services, tables
115
recursive relationship, diagram
conventions
13
revenue, diagram
118
revenue, tables
117
revision table
14
sales hierarchy and credit assignment,
diagram
120
sales hierarchy and credit assignment,
tables
119
sales portfolio management, diagram
122
sales portfolio management, tables
121,
135
service agreement, diagram
124
service agreement, tables
123
service calendars and work shifts,
diagram
126
service calendars and work shifts,
tables
125
service request, diagram
128
service request, tables
127
shipment, diagram
130
shipment, tables
129
Siebel Assistant, diagram
132
Siebel Assistant, tables
131
territory management - LS, diagram
136
territory management, diagram
134
territory management, tables
133
textile, apparel, and footwear,
diagram
138
textile, apparel, and footwear, tables
137
time sheet, diagram
140
time sheet, tables
139
trade promotions, diagram
142
trade promotions, tables
141
training curriculum course, diagram
144
training curriculum course, tables
143
training test engine, diagram
146
training test engine, tables
145
versioned object definition, diagram
148
versioned object definition, tables
147
warranty, diagram
150
warranty, tables
149
exclusive arc relationship
about
12
diagram conventions
12
expense reports ERD
about
50
diagram
51
tables
50
extension (Siebel) table type
about
155
obsolete table marked as
155
extension table type, about
155
F
field service inventory ERD
about
52
diagram
53
tables
52
field service scheduler ERD
about
54
diagram
55
tables
54
financial accounts
personal account ERD
99
financial review, personal financial review
ERD
101
Financial Services
commercial banking ERD
31
footwear
See textile, apparel, and footwear ERD
forecasts ERD
about
56
diagram
57
tables
56
G
Global Account Views, support by account
entity
18
H
high tech marketing development fund ERD
Siebel Data Model Reference Version 8.0
19 1
Index I
about
58
diagram
59
tables
58
diagram
81
tables
80
Master Data Item, about
43
MDFs
See CG promotion planning ERD
I
Include Only field
159
index column fields
159
index naming conventions
153
insurance
personal account ERD
99
INTEGRATION_ID columns, about
invoiceable charges ERD
about
60
diagram
61
tables
60
invoices ERD
about
62
diagram
63
tables
62
159
L
limit checking for data types
160
M
marketing campaign ERD
about
66
diagram
65, 67
tables
66
marketing collaboration ERD
about
68
diagram
69
tables
68
marketing development funds
See CG promotion planning ERD
marketing encyclopedia ERD
about
70
diagram
71
tables
70
marketing events ERD
about
72
diagram
74
tables
72
marketing plans ERD
about
75
diagram
76
tables
75
marketing program ERD
about
77
diagram
79
tables
77
marketing resource management: document
ERD
about
80
192
naming conventions
columns
153
indexes
153
physical model listings, abbreviations
used
154
table names
151
table prefixes
152
table suffixes
152
non-Siebel application products, caution
about inserting or updating data
normalized, defined
9
opportunity management ERD
about
82
diagram
83
tables
82
Oracle Applications, about use of
INTEGRATION_ID columns
order life cycle ERD
about
84
diagram
85
tables
84
orders ERD
about
86
diagram
87
tables
86
P
partner collaboration ERD
about
88
diagram
89
tables
88
partner program registration ERD
about
90
diagram
91
tables
90
party model ERD
about
92
diagram
93
tables
92
party, defined
92
payments ERD
about
94
diagram
95
tables
94
Siebel Data Model Reference Version 8.0
159
Index R
performance review ERD
about
96
diagram
98
tables
96
personal account ERD
about
99
diagram
100
tables
99
personal financial review ERD
about
101
diagram
102
tables
101
physical model
column naming conventions
153
column type definitions
157
columns of numeric physical type
158
database schema version number, finding and
format
160
domain type definitions
157
Include Only field
159
index naming conventions
153
INTEGRATION_ID columns, about
159
limit checking for data types
160
party model, aboutparty model, about
161
physical model listings, abbreviations
used
154
Siebel repository tables, about
159
Siebel system fields
158
table naming conventions
151
table status definitions
156
table type definitions
155
validating Siebel Schema
160
pricing comparison ERD
about
103
diagram
104
tables
103
pricing ERD
about
105
diagram
106
tables
105
product promotion ERD
about
107
diagram
108
tables
107
product quality tracking ERD
about
109
diagram
110
tables
109
product recommendation ERD
about
111
diagram
112
tables
111
products or services ERD
about
113
diagram
114
tables
113
professional services ERD
about
115
diagram
116
tables
115
projects, professional services ERD
115
R
recursive relationship
about
13
diagram conventions
13
repository, about Siebel repository
revenue ERD
diagram
118
tables
117
159
S
sales hierarchy and credit assignment ERD
about
119
diagram
120
tables
119
Sales Hierarchy Module
See sales hierarchy and credit assignment
ERD
sales portfolio management ERD
about
121
diagram
122
tables
121, 135
schema
database schema version number, finding and
format
160
defined
9
validating Siebel Schema
160
service activities, field service scheduler
ERD
54
service agreement ERD
about
123
diagram
124
tables
123
service calendars and work shifts ERD
about
125
diagram
126
tables
125
service region, field service scheduler
ERD
54
service request ERD
about
127
diagram
128
tables
127
shipment ERD
about
129
diagram
130
Siebel Data Model Reference Version 8.0
19 3
Index T
tables
129
Siebel Assistant ERD
about
131
diagram
132
tables
131
Siebel Financial Services
commercial banking ERD
31
Siebel repository, about
159
Siebel SAP R/3 Connector, about use of
INTEGRATION_ID columns
159
Siebel system fields
158
special ERD conventions
exclusive arc relationship
12
recursive relationship
13
system fields
158
T
tables
naming conventions
151
prefix naming conventions
152
suffix naming conventions
152
table status definitions
156
types of
155
territory management - LS ERD
diagram
136
territory management ERD
about
133
diagram
134
tables
133
territory quota rollup ERD
about
135
tests, training test engine ERD
145
textile, apparel, and footwear ERD
about
137
diagram
138
194
tables
137
time sheet ERD
about
139
diagram
140
tables
139
trade promotions ERD
about
141
diagram
142
tables
141
training curriculum course ERD
about
143
diagram
144
tables
143
training test engine ERD
about
145
diagram
146
tables
145
V
validating Siebel Schema
160
versioned object definition ERD
about
147
diagram
148
tables
147
W
warranty ERD
about
149
diagram
150
tables
149
work shifts
See service calendars and work shifts ERD
workflow process
See content management ERD
Siebel Data Model Reference Version 8.0
You might also like
- Siebel Data Model Reference: November 2011No ratings yetSiebel Data Model Reference: November 2011550 pages
- Siebel Marketing User Guide: November 2008No ratings yetSiebel Marketing User Guide: November 2008238 pages
- Developing and Deploying Siebel Business Applications: Version 8.1, Rev A December 2010No ratings yetDeveloping and Deploying Siebel Business Applications: Version 8.1, Rev A December 2010212 pages
- Siebel Object Types Reference: March 2008No ratings yetSiebel Object Types Reference: March 2008404 pages
- Siebel Data Model Reference For Industry Applications v8.1.175% (4)Siebel Data Model Reference For Industry Applications v8.1.1330 pages
- Siebel Master Data Applications Reference For Industry ApplicationsNo ratings yetSiebel Master Data Applications Reference For Industry Applications268 pages
- Solution Proposal for New Office IT Infrastructure SetupNo ratings yetSolution Proposal for New Office IT Infrastructure Setup22 pages
- Siebel Data Model Reference: Version 8.0, Rev. A May 2008No ratings yetSiebel Data Model Reference: Version 8.0, Rev. A May 2008196 pages
- Siebel Reports Guide: Version 8.1, Rev. C June 2010No ratings yetSiebel Reports Guide: Version 8.1, Rev. C June 2010160 pages
- Oracle Marketing Segmentation Guide: January 2008No ratings yetOracle Marketing Segmentation Guide: January 2008120 pages
- Siebel Mobile Connector Guide: March 2008No ratings yetSiebel Mobile Connector Guide: March 2008170 pages
- Siebel Portal Framework Guide: November 2008No ratings yetSiebel Portal Framework Guide: November 2008126 pages
- Using Siebel Tools: Version 8.0, Rev. A August 2007No ratings yetUsing Siebel Tools: Version 8.0, Rev. A August 2007244 pages
- Systems: Unit-V: Computer Control of PowerNo ratings yetSystems: Unit-V: Computer Control of Power14 pages
- Quick Guide on AIS with Analytics v2024No ratings yetQuick Guide on AIS with Analytics v2024220 pages
- 1Z0-997 - OCI Architect Professional Study Guide PDF0% (1)1Z0-997 - OCI Architect Professional Study Guide PDF6 pages
- 1Z0-997 - OCI Architect Professional Study Guide PDF0% (1)1Z0-997 - OCI Architect Professional Study Guide PDF6 pages
- Study On The Source of E Waste Management and Disposal MethodsNo ratings yetStudy On The Source of E Waste Management and Disposal Methods22 pages
- Delta Lake: High-Performance ACID Table Storage Over Cloud Object StoresNo ratings yetDelta Lake: High-Performance ACID Table Storage Over Cloud Object Stores14 pages
- Mit Sap Big Data and Social Analytics Online Short Course BrochureNo ratings yetMit Sap Big Data and Social Analytics Online Short Course Brochure9 pages
- Key Questions Topic For Sap Terp10 CourseNo ratings yetKey Questions Topic For Sap Terp10 Course4 pages
- For New Students Admitted in AY2013/2014 For Existing Students Admitted in AY2012/2013 and BeforeNo ratings yetFor New Students Admitted in AY2013/2014 For Existing Students Admitted in AY2012/2013 and Before3 pages
- Festal® N: For The Use Only of A Registered Medical Practitioner or A Hospital or A LaboratoryNo ratings yetFestal® N: For The Use Only of A Registered Medical Practitioner or A Hospital or A Laboratory1 page
- AP Repeater On Dlink Dir-300 - DD-WRT WikiNo ratings yetAP Repeater On Dlink Dir-300 - DD-WRT Wiki2 pages
- Comprehensive ClickUp Administration: Definitive Reference for Developers and EngineersFrom EverandComprehensive ClickUp Administration: Definitive Reference for Developers and EngineersNo ratings yet
- Testing Laboratory Revenues World Summary: Market Values & Financials by CountryFrom EverandTesting Laboratory Revenues World Summary: Market Values & Financials by CountryNo ratings yet
- The Data Detective's Toolkit: Cutting-Edge Techniques and SAS Macros to Clean, Prepare, and Manage DataFrom EverandThe Data Detective's Toolkit: Cutting-Edge Techniques and SAS Macros to Clean, Prepare, and Manage DataNo ratings yet
- Automated Product Handling Systems Equipment World Summary: Market Values & Financials by CountryFrom EverandAutomated Product Handling Systems Equipment World Summary: Market Values & Financials by CountryNo ratings yet
- The Business Analyst's Guide to Oracle Hyperion Interactive Reporting 11From EverandThe Business Analyst's Guide to Oracle Hyperion Interactive Reporting 115/5 (1)
- PROC REPORT by Example: Techniques for Building Professional Reports Using SAS: Techniques for Building Professional Reports Using SASFrom EverandPROC REPORT by Example: Techniques for Building Professional Reports Using SAS: Techniques for Building Professional Reports Using SASNo ratings yet
- Learning Dynamics NAV Patterns: Create solutions that are easy to maintain, are quick to upgrade, and follow proven concepts and designFrom EverandLearning Dynamics NAV Patterns: Create solutions that are easy to maintain, are quick to upgrade, and follow proven concepts and designNo ratings yet
- Re-Architecting Application for Cloud: An Architect's reference guideFrom EverandRe-Architecting Application for Cloud: An Architect's reference guide4/5 (1)
- Application Design: Key Principles For Data-Intensive App SystemsFrom EverandApplication Design: Key Principles For Data-Intensive App SystemsNo ratings yet
- SAP ECC FI Transaction Codes: Unofficial Certification and Review GuideFrom EverandSAP ECC FI Transaction Codes: Unofficial Certification and Review Guide5/5 (2)
- Knight's Microsoft Business Intelligence 24-Hour Trainer: Leveraging Microsoft SQL Server Integration, Analysis, and Reporting Services with Excel and SharePointFrom EverandKnight's Microsoft Business Intelligence 24-Hour Trainer: Leveraging Microsoft SQL Server Integration, Analysis, and Reporting Services with Excel and SharePoint3/5 (1)
- Oracle® Financials Interview Questions: Unofficial Oracle Financials Certification ReviewFrom EverandOracle® Financials Interview Questions: Unofficial Oracle Financials Certification Review2.5/5 (6)
