DMR2014 PDF

Siebel Data Model
Reference
Siebel Innovation Pack 2014, Rev. A
July 2015
Copyright 2005, 2015 Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions
on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in
your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast,
modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by
any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law
for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-
free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing
it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,
any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users
are commercial computer software pursuant to the applicable Federal Acquisition Regulation and
agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and
adaptation of the programs, including any operating system, integrated software, any programs installed
on the hardware, and/or documentation, shall be subject to license terms and license restrictions
applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management
applications. It is not developed or intended for use in any inherently dangerous applications, including
applications that may create a risk of personal injury. If you use this software or hardware in dangerous
applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and
other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any
damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be
trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks
are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD,
Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced
Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content,
products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and
expressly disclaim all warranties of any kind with respect to third-party content, products, and services
unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and
its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use
of third-party content, products, or services, except as set forth in an applicable agreement between you
and Oracle.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program
website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers that have purchased support have access to electronic support through My Oracle
Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Contents
Siebel Data Model Reference 1
Chapter 1: Whats New in This Release
Chapter 2: Siebel Logical Model

Overview of Siebel Data Model 11
Entity Relationship Diagram Conventions 12
General Entities 12
Exclusive Arc Relationship 13
Recursive Relationship 14
Entity Relationship Diagrams and Descriptions for Siebel Cross-Industry Applications
15
Account 18
Adjustment Group 21
Asset Management 23
Auction 25
Auto Email Response Generator 27
CG Promotion Planning 29
Compensation Planning Administration 32
Compensation Planning Execution 34
Competency Management System 36
Content Management 38
Contract Conditions 40
Contracts 42
Data Visibility 44
Dun & Bradstreet Integration 47
Employee KPI 49
Expense Reports 51
Field Service Inventory 53
Field Service Scheduler 55
Forecasts 57
High Tech Marketing Development Fund 59
In-Memory Next Best Action 61
Invoiceable Charges 63
Invoices 66
Lead Management 68
Marketing Budget Request 71
Siebel Data Model Reference Siebel Innovation Pack 2014, Rev. A 3

Contents
Marketing Campaign 73
Marketing Collaboration 75
Marketing Encyclopedia 77
Marketing Event Driven Dialogue 79
Marketing Events 81
Marketing Plans 84
Marketing Program 86
Marketing Resource Management: Document 89
Opportunity Management 91
Order and Promotion 93
Order Life Cycle 95
Orders 97
Partner Collaboration 99
Partner Program Registration 101
Party Model 103
Payments 105
Performance Review 107
Personal Account 110
Personal Financial Review 112
Pricing 114
Pricing Comparison 116
Product Promotion 118
Product Quality Tracking 120
Product Recommendation and Offer 122
Products or Services 124
Professional Services 126
Promotion Group 128
Revenue 131
Sales Hierarchy and Credit Assignment 133
Sales Portfolio Management 135
Service Agreement 137
Service Calendars and Work Shifts 139
Service Request 141
Shipment 143
Siebel Assistant 145
Social Media 147
Territory Management 149
Territory Quota Rollup 151
Textile, Apparel, and Footwear 153
Time Sheet 155
Trade Promotions 157
Training Curriculum Course 159
4 Siebel Data Model Reference Siebel Innovation Pack 2014, Rev. A

Contents
Training Test Engine 161

Versioned Object Definition 163
Warranty 165
Warranty Claim 168
Work Order 171
Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 173
Account Targeting 176
Activity 178
Affiliations and Best Times 180
Agencies/Agent 182
Automotive Retail 184
Brick 186
Clinical Study Management 188
Clinical Study Site Management 191
Communications, Media, and Energy (CME) Account 193
CME Agreement 195
CME Alert 197
CME Energy Products, Service, and Usage 199
CME Order Management 201
Commercial Banking 203
Commercial Insurance 206
Community/Chat Discussion 208
Dealer Sales and Service Promotion 210
Document ID and Tax ID 212
Event Tax Administration 214
Financial Account 216
Financial Account Application 218
Financial Account Origination 220
Financial Investments 222
Financial Products 224
Financial Services Events 226
Fleet Management 229
Fleet Management - Location 232
FLEXCUBE Universal Banking Integration 234
Group Insurance Policies 236
Group Pensions 238
Health Provider and Provider Group 240
High Tech Special Pricing Authorization 242
Hospitality Category 244
Hospitality - Meeting Package 246
Institutional Sales 248
Insurance Claims 250

Contents
Insurance Policies 253

Life Insurance Policy 255
Loyalty 257
Loyalty Flowchart and Formula 261
Managed Care 263
Medical Education Event Management 265
Objectives 267
Personalized Content Delivery 269
Public Sector Benefit Case Management 271
Public Sector Case Lead Management 274
Public Sector Child Welfare 277
Public Sector Contact Identity 279
Public Sector Evidence Management 281
Public Sector Incident Management 283
Public Sector Service Provider and Referral Management 285
Real-Time Scheduler Integration 287
Routes and Best Call Hours 289
Sales Volume Planning 291
Sample Management 293
Special Rate List 295
Syndicated Data 297
Teller Administration 299
Territory AlignmentQuota Assignment 301
Territory Management - Consumer Sector 303
Territory Management - Life Sciences 305
Universal Customer Master 307
Vehicle 310
Vehicle Collection 312
Vehicle Financing 314
Vehicle Sales 316
Chapter 3: Siebel Physical Model

Data Model Naming Conventions 319
Table Naming Conventions 319
Index Naming Conventions 321
Column Naming Conventions 321
Abbreviations Used in the Physical Model Listings 322
Data Model Type Definitions 322
Table Type Definitions 323
Table Status Definitions 324
Column Type Definitions 325

Contents
Domain Type Definitions 325

Columns of Numeric Physical Type 326
Siebel System Fields 326
INTEGRATION_ID Columns 327
Include Only Field 327
Siebel Repository 327
Database Schema Version 327
Limit Checking for Data Types 328
Validating the Siebel Schema 328
Party Model Unifies Access to Data 328
Generating a Report about Tables 329
Chapter 4: Schema Changes

Schema Changes Implemented in Siebel Innovation Pack 2014 331
New Tables Added to Innovation Pack 2014 331
Changes to Table Columns Implemented in Innovation Pack 2014 332
Changes to Table Indexes Implemented in Innovation Pack 2014 335
Index

Contents

1 Whats New in This Release
Whats New in Siebel Data Model Reference, Siebel Innovation Pack

2014, Rev. A
Table 1 lists the changes in this revision of the documentation to support this release of the software.
Table 1. New Product Features in Siebel Data Model Reference, Siebel Innovation Pack 2014,
Rev. A
Topic Description
New Tables Added to Innovation Pack Modified topic. A listing of the new tables that have been
2014 on page 331 added to Siebel Innovation Pack 2014.
Changes to Table Columns Modified topic. A listing of the table columns that have
Implemented in Innovation Pack 2014 changed in Siebel Innovation Pack 2014.
on page 332
Changes to Table Indexes Implemented Modified topic. A listing of the table indexes that have
in Innovation Pack 2014 on page 335 changed in Siebel Innovation Pack 2014.
Whats New in Siebel Data Model Reference, Siebel Innovation Pack

2014
Table 2 lists the changes in this revision of the documentation to support this release of the software.
NOTE: Siebel Innovation Pack 2014 is a continuation of the Siebel 8.1/ 8.2 release.
Table 2. New Product Features in Siebel Data Model Reference, Siebel Innovation Pack 2014
Topic Description
In-Memory Next Best Action on page 61 New topic. Organizations can provide contextual
recommendations to their customers on all channels.
Universal Customer Master on page 307 Modified topic. Added two new entities: UCM Social
Media Profile of Contacts and UCM Social Media Profile
Attribute of Contacts.
Schema Changes Implemented in Siebel Modified topic. A listing of the schema changes
Innovation Pack 2014 on page 331 implemented in Siebel Innovation Pack 2014.

Whats New in This Release
Table 2. New Product Features in Siebel Data Model Reference, Siebel Innovation Pack 2014
Topic Description
Schema Changes Implemented in Siebel Removed topic.

CRM Version 8.1.1.11/8.2.2.4 Compared
with Version 8.1.1.10.
Schema Changes Implemented in Siebel Removed topic.

CRM Version 8.1.1.11/8.2.2.4 Compared
with Version 8.2.2.3.
What's New in Siebel Data Model Reference Version 8.1/8.2

Table 3 lists changes described in this version of the documentation to support this release of the
software. The new features described in Table 3 are available in Siebel CRM version 8.1.1.11, Siebel
CRM version 8.2.2.4, and later.
Table 3. New Product Features in Siebel Data Model Reference, Version 8.1/8.2
Topic Description
Clinical Study Management on Modified topic. Added two new entities: Contract and
page 188 Exception Activity.
Schema Changes Implemented in Modified topic. A listing of the schema changes

Siebel CRM Version 8.1.1.11/8.2.2.4 implemented in version 8.1.1.11/8.2.2.4 compared with
Compared with Version 8.1.1.10 on version 8.1.1.10.
page 329
Schema Changes Implemented in Modified topic. A listing of the schema changes

Siebel CRM Version 8.1.1.11/8.2.2.4 implemented in version 8.1.1.11/8.2.2.4 compared with
Compared with Version 8.2.2.3 on version 8.2.2.3.
page 361

2 Siebel Logical Model
The entity relationship diagrams (ERDs) included in this chapter 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:
Overview of Siebel Data Model
Entity Relationship Diagram Conventions

Entity Relationship Diagrams and Descriptions for Siebel Cross-Industry Applications on page 15
Entity Relationship Diagrams and Descriptions for Siebel Industry Applications on page 173
Overview of Siebel Data Model

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 might not be implemented in the physical model at the present time.
Oracles Siebel Data Model defines how the data used by Siebel Business Applications is stored in a
standard relational DBMS such as Oracle, DB2, or Microsoft SQL Server. 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 CRM products you have purchased.
You are not entitled to use any portion of the Siebel Data Model to support Siebel CRM 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 need to update the same unit of data in several different locations. Most tables in an OLTP
database includes 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.

Siebel Logical Model Entity Relationship Diagram Conventions
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, see
Siebel Enterprise Integration Manager Administration Guide.
NOTE: The Siebel Bookshelf is available on Oracle Technology Network (http://www.oracle.com/

technetwork/indexes/documentation/index.html) and Oracle Software Delivery Cloud. It might also be
installed locally on your intranet or on a network location.
Entity Relationship Diagram

Conventions
The Siebel logical model represents the following in Siebel Business Applications:
Entities
Relationships between entities
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.
This topic describes entity relationship diagram conventions, as follows:
General Entities on page 12
Exclusive Arc Relationship on page 13
Recursive Relationship on page 14
General Entities
Figure 1 shows the diagram conventions for general entities used in this guide.

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:
Each [entity] must be [relationship name] either to only one [entity] or [relationship name] to only
one [entity]. For example, each Product Comparison must be to only one Product Internal or to only
one Product External, see 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 can be part of only one activity, or
each activity can be made up of one or more activities, see 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 Logical Model Entity Relationship Diagrams and Descriptions for Siebel Cross-
Industry Applications
Entity Relationship Diagrams and

Descriptions for Siebel Cross-Industry
Applications
The ERD descriptions and diagrams in this topic apply to Siebel Cross-Industry Applications. These
applications are designed for particular business activities and operate across industries. They
include the Siebel Call Center, Siebel Service, Siebel Sales, Siebel Marketing, and other applications.
Table 4 provides a list of ERDs in alphabetic order.
Table 4. Entity Relationship Diagrams for Siebel Cross-Industry Applications
Figure Num. and

ERD Name Page Functional Area
Account Figure 4 on page 20 General
Adjustment Group Figure 5 on page 22 General
Asset Management Figure 6 on page 24 General
Auction Figure 7 on page 26 General
Auto Email Response Generator Figure 8 on page 28 General
CG Promotion Planning Figure 9 on page 31 Marketing
Compensation Planning Administration Figure 10 on page 33 ERM
Compensation Planning Execution Figure 11 on page 35 ERM
Competency Management System Figure 12 on page 37 ERM
Content Management Figure 13 on page 39 General
Contract Conditions Figure 14 on page 41 General

Contracts Figure 15 on page 43 General
Data Visibility Figure 16 on page 46 General
Dun & Bradstreet Integration Figure 17 on page 48 Sales and Marketing
Employee KPI Figure 18 on page 50 ERM
Expense Reports Figure 19 on page 52 General
Field Service Inventory Figure 20 on page 54 Service
Field Service Scheduler Figure 21 on page 56 Service
Forecasts Figure 22 on page 58 Sales and Marketing
High Tech Marketing Development Fund Figure 23 on page 60 Marketing
In-Memory Next Best Action Figure 24 on page 62 Marketing
Invoiceable Charges Figure 25 on page 65 Service
Invoices Figure 26 on page 67 Service

Figure Num. and

Lead Management Figure 27 on page 70 Sales and Marketing
Marketing Budget Request Figure 28 on page 72 Marketing
Marketing Campaign Figure 29 on page 74 Marketing
Marketing Collaboration Figure 30 on page 76 Marketing
Marketing Encyclopedia Figure 31 on page 78 Sales and Marketing
Marketing Event Driven Dialogue Figure 32 on page 80 Marketing
Marketing Events Figure 33 on page 83 General
Marketing Plans Figure 34 on page 85 Marketing
Marketing Program Figure 35 on page 88 Marketing
Marketing Resource Management: Document Figure 36 on page 90 Marketing
Opportunity Management Figure 37 on page 92 Sales
Order and Promotion Figure 38 on page 94 General
Order Life Cycle Figure 39 on page 96 General
Orders Figure 40 on page 98 General
Partner Collaboration Figure 41 on page 100 General
Partner Program Registration Figure 42 on page 102 General
Party Model Figure 43 on page 104 General
Payments Figure 44 on page 106 General

Performance Review Figure 45 on page 109 ERM
Personal Account Figure 46 on page 111 Industry-Specific
Personal Financial Review Figure 47 on page 113 Industry-Specific
Pricing Figure 48 on page 115 General
Pricing Comparison Figure 49 on page 117 Energy
Product Promotion Figure 50 on page 119 General
Product Quality Tracking Figure 51 on page 121 General
Product Recommendation and Offer Figure 52 on page 123 General
Products or Services Figure 53 on page 125 Service
Professional Services Figure 54 on page 127 General
Promotion Group Figure 55 on page 130 General
Revenue Figure 56 on page 132 General

Figure Num. and

Sales Hierarchy and Credit Assignment Figure 57 on page 134 Sales
Sales Portfolio Management Figure 58 on page 136 Sales
Service Agreement Figure 59 on page 138 Service
Service Calendars and Work Shifts Figure 60 on page 140 Service
Service Request Figure 61 on page 142 Service
Shipment Figure 62 on page 144 General
Siebel Assistant Figure 63 on page 146 General
Social Media Figure 64 on page 148 General
Territory Management Figure 65 on page 150 Sales
Territory Quota Rollup Figure 66 on page 152 Sales
Textile, Apparel, and Footwear Figure 67 on page 154 Consumer Sector
Time Sheet Figure 68 on page 156 General
Trade Promotions Figure 69 on page 158 General
Training Curriculum Course Figure 70 on page 160 General
Training Test Engine Figure 71 on page 162 General
Versioned Object Definition Figure 72 on page 164 General
Warranty Figure 73 on page 167 Service
Warranty Claim Figure 74 on page 170 Service

Work Order Figure 75 on page 172 Service

Account
This ERD (see Figure 4) illustrates the account entity, 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.
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 can
represent a company, a site, a subsidiary, a division, or any other subset of an organization. An
account can 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 5 lists the entities in this ERD and their corresponding tables.
Table 5. Account ERD Entities and Tables
Entity Table
Account S_ORG_EXT, S_PARTY
Account Synonym S_ORG_SYN
Activity S_EVT_ACT
Address S_ADDR_ORG (Siebel Cross-Industry Applications)

S_ADDR_PER (Siebel Industry Applications)
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

Table 5. Account ERD Entities and Tables
Entity Table
Position S_POSTN, S_PARTY
Price List S_PRI_LST
Sales or Service Team Member S_ACCNT_POSTN

20
CHARACTERISTIC
INDUSTRY SALES OR SERVICE
TEAM MEMBER
Figure 4.
classification for user characteristics for
ACCOUNT SYNONYM
CORRESPONDENCE ASSIGNMENT
GROUP responsible for holders
a report to of
(TERRITORY)
Account
another name for

addressed to
a parent of
NAMED HIERARCHY
ACCOUNT DECISION participant in

Siebel Logical Model
ISSUES MARKET
ACTIVITY SEGMENT PRICE LIST
for of ADDRESS
for action for
for
current price applicable to
made visible through type of list for
for belong to
PARTY participate in described in

located at known as part of target of target of user of access to
ACCOUNT responsibility of
responsibility of pay or payed by composed of a parent of a report to held by

responsible for contact of
POSITION
OTHER
BUSINESS UNIT PARTY PERSON
OTHER PERSON EMPLOYEE / AGENT

constrained to use
made up of acessible to default payment term for
NAMED HIERARCHY PAYMENT TERM
Siebel Data Model Reference Siebel Innovation Pack 2014, Rev. A

Entity Relationship Diagrams and Descriptions for Siebel Cross-
Adjustment Group
This ERD (see Figure 5) 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 6. Adjustment Group ERD Entities and Table
Entity Table
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

22
ADJUSTMENT GROUP
# ADJ_GROUP_NAME
Figure 5.
PRODUCT COMPATABILITY MATRIX RULE for
# MTRX_RULE_NUM
contain
PRODUCT ELIGIBILITY MATRIX RULE for

# MTRX_RULE_NUM
contain
Adjustment Group
PRODUCT PROMOTION PRICING MATRIX RULE for

# MTRX_RULE_NUM
contain
STANDARD ENTITLEMENT PRICING MATRIX for

RULE
# MTRX_RULE_NUM contain
STANDARD PRODUCT PRICING MATRIX RULE for

# MTRX_RULE_NUM
contain
STANDARD TRAINING PRICING MATRIX RULE for

# MTRX_RULE_NUM
contain
contain
for

ADJUSTMENT GROUP
DIMENSION
# FIELD_NAME
Asset Management
This ERD (see Figure 6) 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 7. Asset Management ERD Entities and Tables
Entity Table
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 (Siebel Cross-Industry Applications)

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
Personal Address S_ADDR_PER
Product Instance (Asset) S_ASSET
Service Request S_SRV_REQ

24
ADDRESS for initiated by
OPPORTUNITY OPPORTUNITY
PERSONAL ASSET
ADDRESS
Figure 6.
part of of
BUSINESS ASSET EXTERNAL ORGANIZATION
ACTIVITY made up of ADDRESS
of to
performed on ASSET EMPLOYEE RELATIONSHIP
for
part of initiator of defined for
ASSET of to
defined for NOTE ASSET CONTACT RELATIONSHIP

RELATIONSHIP
for of
for
of to
Asset Management
associated with
associated with located at subject of subject of
subject of subject of PERSON associated with
subject of initiator of subject of
currently owned byCONTACT
PRODUCT INSTANCE (ASSET)
associated with
owner of
an assembly of
EMPLOYEE
possessor of
a component of
currently possessed by
associated with
made up of
EXTERNAL
for problems with currently owned by ORGANIZATION
SERVICE subject of
REQUEST owner of ACCOUNT
instance of
moved by subject of modified by involved in
OTHER EXTERNAL
ORGANIZATION
for problems with for
ASSET for use of
FEATURE classification for VENDOR
COMPETITIVE ASSET
of of use of
METRIC MODIFICATION vendor of
initiated by
classification for
COMPETITIVE produced by child of parent of
of
ACTIVITY PART PRODUCT involved in
for subject of
MOVEMENT FEATURE
PRODUCT made into
moved by
INTERNAL PRODUCT EXTERNAL
of subject of
SERIALIZABLE PRODUCT
subject of NON-SERIALIZABLE PRODUCT

PRODUCT
Auction
This ERD (see Figure 7) illustrates how the Siebel Data Model represents the auctioning of goods or
services to bidders. An auction item can be a stand-alone offering, or can 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 can 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 can be tracked through one or more order items.
Finally, users can set up watched items, define alerts, and rate fellow listers or bidders.
Table 8. Auction ERD Entities and Tables
Entity Table
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

26
part of
accessed
via
CATALOG CATEGORY ITEM CATALOG CATEGORY
owner of made up of Figure 7.
represented by represented by
Auction
created from
ORDER ITEM represented as
displayed as
fulfillment of pricing
AUCTION ITEM for applicable to

mechanism PRODUCT
fulfilled as for owner of
part of
priced by
composed of CATALOG
displayed as
ORDER
priced by ASSET
pricing subject of
mechanism
for for created AUCTION ALERT
AUCTION ITEM from DEFINITION
PROMOTION featured in subject of TRIGGERED AUCTION ITEM ALERT
genesis of
for
for created by
AUCTION ITEM BID AUCTION LISTER/BIDDER
for RATING
subject of AUCTION ITEM WATCH
subject of
for
placed by for made by rating of
listed by
PARTY
PERSON
OTHER PARTY
placer of lister of creator of alerted by creator of subject of creator of

OTHER PERSON USER
Auto Email Response Generator

This ERD (see Figure 8) 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 9. Auto Email Response Generator ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Catalog S_CTLG
Category Usage Notification S_COMM_CTG_NTFY
Communication Template Usage Notification S_COMMTMPL_NTFY
Problem Resolution Document S_RESITEM
Template Communication Response S_DMND_CRTN_PRG

28
ACTIVITY
Figure 8.
part of made up
CATALOG CATEGORY
categorized within
INBOUND COMMUNICATION
classification for
PROBLEM
RESOLUTION
DOCUMENT categorized under
OUTBOUND RESPONSE classification for
Auto Email Response Generator
COMMUNICATION TMPL USAGE CATEGORY

NOTIFICATION USAGE for usage of
NOTIFICATION
subject of
for usage of to notify to notify
target of target of part of

classification of
PERSON
made up of
CATALOG
subject of default response for
TEMPLATE COMMUNICATION RESPONSE

CG Promotion Planning
This ERD (see Figure 9) 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 can 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 10. CG Promotion Planning ERD Entities and Tables
Entity Table
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
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
Promotion Product S_SRC

Table 10. CG Promotion Planning ERD Entities and Tables
Entity Table
Promotion Category S_SRC
Promotion Account Product S_SRC

PAYMENT MARKETING EVENT OR ACTIVITY
Oracle
OTHER PAYMENT
Figure 9.
PROMOTION PLAN
FUND PROMOTION
ALLOCATION PROMOTION PAYMENT for
covered by
subject of
PROMOTION ACCOUNT
sub allocation of for
to
requested by recipient of
PERSON PROMOTION CATEGORY
sub allocated to
approved by requestor of
EMPLOYEE / AGENT
approver of made of PROMOTION PRODUCT
assigned to
CG Promotion Planning
OTHER PERSON
responsible for POSITION
made up of of part of
PROMOTION ACCOUNT PRODUCT
subject of
subject of
assigned to ACCOUNT
MARKETING
part of DEVELOPMENT defined for
responsible for OTHER MARKETING EVENT OR
FUND target of
target of ACTIVITY
designated to available to
ACCRUAL related to
FUND user of defined for of
AUTHORIZED
PRODUCT
used by PRODUCT
relation of
at STRUCTURE
subject to
subject of PRICE LIST for
of
applicable to
for
FIXED FUND PRICE LIST ITEM basis for a component of
composed of promoted via
an assembly of
based on
of subject of INTERNAL PRODUCT OR
SERVICE
of subject of
subject of
for promotion of
MIXED FUND subject of
PRODUCT LINE composed of part of
for promotion of hierarchy parent of
earned by
MDF ACCRUAL earner of
funded through earned by earner of

for subject of
earned in subject of
PERIOD hierarchy child of
defined for subject of

31
Compensation Planning Administration

This ERD (see Figure 10) illustrates the administration activities of compensation planning, which
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 11. Compensation Planning Administration ERD Entities and Tables
Entity Table
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

Title : Compensation Planning Administration
Author : Oracle, Confidential
allocated for
EMPLOYEE / AGENT
COMPENSATION BUDGET
has
ITEM FOR EMPLOYEE
located in salary plan has salary
COMPENSATION grade defined grade
CHANGE EFFECTIVITY salary in defined
COMPENSATION GUIDELINE
DATE defined in
DEFINITION
budget allocation for in
valid date for
have values for job code for
employed by
COMPENSATION CYCLE PLANNING PERIOD compensation location for JOB CODE
COMPENSATION
have REGION have part of
has used by defined for constrained by subject of defined for categorized
in
defined for COMPENSATION GUIDELINE TABLE
COMPENSATION BUDGET ITEM
subject of 2 factor 1 factor defined defined

defined defined for for
subject of type of constrained by
in in
defined for defined for grouping for
Figure 10. Compensation Planning Administration
user of component of for

used in used in JOB
EMPLOYEE ELIGIBILITY container for FAMILY
type for (PDQ) SALARY PLAN
COMPENSATION
type for COMPENSATION have
GUIDELINE salary grades for
COMPENSATION TYPE GUIDELINE SET FACTOR for
type of
category for
container for SALARY PLAN FOR
SALARY GRADE
JOB
COMPENSATION PLANNING PERIOD CATEGORY
salary plan for
used in defined for component of defined in defined for for

container for used by period for
PERIOD
QUARTERLY PERIOD SALARY GRADE
COMPENSATION BUDGET DEFINITION
defined for
POSITION
ANNUAL PERIOD sub-org of
used in
budget for support
have have manage by employer of
composed of
BUSINESS UNIT

33
Compensation Planning Execution

This ERD (see Figure 11) illustrates the execution phase of compensation planning. In this phase, 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 can grant to his employees. Authorized persons such as managers,
or HR personnel approve the plans. Totals are maintained for each manager and organization.
Table 12. Compensation Planning Execution ERD Entities and Tables
Entity Table
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

Oracle
"'+0

$

"$%$'$"*"'+

"$%$'$*"'+
2

1 3

113
"$%$
"$%$ '$ 1
'$ ""$% 213
2
2
313
513
"$%$
'$' 2 6
613
Figure 11. Compensation Planning Execution
6

3 3
21
"$%$+

3

"$%$

&!'$
!*$$ "$%$ 14 "$%$'$$$
!
+ ''$$$
!
!
2
3
"$%$
.&!
"*
14 "'+
"$%$
.&!
" 313
14
13 3
13 1
2 "$%$ .&%$%%
14 .&!
&$
2
"$%$ !*$$
14

&!'$.'
"$%$

&!'$%

35
Competency Management System

This ERD (see Figure 12) illustrates how 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
he or she complete those courses.
Table 13. Competency Management System ERD Entities and Tables
Entity Table
Career Path S_JOB_PRFL_TRNS
Competency, Competency Category, Root Competency S_CMPTNCY

Category
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

3"%3 7&'* $8$ %$
Oracle
*%%$' * $ "'+
0
$
*%%$'"".%9
13
!& $'7&'* $
%;<8$
9$%$!;!%

"$ + " "$ +


"'+ &$ "$ +

14

"'+ "$ +
9$
14
2613

26
? ? @
Figure 12. Competency Management System

3
"$ +

+ >;$

"$ +
+ >;$
% ' 9
%$

513
$$
&%

2
9
2
? 13
13
=.*'
=. !

3


313 6 5 6
3
37
Content Management
This ERD (see Figure 13) 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 can be the responsibility of, reviewed by, or approved by
one or more Positions.
Table 14. Content Management ERD Entities and Tables
Entity Table
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
Product S_PROD_INT

Title : Content Management
PICK LIST
CONTENT ITEM
TYPE
CONTENT
PROJECT picked via
ITEM
used by
viewed via VIEW

an example of used by
type for used by

MASTER DATA ITEM viewed via

Figure 13. Content Management
for managing
changes to LITERATURE CONTENT OBJECT
managed by part of picked via

OTHER MASTER
PRODUCT DATA ITEM used by
made
up of
generally responsible for

responsibility POSITION
of
generally the responsibility of picked via based on published via
responsible held by
for PERSON basis for
holder of generally picked via
controlled
CONTENT produced by BUSINESS
by
PROJECT OBJECT
owned by producer of
owner of generally followed used by
by
controlled by EAI
WORKFLOW PROCESS INTEGRATION
followed by OBJECT
used by used by
picked via
PICK APPLET
used by
picked via
used by

39
Contract Conditions
This ERD (see Figure 14) illustrates the usage of templates to create agreements. An agreement
could comprise one or more entitlements. A contracts administrator can 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 15. Contract Conditions ERD Entities and Tables
Entity Table
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

Template Benefit S_ENTL_BNFTTMPL
Template Condition S_ENTL_CONDTMPL
Template Term S_AGR_TERM_TMPL
Term S_AGR_TERM_DESC

Title : Contract Lifecycle Management
CONTRACT CONDITION
in reference to OBJECT
PRODUCT
TERM basis for
dependent upon
based on comprise
TEMPLATE TERM
used in
# TERM_NUM
applicable to CONDITION COMPLIANCE
# COMPL_NUM in reference to
subject of
in reference to
subject of
Figure 14. Contract Conditions
in reference to
CONDITION subject of
# SEQ_NUM in reference to
TEMPLATE CONDITION
# SEQ_NUM PRODUCT LINE
subject of
in context of belong to
applicable to
applicable to applicable to
composed of
governed by
TEMPLATE BENEFIT in reference to
based on # SEQ_NUM
BENEFIT
# SEQ_NUM subject of OBJECT CLASS
used by
in reference to subject of
correspond to applicable to
governed by used by composed of
based on ENTITLEMENT TEMPLATE

ENTITLEMENT
# NAME used by
# NAME
CATEGORY
applicable to
subject of subject of
comprise comprise
CONTRACT
AGREEMENT OTHER
CONTRACT

41
Contracts
This ERD (see Figure 15) 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 time frame. The customer is usually an account, but can 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 16. Contracts ERD Entities and Tables
Entity Table
Asset S_ASSET
Contract S_DOC_AGREE, S_DOC_QUOTE, S_ORDER
Contract Line Item S_AGREE_ITEM, S_QUOTE_ITEM, S_ORDER_ITEM
Deleted Contract Item S_ORDER_ITM_DEL, S_QUOTE_ITM_DEL, S_ASSET_DEL
Internal Product or Service S_PROD_INT

Title : Contracts
DELETED CONTRACT ITEM
for for
for
part of composed of subject of composed of subject of subject of
CONTRACT LINE ITEM

part of ASSET an instance of INTERNAL
Figure 15. Contracts
for PRODUCT OR
AGREEMENT LINE QUOTE LINE ITEM made into SERVICE
ITEM subject of
for
ORDER LINE ITEM subject of
priced by
pricing
method for
OTHER CONTRACT LINE ITEM
priced by
PRICE LIST
pricing for
part of
composed of
priced by
CONTRACT
default pricing for
applicable to subject to
AGREEMENT ORDER QUOTE
subject to for
OTHER CONTRACT
for ACCOUNT subject to PAYMENT
TERM
subject of for
responsibility of responsibility of involved by

employer of
responsible for responsible for primary contact for employed at
BUSINESS UNIT POSITION PERSON

43
Data Visibility
The main business entities represented (see 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 can be made up of smaller access groups and can
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 can 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 17. Data Visibility ERD Entities and Tables
Entity Table
Access Group S_PARTY
Account S_ORG_EXT
Activity S_EVT_ACT
Catalog S_CTLG
Category S_CTLG_CAT
Dynamic Account Hierarchy S_DYN_HRCHY
Dynamic Account Hierarchy Node S_DYN_HRCHY_REL
Group S_PARTY
Internal/Partner Organization Unit S_ORG_EXT
Literature Item S_LIT
Opportunity S_OPTY

Table 17. Data Visibility ERD Entities and Tables
Entity Table
Order S_ORDER
Organization Unit S_ORG_EXT, S_PARTY
Party S_PARTY
Product S_PROD_INT
Quote S_DOC_QUOTE

Figure 16. Data Visibility
!>13
Oracle "%!"

+

&%"!" '% @

&$+ 7& !
"$ '&"
1
!&
%> >+ 9 &%"
7&% !"
9"%
!" '
613
13
13

+

%$
"'+0
$ 9%$ %%
&

1

9+
1

&

$[$&$

9
$[$&$
%$
$$'0$
$[$&$
9
6 6 6
$$'0$

$[$&$
.&%$%%&$
@

9
&
@6

Dun & Bradstreet Integration

This ERD (see Figure 17) illustrates how Siebel Business Applications integrate with Dun & Bradstreet
Organization information. A D & B organization can be classified as doing business in one or more
industries, and can provide information about contacts at the organization and their management
responsibilities. In addition, a D & B organization can 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 18. Dun & Bradstreet Integration ERD Entities and Tables
Entity Table
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
Prospect S_PRSP_CONTACT

Title : Dun & Bradstreet Integration
48
D&B ORGANIZATION INDUSTRY CLASSIFICATION
ORGANIZATION INDUSTRY CLASSIFICATION
specifier of specifier of
classifier of classifier of
classification for
INDUSTRY
primarily a
classified banking
classified within direct
within customer of classification for
parent of
ORGANIZATION UNIT direct D&B STANDARD INDUSTRY

child of D&B ORGANIZATION
a bank for CLASSIFICATION
Figure 17. Dun & Bradstreet Integration
equivalent to equivalent to
parent of child of
domestic parent of domestic child of
global parent of global child of
CALL LIST D&B

of source of
ORGANIZATION
domestic global child
parent of of
D&B CONTACT RESPONSIBILITY

domestic
for child of composed of global
parent of
for of
affiliated with bearer of
created from
PROSPECT assigned to

CALL LIST OTHER D&B CONTACT D&B MANAGEMENT
PROSPECT RESPONSIBILITY TYPE
composed of
member in
Employee KPI
This ERD (see 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 19. Employee KPI ERD Entities and Tables
Entity Table
BUSINESS UNIT S_BU
EMPLOYEE PERFORMANCE S_EMP_PERF_MEAS

MEASUREMENT
GROUP, ACCESS GROUP S_PARTY
KEY PERFORMANCE INDICATOR S_KPI, S_KPI_AGRP

DEFINITION
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 S_CONTACT, S_EMP_PER, S_USER

PERSON

Figure 18. Employee KPI
Title : Employee KPI

KPI VALUE PERFORMANCE

FOR MEASUREMENT
OBJECTIVE contain value for ITEM
measured in
contain value for objective for

KPI VALUE FOR EMPLOYEE
user of defined for
KPI VALUE HISTORY subject of

used to
generate value history for history for
EMPLOYEE
for PERFORMANCE
source for has MEASUREMENT
KEY PERFORMANCE INDICATOR DEFINITION

measurement
of
approved by
accessed by
parent visibility node of approver of
PARTY child visibility node of
GROUP PERSON has have subject of

ORGANIZATION UNIT OTHER
have access to PARTY
DIVISION EMPLOYEE / AGENT
ACCESS GROUP
OTHER PERSON

Expense Reports
This ERD (see 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 can 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 20. Expense Reports ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
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
Party S_PARTY
Project S_PROJ

Figure 19. Expense Reports
Title : Expense Reports

incurred for
EXPENSE ITEM
PROJECT
subject of
incurred for
OPPORTUNITY
subject of
for
ACTIVITY
source of
incurred during
for
source of
subject of
of EXPENSE ITEM TYPE
classification for
made up of
part of PARTY
incurred for ORGANIZATION UNIT

subject of
involver of
PERSON OTHER
involved in
ORGANIZATION UNIT
incurred by
EMPLOYEE / OTHER
incurrer of AGENT PERSON
EXPENSE REPORT
APPROVAL
by
reported on
provider of
of
composed
of subject of
reported for INTERNAL
PERIOD ORGANIZATION /
EXPENSE REPORT
the reporting period for PARTNER
reported by
accounting approval by reporter of
approver of
charged to
charged with

Field Service Inventory

This ERD (see Figure 20) illustrates how Siebel Business Applications track field service parts
inventory. Parts can 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 can be located at a third-party provider, as well as
within the internal organization. They can also be related to other inventory locations for the
purposes of replenishment or fulfillment.
Table 21. Field Service Inventory ERD Entities and Tables
Entity Table

Asset S_ASSET
Inventory Location S_INVLOC
Inventory Transaction S_INV_TXN
Party 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

54
Title : Field Service Inventory
of
Author : Oracle, Confidential INVENTORY TRANSACTION INVENTORY
for TRANSACTION TYPE
ASSET (PRODUCT participates in SERIALIZED NON-SERIALIZED

INSTANCE) TRANSACTION TRANSACTION
for replenishment
replenished from source for made up part of
currently in
is a defines defines movement
inventory at
is affected movement to from INVENTORY LOCATION
status of
by is affected by
PRODUCT INVENTORY
WAREHOUSE VIRTUAL INVENTORY

LOCATION
type of counts product for
are counted via
Figure 20. Field Service Inventory
PRODUCT INVENTORY at
LOCATION PERSONAL (TRUNK) OTHER INVENTORY
stores
INVENTORY LOCATION LOCATION
of for
INVENTORY responsibility of
LOCATION TYPE type of
PERSON
for type of accessed by located responsibility visible
at replenished of to
affiliated holder of for
PRODUCT from
with
INVENTORY
ADDRESS
CATEGORY
responsible responsible for

held by for for
POSITION
an assembly of accessor of
a component of composed supplier responsible
of for of for
composed of located at
BUSINESS
PRODUCT OR SERVICE UNIT
is made into stored in located at
ORGANIZATION UNIT

PRODUCT INTERNAL INTERNAL/PARTNER OTHER
ORGANIZATION ORGANIZATION
NON-SERIALIZABLE SERIALIZABLE
sub-org
PRODUCT PRODUCT composed of of
Field Service Scheduler

This ERD (see 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 can 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 22. Field Service Scheduler ERD Entities and Tables
Entity Table

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
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

Figure 21. Field Service Scheduler

Title : Field Service Scheduler
above under
for within SCHEDULER
SCHEDULER RULE NODE SCHEDULER RULE RULE SET
subject of made up of
SERVICE user of
ACTIVITY SERVICE in SERVICE REGION
for
REQUEST used by
subject of for
assigned to SCHEDULER COST

FUNCTION
owner of VARIABLE
assigned to
EMPLOYEE defined for
assigned with
subject of
user of SCHEDULER COST

used by FUNCTION
EMPLOYEE
for
EXCEPTIONAL at
WORK HOURS
with
for
SCHEDULER TIME
in MAP DURATION
starting ending at
WORK SHIFT for for defined for

EXCEPTION HOUR subject of
ADDRESS user of
SCHEDULER
used by TIME MAP
defined for
in in in user of
for for
defined for
WORK SHIFT HOUR WORK SHIFT SCHEDULER
defined by PARAMETER
with with in
within
defined by for for for
for for used by made up of
WORK SHIFT EXCEPTION TIMEZONE

ZIPCODE SCHEDULER PARAMETER SET

Forecasts
This ERD (see 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 can be attributed
to different kinds of business transactions, and can be defined at any of a number of levels based on
business rules. These forecast items can be generated based on known revenue items. Forecasts that
managers make can contain items from the forecasts of their subordinates.
Table 23. Forecasts ERD Entities and Tables
Entity Table
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

Project S_PROJ
Quote S_DOC_QUOTE
Revenue Item S_REVN

58
Title : Forecasts
REVENUE ITEM generated for FORECAST ITEM DETAIL
forecasted via
manager's forecast of
for subordinator's forecast of
member of summary of subject of

FORECAST
FORECASTED ITEM member of original forecast of
Figure 22. Forecasts
for
subject of
PERSON
submitter of
defined by EMPLOYEE /
AGENT submitted by
author of
OTHER PERSON
for
ORGANIZATION UNIT
partner attributed to
for
OTHER
account attributed to ORGANIZATION
UNIT
for for for for for for for

for INTERNAL
ORGANIZATION
UNIT
owned by submitted for
attributed to governed by
attributed to attributed to attributed to
MARKETING AGREEMENT QUOTE PRODUCT OR owner of period for

EVENT OR SERVICE
ACTIVITY
POSITION FORECAST PERIOD
a report to
AGGREGATE
DIMENSION valid period for
manager of participant of
attributed to attributed to attributed to defined for

attributed to
aggregated by applicable to for subject of
OPPORTUNITY SERVICE REQUEST PROJECT PRODUCT LINE

FORECAST SERIES
High Tech Marketing Development Fund

This ERD (see 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 can 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 24. High Tech Marketing Development Fund ERD Entities and Tables
Entity Table
Account, Partner, Other Account S_ORG_EXT
Claim Item S_SRC_PAYITM
Claim, Payment, Other Payment S_SRC_PAYMENT
Event Item S_SRC_COST
General Fund S_MDF
Market Segment S_MKT_SEG

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

60
Title : High Tech Marketing Development Fund
Author : Oracle, Confidential made of
MARKETING EVENT OR
to part of
ACTIVITY
FUND ALLOCATION
recipient of
subject of
PARTNER EVENT
ACCOUNT ACTIVITY
defined for
target of
PARTNER
to available to
has OTHER
ACCOUNT
target of has
belongs to
EVENT ITEM
of has
subject of
subject of CLAIM ITEM
subject of defined for
POSITION for
MARKETING part of
DEVELOPMENT for
has
FUND belongs
PAYMENT has
designated to
for
CLAIM
Figure 23. High Tech Marketing Development Fund
PARTNER basis for

PARTNER for SPECIFIC
PROGRAM FUND .
OTHER PAYMENT
APPLICATION
belongs to OTHER MARKETING
EVENT OR ACTIVITY
for of
MARKET .
MDF TRANSACTION promoted via
SEGMENT
belongs to .
funded through DEBIT CREDIT earned by INTERNAL PRODUCT OR
SERVICE
for earned by earner of
PARTNER for part of PRODUCT
PROGRAM GENERAL earner of LINE
belongs to
FUND for promotion of composed of
subject of part of hierarchy parent of
for for promotion of

MDF hierarchy child of
SNAPSHOT . subject of

In-Memory Next Best Action

This ERD illustrates how organizations can provide contextual recommendations to their customers
on all channels using Siebel In-Memory Next Best Action. Siebel In-Memory Next Best Action
provides an open, flexible, and configurable integration framework between Siebel Contact Center
and Oracle Real-Time Decisions. A closed-loop Response Action Framework provides feedback on the
customer interaction in real time, and it tailors product recommendations to the actions that the
customer takes.
Table 25. In-Memory Next Best Action ERD Entities and Tables
Entity Table
Request S_RTD_REQUEST
Request Parameter S_RTD_REQ_ATTR
Request Recommendation Response S_REQ_RECO_RESP
Message Response Action S_PROD_MSG_RESP, S_MSG_RESP_ACTN
Message Response Action Parameter S_RESPACTN_PARM

Figure 24. In-Memory Next Best Action

Title : In Memory Next Best Action
Author : Oracle Confidential
REQUEST REQUEST PARAMETER
carry
sent with
for
has
RECOMMENDATION TYPE RECOMMENDATION
for
refer to
may have
against
RESPONSE TYPE RESPONSE

for
belongs to
can have
for
ACTION ACTION PARAMETER
may have
belongs to

Invoiceable Charges
This ERD (see Figure 25) 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 26. Invoiceable Charges ERD Entities and Tables
Entity Table
Activity S_EVT_ACT

Agreement Entitlement S_ENTLMNT
Agreement Line Item S_AGREE_ITEM
Asset S_ASSET
Auction Item S_AUC_ITEM
Expense Item S_EXP_ITEM
Financial Account S_ASSET
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
Project Item S_PROJITEM
Project Team Role S_PROJ_RSRC

Table 26. Invoiceable Charges ERD Entities and Tables
Entity Table
Shipment S_SHIPMENT
Time Sheet Item S_TMSHT_ITEM

Title : Invoiceable Charges
for charged via
INVOICEABLE CHARGE FINANCIAL ACCOUNT
for charged via SERVICE
REQUEST
for charged via
Figure 25.
INVOICE ITEM
TIME SHEET ITEM
RECONCILIATION ENTRY
for charged via
INVOICE ITEM EXPENSE ITEM
DETAIL for
PART REPAIR
for for charged via
INVOICE ITEM for charged via
AGREEMENT
INVOICEABLE
CHARGE subject of based on basis of part of
AGREEMENT
for
ENTITLEMENT made up of
invoiced into ACTIVITY
charged via based on
for
composed of
Invoiceable Charges
ASSET basis for

charged via part of
for
AGREEMENT made up of
charged via LINE ITEM
part of for
AUCTION ITEM
charged via
subject of for
for charged via PART MOVEMENT
part of
INVOICE ITEM ACTIVITY ORDER SHIPMENT
for PART PART
PROJECT
ITEM MOVEMENT MOVEMENT composed of
charged via
part of for
PROJECT for object for
charged via TEAM ROLE of
PAYMENT
for fulfilled by charged via
PRODUCT OR
of
SERVICE
fulfilled by ORDER LINE ordered on
for
ITEM part of
for charged via ORDER
composed of
based on charged via
for PAYMENT TERM
billed to billed to for billed to
made up of made for

for PARTY charged via
for
INVOICE ORGANIZATION UNIT OTHER
ADDRESS for PARTY
ACCOUNT OTHER
located at primary billing contact of
ORGANIZATION
UNIT PERSON
for subject of

billed to contact of
65
Invoices
This ERD (see Figure 26) illustrates the invoicing and payment processes. An invoice can be
considered a receivable or a payable for the company. It can 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 can be reconciled with one
or more other entities as well. A payment can be made for one or more Invoices, and an invoice can
be paid through one or more payments.
Table 27. Invoices ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Expense S_EXP_ITEM
Invoice S_INVOICE
Invoice Attachment S_INVOICE_ATT
Order S_ORDER
Part Movement S_ORDPART_MVMT
Part Repair S_PART_RPR
Period S_PERIOD
Product S_PROD_INT
Project S_PROJ
Shipment S_SHIPMENT

Title : Invoices
INVOICE ATTACHMENT PAYMENT
made for
for
source for fulfilled by
INVOICE
Figure 26. Invoices
OTHER INVOICE RECEIVABLE INVOICE PAYABLE INVOICE
composed billed via generated for

based on
of
part of for generated generated generated generated generated generated

for for for for for for
INVOICE ITEM reason for
for
PROJECT
reason for reason for
PAYMENT
AGREEMENT TERM
PERIOD
billed via reason for
for
ACTIVITY
UNIT OF detail for
for billed via LABOR for
reason for
for billed via
SERVICE REQUEST
for billed via reason for
PART REPAIR
for billed via
billed via reason for
EXPENSE
for ORDER
for billed via

part of
billed via
ORDER ITEM
composed of
for fulfillment for
PART MOVEMENT
fulfilled by part of
of
for SHIPMENT
SHIPPED PART
composed
billed via
of
object for
ordered on for
for billed via
PRODUCT

67
Lead Management
This ERD (see Figure 27) illustrates how the lead management process is supported. A lead refers to
a new prospect or an existing customer who is interested in certain products or services and can be
converted into an Opportunity. A lead can be generated as a result of a marketing campaign, a
marketing offer or other marketing activities. A lead can be referred by a partner organization. A
lead can be assigned to internal team members or partners. Responses or various activities are
tracked for each lead.
Steps in the lead management process include:
Lead Entity. Views for sales users to create leads which are distinct from contacts/prospects,
responses and opportunities, and manage their leads.
Lead Import. Import lists of customers, prospects, responses or leads from an outside party or
another internal source.
Lead Quality Control. Rule-based user interface that enables the business user to create a
formula or set of rules that compute a score for a lead
Lead Assignment. Lead-assignment rule system that can be fully administered by a sales
operations user or sales manager. Leads can also be assigned to partner organizations or partner
users.
Lead Conversion. End-user actions to convert a lead into an opportunity, quote or order in one
step, reject the lead or retire the lead.
Table 28. Lead Management ERD Entities and Tables
Entity Table
Lead S_LEAD
Lead Note S_NOTE_LEAD
Opportunity S_OPTY
Product S_PROD_INT
Marketing Import Task S_MKT_IMPRT_TSK
Lead Source S_SRC
Campaign Contact S_CAMP_CON
Marketing Offer S_DMND_CRTN_PRG
Response S_COMMUNICATION
Activity S_EVT_ACT
Prospect Contact S_PRSP_CONTACT
Contact S_CONTACT
Business Unit S_BU

Table 28. Lead Management ERD Entities and Tables
Entity Table
Position S_POSTN
Account S_ORG_EXT
Internal Organization S_ORG_EXT
Partner Organization S_ORG_EXT
Assigned External Organization S_ORG_EXT

Title : Lead Management
70
Author : Oracle ,Confidential
OPPORTUNITY
PARTY
generated
Figure 27. Lead Management
primary for BUSINESS

from UNIT
owns
POSITION
PRODUCT LEAD DEMAND OTHER ORGANIZATION
SOURCE CREATION responsible
PROGRAM for
consideration primary for INTERNAL PARTNER
source
of for generates
PROSPECT CONTACT refers
CONTACT ACCOUNT owns
ASSIGNED
MARKETING EXTERNAL
IMPORT TASK creates
CAMPAIGN creates
CONTACT
involver of reponsible
imports for
generates
considered turns belongs

on created generated into involved assigned referred
discovered for for to belongs
via generated from under in to by
from by to
for for
attached
to
LEAD NOTE LEAD
subject
of
generated
RESPONSE for
subject
of
ACTIVITY
subject of
generated
for

Marketing Budget Request

This ERD (see Figure 28) 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 29. Marketing Budget Request ERD Entities and Table
Entity Table(s)
Budget Request S_MKTG_BDGT_REQ
Purchase Request S_ORDER
Marketing Plan S_SRC
Marketing Fund S_MDF
Marketing Tactics S_SRC
Tactics Expense S_SRC_COST
Purchase Request Line Item S_ORDER_ITEM

72
%8$% "5.?
Oracle
14
14
"<$
%
"<$
!>'"$*&$!
$> 14 13
1
14
& 9% "<$

'$
7&%'$
Figure 28. Marketing Budget Request
"
14

14
2
.&!
7&%
& 9%7&%
13 1

$

2
1 1 13 1
13
14 2
"<$
$!&%+ !
*&$!
14 14
.&%$%%&$ %$ !& !& '$

Marketing Campaign
This ERD (see Figure 29) illustrates campaign management, execution, and evolution. Campaign
management can 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 can 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 can 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 30. Marketing Campaign ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Call List Member S_CALL_LST_CON
Campaign Call List S_CAMP_CALL_LST
Fulfillment Recipient S_FUL_RECIP
Fulfillment Request S_EVT_FUL_REQ
Fulfillment Request Item S_FUL_REQ_ITEM
Opportunity S_OPTY
Opportunity Contact S_OPTY_CON
Order S_ORDER
Prospective Contact S_PRSP_CONTACT
Territory S_ASGN_GRP

74
Title : Marketing Campaign OPPORTUNITY CONTACT
Author :Oracle, Confidential
associated with
for of
RESPONSE generated by CAMPAIGN CONTACT
targeted at ORDER originator of
generated by originator of
ACTIVITY OPPORTUNITY
generated by originator of
for primarily from
initiated by
MARKETING EVENT OR ACTIVITY of of
part of initiator of CALL LIST
introduction to targeted at MEMBER

conducted as
MARKETING CAMPAIGN
FULFILLMENT of source of
RECIPIENT FULFILLMENT in
for made up of
REQUEST part of of
Figure 29. Marketing Campaign
of
addressed to
subject of CALL LIST
part of
FULFILLMENT
REQUEST ITEM made up
of
of LITERATURE relevant to MARKETING

ITEM SEGMENT
subject of promoted via
CAMPAIGN responsibility of user of

TEAM MEMBER PURCHASED
for
LIST
NOTE OTHER
subject of
MARKETING
assigned to EVENT OR
ACTIVITY
TERRITORY focus of part of
used in
role played by
managed within
POSITION assigned to made
part of
of
assigned to
assigned to
made up of
responsible for a report to
for of subject
assigned to sell in
for of
ORGANIZATION UNIT subject
composed of a parent CAMPAIGN CALL LIST subject of
to of
PERSON
PROSPECTIVE CONTACT

recipient of
OTHER PERSON
Marketing Collaboration
Collaborative marketing (see Figure 30) assists marketers in maintaining the balance between the
need for consistent customer management among partners and effective brand building with local
expertise. It includes 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 31. Marketing Collaboration ERD Entities and Tables
Entity Table
Internal Partner/Organization S_ORG_EXT, S_PARTY
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

Figure 30. Marketing Collaboration

Title : Marketing Collaboration
Author : Oracle, Confidential PARTY
ORGANIZATION UNIT
responsible for
PARTNER INTERNAL /
ORDER
responsibility of ORGANIZATION PARTNER
collaborating on
ORGANIZATION
item of collaboration for
generated from basis for based on
responsible for
QUOTE
responsibility of collaborating on
generated from
lead to
responsible for
OPPORTUNITY

generated from

RESPONSE collaborating on
responsibility of
responsible for
created for
source of source of source of

MARKETING EVENT OR ACTIVITY
OTHER ORGANIZATION UNIT

responsible for
OTHER PARTY

Marketing Encyclopedia
This ERD (see Figure 31) illustrates how Siebel Business Applications track competitive information
about products and companies. A standard set of metrics can 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 can be associated both with organizations and with products. The relevance of key decision
issues to the various competitive metrics can be defined.
Table 32. Marketing Encyclopedia ERD Entities and Tables
Entity Table
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
Product Comparison S_PROD_CMP
Product Detail S_PROD_SPEC
Product External S_PROD_EXT
Product Literature S_PROD_LIT

78
Title : Marketing Encyclopedia
COMPETITIVE PRODUCT PRODUCT COMPARISON PRODUCT COMPANY COMPETITIVE

PRODUCT DETAIL LITERATURE LITERATURE COMPANY
FEATURE FEATURE
of for of of to about usage of usage of about for of

Figure 31. Marketing Encyclopedia
subject of characterized by
competitor of competitor of subject of reference to reference to
PRODUCT OR SERVICE LITERATURE ITEM
INTERNAL PRODUCT EXTERNAL

OR SERVICE PRODUCT
produced by
DECISION
ISSUE
vendor of subject of subject of

relevant to
ORGANIZATION UNIT
INTERNAL / PARTNER EXTERNAL ORGANIZATION UNIT

ORGANIZATION UNIT
subject of
COMPETITIVE METRIC
classification for
classification for

COMPETITIVE PRODUCT METRIC COMPETITIVE COMPANY METRIC
Marketing Event Driven Dialogue

The Event Driven Dialogue feature helps enable timely sales and services designed around specific
customer needs. Specific events are tracked for different customers and these events are used to
trigger appropriate program stages for the marketing program. This ERD (see Figure 32) illustrates
the various relationships between Marketing Program, Stage, and Event Triggers. The wait period
between stages is also tracked.
Table 33. Marketing Event Drive Dialogue ERD Entities and Tables
Entity Table
Action List S_MKTPRGACT_LST
Event Trigger S_MKT_EVT_TRG
Event Trigger History S_MKTEVTRG_HST
Event Trigger Mapping S_MKTEVTRG_MAP
Lead Source S_SRC
Marketing Campaign S_SRC
Marketing Program S_SRC
Marketing Program Action S_SRC
Marketing Stage S_SRC
Marketing Stage Wait S_MKT_STGWAIT, S_MKT_STGWT_REL

Offer S_DMND_CRTN_PRG
Party S_PARTY
Person S_CONTACT
Position S_POSTN

Title : Marketing Event-Driven Dialogue
80
PARTY
target of CALL LIST

attached made up PERSON
CAMPAIGN CONTACT OFFER
for of subject of
from
OTHER PERSON
RESPONSE of
of
subject of
of
subject of
PROSPECT
created for CONTACT
EVENT
TRIGGER ACTION LIST
EVENT TRIGGER HISTORY for
subject of
part of for
associated with
consists of
POSITION
for
EVENT
Figure 32. Marketing Event Driven Dialogue
MARKETING
TRIGGER PROGRAM ACTION
MAPPING MARKETING
STAGE WAIT
related by
for
belongs to
for
LEAD SOURCE associated subject of

for with subject of subject of
source of
MARKETING
CAMPAIGN
MARKETING MARKETING STAGE
EVENT OR
ACTIVITY
belongs to
belongs to
promoted
vehicle subject of subject of
MARKETING PROGRAM

Marketing Events
This ERD (see Figure 33) illustrates how Siebel Business Applications support marketing events and
activities planning. A marketing event can 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 can 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 can then register for the event or
even for specific sessions. Attendees can be quoted registration prices through a quote and purchase
tickets to the event through an order.
Table 34. Marketing Events ERD Entities and Tables
Entity Table
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

Location Room S_EVTLOC_ROOM
Order S_ORDER
Parent Event S_SRC_EVT, S_SRC
Quote S_DOC_QUOTE
Room Avail Equipment S_EVTLOC_RM_EQP
Travel Participant S_EVT_TRVL_PER

Table 34. Marketing Events ERD Entities and Tables
Entity Table
Travel Plan S_EVT_TRVL_PLAN
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

reviewed by reviewer of
Title : Marketing Event VENDOR VENDOR VENDOR PERSON
Author : Oracle, Confidential OFFER SERVICE REVIEW
offered by offered by for

TRAVEL PLAN TRAVEL
provider of provider of subject of have PARTICIPANT a member of Figure 33.
service participate classified as
EVENT VENDOR
serviced by
for incur incur created for
VENUE VENUE VENUE
belong to OFFER SERVICE REVIEW
reviewed by incurred by associated with reviewer of
offered at offered by for EVENT COST
Marketing Events
subject of provider of subject of

incurred by
EVENT VENUE ACTIVITY EQUIPMENT
REQUIREMENT
location of
of
for required by
subject of in need of incur have
held at subject of staffed by on staff for
MARKETING EVENT OR ACTIVITY inviter of invited to
for for
parent company of OTHER MARKETING EVENT EVENT PARENT
EVENT OR ACTIVITY SESSION composed of EVENT EVENT
composed of for for
REGISTRATION
ORGANIZATION held at ATTENDEE
uses responsibility of subject of
UNIT ROOM EQUIPMENT promoted via
AVAILABILITY WAIT LIST
available in
CANCELLED
auction REGISTRANT CONTRACT
price list
location of for responsible for relevant to
use equipped with recipient of ORDER
ordered by
LOCATION ROOM PRICE POSITION LITERATURE
LIST ITEM for QUOTE
CONTRACT LINE ITEM
for composed of
in
for OTHER
CONTRACT
used by for supplier of subject of
EVENT LOCATION PRODUCT OR SERVICE
VENUE EVENT PRODUCT OTHER PRODUCT OR

OTHER LOC
SERVICE

83
Marketing Plans
This ERD (see Figure 34) 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 top-level
plan. Funds can also be allocated for different plans in different periods and used as inputs for
accounting purposes or in financial calculations.
Table 35. Marketing Plans ERD Entities and Tables
Entity Table
Marketing Event Cost S_SRC_COST
Marketing Event or Activity, Marketing Plan, Other Marketing Plan S_SRC

or Activity
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

Title : Marketing Plans
PLANNED attributed to
MARKETING MARKETING EVENT
DEVELOPMENT has OR ACTIVITY
FUND ALLOC MARKETING
GOAL
MARKETING
PLAN
estimated for
Figure 34. Marketing Plans
consists of
INVOICE ITEM MARKETING attributed to

EVENT COST
incur
part of basis of
made up of based on created from
PRODUCT
PROMOTION source of
INVOICE
promotion item for created for
defined for
PRODUCT OR SERVICE
has belong to
valid in launched in
defined for
reserved from defined for launch of
source of compose of
defined for the budget of
PERIOD
MARKETING valid in owner for valid in
DEVELOPMENT defined for
FUND type of
FOR
for BUDGET
REQUEST SUBJECT OF
uses
OTHER
CALL LIST CAMPAIGN
source of created for MARKETING
CALL LIST EVENT OR
created from requirer of ACTIVITY

used for
user of
85
Marketing Program
This ERD (see Figure 35) 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
can be defined on measures and attributes by using 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 can 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 can 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 36. Marketing Program ERD Entities and Tables
Entity Table
Assignment Rule Group S_ASGN_RULE_GRP

Campaign Allocation S_CAMP_CALL_LST
Campaign Load S_CAMP_LD_WAVE
Campaign Offer S_SRC_OFFR
Campaign Wave S_DD_CAMP_WAVE
Contact Status S_ SRCDCP_CONSTA
Deal S_DEAL
Filter S_DD_FILTER
Filter Clause S_DD_FILTER_DTL
Load Wave S_CAMP_LD_WAVE

Table 36. Marketing Program ERD Entities and Tables
Entity Table
Marketing Activity S_SRC
Marketing Segment S_CALL_LST
Offer S_MKTG_OFFR
Offer Media Package S_DMND_CRTN_PKG
Program Segment S_CAMP_CALL_LST
Prospective Contact S_PRSP_CONTACT
Purchased List S_CALL_LST

88
"
$ $ +
%$
14
'''%

9
13 & 9%! %$
'%

"
%
"$ % >
%
"$ $
14

' '!%&
14 %$

$[$
Figure 35. Marketing Program
&$
"<$
"
$ 2
"<$

'!;> >$
2
"
$'%
!%.&$
1 2

"
$'! 14
14
1 "<$

'$
14
3
%& !
"<$
'"$
**"! <
"
$ %

;> 14

14
2
2
** 2 "
$** %& !
"<$

*"

"

!& %>


1 .&%$%%&$ "5
Oracle
6
Marketing Resource Management: Document

This ERD (see Figure 36) 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 37. Marketing Resource Management: Document ERD Entities and Tables
Entity Table
Marketing Material S_CB_ASSET
Material Inventory by Location S_MKTG_DOC_INVT
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

""! "
90
Oracle
>$!.!!$
"

"'$>$+.+' $

1 33 "*&'*'' 14

2 >$!.!!$
7&%
9"$ "'
*&'*''"$"
2 13

$ >$ 3
' $
1
3
13 2
8$'

$[$
"'*&'*IL'"$7&%
6
1
14
Figure 36. Marketing Resource Management: Document
"<$
"'

**
! &"$ '!%& ! &"$ =
! &"$

** "
$

2
2 2
**"! '!%&
<
=

Opportunity Management
This ERD (see Figure 37) illustrates the significant entities related to an opportunity (or lead),
including relationships to contacts, employees (generally sales representatives), products, accounts,
and so on.
Table 38. Opportunity Management ERD Entities and Tables
Entity Table

Event S_EVT_ACT
External Organization Unit S_ORG_EXT, S_PARTY
Issue S_ISS
Opportunity S_OPTY
Opportunity Relationship S_OPTY_REL
Product S_PROD_INT
Quote S_DOC_QUOTE
Sales Stage S_STG
Source S_SRC

Title : Opportunity Management
92
ADDRESS
for for
located at
in partnership with a partner to a report to a parent to located at
ORGANIZATION UNIT PERSON

OTHER ORGANIZATION UNIT
INTERNAL / PARTNER composed of
ORGANIZATION UNIT OTHER EMPLOYEE /

affiliated with PERSON AGENT
involved on vendor of
SALES DOCUMENT
MARKETING EVENT OR
Figure 37. Opportunity Management
ACTIVITY based on
QUOTE AGREEMENT CORRESPONDENCE
basis for
initiator of
for
SALES PRODUCT owned by
METHODOLOGY STRUCTURE OPPORTUNITY ISSUE resource for
targeted at
driven by of for EVENT ACTIVITY subject of
composed of relevant to relevance of
performed by
a collection of performer of
produced by
a component of relevant as
owned by
PRODUCT OR ISSUE
SERVICE responsible for
for a report to
consideration on
considered on
SALES
TERRITORY OPPORTUNITY
STAGE part of part of RELATIONSHIP
on manager of
classification of
made up of for of
within made up of
involver of driver of subject of
classified in source of involver of
initiated by subject to

consideration of subject to
part of collection of
OPPORTUNITY
Order and Promotion

This ERD (see Figure 38) describes the relationship between Product Promotions and Order, Quote
and Assets.
Table 39. Order and Promotion ERD Entities and Tables
Entity Table
Asset S_ASSET
Product Promotion S_PROD_INT
Product Promotion Item S_PROM_ITEM
Product Promotion Operation S_PROM_OPER
Quote Item S_QUOTE_ITEM

Figure 38. Order and PromotionOrder Life Cycle

Title : Order and Promotion
ORDER ITEM
for uses for
QUOTE ITEM
for for uses
has has used by used by
ASSET has PRODUCT PROMOTION ITEM PRODUCT PROMOTION

OPERATION
for
has made up defined for
PRODUCT
associated to contain associated to has associated to
PRODUCT PROMOTION

Order Life Cycle

This ERD (see Figure 39) 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 can 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 40. Order Life Cycle ERD Entities and Tables
Entity Table
Invoice S_INVOICE
Opportunity S_OPTY
Opportunity Product S_REVN
Order S_ORDER
Order Part Movement S_ORDPART_MVMT
Quote S_DOC_QUOTE

Shipment S_SHIPMENT

Title : Order Life Cycle
96
ACCOUNT
target of receiver of target of billed via
of taken for has for

lead to prepared for

OPPORTUNITY ORDER INVOICE
Figure 39. Order Life Cycle
for original order for

QUOTE reason for
lead to lead to generated for part of made up of
for created from SHIPMENT

composed of has
consideration of purchase of composed of billed via for
backup order for
vehicle for fulfillment of
original item for composed of subject of
part of part of
for part of for
for
ORDER PART MOVEMENT
OPPORTUNITY on
composed of QUOTE ITEM ORDER ITEM INVOICE ITEM
PRODUCT billed via
base item for
composed of has for from
OTHER PART SHIP
for MOVEMENT MVMT
part of billed via
lead to has
composed of RECEIPT
for has MVMT
for
original item for
fulfilled by
of of ALLOCATION
base item for
a step toward the
has of fulfillment of
of preceded by followed by
considered for purchase on

quoted for purchase on ordered on billed via delivered by
PRODUCT OR SERVICE
Orders
This ERD (see Figure 40) 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 can be assigned or credited to one or more
positions.
Table 41. Orders ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Asset S_ASSET
Inventory Transaction S_INV_TXN
Inventory Transaction Type S_INV_TXN_TYPE
Order S_ORDER
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

98
Title : Orders
PART MOVEMENT
proceded by followed by
ACTIVITY PART OTHER PART
INVENTORY result of ORDER PART MOVEMENT MOVEMENT MOVEMENT
TRANSACTION
cause of
Figure 40. Orders
of for
of of of
for to from
fulfilled by
subject to
for
for part of for
ASSET
ORDER ITEM
subject of PART subject of
INVENTORY
an instance of MOVEMENT
TRANSACTION
made into moved on TYPE
TYPE for ACTIVITY
composed of
PRODUCT
subject of
part of related to
composed of part of composed of
related to
ORDER of
ORDER TYPE
for
SALES ORDER destination of source of
from
INVENTORY LOCATION
to source of
SERVICE ORDER destination of
PARTY
ORGANIZATION UNIT
PURCHASE ORDER responsibility of
INTERNAL/PARTNER ORGANIZATION
responsible for
for
customer of
OTHER ORGANIZATION
RMA
responsibility of
POSITION OTHER
responsible for PARTY

OTHER ORDER
for
PERSON
primary contact for
Partner Collaboration
Partner collaboration (see Figure 41) 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 might want to add the resource to a project or an opportunity.
Table 42. Partner Collaboration ERD Entities and Tables
Entity Table
Business Unit S_BU
Collaboration S_PARTY_GROUP
Collaboration Resource S_PARTY_PER
Collaboration Invitation S_BRDCST_MSG
Party S_PARTY
Position S_POSTN

1
100
Oracle,
.&%$%%$% $""".
.&%$%%$%^%$%.' .&%$%%$%^%$%.'

%$
$[$
1 313 313

.&%$%%$% $
+
Figure 41. Partner Collaboration
3
$[$&$
''.$%9!%&
%$ 3

%9!%$* ''.$
$$'0$

$[$

%9!
$[$* ''.$

''.$

1
"%%

''.$$>$
14

13

9
$[O$
&$

9"%%
9+
Partner Program Registration

Partner Program Registration (see Figure 42) 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 43. Partner Program Registration ERD Entities and Tables
Entity Table
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

Oracle, '$
&

$
"
102
14

'&"
14
' $ '' ' $

7&%$ % &$ 9"$ !& '$
$%;

"<
%
"$

2 2

''% 9 !!$!

"

$
"' $
6
14
2 1 113

13
$
""".%9
14
Figure 42. Partner Program Registration
.%
"

>''%
14

'
.'+'%
14

' $
>'" $;'%
14

6

3 1

1
$ d

6 6 $
"
'

+
&
"
.&%$%%&$

%$

"" '
'

+

Party Model
This ERD (see Figure 43) 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 can be an employee or agent of the company using
Siebel Business Applications. A person can 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 can be tracked for a person, a household, or an organization.
Table 44. Party Model ERD Entities and Tables
Entity Table
Business Address S_ADDR_ORG (Siebel Cross-Industry Applications)

Group S_PARTY
Household S_ORG_GROUP, S_PARTY
Organization Relationship S_ORG_REL (Siebel Cross-Industry Applications)

S_PARTY_REL (Siebel Industry Applications)
Party S_PARTY
Party Relationship S_PARTY_REL

Person Relationship S_PARTY_REL or S_CONTACT_REL
User List S_PARTY
User Login S_USER
Figure 43. Party Model
3"

Oracle
+'$%9
%$'$%9
!!%%
%$'!!%% .&%$%%!!%%
$[$'$%9

9'$%9

6

+

&
%%
%$ 9&%9'! &%'%
&
1
"'+0

$ %$ 9
&

1

$[$&$
9
%$ &$
9+

9
$[$&$

&%'
$
Payments
This ERD (see Figure 44) 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 can be made to directly settle an order
or to settle one or more Invoices. An invoice can be paid through one or more payments. A payment
can be taken as a deduction from a prepayment balance available to the paying party.
Table 45. Payments ERD Entities and Tables
Entity Table

Invoice S_INVOICE
Order S_ORDER
Party S_PARTY
Prepayment Balance S_PREPAY_BAL
Figure 44. Payments

Title : Payments
INVOICE
PAYMENT
in settlement of
paid by
generated for
INBOUND PAYMENT
billed via
in settlement of ORDER
paid by
received from
debited from
PREPAYMENT
source of BALANCE
OUTBOUND PAYMENT
ADDRESS
addressed to
used in available to
paid to addressed to
for
located at entitled to
receiver of
PARTY
PERSON
source for receiver of
ORGANIZATION UNIT
OTHER ACCOUNT
ORGANIZATION
Performance Review
This ERD (see Figure 45) 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 can consist 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.
Optionally, an employee can 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 can 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 46. Performance Review ERD Entities and Tables
Entity Table
360 Evaluation S_PERF_360_EVAL
Competency S_CMPTNCY
Employee Criteria (PDQ) S_APP_VER, S_RVW_360_CS
Evaluation Script S_CS_PATH, S_CS_PATH_SCPT

Evaluation Script Answer S_CS_RUN, S_CS_RUN_ANSWR
Job Family S_JOB_FAMILY
Party S_PARTY
Performance Measurement Item S_PERF_MEAS_ITM
Performance Review S_EMP_PERF_MEAS
Period S_PERIOD
Review Component S_PERF_RVW_CMP
Review Component Language S_RVW_COMP_LANG
Review For Skill Item S_PERF_CMPTNCY
Table 46. Performance Review ERD Entities and Tables
Entity Table
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
26
Oracle
*"$ "%&"$"
>;*%<''" *"$ *"$

.= > >;"
26 1 1

>'&$% 142 1 1
$%; 14
>;"
6 "$ +
2 3

|}~>'&$ >;"' "$$

3 >; "$$
Figure 45. Performance Review

213
?

2
>'&$%
14 >; >;$

$
% ' >; "$$
1 313 "$$ +
'$
&

"'+*"$

"%&"$
1 >;"'
"'+ ! >;
*"$ >;
"'+ ". $$&'>; 9>;+

9"'+
`!7{ *"$
"%&"$ 1 1 1
!
14

"'+ &%"
%%* $%
!+ =.*"'+
2

2
+
%$
14 9%$
2 14

$[$&$
$$'0$
"'+0
$ %$
$[$
13
313
.&%$%%&$ 9
$[$
3

109
Personal Account
This ERD (see Figure 46) 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 47. Personal Account ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Opportunity S_OPTY
Personal Account S_ASSET
Personal Account Contact S_ASSET_CON
Product S_PROD_INT
Figure 46. Personal Account

Title : Personal Account
Author : Oracle, Confidential PERSONAL
ADDRESS
PERSONAL ACCOUNT CONTACT
user of
used by
for party on
for OPPORTUNITY SERVICE REQUEST

ACTIVITY
source of
defined for
source of applicable to
accessed by subject of derived from subject of
PERSONAL ACCOUNT
user of
used by
part of parent of of
subject of
PRODUCT OR SERVICE
named as
ORGANIZATION UNIT
CONTACT
member of GROUP
made up of
by owner of
ADDRESS ACCOUNT
USAGE user of defined for
by
user of
of
subject of
Personal Financial Review

This ERD (see Figure 47) 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 can be located at
a personal address and can be a source of income. Similarly, a liability, such as a mortgage, can be
secured by an associated asset and can have periodic expenses associated with the liability.
Table 48. Personal Financial Review ERD Entities and Tables
Entity Table
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 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
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
Title : Personal Financial Review
PRODUCT OR SERVICE ORGANIZATION UNIT ORG MEMBER CONTACT HOUSEHOLD/

RELATIONSHIP ACCOUNT
vendor of made up of
produced by in
owns
subject of subject of of of
considered on to defined for made up of
vendor of source of
consideration of owned by
part of member of has has head of member of
made of of
OPPORTUNITY owned by
because of PRODUCT INSTANCE CONTACT
owns
affects
associated with of PROD. INST. with
source of CONTACT associated to
from is a
subject of
of subject of
RCIVD PROD. INST.
Figure 47. Personal Financial Review
with
primary subject of
part of made up of of NEED CONTACT with jointly has
of of
FINANCIAL NEED has
with owns
is addressed by
ASSET LIAB. with associated to
communicated during ACTIVITY PROD. CONTACT has has participates in
INST. subject of
located at
with
from is primarily incurred by
of of INC. EXP.
of managed by INCOME (EXPENSE) CONTACT
owned by incurred by
addresses is a associated with
of for
ASSET (LIABILITY) because of reported during
source of PERSONAL ADDRESS
ADDRESSED NEED of location of
subject of located at
on has a reported during

to review part of
to review
of ACTIVITY
to understand made up of in
FINANCIAL
for REVIEW ACTIVITY CONTACT
for source of for PROCESS
regarding involves
subject of recommended during
FINANCIAL RECOMMENDATION source of in
for
RECOMMENDATION CONTACT
of
with

113
Pricing
This ERD (see Figure 48) 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 can be adjusted for certain extended attributes
as defined in a specified pricing matrix. They can be adjusted based on changes to a customizable
product through component price adjustments. They can also be modified through a specified pricing
model made up of pricing factors.
Table 49. Pricing ERD Entities and Tables
Entity Table
Component Price Adjustment S_PRI_CFG_ITEM
Object Class Extended Attribute S_XA_ATTR
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 Structure S_PROD_ITEM
Title : Pricing
an adjustment for INTERNAL

COMPONENT PRICE PRODUCT OR
ADJUSTMENT the subject of SERVICE
for
Figure 48. Pricing
for PRODUCT OR
an assembly of
adjusted via SERVICE of
STRUCTURE
PRICE LIST of a component of
ITEM
subject of
PRICE LIST
for
composed of PRICING FACTOR

ITEM ATTRIB
configured via
constraint for
constrained by
PRICING MATRIX
VALUE defined for
PRICING FACTOR ITEM
referenced by
priced via
for for
PRODUCT
for EXTENDED
subject of described by
ATTRIBUTE
PRICING MATRIX PRICING MATRIX made up of classified as
ITEM ATTRIBUTE
based on
PRICING MODEL
FACTOR subclass of
part of classification for
for
used by
based on for OBJECT CLASS

made up of
used by parent class of
made up of basis of
PRICING MATRIX
PRICING MODEL
OBJECT CLASS
EXTENDED
for
ATTRIBUTE
described by
of object class
have types

115
Pricing Comparison
This ERD (see Figure 49) 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 50. Pricing Comparison ERD Entities and Tables
Entity Table
Object Class Extended Attribute S_XA_ATTR
Opportunity S_OPPTY
Pricing Matrix S_PRI_MTRX
Pricing Matrix Item S_PRI_MTRX_ITEM
Product Extended Attribute S_PROD_INT_XA
Product or Service Structure S_PROD_ITEM

Quote S_DOC_QUOTE

Quote Item Extended Attribute S_QUOTE_ITEM_XA
Tier Price Value S_VDISCNT_ITEM
Tier Pricing S_VOL_DISCNT
Figure 49. Pricing Comparison

Title : Pricing Comparison
for
PRICE LIST ITEM PRODUCT OR
subject of
part of SERVICE
COMPETITOR composed of
ITEM QUOTE ITEM QUOTE ITEM
EXTENDED for quotation for
ATTRIBUTE
described subject of
by
comparison for
for
compared to composed of
INTERNAL QUOTE OPPORTUNITY

ITEM for
COMPETITOR
subject
COMPARISON of
priced via
for priced via

for
composed of used by PRODUCT OR
SERVICE assembly
STRUCTURE of
PRICE LIST of
COMPETITOR INTERNAL PRICE
LIST component
PRICE LIST
of
PRODUCT
EXTENDED for
TIER PRICE VALUE ATTRIBUTE
described by
subject of
for based on classified as
TIER PRICING subclass of

classification
basis of for
parent class of
subject of
for OBJECT CLASS OBJECT CLASS
EXTENDED
PRICING MATRIX ITEM ATTRIBUTE
for
used by based on described

for by
PRICING MATRIX for
have types
of
Product Promotion
Product Promotion (see Figure 50) 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 51. Product Promotion ERD Entities and Tables
Entity Table
Conditional Charge Prorata 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 Operation S_PROM_OPER
Product Promotion Operation Component S_PROM_OPER_CPT
Product Promotion Pricing Matrix Rule S_PROM_PMTRX
Product Promotion Term S_PROMITM_TRMS
Product Promotion Term Description S_PROD_TRM_DESC
Title : Product Promotion
Figure 50.
associate to
PRODUCT PROMOTION CONDITIONAL
CHARGE associate by CHARGE
PRORATA PLAN
PRODUCT PROMOTION ITEM
ATTRIBUTE VALUE
define for
define for has
PRODUCT PROMOTION ITEM

ATTRIBUTE
Product Promotion
PRODUCT PROMOTION ADJUSTMENT define for

PRICING MATRIX RULE for GROUP
contain child of
child of parent of
root of has
uses
define for PRODUCT PROMOTION ITEM
used by
made up
PRODUCT PROMOTION PRODUCT PROMOTION uses
TERM OPERATION COMPONENT
used by
define for
PRODUCT define for associated
PROMOTION TERM to
DESCRIPTION
has
define for PRODUCT applies

PROMOTION
OPERATION applicable
to
defined for
PRODUCT
has has has has contain has has
PRODUCT PROMOTION

119
Product Quality Tracking

This ERD (see Figure 51) illustrates the significant entities related to product defect tracking. Defects
can be associated with service requests and can include associated activities defined to fix the defect.
Associations can 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 can be recorded. Defects can be associated with other, related
defects.
Table 52. Product Quality Tracking ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Defect Symptom S_PRDFCT_SYMP
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
Title : Product Quality Tracking
Author : Oracle, Confidential PROJECT made up of
OTHER
PROJECTS
DEFECT PROJECT ITEM ACTIVITY OTHER ACTIVITY

SYMPTOM belong to
PRODUCT QUALITY ENHANCEMENT part of
QA TEST REQUIRED RELEASE ACTIVITY SERVICE REQUEST ACTIVITY
FEATURE includes PROJECT
observed for part of
defined for
defined for based on
fixed via
RESOLUTION ITEM
resolved by made up of
duplicated
solution to
as
PRODUCT QUALITY ITEM related to relation solution to
of resolved by SERVICE REQUEST
exhibition of handled via basis for
reported via caused by
Figure 51. Product Quality Tracking
PRODUCT DEFECT PRODUCT PATCH / ORGANIZATION UNIT owned by reported by

ENHANCEMENT owned by
duplicate REQUEST
of owner of INTERNAL /
primarily by PARTNER
ORGANIZATION
primary of UNIT
OTHER PRODUCT QUALITY ITEM
OTHER
reported for planned to in environment of reported by owned by ORGANIZATION
be fixed in UNIT
actually fixed in reporter of owner of reporter of
owner of
PERSON
OTHER PERSON EMPLOYEE / AGENT
part of
PRODUCT OR SERVICE
target EXTERNAL PRODUCT
afflicted fix for
with a component of an assembly of
actual fix for
INTERNAL PRODUCT OR SERVICE
INTERNAL PRODUCT VERSION INTERNAL PRODUCT OTHER INTERNAL PRODUCT

OR SERVICE
version of
produced in

121
Product Recommendation and Offer

This ERD (see Figure 52) provides a method 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. Similarly, Product Offer allows the user to clearly
define the messages, the set of possible responses, the set of actions for the offer responses, the
set of parameters for the offer response, and the offer itself
Table 53. Product Recommendation ERD Entities and Tables
Entity Table
Communication S_COMMUNICATION
Product Line S_PROD_LN, S_PROD_LN_PROD
Product Message S_PROD_MSG
Product Message Response S_PROD_MSG_RESP
Product Message Variable S_PROD_MSG_VAR
Product Offer S_PROD_INT
Product Offer Response S_PROD_OFR_RESP
Product Offer Response Action S_PROD_OFR_ACTN
Product Offer Response Action Parameter S_PROD_OFR_PARM
Product Recommendation S_PROD_RECMNDTN
Title : Product Recommendation and Offer
have COMMUNICATION PRODUCT

PRODUCT PRODUCT
MESSAGE defined for
RECOMMENDATION actual MESSAGE
VARIABLE
response for user of
displayed by
template for
recommendation for PRODUCT

OR
recommended by
SERVICE
for
subject of have
Figure 52. Product Recommendation and Offer
user of parameter for

PRODUCT
OFFER user of PRODUCT
RESPONSE PRODUCT LINE
ACTION OFFER root product for part of
PARAMETER user of
RESPONSE
ACTION composed
component for of
for offer
upgrade for base
has
product for product for
refer to
PRODUCT
MESSAGE
user of RESPONSE
for PRODUCT
OFFER used by
has
RESPONSE
for PRODUCT OFFER
has

123
Products or Services
This ERD (see Figure 53) 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 54. Products or Services ERD Entities and Tables
Entity Table
Catalog S_CTLG
Class Attribute S_XA_ATTR
Class of Product or Service S_VOD, S_VOD_VER
Language S_LANG
Product Assembly Port S_PROD_ITEM
Product or Service S_PROD_INT or S_PROD_EXT
Product or Service Attribute S_PROD_INT_XA
Product Structure S_PROD_ITEM, S_PROD_REL
Product User Defined Attribute S_PROD_USRDEFATR

Vendor S_ORG_EXT, S_PARTY
Title : Products or Services
LANGUAGE
translation for translation for translation for translation for translation for
PRODUCT
USER
DEFINED translated into PRODUCT OR SERVICE
ATTRIBUTE ATTRIBUTE
PRODUCT ASSEMBLY PORT

for
Figure 53. Products or Services
translated into child of of based on

constrained by defined for
CATALOG
CATEGORY parent to valid for PRICE LIST ITEM
part of
grouped
by
for part of PRODUCT of for translated into
PRODUCT
STRUCTURE a
for LINE basis for
collection
translated into of composed of
made up of
for of composed of CLASS ATTRIBUTE
PRICE
CATALOG LIST
of
PRODUCT OR SERVICE
a
an assembly component
of of subject of
has categorized in part of described via
subject of translated into
subject of
a classification for CLASS OF PRODUCT OR
SERVICE
classified in
a report to
produced by VENDOR
EXTERNAL PRODUCT OR SERVICE producer of a parent to

125
Professional Services
This ERD (see Figure 54) 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 55. Professional Services ERD Entities and Tables
Entity Table
Activity S_EVT_ACT

Billing Rate List S_PRI_LST
Internal/Partner Organization S_ORG_EXT, S_PARTY
Invoice S_INVOICE
Lead Source S_SRC

Opportunity S_OPTY
Potential Project Resource S_PROJ_PTL_RSRC
Project S_PROJ
Project Contact S_PROJ_CON
Project Issue S_PROJ_ISS
Skill S_PROJRSRC_SKL
Title : Professional Services
SKILL
BILLING RATE for SERVICE
LIST BILLING
required by for the resolution of required by billed via POSITION
TYPE
PROJECT ISSUE
ACTIVITY
subject of
for assigned to
assigned to requirer of
billed as
PROJECT TEAM ROLE
Figure 54. Professional Services
billing type for

defined by
defined for subject of filled by
billing type for
assigned to fill
for
of PERSON
POTENTIAL PROJECT
RESOURCE
defined as
OPPORTUNITY OTHER
for PERSON
billed as
of
LEAD PROJECT CONTACT
SOURCE involved in occupant of
source of subject of POSITION
for billed for EMPLOYEE / held by
source of INVOICE AGENT
billed in
subject of billed for sent to
subject of to track work on because of employed by
the outcome of targeted at
requirer of requirer of
subject of billed by
for
composed of
located at for
PROFESSIONAL SERVICE PROJECT
ADDRESS
for ORGANIZATION UNIT
located at
for
INTERNAL/PARTNER OTHER
subcontracted to the client of ORGANIZATION ORGANIZATION
UNIT
responsibility of a partner for
responsible for
accessible to
accessor of

127
Promotion Group
Promotion Groups (see Figure 55) offer advanced product and service bundling and new community
offerings that tie various customer assets in a loosely-coupled network and they provide shared
benefits and provisioning functions.
Promotion Group Validation provides the ability to define and enforce validation rules for Promotion
Groups, such as eligibility and compatibility rules or rules validating the consistency in a Promotion
Group.
Promotion Group pricing provides the ability to define and enforce all pricing-related aspects of a
Promotion Group, such as assigning charges to Promotion Group memberships or adjusting prices
for Promotion Group components.
Promotion Group Access Control provides the ability to define and enforce business rules governing
who can manage the membership of a given Promotion Group.
Promotion Group Notification provides the ability to define the different types of notifications to be
sent to Promotion Group owners and members in response to business events like new or canceled
membership.
Table 56. Promotion Group ERD Entities and Tables
Entity Table
Account S_ORG_EXT
Adjustment Group S_ADJ_GROUP
Asset S_ASSET
Communication Template S_DMND_CRTN_PRG
Conditional Charge Prorata Plan S_AGR_PR_PLAN

Product Compatibility Matrix S_PRODCOMP_MTRX
Product Membership Compatibility S_PRODCOMP_MEM
Promotion Configuration Item S_PRO_CFG_ITEM
Promotion Group S_PROD_INT
Promotion Group Access S_PROMGRP_ACESS
Promotion Group Charge S_PROM_CHRG
Promotion Group Item S_PROM_ITEM
Promotion Group Member S_PROD_INT
Promotion Group Notification S_PROM_GRP_NTFY
Promotion Group Pricing Matrix Rule S_PROM_PMTRX
Table 56. Promotion Group ERD Entities and Tables
Entity Table
Promotion Group Term Description S_PROD_TRM_DESC
Title : Product Promotion Group
130
Author : Oracle, Confidential PRODUCT COMPATIBILITY MATRIX
for related applies to for related to

Figure 55.
to
has
has has
PROMOTION GROUP ADJUSTMENT PROMOTION
PRICING MATRIX RULE for GROUP GROUP defined for
PROMOTION
ACCESS
has has GROUP ITEM

has
for defined ASSET
Promotion Group
for for
belongs to
for
has QUOTE
ITEM has uses
CONDITIONAL
owned by used by CHARGE
PROMOTION CONFIGURATION ITEM for
has PRORATA
made up of PLAN
for associate
to
for for for ORDER ITEM PROMOTION
GROUP
PRODUCT MEMBERSHIP COMPATIBILITY
CHARGE associate
owned by by
for
owner of owner of
defined for
defined for defined for
defined for ACCOUNT
PROMOTION GROUP PROMOTION
NOTIFICATION GROUP TERM
notified by DESCRIPTION
defined for user of
defined
used by for
defined for
COMMUNICATION
TEMPLATE
has has has
has
notify
PRODUCT associated associated
has has has has associated to to to contains has has
has has has
PROMOTION GROUP PROMOTION GROUP

MEMBER

Revenue
This ERD (see Figure 56) illustrates how revenue items are tracked and analyzed in Siebel Business
Applications. Revenue Items can 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 57. Revenue ERD Entities and Tables
Entity Table
Agreement Item S_AGREE_ITEM
Invoice S_INVOICE
Invoice Item S_INVC_ITEM
Opportunity S_OPTY

Project S_PROJ
Revenue Item S_REVN
Revenue Template S_REVN_TMPL
Revenue Template Item S_REVN_TMPL_ITM
Title : Revenue
132
a report to manager of
revenue plan for
PERSON
POSITION OTHER PERSON
REVENUE ITEM for held by EMPLOYEE / AGENT
Figure 56. Revenue
owner of occupant of
for
detailed item of attributed to
for PROJECT
attributed to
ORGANIZATION UNIT
for
SERVICE REQUEST
attributed to
for
MARKETING EVENT OR
attributed to ACTIVITY
for INTERNAL /
PARTNER
for attributed to ORGANIZATION
INVOICE UNIT
attributed to
for belongs to
INVOICE ITEM
attributed to subject of
for part of
CONTRACT ITEM AGREEMENT
for attributed to made up of
subject of
for
OPPORTUNITY
attributed to
OTHER
for ORGANIZATION
UNIT
subject of PRODUCT OR SERVICE
for PRODUCT LINE composed of
subject of part of
based on

REVENUE TEMPLATE
template for
based on REVENUE TEMPLATE details of
ITEM
template item for consist of
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 (see Figure 57)
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 58. Sales Hierarchy and Credit Assignment ERD Entities and Tables
Entity Table
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 Territory Assignment S_SLSTERR_POSTN
Sales Hierarchy S_SLS_HIER

Sales Territory S_SLS_TERR
Title : Sales Hierarchy and Credit Assignment
Author : Oracle, Confidential PARTY
134
CREDIT ALLOCATION
allocated to
POSITION
rollup to recipient of
transfer to recipient of
recipient of
CREDIT RULE CRITERIA
VALUE allocation of
subject of
defined for
approved
CREDIT ASSIGNMENT by
RULE approved by approve
characterized by
POSITION TERRITORY ASSIGNMENT
approve
CREDIT RULE CRITERIA defined for assigned territory
of
characterized by assigned to
applicable to assignment of
subject of consists of
approved by
VALIDATION RULE SALES TERRITORY
approve
Figure 57. Sales Hierarchy and Credit Assignment
categoried by applied to belongs to assigned to
subject of version of
RULE TYPE HIERARCHY VERSION HIERARCHY

TERRITORY part of VERSION approved by
subordinate to composed of approve
parent of version of
OTHER PARTY
validated by consists of versioned by
SALES HIERARCHY

Sales Portfolio Management

This ERD (see Figure 58) 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 59. Sales Portfolio Management ERD Entities and Tables
Entity Table
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
% "
136
Oracle *'.&%$%% *'.&%$%%
$> !>
14

*' &$ "
$
14
22 *' *'%&. &$

&$
9"$
"
$
14 14

Figure 58. Sales Portfolio Management
&$! *' &$

$[$&$
**$

2 &$
6
13
@

*'
*'!& "
$
**$
*' *'
$[$
"
9"$
+

1
$
2
$[$

14 14 *'
$
!&
%'%*'
**$
9

&$
Service Agreement
This ERD (see Figure 59) 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
provide 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 can be subject to one or more metrics
(that describe a guaranteed two-hour response, for example). For covered items, covered labor and
covered faults can be defined.
Table 60. Service Agreement ERD Entities and Tables
Entity Table
Agreement Entitlement S_ENTLMNT
Agreement Line Item S_AGREE_ITEM
Asset S_ASSET
Entitled Product or Asset S_ENTLMNT_ITEM
Entitled Service S_ENTL_ACT_TYPE
Expense Type S_EXP_ITEM_TYPE
Fault/Trouble Code S_FAULT_CODE, S_AGRITM_FLTCD
Labor Operation Code S_LAB_OPER_CODE, S_AGRITM_LABOPR

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
Work Type S_PROJ
Title : Agreement Entitlement
138
PRICE ADJUSTMENT
defined for
EXPENSE billable to ENTITLED PRODUCT OR ASSET

ENTITLED
TYPE
billed for SERVICE
for of
billable to
WORK of ACTION LABOR OPERATION FAULT/TROUBLE

TYPE TYPE CODE CODE
billed for for
Figure 59. Service Agreement
covered in covered in
billable to
MATERIAL include
billed for include
subject of
defined for applicable to
AGREEMENT LINE
basis for ITEM ASSET
subject of
based on for
AGREEMENT ENTITLEMENT subject
basis for of
granted because of
SERVICE
REQUEST
basis for granting
part of
granted because of
ORDER made up of
basis for granting
part of AGREEMENT
made up of
SERVICE measurement for
METRIC with
measured by
subject of
EMPLOYEE/C
for employed at ACCOUNT

PREVENTIVE part of covered by employer of
MAINTENANCE
PLAN ITEM agreement to provide for
covered by
constrained by
SERVICE
used by CALENDER
Service Calendars and Work Shifts

This ERD (see Figure 60) 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 61. Service Calendars and Work Shifts ERD Entities and Tables
Entity Table
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
Schedule Calendar S_SCHED_CAL
Schedule Calendar Hours S_SCHED_CAL_HRS
Service Calendar S_SCHED_CAL
Work Shift S_SCHED_CAL
Figure 60. Service Calendars and Work Shifts

Title : Service Calendars and Work Shifts
SCHEDULE EXCEPTION
CALENDAR CALENDAR
HOURS HOURS
EMPLOYEE
EXCEPTION
HOURS
worked by for for
of
of
contributor of EXCEPTION
SCHEDULE CALENDAR
CALENDAR
PERSON SERVICE CALENDAR for of
EMPLOYEE /
OTHER PERSON AGENT
assigned to
WORK SHIFT
worked by
manager of a report to
Service Request
This ERD (see Figure 61) 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 62. Service Request ERD Entities and Tables
Entity Table
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
made up of part of
Title : Service Request
142
ACTIVITY
SERVICE REQUEST ACTIVITY OTHER ACTIVITY
for responsibility of
responsibility of
part of
made up of subject of
SERVICE REQUEST PARTY

PERSON
Figure 61. Service Request
responsible for
responsibility of responsible for

SERVICE
responsible for REGION
responsibility of EMPLOYEE / AGENT
responsible for
OTHER PERSON
reported by
reporter of
OTHER PARTY
responsibility of ORGANIZATION UNIT
responsible for INTERNAL / PARTNER

in in ORGANIZATION UNIT
environment environment for problems for problems
of of with with
subject of
owned by
ASSET (PRODUCT
INSTANCE) owner of
part of part of OTHER ORGANIZATION
profile of profile of an instance of UNIT
EXTERNAL PRODUCT OR SERVICE subject of manufactured into

PRODUCT
PRESENCE of EXTERNAL INTERNAL PRODUCT OR SERVICE

PRODUCT OR
subject of SERVICE
at
subject of
Shipment
This ERD (see Figure 62) 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 63. Shipment ERD Entities and Tables
Entity Table
Order S_ORDER, S_ORDER_SHIP
Order Item Delivery Request S_ORDPART_REQ
Order Part Movement S_ORDPART_MVMT, S_SHIPMENT_MVMT
Part Movement Type S_PARTMVMT_TYPE
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
%
Oracle
144
13
!">"$
!&
613 $$'
%9"$'$"
3 ">"$
!"!'>+"% +
3
Figure 62. Shipment

9">"$

7&"
!'>+
!" 7&"
"%
!'>+7&% !'>+7&%

13
%9"$ !'$" 1 7&'$"
1
232
213

!
1
7&
1

$>$+' $

Siebel Assistant
This ERD (see Figure 63) 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 64. Siebel Assistant ERD Entities and Tables
Entity Table
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

Opportunity S_OPTY
Opportunity Stage S_OPTY_STG
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
Title : Siebel Assistant
146
part of made up of
ASSESSMENT VALUE ASSESSMENT ATTRIBUTE ACTIVITY STAGE PLAN ITEM STAGE

VALID VALUE
RECOMMENDATION
OTHER ACTIVITY
for defined for defined for
for for for
assesed via validated via TEMPLATE ACTIVITY
ACTIVITY PLAN
ASSESSMENT ATTRIBUTE
Figure 63. Siebel Assistant
a component of
for instance of
ASSESSMENT
for
container of made up of instantiated as of
SALES PLANNING ITEM
created from ASSESSMENT ACTIVITY PLAN TEMPLATE

TEMPLATE
for of at
created during for
SALES STAGE
for
of of of
subject of
planned by
PERSON
EMPLOYEE /
AGENT OPPORTUNITY STAGE of
for
OTHER of
PERSON
subject of for
currently at
subject of OPPORTUNITY
for for

ACCOUNT composed of
governed by
SALES
governor of METHODOLOGY
Social Media
This ERD (see Figure 64) illustrates how social media data is integrated with the Siebel application
to generate service requests, leads, and loyalty credits. Loyalty credits can be defined for customers
who post information in social media about a company's products or perform other activities that
might result in customer adoption or increased market awareness of the product.
Table 65. Social Media ERD Entities and Tables
Entity Table
Employee/Agent S_CONTACT, S_USER, S_EMP_PER, S_PARTY
Contact Social Media Profile S_CON_SM_PROF
Contact Social Media Profile Attribute S_CON_SM_ATTR
Lead S_LEAD, S_SM_DATA_LEAD
Loyalty Transaction S_LOY_TXN
Person S_CONTACT, S_PARTY, S_SM_DTASRC_USR
Social Media Channel S_SM_CHANNEL
Social Media Data S_SM_DATA
Social Media Data Source S_SM_DTA_SOURCE
Figure 64. Social Media
Title : Social Media CONTACT SOCIAL

Author : Oracle, Confidential MEDIA PROFILE
ATTRIBUTE
SOCIAL MEDIA DATA

defined for
PARTY
SERVICE
REQUEST based on
source for
has PERSON
LOYALTY based on
TRANSACTION CONTACT
source for SOCIAL
authored by owned by
MEDIA
PROFILE OTHER
author of owner of PERSON
LEAD based on
source for
listened by posted on
EMPLOYEE /
publisher for AGENT
administered by
SOCIAL MEDIA CHANNEL
primary administrator for
accessed by
listener for accessor of
SOCIAL MEDIA DATA administered by

SOURCE administrator for
OTHER PARTY
Territory Management
This ERD (see Figure 65) 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 66. Territory Management ERD Entities and Tables
Entity Table
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)
3"
150
Oracle
+

%$+
%%
$"$ 13
+"$
$ 0 &$0 %%0

0
"$
"$
"$
"$

$ """.
+
Figure 65. Territory Management
>%$
2

&$""".

13

9 '
%%" $
"".
[ ! +
9 9+

13
&$

$ 13

13
.&%$%%&$
%%

@13 1

%$ !>%$
13 9!>%$ %'%*

Territory Quota Rollup

This ERD (see Figure 66) 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 for each period.
Table 67. Territory Quota Rollup ERD Entities and Tables
Entity Table
Sales Quota S_SLS_QUOTA
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
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

+7& +
152

$7& $ 7&
7&
! ! !

+7&"$
070 $ 070 $ 070

213

14
15 6
Figure 66. Territory Quota Rollup
7& 7&"$

.<!;$ .<!;$ +"$

1 2

&$0 $
0
3 "$
"$
0
2
"$
!

6
2

2

9 '
&$ $
1
7&%%
$"$ [ !
$
! .<!;$
7&
15 6

14

14 7&%%

$"$
%'%7& &$07& $ 07&

07& 37
Oracle

Textile, Apparel, and Footwear

This ERD (see Figure 67) 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 Figure 67 indicate examples of the types of data that can be found within a
supertype. They are not intended to indicate strict subtypes.
Table 68. Textile, Apparel, and Footwear ERD Entities and Tables
Entity Table
Marketing Segment S_MKT_SEG
Order S_ORDER
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
ORDER ITEM
primarily composed of subject of PRODUCT ATTRIBUTE VALUE
154
relevant to
ORDERED secondarily composed of subject of
ASSORTMENT SHOE SIZE COLOR
PLAN ITEM
primarily of subject of COLOR
PROPORTION
FAMILY
PRODUCT OPTION OTHER ATTRIBUTE VALUE includer
MIX PROPORTION of
of QUOTE ITEM secondarily of subject of
subject subject of
split into of a value
ASSORTMENT PLAN ITEM applicable to
of
for of SCHEDULED DELIVERY
ORDERED
ASSORTMENT
PLAN ITEM of subject of the domain

defined
for
for primary defined by collection of
scheduled PRODUCT OPTION MIX PREFERENCE
by (SPREAD) PRODUCT
primarily specified secondary defined by collection of ATTRIBUTE
for of on TYPE
ASSORTMENT specify ACCOUNT RECOMMENDED
PLAN ITEM secondarily specified SPECIFIC MIX
specify on MIX
for primarilly secondarily
specific to the specific to of of primary secondary
default items within domain domain for
composed mix for for
for PRODUCT OPTION
Figure 67. Textile, Apparel, and Footwear
of RANGE MEMBER
ordered on belonging to scope of
ORDER definer of
for
billed to for PRODUCT INTERNAL
ORGANIZATION recommended to be ordered in
EXTERNAL
STYLE/COLOR/DIMENSION
ACCOUNT
primarily
defined created from launched applicable defined for collection defined by secondarily
for in to of defined by
STORE composed
composed of
of parent to defined for
lead to PRODUCT OPTION RANGE
OTHER CATEGORY
subject of ORGANIZATION
QUOTE
defined for NON-SEASONAL
for primarily
for manufactured in in
ASSORTMENT subject of composed of SIZE RUN
PLAN
MARKETING secondarily
SEGMENT the target of targetted at LINE OF BUSINESS manufactured in in
defined for SEASONAL
debut season for a collection of
COLOR PALETTE
PERIOD subject of defined for
SEASON
subject of

delivery period for delivery period for
of made up
PERIOD RELATIONSHIP of
Title : Textile, Apparel and Footwear
to part of Author : Oracle, Confidential
WEEK OTHER PERIOD TYPES
Time Sheet
This ERD (see Figure 68) 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 69. Time Sheet ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Period S_PERIOD
Project S_PROJ
Time Unit S_TMSHT_ITEM
Timesheet S_TMSHT
Timesheet Approval S_TMSHT_APPR
Timesheet Line S_TMSHT_LN
Work Type S_PROJ
Title : Time Sheet
156
adjusted
ACTIVITY
TIME UNIT
Figure 68. Time Sheet
adjustment
TIME ADJUSTMENT WORK TIME UNIT based
basis for
owned by targeted at owned by associated with

reported via subject of classified as for reported by for
for
classification for subject of subject of
made up of PROJECT TASK PROJECT TEAM ROLE OPPORTUNITY

subject of
TIME SHEET LINE report of time belongs to defined for

SERVICE worked on
REQUEST
ORGANIZATION UNIT
made up require
WORK TYPE have ownership of subject of
part of NON-PROJECT PROJECT

WORK TYPE INTERNAL OTHER
ORGANIZATION UNIT ORGANIZATION
made up of
UNIT
submitted for
TIME SHEET referenced by
composed of
PERIOD
reported for
reporter of affiliated with
for
owner of
PERSON
reported by
EMPLOYEE/AGENT
reporter of
approved
contact for
approver
OTHER PERSON

Trade Promotions
This ERD (see Figure 69) 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 70. Trade Promotions ERD Entities and Tables
Entity Table
Contract S_D0C_AGREE, S_DOC_QUOTE, S_ORDER
Contract Item S_AGREE_ITEM, S_QUOTE_ITEM, S_ORDER_ITEM
Internal Product Presence S_ORG_PROD
Marketing Event or Activity S_SRC, S_SRC_CHNL
Note S_NOTE_SRC
Order S_ORDER
Other Contract S_DOC_AGREE, S_DOC_QUOTE
Product S_PROD_INT, S_PROD_EXT

Oracle
158
!"
13

"<$
!>'"$*&$!

*&$!
'' $ 14
Figure 69. Trade Promotions

?13
%$
?

&$
"<$
>$ >+ $
13
6
"$'$ "$ !
!&
3
2
"$
&$!& 2
"$ &$ 9

$
14
213
9"<$
"$
>$ >+ 14
$

!&
!& 8$'
14 14

!& $$'
Training Curriculum Course

This ERD (see Figure 70) 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 can 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 71. Training Curriculum Course ERD Entities and Tables
Entity Table
Employee Course S_EMP_CRSE
Employee Course Status S_EMP_CRSE_STAT
Title : Training Curriculum Course
CURRICULUM CURRICULUM ACCESS GROUP
160
TRAINING
CURRICULUM STEP TARGET AUDIENCE CATEGORY
part of
TRAINING
CURRICULUM composed of
STEP COURSE part of target of for granted access to
composed of targeted at belongs to accessed by

TRAINING CURRICULUM
part of
composed of
of
categorized into provide training for subject of subject of
Figure 70. Training Curriculum Course
EMPLOYEE COURSE STATUS
of
COURSE
AVAILABLE
LANGUAGE tracked by
EMPLOYEE COURSE certified for

available for path satisfied by for
needed by for
CATALOG CATEGORY JOB PROFILE LITERATURE CURRICULUM
PERSON
for satisfied by for

OTHER MARKETING EVENT OR
ACTIVITY certification of
TRAINING COURSE OFFERING
based on registered by
instructed by
subject of offered in in need of subject of
subject of instructor of enrolled in
PRODUCT OR SERVICE categorized into provide training for for

basis of PERSON

TRAINING COURSE
OTHER PRODUCT OR SERVICE

Training Test Engine

This ERD (see Figure 71) illustrates the entities and relationships relevant to the training test engine
business function. Tests can be defined for one or more course offerings, or for one or more courses,
including test questions and possible answers, and can 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 of
whether the individual has attempted to answer the question.
Table 72. Training Test Engine ERD Entities and Tables
Entity Table
Course/Course Offering Test S_CRSE_OFFR_TST
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
Pool Question S_POOL_QUES
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

Oracle
162
'7&%$

$!>!&'% 213 7&%$0%%.'$%;
%$%;
2 14
14
7&%$07&%$'

14 7&%$ 7&%$

14 '

$!>!&'%%
7&%$
Figure 71. Training Test Engine
13

%7&%$
13

$!>!&'%% %>'.' @ 1

+ '$
&

3 21
13
$!>!&'%%
$$
%

14
7&%$ 0.= >

+
>$' $
6

&%0 &%**$
%
6 6
14 14
14
"<$
>$ >+ !& %>
1

$$
&%**$
$$
&%
1
9"<$
>$ >+ 9!& %>
Versioned Object Definition

Versioned Object Definition (see Figure 72) 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 73. Versioned Object Definition ERD Entities and Tables
Entity Table
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
Title : Versioned Object Definition
164
OBJECT ATTRIBUTE VALUE JOINT WORKSPACE
PRODUCT ATTRIBUTE VALUE PRODUCT TEMPLATE

ATTRIBUTE VALUE
for for for for

have
for
have
OBJECT ATTRIBUTE JOINT WORKSPACE

Figure 72. Versioned Object Definition
have ITEM
PRODUCT PRODUCT TEMPLATE

ATTRIBUTE ATTRIBUTE
locally locally for

defined globally defined via
defined
for for grouped in
VERSIONED OBJECT DEFINITION
have have have for

have
PRODUCT HEADER PRODUCT TEMPLATE HEADER ATTRIBUTE HEADER DEFINITION OTHER VERSIONED OBJECT HEADER
DEFINITION DEFINITION DEFINITION
have for have have

parent of have
child for for for for
for have ATTRIBUTE DEFINITION ATTRIBUTE VALUE VERSIONED OBJECT

OBJECT DEFINITION

DEFINITION VERSION
PRODUCT DEFINITION PRODUCT TEMPLATE
DEFINITION
Warranty
This ERD (see Figure 73) illustrates how Siebel Business Applications track product warranty
coverages. Warranty coverage is provided by an organization (often the vendor of the product) and
covers one or more products. The products covered under the warranty coverage are specified
directly through product warranty coverage entries. Warranty service can be provided by one or more
authorized service providers.
The various warranty coverages are applied to an asset through a Warranty Policy. A warranty can
be tracked throughout its life, and can be applied to fully or partially compensate the service provider
for service requested in a service order. Warranties can also include coverage lists, exclusions from
coverage, fault codes, trouble codes, repair operation codes, and repair operation times associated
with them.
A Supplier Warranty Policy is an agreement between the parts supplier and the original equipment
manufacturer. Parts are covered as line items of the agreement with the rules and conditions of
compensation specified.
Table 74. Warranty ERD Entities and Tables
Entity Table
Account S_ORG_EXT
Asset S_ASSET
Asset Warranty Coverage S_ASSET_WRNTY
Contact S_CONTACT
Coverage List S_CVRG_LST, S_WRNTY_CVRGLST
Exclusion S_EXCLUSION, S_WRNTY_EXLSN
Fault/Trouble Code S_FAULT_CODE
Labor Operation Code S_LAB_OPER_CODE, S_CVRGLST_LABOP

Labor Operation Time S_LAB_OPER_TM
Order S_ORDER
Partner Labor Rate S_PRTNR_LAB_RATE
Position S_POSTN
Product S_PROD_INT, S_CVRGLST_PART
Product Line Warranty Coverage S_PRDLN_WRNTY
Product Warranty Coverage S_PROD_WRNTY
User S_USER
Table 74. Warranty ERD Entities and Tables
Entity Table
Warranty Coverage S_WRNTY_CVRG, S_WRNTY_CVRG_X
Warranty Coverage Attachment S_WRNT_CVRG_ATT
Warranty Service Provider S_WRNTY_SRV_ORG
Title : Warranty
provided to policy holder for
ASSET PERSON
WARRANTY
COVERAGE subject
Figure 73.
ORDER LINE claimed against of of ASSET as instance of PRODUCT
ITEM
applied to made into
for for AGREEMENT part of subject of

Warranty
part of by associated to subject to vended by

LINE ITEM belongs to
policy dealer
holder of of
for has
ACCOUNT
associated composed of
to for
has for PRODUCT
LINE
FAULT/TROUBLE LABOR OPERATION of
composed of CODE TIME
applicable to subject of
related to
ORDER for specified for PRODUCT
associated
to WARRANTY
PARTNER of COVERAGE
SERVICE ORDER EXCLUSION for
LABOR RATE
for
for has
COVERAGE LIST PRODUCT by
OTHER ORDER for LINE
for LABOR OPERATION associated to WARRANTY
CODE COVERAGE
for
associated
parent of for by
made to
associated
up of
has to for made up of made up of
WARRANTY
COVERAGE for
ATTACHMENT WARRANTY COVERAGE
has
of
WARRANTY
SERVICE provided by
PROVIDER
held by approved by assigned to provided by a part of made up of
holder of approver of for
USER POSITION
vendor of
warrantor of
role played by
ORGANIZATION UNIT

subject of
167
Warranty Claim
Warranty Claim (see Figure 74) is the dealer's or service provider's claim for repair or replacement,
or compensation for nonperformance or under-performance, of an item as provided for in its
warranty. Prewarranty authorization is the request submitted by the dealer or service provider to
seek approval to carry out the repair work for the claim. Warranty claim items can relate to repair
or replacement of certain parts of the asset. The compensation details for the failures are included.
Compensation can be claimed for repair or replacement of parts, labor charges, and sublet charges.
Table 75. Warranty Claim ERD Entities and Tables
Entity Table
Account S_ORG_EXT
Asset S_ASSET
Business Unit S_BU
Campaign S_SRC
Contact S_CONTACT
Event Activity S_EVT_ACT
Exclusion S_EXCLUSION
Labor Operation Code S_LAB_OPER_CODE
Order S_ORDER
Partner Labor Rate S_PRTNR_LAB_RATE
Position S_POSTN
Product S_PROD_INT
Source Asset S_SRC_ASSET
Source Payment S_SRC_PAYMENT
Source Payment Item S_SRC_PAYMT_ITM
User S_USER
Validation Message S_ISS_VALDN_MSG
Warranty Claim S_WRNTY_CLAIM
Warranty Claim Attachment S_WRNTY_CLM_ATT
Table 75. Warranty Claim ERD Entities and Tables
Entity Table
Warranty Claim Item S_WRNTY_CLM_IT
Warranty Claim Part S_WRNTY_IT_PROD
Title : Warranty Claim prewarranty
authorization for
WARRANTY CLAIM ITEM LABOR OPERATION CODE
170
Author : Oracle, Confidential for
has subject of
VALIDATION
MESSAGE
has for
Figure 74.
has
SOURCE PAYMENT ITEM CAMPAIGN
has for recall campaign for
has uses
SOURCE ASSET PARTNER LABOR RATE
for used by
associated
original has fault code for

to
part for
WARRANTY PRODUCT has trouble code for FAULT/TROUBLE CODE
CLAIM PART for has
Warranty Claim
has ASSET
WARRANTY
for has submitted by submitter for claimed against COVERAGE
AGREEMENT approved by approver of USER
uses used for has
for for
for has
has
prewarranty
ORDER ITEM consists of authorization for
prewarranty submitted by submitter for
for authorization for
WARRANTY CLAIM approved by approver of
composed of has claimed against
has
ORDER
has for CONTACT
filed by filer of
associated to
EVENT ACTIVITY
for for has
ACCOUNT
for partner of
for
BUSINESS UNIT
associated to vended by vendor of
assigned to has
for
EXCLUSION POSITION
has
for assigned to
has for has

SOURCE PAYMENT ASSET
for
for associated to
WARRANTY CLAIM SERVICE REQUEST

ATTACHMENT has for
Work Order
A work order (see Figure 75) is created when a dealer performs any kind of service, which can be
part of a warranty claim or a paid service on the asset. The work order is used to document all repair-
related information. Work Order Items can relate to replacement of certain parts of the asset.
Compensation details for failures are included. Compensation can be claimed for parts replacement,
labor charges, and sublet charges.
A supplier recovery claim is the claim for failed parts supplied by the supplier. The claim is based on
the supplier warranty policy and made by the original equipment manufacturer to the supplier.
Table 76. Work Order ERD Entities and Tables
Entity Table
Account S_ORG_EXT
Asset S_ASSET, S_ASSET_EXLSN
Business Unit S_BU, S_WRK_ORDR_BU
Contact S_CONTACT
Exclusion S_EXCLUSION
Fault and Related Operation S_FLT_LABOPER
Fault and Related Trouble S_FLT_TRBL_REL, S_FAULT_CODE
Labor Operation Code S_LAB_OPER_CODE

Position S_POSTN, S_WRKORDR_POSTN
Product S_PROD_INT
User S_USER
Warranty Claim S_WRNTY_CLAIM
Warranty Claim Item S_WRNTY_CLM_IT
Work Order S_WORK_ORDER
Work Order Attachment S_WRKORDR_ATT
Work Order Item S_WRK_ORDR_ITEM
Work Order Part S_WRKORDER_PART
Title : Work Order has for
WORK ORDER ITEM LABOR OPERATION CODE
172
has for
ASSET
WARRANTY
for has has fault code for COVERAGE Figure 75.
WORK ORDER PART FAULT/TROUBLE
CODE
has trouble code for
has associated to
prewarranty
has authorization for
WARRANTY CLAIM
Work Order
for for ITEM

submitted by submitter for

ORDER ITEM PRODUCT original part for USER for
approved by approver of
has
assigned to for POSITION

for
consists of
assigned to has
WORK ORDER
for assigned to
submitted by submitter for

for
approved by approver of
BUSINESS UNIT
associated to consists of
prewarranty
has authorization for
WARRANTY CLAIM
for
EXCLUSION
has has
CONTACT
for
has partner for
WORK ORDER for ACCOUNT
ATTACHMENT
has
has for
created for
ASSET
associated to associated to
EVENT ACTIVITY
for
SERVICE REQUEST

associated to for
Siebel Logical Model Entity Relationship Diagrams and Descriptions for Siebel Industry
Applications
Entity Relationship Diagrams and

Descriptions for Siebel Industry
Applications
The ERD descriptions and diagrams in this topic apply to Siebel Industry Applications. These
applications are designed for specific industries such as the pharmaceutical, energy, insurance, and
healthcare industries. They include Siebel Consumer Sector, Siebel Energy, Siebel Finance, Siebel
High Tech and Manufacturing, Siebel Life Sciences, Siebel Public Sector, and Siebel Travel and
Transportation, and other applications. Table 77 provides a list of ERDs in alphabetic order.
Table 77 provides a list of ERDs in alphabetic order.
Table 77. Entity Relationship Diagrams for Siebel Industry Applications
ERD Name Figure Num. and Page Functional Area
Account Targeting Figure 76 on page 177 Consumer Sector
Activity Figure 77 on page 179 Life Sciences
Affiliations and Best Times Figure 78 on page 181 Life Sciences
Agencies/Agent Figure 79 on page 183 Financial Services
Automotive Retail Figure 80 on page 185 Automotive
Brick Figure 81 on page 187 Life Sciences
Clinical Study Management Figure 82 on page 190 Life Sciences
Clinical Study Site Management Figure 83 on page 192 Life Sciences
Communications, Media, and Energy (CME) Figure 84 on page 194 CME

Account
CME Agreement Figure 85 on page 196 CME

CME Alert Figure 86 on page 198 CME
CME Energy Products, Service, and Usage Figure 87 on page 200 CME
CME Order Management Figure 88 on page 202 CME
Commercial Banking Figure 89 on page 205 Financial Services
Commercial Insurance Figure 90 on page 207 Financial Services
Community/Chat Discussion Figure 91 on page 209 Life Sciences
Dealer Sales and Service Promotion Figure 92 on page 211 Automotive
Document ID and Tax ID Figure 93 on page 213 Handheld
Event Tax Administration Figure 94 on page 215 Hospitality
Financial Account Figure 95 on page 217 Financial Services
Financial Account Application Figure 96 on page 219 Financial Services
Applications
Financial Account Origination Figure 97 on page 221 Financial Services
Financial Investments Figure 98 on page 223 Financial Services
Financial Products Figure 99 on page 225 Financial Services
Financial Services Events Figure 100 on page 228 Financial Services
Fleet Management Figure 101 on page 231 Financial Services
Fleet Management - Location Figure 102 on page 233 Financial Services
FLEXCUBE Universal Banking Integration Figure 103 on page 235 Financial Services
Group Insurance Policies Figure 104 on page 237 Financial Services
Group Pensions Figure 105 on page 239 Financial Services
Health Provider and Provider Group Figure 106 on page 241 Financial Services
High Tech Special Pricing Authorization Figure 107 on page 243 Sales
Hospitality Category Figure 108 on page 245 General
Hospitality - Meeting Package Figure 109 on page 247 General
Institutional Sales Figure 110 on page 249 Financial Services
Insurance Claims Figure 111 on page 252 Financial Services
Insurance Policies Figure 112 on page 254 Financial Services
Life Insurance Policy Figure 113 on page 256 Financial Services
Loyalty Figure 114 on page 260 General
Loyalty Flowchart and Formula Figure 115 on page 262 General

Managed Care Figure 116 on page 264 Life Sciences
Medical Education Event Management Figure 117 on page 266 Life Sciences
Objectives Figure 118 on page 268 Consumer Sector
Personalized Content Delivery Figure 119 on page 270 Life Sciences
Public Sector Benefit Case Management Figure 120 on page 273 Public Sector
Public Sector Case Lead Management Figure 121 on page 276 Public Sector
Public Sector Child Welfare Figure 122 on page 278 Public Sector
Public Sector Contact Identity Figure 123 on page 280 Public Sector
Public Sector Evidence Management Figure 124 on page 282 Public Sector
Public Sector Incident Management Figure 125 on page 284 Public Sector
Public Sector Service Provider and Referral Figure 126 on page 286 Public Sector
Management
Applications
Real-Time Scheduler Integration Figure 127 on page 288 Service
Routes and Best Call Hours Figure 128 on page 290 Sales
Sales Volume Planning Figure 129 on page 292 Consumer Sector
Sample Management Figure 130 on page 294 Life Sciences
Special Rate List Figure 131 on page 296 Communications
Syndicated Data Figure 132 on page 298 Life Sciences
Teller Administration Figure 133 on page 300 Financial Services
Territory AlignmentQuota Assignment Figure 134 on page 302 Sales
Territory Management - Consumer Sector Figure 135 on page 304 Service
Territory Management - Life Sciences Figure 136 on page 306 Sales
Universal Customer Master Figure 137 on page 309 General
Vehicle Figure 138 on page 311 Automotive
Vehicle Collection Figure 139 on page 313 Automotive
Vehicle Financing Figure 140 on page 315 Automotive
Vehicle Sales Figure 141 on page 317 Automotive
Applications
Account Targeting
This ERD (see Figure 76) illustrates how Siebel Enterprise applications (Consumer Goods) support
account targeting as an extension of basic querying. Account targeting provides the capability to
save the results of account queries and apply those account lists when you schedule routes. The
results that you save are called target lists. Target lists consist of sets of accounts that meet the
conditions defined by the query. Typically, the target lists you create in account targeting are for a
specific purpose and period of time. For example, the target lists might be used to support a
promotion, a campaign, or an objective.
Table 78. Account Targeting ERD Entities and Tables
Entity Table
Criteria S_CG_QUERY_ITEM
Employee S_CONTACT, S_PARTY
Objective S_SRC
Query S_CG_QUERY
Route S_ACCNTRT
Applications
Figure 76. Account Targeting
OBJECTIVE ROUTE ACCOUNT

EMPLOYEE
created from created from
applied to
applied to
QUERY RESULT SET consist of appear on

combine
combined by
returned by
return
submit QUERY
submitted by
have
belong to
CRITERIA
Applications
Activity
This ERD (see Figure 77) illustrates how activities, contact calls, account calls, attendee calls, and
meetings are managed. Every activity belongs to the employee creator and other employees
assigned to the activity. Activities can be associated with one or more contacts and one account.
Contact calls are associated with the employee creator and the contact, and can be associated with
other employees who have been assigned, product details, samples, promotional items, and decision
issues. Account calls are associated with the employee creator and an account, and can be associated
with other employees who have been assigned, product details, and multiple attendee calls. Each
attendee call is associated with the product details from the account call and one contact, and can
be associated with samples, promotional items, and decision issues. Meetings include the employee
who owns the meeting, the contacts invited to attend, the account where the meeting is taking place,
and the product to be discussed at the meeting.
Table 79. Activity ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Contact S_CONTACT
Indication S_PROD_APPLCTN
Issue S_PROD_ISS
Product S_PROD_INT
Title : Activity
PERSON
PRODUCT belong to EMPLOYEE

Figure 77. Activity
personal list of
ACTIVITY
responsibility of
PROMOTIONAL ITEM
dropped at responsible for
CONTACT CALL
INDICATION
for
CONTACT
ATTENDEE CALL
DETAIL discussed at
contain
SIGNATURE
for discussion of
captured for
contains
for
sampled at
SAMPLE subject of
sampling of
ISSUE belongs
subject to consideration on
consideration on subject to
ACCOUNT
have
ACCOUNT CALL
subject of
for
composed of
affiliated with
MEETING
subject of
for
ATTENDEE / INVITEE
invite/attend
invited to/attend

Applications
Entity Relationship Diagrams and Descriptions for Siebel Industry
179
Applications
Affiliations and Best Times

This ERD (see Figure 78) illustrates how contacts and accounts can be affiliated with one another,
and how best times can be stored. Contacts can have multiple account affiliations, and can store
multiple types or roles and best times for each account affiliation. Contacts can have multiple
addresses and can share address records with other contacts. Contacts can also have a primary
address for each position that is on the team. Accounts can also have multiple addresses and can
share address records with other accounts. Contacts and accounts can share address records. Best
times are stored for each address for each contact. Best times are also stored for each account.
Table 80. Affiliations and Best Times ERD Entities and Tables
Entity Table
Account Affiliation S_PARTY_PER
Address S_ADDR_PER
Address Usage S_CON_ADDR
Best Times (Account) S_BEST_CALL_HRS
Best Times (Account Affiliation) S_PARTY_PER_HRS
Best Times (Contact Address) S_CON_ADDR_HRS
Organization S_ORG_EXT, S_PARTY
Person Position S_POSTN_CON
Type S_PARTY_PER_DTL
Applications
Figure 78. Affiliations and Best Times
ADDRESS USAGE
for located at for having
PERSON POSITION POSITION

composed of belong to
for
BEST TIMES
(CONTACT
composed of located at ADDRESS)
for for
ADDRESS
BEST TIMES
(ACCOUNT)
TYPE BEST TIMES
(ACCOUNT
AFFILIATION)
belong to
of
belong to
defined by located at having

having
composed of ORGANIZATION
ACCOUNT AFFILIATION
for
located at for for composed of
CONTACT
Applications
Agencies/Agent
This ERD (see Figure 79) illustrates how Siebel Financial Services supports generation of internal
organization units (such as insurance agencies) that can use external organization units or agencies
(such as insurance brokers) as well as individual agents to distribute their products. Each external
organization unit agency or agent can be associated with details (such as licensing, appointments,
commission contracts, and NASD registrations, and other selling agreements).
Table 81. Agencies/Agent ERD Entities and Tables
Entity Table
Agency Line of Business S_AGNC_LCNSLOB
Agent Line of Business S_AGENT_LCNSLOB
Agent Detail S_AGENT_DETAIL
Agency Detail S_AGENCY_DETAIL
Applications
Figure 79. Agencies/Agent
AGENCY LINE OF based on for AGENT LINE OF

PRODUCT LINE
BUSINESS BUSINESS
for based on
for for
AGENCY DETAIL ORGANIZATION UNIT AGENT DETAIL

deals
with
contracted by INTERNAL
ORGANIZATION UNIT
deals with contracted
by
for
CONTACT
EXTERNAL has
ORGANIZATION UNIT
AGENT
for AGENCY employs

has works for
Applications
Automotive Retail
This ERD (see Figure 80) illustrates the Automotive retail process at dealerships. Sales goals are
defined for every sales representative as well as the dealership for a period (month, quarter, and so
on.). These goals are for new and used vehicles or a fleet of vehicles. The sales process could
comprise several steps and an opportunity to sell a vehicle might involve some of these sales steps.
The sales steps taken by every sales representative are aggregated for the period to determine the
effectiveness of each sales step.
Table 82. Automotive Retail ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Asset S_ASSET
Employee S_EMP_PER, S_CONTACT, S_USER
Employee Budget/Forecast S_AT_PER_FCST
Opportunity S_OPTY, S_OPTY_ATX
Opportunity Sales Step S_OPTY_SLS_STEP
Organization S_ORG_EXT, S_BU
Period S_PERIOD
Person S_CONTACT, S_CONTACT_ATX, S_CONTACT_BU
Sales Step S_SALES_STEP
Sales Step Goal S_FCST_SLS_STEP
Showroom Log Entry S_COMM_LOG

Store Budget/Forecast S_AT_ORG_FCST
Vehicle S_ASSET, S_ASSET_ATX
in context of PERIOD
SALES STEP EMPLOYEE defined for
GOAL BUDGET/FORECAST
subject of
subject of
submitted by
STORE BUDGET/FORECAST
instance of defined for
subject of
SHOWROOM LOG
ENTRY set by
for assigned to
Figure 80. Automotive Retail
in
PERSON of has
submitter of owner of ORGANIZATION
set
OTHER EMPLOYEE responsible
has for DEALER/PARTNER OTHER
PERSON
POSITION ORGANIZATION
of handled
by
owner of
owner of set up
on
visibility of responsible for
visible to
ACTIVITY
ASSET
VEHICLE OTHER ASSET

for of
presented in traded in
owned source of
assigned to involver of by presented has trade-in of responsibility of
for OPPORTUNITY
OPPORTUNITY
SALES STEP subject of
of
used by used in for for

SALES STEP
Applications
185
Applications
Brick
This ERD (see Figure 81) illustrates how region (brick and mini brick) is used in Siebel Life Sciences.
Area can be associated with multiple positions. Area is defined at the address level for organizations
and at the contact level. Area is tracked for activities. Syndicated data is also available at the area
level.
Table 83. Brick ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Account Address S_CON_ADDR
Address S_ADDR_PER
Position S_POSTN
Region S_REGION
Syndicated Data S_SYND_DATA
parent of
REGION
child of
BRICK OTHER REGION
Figure 81. Brick
source of holders of subject of assigned to assigned to

for for
for
held by located at
ADDRESS
CONTACT ACCOUNT ADDRESS defined by
ACTIVITY POSITION SYNDICATED DATA
for
for
located at
ORGANIZATION
parent of
child of

Applications
187
Applications
Clinical Study Management

This ERD (see Figure 82) illustrates how clinical trials are managed. Each clinical trial starts with a
protocol for a specific compound (product). Each protocol is conducted by sites and managed by site
personnel. A protocol can have many versions and multiple protocols can roll up to a single program.
Protocols can also roll up to regions. Subjects are screened and enrolled at protocol sites for specific
protocol versions. Protocol sites are paid, based on the activities they complete. Visits and activities
are generated for subjects based on templates defined for the protocol. The Clinical Research
Associates perform site initiation activities for protocol sites and submit periodic trip reports. A
protocol can also be associated with one or more projects. For a complete layout of projects, refer
to Professional Services on page 126.
Table 84. Clinical Study Management ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Address S_ADDR_PER
Affiliation S_PTCL_ST_CON_LS
Application S_CL_PGM_APP_LS
Clinical Payment S_SRC_PAYMENT
Design S_CL_DSGN_LS
Exception Activity S_CL_ACT_EXC_LS

Position S_POSTN
Product S_PROD_INT
Program S_CL_PGM_LS
Project S_PROJ
Project Subcontractor S_PROG_ORG
Project Subcontractor Contact S_PROJ_ORG_CON
Protocol S_CL_PTCL_LS
Protocol Site S_PTCL_SITE_LS
Subject S_CL_SUBJ_LS
Subject Status S_CL_SUBJ_ST_LS
Subject Template S_SUBJ_TMPL_LS
Template Version S_SBJTMP_VER_LS
Applications
Table 84. Clinical Study Management ERD Entities and Tables
Entity Table
Template Visit S_TMPL_PLANITEM
Trip Report S_EVT_ACT
Visit S_EVT_ACT
Applications
Figure 82. Clinical Study Management
Applications
Clinical Study Site Management

This ERD (see Figure 83) is an extension of Clinical Study Management and illustrates:
Activities related to subjects participating in clinical studies and the list of visit types to be
scheduled for this subject.
How site visit logs are maintained. Clinical Research Associates visit different targeted sites
depending on research requirements and their visits are logged.
How organizations, such as vendors, sponsors, clinical research organizations, central

laboratories, and institutional review boards, are associated with clinical protocol and clinical
protocol sites.
How summaries of subject visits are organized by visit type and by protocol site.
Table 85. Clinical Study Site Management ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Address S_ADDR_PER_S_CON_ADDR
Affiliation S_PTCL_ST_CON_LS
Protocol S_CL_PTCL_LS
Protocol Site S_PTCL_SITE_LS
Protocol Organization S_PTCL_ORG_LS
Protocol Site Organization S_PTCLST_ORG_LS

Site Status Summary S_CL_SIT_ST_SUM
Subject S_CL_SUBJ_LS
Subject Status S_CL_SUBJ_ST_LS
Subject Template S_SUBJ_TMPL_LS
Subject Visit Type S_CL_SUBJVST_TP
Template Version S_SBJTMP_VER_LS
Template Visit S_TMPL_PLANITEM
Visit S_EVT_ACT
Visit Log S_SITE_VST_LOG
Title : Clinical Study Site Management CONTACT
192
study conducted by located at
having for
PROTOCOL SITE ORGANIZATION
ACTIVITY AFFILIATION ADDRESS
Applications
for for primary site for has

affiliated to having investigator
has
for
PROTOCOL SITE
VISIT TRIP
made for source of SITE STATUS
LOG for REPORT has SUMMARY

has subject of
for
VISIT TYPE
type for for
has
SUBJECT for PROTOCOL
STATUS SUBJECT participant at ORGANIZATION
have
VISIT made by for
Figure 83. Clinical Study Site Management
involved in has used for
having
TEMPLATE organization organization
VISIT for for
composed of for ACCOUNT

for applied to participating in
used by
TEMPLATE VERSION
using
having participant of
SUBJECT
composed of TEMPLATE
for
associated with conducted at user of

has
PROTOCOL

REGION
Applications
Communications, Media, and Energy (CME) Account

This ERD (see Figure 84) illustrates how complex hierarchies of accounts are maintained in Siebel
Communications and Siebel Energy. Profiles are the way an account is further described. Addresses
are associated with contacts and accounts. Addresses are unique in the database. Trouble tickets
(service requests) and activities can be associated at the accounts level.
Table 86. CME Account ERD Entities and Tables
Entity Table
Account S_ORG_EXT
Activity S_EVT_ACT
Address S_ADDR_PER
Billing Profile S_INV_PROF
Exemption Profile S_SUBSIDY
Financial Profile S_FINAN_PROF
Trouble Ticket S_SRV_REQ
Applications
Figure 84. Communications, Media, and Energy (CME) Account
ADDRESS
PREMISE
SERVICE ADDR
for
for
for for for
associated child of
described with
FINANCIAL by
PROFILE for
ACCOUNT
parent of
described
for by CUSTOMER
EXEMPTION ACCT
PROFILE located at
PREMISE ACCT
located at
mailed to
associated with
SERVICE ACCT
BILLING PROFILE
CONTACT
has
INVOICE described by
for BILLING ACCT associated with
for associated with
STATEMENT
tracked by tracked by
for
problems
with
TROUBLE TICKET
made
up of associated
part of with
ACTIVITY
Applications
CME Agreement
This ERD (see Figure 85) illustrates how an agreement is managed in Siebel Business applications.
An agreement can be associated with many accounts. Terms and entitlements are associated with
an agreement. An agreement covers service instances and products through the account with which
it is associated.
Table 87. CME Agreement ERD Entities and Tables
Entity Table
Accounts S_ORG_EXT, S_PARTY
Agreement Note S_NOTE_AGR_CUT
Agreement Terms S_AGREE_TERMS
Parameter S_QUOTE_ITEM_XA
Quote S_DOC_QUOTE
Solution Set S_QUOTE_ITEM
Title : CME AGREEMENTS
196
Author : Oracle. Confidential
Applications
QUOTE ITEM
belongs to child of
has ACCOUNTS
Figure 85. CME Agreement
parent of
QUOTE for subject of
AGREEMENT AGREEMENT EVENT ACTIVITY

TERMS NOTE
associated associated
consists of with
with
bound by has a
tracked associated
governs part of for by with
AGREEMENT
child of
parent of

Applications
CME Alert
This ERD (see Figure 86) illustrates how credit and fraud alerts are managed for communications and
utilities customers. A fraud alert is associated with an account. Profile attributes provide more
information about the fraud threshold for an account. A credit alert is related to an account and a
statement. Activities can be performed on both types of alerts.
Table 88. CME Alert ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Alert Attachment S_ALERT_ATT_CUT
Alerts S_ALERT_CUT
Asset S_ASSET
Bill Transactions S_BILL_MAINT
Billing Profile S_INV_PROF
Energy Consumption S_USAGE
Fraud Profile S_FRD_PROF_CUT
Applications
Figure 86. CME Alert

Title : CME Alert
child of parent of
ACCOUNT
FRAUD PROFILE for
described by
child of
for
INVOICE LINE
parent of ITEMS associated with
has
has for
subject
generated by for
created for BILLING ENERGY CONSUMPTION

ALERT
PROFILE
has USAGE
ALERT ATTACHMENT
for
for
consists BILL
generates
made up of subject of for
on attached to
part of
ASSET
ACTIVITY
EQUIPMENT
for METER
attached to
OTHER
Applications
CME Energy Products, Service, and Usage

This ERD (see Figure 87) illustrates how products and services in use, inactive, or planned are
associated with, tracked, and maintained by account. Assets are instances of internal products with
the Siebel products catalog and can represent equipment, services designated by the administrator.
Services are represented as assets that consist of specific commodities or energy service with
corresponding rates or prices (for example, commercial electric service with rate CE5). Each of these
services can be further associated with one or multiple meters. After a service has been established
as an asset with corresponding rate and meter detail, the utility consumption is recorded for each
period, and an invoice is generated.
Table 89. CME Energy Products, Service, and Usage ERD Entities and Tables
Entity Table
Address S_ADDR_PER
Asset S_ASSET
External Product Presence S_ORG_PRDEXT
Invoice S_INVOICE
Invoice Adjustment S_INVOICE_ADJ
Period S_PERIOD
Product: External S_PROD_EXT
Product: Internal S_PROD_INT

Service Instance S_ASSET
Usage S_USAGE
200
Title : CME Energy Products, Services, and Usage
Applications
PRODUCT INVOICE ITEM

INTERNAL PRODUCT
for line item of

EXTERNAL PRODUCT
USAGE INVOICE
subject of is made into ADJUSTMENT
recorded used for

for for
by
made subject
subject displayer
of is a of of
of of
EXTERNAL PRODUCT ASSET INVOICE

PRESENCE
METER
EQUIPMENT for for subject of

Figure 87. CME Energy Products, Service, and Usage
OTHER
at of associated recorded
with in recorded
made up of in
for
SERVICE INSTANCE PERIOD
PAYMENT
made by
service
subject of at responsible for
for consumer subject of

ACCOUNT of

CUSTOMER SERVICE BILLING
Applications
CME Order Management

This ERD (see Figure 88) illustrates order management. Companies provide products and services to
their customers over an extended period of time. Quotes and orders are used to capture the changes
to a customer's installed services. The cycle starts when a customer requests the initial installation
of a product or service in the form of a quote. The quote is converted to an order and that order is
provisioned. At that time, the products and services described in the order are converted into assets
associated with the customer's account. Subsequent changes to the configuration, disconnect
instructions, or additions to the installed assets are captured in further quotes and orders. Order
synchronization failures can also be tracked.
Table 90. CME Order Management ERD Entities and Tables
Entity Table
Asset S_ASSET
Asset Attribute S_ASSET_XA
Order S_ORDER
Order Item Attribute S_ORDER_ITEM_XA
Quote S_DOC_QUOTE
Quote Item Attribute S_QUOTE_ITEM_XA
Failed Service Order S_SRV_ORD_FAIL

Applications
Figure 88. CME Order Management

Title : CME Order Management
ORDER ITEM ASSET ATTRIBUTE subject of QUOTE ITEM ATTRIBUTE

instance of
ATTRIBUTE
subject of instance of
subject of
part of subject of part of
of composed of of of
FAILED SERVICE for ORDER ITEM QUOTE ITEM

ORDER composed of
associated
to
subject of for provision of for of
for for for
associated
to subject of
ASSET
has
SERVICE an instance of
REQUEST
ordered on quoted for purchase on
made into
PRODUCT OR SERVICE
associated to composed of composed of
ORDER QUOTE
created from
leads to
billed by serviced by serviced by billed by
associated with associated with

ACCOUNT
SERVICE ACCOUNT
associated with
associated with
OTHER
BILLING ACCOUNT ACCOUNT
Applications
Commercial Banking
This ERD (see Figure 89) illustrates how Siebel Financial Services supports generation of a
commercial loan (or facility) application by portfolio type. Each application is associated with many
organizations as borrowers or lenders. The application tracks the collateral, policies, prices of a
facility, and documents used in the application process, for example, trailing documents and
attachments. An application must undergo several stages of approvals before it is finally approved
to become a financial account.
Table 91. Commercial Banking ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Approval S_FN_APPR
Attachment S_OPTY_ATT
Borrower S_OPTY_ORG
Collateral S_FN_OFFR_COLT
Correspondence S_EVT_FUL_REQ
Exception S_OPTY_ORG_FNXM
Facility S_REVN
Facility Detail S_OPTY_PROD_FNXM
Facility Organization S_OPTYPRD_ORG
Fee S_FN_OFFR_FEE
Note S_NOTE_OPTY
Opportunity S_OPTY
Opportunity Detail S_OPTY_DTL
Portfolio Type S_MKT_SEG
Product S_PROD_INT
Rating S_OPTY_ORG_FNXM
Revenue S_REVN
Revenue S_REVN
Applications
Table 91. Commercial Banking ERD Entities and Tables
Entity Table
Trailing Document S_OPTY_DOC
Underwriting Standard S_MKT_SEG_VAL
Title : Commercial Banking part of
Author : Oracle, Confidential OPPORTUNITY DETAIL
APPROVAL
made up
UNDERWRITING KEY CREDIT of
STANDARD ISSUES
NOTE ATTACHMENT CORRESPONDENCE TRAILING APPROVAL
DOCUMENT subject to STAGE
REQUEST POLICY DECISION
EXCEPTION required by
of of of for
has
of
subject of has subject of subject to has made up of

part of
associated
OPPORTUNITY subject to with
need for
Figure 89. Commercial Banking
APPROVAL
subject of includes generates belongs to LEVEL
part of
EXCEPTION for for UNDERWRITING

RATING FACILITY issued by
FEE STANDARD
subject
of ACTIVITY
for for for
for for has

subject of of has COLLATERAL
subject
of PORTFOLIO TYPE
BORROWER
FACILITY DETAIL
based
on PRODUCT
represented by
PRICE
of associated
with
has
POLICY
generates
subject of
participated in
COVENANT issues of
FACILITY ORGANIZATION
EMPLOYEE
GUARANTOR SYNDICATE
represented by
applied as participated as a parent to generated by
a report to
ORGANIZATION FINANCIAL ACCOUNT
owner of
owned by

Applications
205
Applications
Commercial Insurance
This ERD (see Figure 90) illustrates how Siebel Financial Services supports generation of group
classes of insured items covered by an insurance policy. An insured item can belong to either one or
two group classes, including a region (such as a state), a location, (such as physical location), or a
class (such as an employee). Insurance coverage can be associated with either one or two group
classes.
Table 92. Commercial Insurance ERD Entities and Tables
Entity Table
Asset S_ASSET
Contact S_CONTACT,S_PARTY
Group Class S_FN_GRP_CLASS
Insurance Coverage S_APPLD_CVRG
Insured Item S_INS_ITEM
Policy Contact S_ASSET_CON
Applications
Figure 90. Commercial Insurance

Title : Commercial Insurance
CONTACT INSURED ITEM
associated
with belongs to part of
for
POLICY CONTACT INSURANCE COVERAGE
covers for
of insured as
for covers covered by
GROUP CLASS
CLASS REGION LOCATION

made
up of
associated with part of
ASSET subject of subject of subject of covers
INSURANCE POLICY
Applications
Community/Chat Discussion
This ERD (see Figure 91) illustrates how topics can be created for chat or discussion purposes for a
disease state (market product). Users can register to chat for a particular topic or they can post
messages to the discussion.
Table 93. Community Chat/Discussion ERD Entities and Tables
Entity Table
Discussion Post S_MESG_BRD_LS
Product S_PROD_INT
Registration S_TOPIC_CON_LS
Topic S_TOPIC_LS
Applications
Figure 91. Community/Chat Discussion
Title : Community Chat/Discussion

CONTACT
REGISTRATION of
registered for
for
registration of
TOPIC authored by
author of
for subject of
subject of
about
involving
PRODUCT
DISCUSSION POST
posted to
Applications
Dealer Sales and Service Promotion

This ERD (see Figure 92) illustrates how a call list can be created by searching on specific attributes
of vehicle, person, sales history, or service history. A person might qualify to be on the call list by
virtue of possessing a specific vehicle, having the car serviced with the dealership in the past (the
next service might be due), and so on. The dealer can start a campaign for sales or service specials
and include one or more call lists to be targeted through the campaign.
Table 94. Dealer Sales and Service Promotion ERD Entities and Tables
Entity Table
Call List Contact S_CALL_LST_CON
Call List Contact Vehicle S_C_LST_CON_AST
Campaign S_SRC
Campaign Call List S_CAMP_CALL_LST
Campaign Contact Vehicle S_CAMP_CON_AST
Person S_CONTACT, S_CONTACT_ATX
Applications
Figure 92. Dealer Sales and Service Promotion
Title : eDealer Sales and Service Promotion

CAMPAIGN CONTACT
target of owner of in context of
belong to
for
CAMPIAGN CONTACT VEHICLE VEHICLE
subject of
CALL LIST CONTACT VEHICLE for
subject of
in context of belong to
subject of
CAMPAIGN CALL LIST CALL LIST CONTACT
in context of created belong to in context of

from
subject of owner of subject of
PERSON
MARKETING EVENT OR ACTIVITY source

target subject of subject of
of
OTHER EVENT CAMPAIGN CALL LIST
Applications
Document ID and Tax ID

This ERD (see Figure 93) illustrates how document identification numbers are generated and
assigned to each user. Typically, document IDs are used to support a legal requirement to print
unique numbers on legal documents, such as invoices and receipts. Governments provide
specifications on the document ID formats, and these formats can be used to generate a document
ID mask within the Siebel application. After the mask is created, it must be assigned to individual
users who have the authority to use them. When the user prints from the handheld device, a unique
sequence of numbers are printed onto each legal document defined with the document ID mask.
Table 95. Document ID and Tax ID ERD Entities and Tables
Entity Table
Document Mask Component S_DOC_NUM_SEG
Document Types S_DOC_NUM
Document Values S_DOC_NUM_VAL
Invoice S_INVOICE
Order S_ORDER
Applications
Figure 93. Document ID and Tax ID

Title : Document ID and Tax ID
ORDER EMPLOYEE
have have composed of contains
INVOICE
contains
for
ORDER ITEM
for for
DOCUMENT VALUES
have
have
exists for exists for
AUTHORIZED have
PRICE LIST PRODUCT
ITEM
belongs
exists for
exists for
have
DOCUMENT MASK exists for DOCUMENT

ACCOUNT TYPES
COMPONENTS
for have
have
composed of
exists for exists for
PRICE LIST
Applications
Event Tax Administration

This ERD (see Figure 94) illustrates how the Siebel Hospitality application supports tax and service
charge calculation for invoices. An event is hosted at a property such as a hotel or convention center.
Event functions and associated subfunctions are conducted in rooms at the property. A team of
events managers and operations staff at the property work together to plan and execute the event.
The event functions use assets that are specific instances of products at each property. Each product
is associated with a category and subcategory. Both categories and subcategories are associated with
charge codes. Each charge code is composed of taxes and service charges, which might be taxable.
The taxes and service charges linked with the charge code apply to the product.
Table 96. Event Tax Administration ERD Entities and Tables
Entity Table
Asset S_ASSET
Category S_CTLG_CAT
Charge Code S_EVT_CHRG_LST
Event/Function S_SRC
Event Location Room S_EVTLOC_ROOM
Position S_POSTN
Price List Item S_PRI_LST_ITM
Product S_PROD_INT
Property S_ORG_EXT, S_PARTY
Tax Code/Service Code S_PRI_LST

Team Member S_USER, S_PARTY
Applications
Figure 94. Event Tax Administration
Title : Event- Tax Administration

EVENT/FUNCTION EVENT LOCATION ROOM TAX CODE/SERVICE CODE

held at
FUNCTION
location of
belongs to
for
contains TAX CODE

composed of
held at PROPERTY
EVENT
holds
responsible for
TEAM has
MEMBER responsibility of
for
holders of
held by
POSITION
applies to
ASSET belongs to
owns composed of
user of SERVICE CODE

instance of
current price list of

for
PRICE LIST PRICE LIST
ITEM composed of
for
CHARGE composed of
CODE
for
subject of
child of
child of for subject of for
PRODUCT categorized in CATEGORY

parent to
parent to
for
Applications
Financial Account
This ERD (see Figure 95) illustrates how Siebel Financial Services supports tracking of financial
accounts (instances of products or assets). A financial account can be owned by an organization, or
a number of contacts. The owners can track the activities, service requests, balance history, and
transactions on their accounts, as well as the balance of their external accounts using Siebel Financial
Services. The manager can track the profitability of his customers through contact and account
profitability.
Table 97. Financial Account ERD Entities and Tables
Entity Table
Account Aggregation Service S_FN_AAG_SVC
Account Analysis S_FN_SRVC_TXN
Account Profitability S_ORG_PRFTBLTY
Activity S_EVT_ACT
Address S_ADDR_PER
Asset Relationship S_ASSET_REL
Assignment Group S_ASGN_GRP
Attachment S_ASSET_ATT
Authorization S_ASSETCON_AUTH
Balance History S_FN_ACCNT_BAL
Contact Profitability S_CON_PRFTBLTY

Fee S_FN_ACCNT_FEE
Financial Account Contact S_ASSET_CON
Financial Transaction S_FN_ACCNT_TXN
Note S_NOTE_ASSET
Product S_PROD_INT
Schedule S_FN_ACCNT_SCHD
Title : Financial Account
AUTHORIZATION
ADDRESS ASSIGNMENT
ACTIVITY
GROUP(TERRITORY)
PERSONAL for
ADDRESS participant in
defined for for
subject of
BUSINESS
ADDRESS
FINANCIAL ACCOUNT CONTACT
subject of
for
Figure 95. Financial Account
PRODUCT
ASSET NOTE ACCOUNT for
RELATIONSHIP CONTACT
ANALYSIS BALANCE ACCOUNT
AGGREGATION PROFITABILITY
HISTORY
for of SERVICE
for for
for used by of
FINANCIAL ACCOUNT
TRANSACTION PROFITABILITY
associated associated
located
subject of with with at for of
for problems with subject associated subject of

FINANCIAL ACCOUNT of subject of subject of target of with subject of
uses subject of
for problems with
SERVICE INTERNAL ACCOUNT
REQUEST subject of CONTACT
currently owned by
owner of
for
SCHEDULE subject of
subject of
for ORGANIZATION UNIT

FEE currently owned
subject of
by INTERNAL EXTERNAL
for ORGANIZATION ORGANIZATION
ATTACHMENT owner
of UNIT UNIT
subject of
EXTERNAL ACCOUNT

Applications
217
Applications
Financial Account Application

This ERD (see Figure 96) illustrates how Siebel Financial Services supports generation of a financial
product (loan, mortgage, or similar) application by a consumer (contact) or an organization. The
applicant is assessed based on incomes, expenses, assets, and liabilities. Fees and collateral are
associated with the application, and when it is approved, it generates a financial account (asset).
Table 98. Financial Account Application ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Address S_ADDR_PER, S_CON_ADDR
Application S_OPTY
Application Contact S_OPTY_CON
Application Product S_REVN
Assessment S_ASSESS
Asset Liab Contact S_FN_ASTLB_CON
Asset Liability S_FN_ASSET_LIAB
Collateral S_FN_OFFR_COLT
Credit Report S_FN_CRDT_RPT
Credit Report Item S_CRDT_RPT_ITEM

Fee S_FN_OFFR_FEE
Inc. Exp. Contact S_FN_INCEXP_CON
Income/Expense S_FN_INCM_EXP
Note S_NOTE_OPTY
Product S_PROD_INT
Quote S_DOC_QUOTE
Sales Stage S_STG
Trailing Document S_OPTY_DOC
Title : Financial Account Application
on
ASSET LIABILITY
subject of
uses reported in for has a
INCOME/EXPENSE
for associated
with
FEE COLLATERAL APPROVAL
reported in for incurred
by
for for to review
to review
for
ACTIVITY ASSESSMENT
VALUE
Figure 96. Financial Account Application
APPLICATION PRODUCT NOTE STATEMENT
OTHER ACTIVITY for

generates based on part of
a component of of of
for
TRAILING
QUOTE ASSESSMENT INC.EXP. ASSET LIAB.
DOCUMENT
CONTACT CONTACT
for for for for

based subject with with
based based uses
generates on on on to
associated APPLICATION CONTACT
with
APPLICATION
has LENDER APPLICANT
supported associated associated

with with has
by has
CREDIT ADDRESS
generated REPORT ITEM
used by by generates SALES
# SEQ_NUM for
STAGE for associated
belong has located at
FINANCIAL PRODUCT to
to subject
ACCOUNT in support located at for of has has has
of ORGANIZATION
contain
CREDIT REPORT CONTACT

acknowledged by
has
PRODUCT
for DISCLOSURE acknowledger of

Applications
219
Applications
Financial Account Origination

This ERD (see Figure 97) illustrates how to create an applicant group and how to include one or more
individual applicants or organizations for a financial product, such as loans, mortgages, savings, or
checking, in the applicant group. The organization that is included can also be an applicant or a legal
entity, such as a law firm associated with the applicant. Individual applicants can also include
guarantors, those who hold power of attorney, and so forth. Identity information about individuals,
such as passport or driver's license information, can be captured and used to create multiple actions
using the customer order management process. These actions can include opening accounts,
ordering forms, ordering credit or ATM cards, and so forth, and can be integrated with back-office
applications.
Table 99. Financial Account Origination ERD Entities and Tables
Entity Table
Account S_ORG_EXT, S_PARTY, S_APPLNTGRP_ACC
Applicant Group S_APPLNT_GRP
Applicant Group Contact S_APPLNTGRP_CON
Applicant Group Contact Identity S_APPLNT_IDENT
Contact (Person) S_CONTACT, S_PARTY
Literature S_LIT
Order S_ORDER
Order Document S_ORDER_DOC, S_ORDR_DOC_LIT
Order Item Document S_ORDERITM_DOC, S_ORDITMDOC_LI

Quote S_DOC_QUOTE, S_DOC_ORDER
Applications
Figure 97. Financial Account Origination

Title : Financial Account Origination
LITERATURE QUOTE ITEM

included in ORDER ITEM
DOCUMENT
made up of for for
for
included in ORDER
made up of DOCUMENT has composed of
for ORDER ITEM
QUOTE
for for child of parent to

has composed of for
APPLICANT GROUP referenced in PARTY
CONTACT ORDER
IDENTITY refer to serviced GROUP child of
serviced thro'
serviced thro' for serviced thro' thro' ORGANIZATION UNIT
for made up of parent of
APPLICANT GROUP ACCOUNT
included in
has composed of composed of

included in affiliated with member of
APPLICANT GROUP
CONTACT made up of
PERSON
contact for OTHER PERSON
applicant for
OTHER PARTY
Applications
Financial Investments
This ERD (see Figure 98) illustrates how Siebel Financial Services supports generation of financial
investments and other relevant associations with organizations, financial accounts, holdings,
distribution, and transactions. The major entities are depicted in the lower half of the diagram
(security and external organization).
Table 100. Financial Investments ERD Entities and Tables
Entity Table
Distribution S_FNSEC_DSTRBTN
External Organization S_ORG_EXT, S_PARTY
Earning S_FNSEC_ERNG
Holding S_FN_HLDNG
Industry S_INDUST
Literature S_LIT
Security S_PROD_INT
Transaction S_FN_ACCNT_TXN
Applications
Figure 98. Financial Investments

Title : Financial Investments
DISTRIBUTION
EXTERNAL ORGANIZATION
for
LITERATURE HOLDING TRANSACTION

INSTITUTIONAL
INVESTOR
for for
for for
PUBLIC COMPANY
subject of made against
INDUSTRY EARNING
FINANCIAL ACCOUNT for subject of
DIVIDEND
part of
for FINANCIAL INSTITUTION

for made up of
CAPITAL GAINS
subject of
CONTACT
for
for
subject of subject of subject of made against subject of subject of
SECURITY
invested by investor of
STOCK FUND
INTERNAL EXTERNAL
BOND
Applications
Financial Products
This ERD (see Figure 99) illustrates how Siebel Financial Services supports generation of financial
products and other relevant associations. Internal products, rates, fees, and product line information
is also depicted. The major entities are depicted in the lower half of the diagram (Product Internal).
Table 101. Financial Products ERD Entities and Tables
Entity Table
Benefit S_PROD_BNFT
Condition S_PROD_COND
Feature S_PROD_SPEC
Fee S_PROD_FEE
Product S_PROD_INT
Rate S_PROD_RATE
Applications
Figure 99. Financial Products

Title : Financial Products
BENEFIT CONDITION
for for for
for
contain subset subject of subject of
PRODUCT LINE FEATURE RATE FEE

within
of of of
composed of
part of has subject of has has
PRODUCT INTERNAL
made up of
part of
Applications
Financial Services Events

This ERD (see Figure 100) illustrates how Siebel Financial Services supports generation of marketing
events in a three-level hierarchy (parent events, sub events, and sessions). An event can be
associated with many opportunities, product lines, regions, or industries. It includes a list of
registrants (contacts or organizations). Vendors, venues, and suppliers are tracked for the event in
the organization entity. For persons, tracks the registration procedure and travel plans they might
participate in to attend the event.
Table 102. Financial Services Events ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Equipment Requirement S_ORDER_ITEM, S_QUOTE_ITEM
Event Cost S_SRC_COST
Event Location S_ORG_EXT, S_PARTY
Event Registration S_SRC_EVT_REG
Event Session S_SRC_EVT, S_SRC
Event Venue S_SRC_VENUE
Industry S_INDUST
Location Room S_EVTLOC_ROOM

Person S_EMP_PER, S_CONTACT, S_PARTY
Position S_POSTN
Product S_PROD_INT
Region S_REGION
Room Avail Equipment S_EVTLOC_RM_EQP
Travel Participant S_EVT_TRVL_PER
Travel Plan S_EVT_TRVL_PLAN
Vendor S_SRC_ORG
Vendor Offer S_EVT_VNDR_OFR
Vendor Review S_EVT_VNDR_RVW
Vendor Service S_EVT_VNDR_SVC
Applications
Table 102. Financial Services Events ERD Entities and Tables
Entity Table
Venue S_ORG_EXT, S_PARTY
Venue Offer S_EVT_VENUE_OFR
Venue Review S_EVT_VENUE_RVW
Venue Service S_EVT_VENUE_SVC
Title : Financial Services Events
Author : Oracle, Confidential reviewed by
228
VENDOR VENDOR VENDOR
PERSON
OFFER SERVICE REVIEW
reviewer of
offered by offered by for

provider of provider of subject of
Applications
VENDOR
from has for services

VENUE VENUE VENUE
OFFER SERVICE REVIEW reviewed by reviewer of
TRAVEL PLAN has TRAVEL

offered at offered at for includes

PARTICIPANT
serviced by
subject of provider of subject of participates member of
for
EVENT VENUE ACTIVITY EQUIPMENT POSITION INDUSTRY
REQUIREMENT
of location of for required by responsible subject of

Figure 100.Financial Services Events
subject for
held at subject of of in need of responsibility of has deals with
staffed by
composed inviter of on staff for
of part of
EVENT SESSION SUB EVENT PARENT EVENT invited to
part of composed subject of for
of EVENT
held at for REGISTRATION subject of
deals with promoted subject of has subject of

ROOM AVAIL via
EQUIPMENT ATTENDEE
available
in subject of relevant to deals with deals with
equipped
with location of WAIT LIST
PRODUCT LINE LITERATURE PRODUCT REGION
ITEM
LOCATION ROOM
associated with
CANCELLED
REGISTRANT
EVENT COST
in associated with
COST
participated
as includes
REVENUE
ORGANIZATION UNIT supplier of
for
EVENT LOCATION OTHER INVESTING part of
ORGANIZATION COMPANY
VENUE OTHER LOC UNIT

Applications
Fleet Management
Fleet Management enables transportation management customers to perform order capture, rating,
and order management of transportation orders. Figure 101 shows the Fleet Management ERD.
Return Route Orders functionality allows multiple stops to be created for a given location and allows
both origin and destination locations to reference the same location.
Order Revision Enhancements functionality provides stricter constraints for revising, rejecting, and
cancelling orders. Users will not be able to revise any inactive order or rejected order. Furthermore,
users will not be able to revise any order in which there is a relationship with a cancelled order.
After completing the order, the customer service representative submits the order to Oracle
Transportation Management. Oracle Transportation Management takes over the fulfillment of the
order from the Siebel application. The marketing department of the transportation provider defines
the targeted lanes; that is, the lanes where the company wants to focus on selling transportation
routes. A lane is a route between an origin and a destination, using a given line of business.
Whenever Oracle Transportation Management sends information that an order is complete, the Siebel
application adds information about this order to its order history. The order history aggregates
weekly orders for each account for each lane.
Table 103. Fleet Management ERD Entities and Tables
Entity Table
Account S_ORG_EXT
Address S_ADDR_PER
Business Unit S_BU
Contact S_CONTACT
Favorite Product Action S_PRDFAVITM_ACT

Favorite Product Item S_QUOTE_ITEM
Fleet Management Location S_LOCATION
Fleet Management Location Role S_LOC_ROLE
Fleet Management Order S_ORDER
Fleet Management Order Detail S_ORDER_FM_DTL
Fleet Management Order History S_FM_ORDER_HIST
Order Account S_ORG_EXT
Order Item Stop S_ORDITEM_STOP
Order Stop S_ORDER_STOP
Order Stop Action S_ORDSTOP_ACTN
Order Stop Detail S_ORDERSTOP_DTL
Applications
Table 103. Fleet Management ERD Entities and Tables
Entity Table
Quote S_DOC_QUOTE
Rating Solution S_RTNG_SLTN
Rating Solution Detail S_RTNG_SLTN_DTL
Rating Solution Detail Pricing S_SLTN_DTL_PRC
Targeted Lane S_TARGETED_LANE
Title : Fleet Management
ORDER STOP ACTION TARGETED LANE
RATING FAVORITE for for

SOLUTION PRODUCT
DETAIL ACTION ORDER ITEM STOP ORDER
PRICING STOP DETAIL
for for primary stop for

for
for for associated associated
has has has has
to to
has
ORDER ITEM ORDER STOP FLEET

MANAGEMENT
RATING LOCATION ROLE
Figure 101. Fleet Management
SOLUTION
DETAIL
has for for for for

has
for FLEET
for
has MANAGEMENT
QUOTE FAVORITE ORDER DETAIL
ITEM for PRODUCT ITEM
has has has
associated
for to has
RATING for primary for FLEET BUSINESS
SOLUTION MANAGEMENT UNIT
LOCATION
composed of
for for belongs to
QUOTE has primary for CONTACT
associated
has to
composed of
ADDRESS
has primary for
ORDER has has has has
has
OTHER FLEET MANAGEMENT ORDER owned by owner of
ORDER origin for ACCOUNT
for has
has
has primary for
destination
for
placed by owner for

FLEET MANAGEMENT
ORDER HISTORY
for has

Applications
231
Applications
Fleet Management - Location

This ERD (see Figure 102) illustrates how geographic locations related to fleet management can be
modeled to optimize deliveries or pickups for a given location. In this model, a given location is the
persons and organizations located in that general area and the addresses associated with the parties
in that area.
Table 104. Fleet Management - Location ERD Entities and Tables
Entity Table
Contact S_CONTACT, S_PARTY, S_LOC_CONTACT
Account S_ORG_EXT, S_PARTY, S_LOC_ACCNT
Address S_ADDR_PER, S_ADDR_CON, S_LOC_ADDR
Location S_LOCATION
Location Role S_LOC_ROLE
Applications
Figure 102. Fleet Management - Location
Title : Fleet Management - Location

LOCATION PARTY
has CONTACT
primary contact for
general location for

LOCATION primary role for
ROLE located in
has
defined for
has
parent of
ADDRESS child of
container for for
ACCOUNT
located in has
general location for

located in
has
primary account for
Applications
FLEXCUBE Universal Banking Integration

The FLEXCUBE Universal Banking Integration ERD (see Figure 103) describes the integration of
Siebel CRM with an external banking system. It provides new features, such as financial plans, goals,
and limits that can be specified for a customer.
Financial plans are investment plans created for customers after analyzing the customers financial
position, expected future cash-flows, inflation, returns, and goals. Financial goals include but are not
limited to education, retirement, investment, buying property, and so forth. The individual's goals
are used as guidelines to map a course of action to reach those goals. A financial limit specifies the
total liabilities of the customer arising out of the credit facilities used by the customer. A customer
can also provide financial mandates, which are instructions to initiate payment transactions at a
predetermined future time or frequency or for such future transactions.
Table 105. FLEXCUBE Universal Banking Integration ERD Entities and Tables
Entity Table
Account S_ORG_EXT, S_ORG_EXT_FNX
Branch S_ORG_EXT
Contact S_CONTACT, S_CONTACT_FNX
Financial Account S_ASSET, S_FN_ACCNT1_FNX
Financial Goal S_FN_GOAL
Financial Limit S_FN_LIMIT
Financial Mandate S_FN_MANDATE
Financial Plan S_FN_PLAN
Party S_PARTY
Product S_PROD_INT
Title : Flexcube Universal Banking Integration
PARTY
CONTACT
for
FINANCIAL PLAN
has
for
FINANCIAL GOAL
part of has
available to
FINANCIAL
LIMIT
has
sub-limit for
issued by
FINANCIAL
MANDATE
issuer of
associated to for
PRODUCT
associated to
FINANCIAL for
ACCOUNT
owned by
owner of
held at
BRANCH
for for ACCOUNT
Figure 103. FLEXCUBE Universal Banking Integration
subject of OFFER made by
maker of
owned by
owner of
for
subject of
subject to
specified for

Applications
235
Applications
Group Insurance Policies

This ERD (see Figure 104) illustrates how Siebel Financial Services supports generation of a group
policy instance, which can be either a group health or a group life policy, or other types of employee
benefits. One organization can own many policy instances. Each organization's employee is a primary
policy contact, and determines the type of coverage and the elements of coverage they enjoy. Each
contact covered by a policy instance includes an insurance coverage role, and the contact's
dependents are stored as coverage elements. The coverage role provides each coverage element
with multiple possible benefits.
Table 106. Group Insurance Policies ERD Entities and Tables
Entity Table
Census S_ORG_CENSUS
Census Detail S_CENSUS_DETAIL
Class S_VOD, S_VOD_VER
Class Attribute S_XA_ATTR
Coverage Role S_FN_CVRG_ROLE
Employee Class S_FN_GRP_CLASS
Instance Attribute S_ASSET_ITEM_XA
Policy Instance S_ASSET
Primary Policy Member S_ASSET_CON

Product Attribute S_PROD_INT_XA
Product Class S_FN_HLDNG
Product Class Rate S_FN_HLDNG_RATE
Product Component S_PROD_ITEM
Product Enrollment S_FNCVRG_ELMNTS
Product For Member S_APPLD_CVRG
Product Instance S_ASSET_ITEM
Rate Band S_PROD_RATE
Title : Group Insurance Policy
COVERAGE ROLE
for beneficiary of under PRODUCT CLASS RATE

benefits
PRODUCT
ENROLLMENT applied to
for part of
made up subject to
for
of belongs
to
PRODUCT FOR PRODUCT CLASS
MEMBERS has
based on
for available for for based on
CONTACT INSTANCE ATTRIBUTE
Figure 104.Group Insurance Policies
made up of for has of based on

of made up of
CENSUS
primary of subject of has DETAIL part of PRODUCT
INSTANCE
PRIMARY POLICY MEMBER belongs to EMPLOYEE
CLASS for part part of has
has part of of basis of
of
for used for for has

PRODUCT CLASS
COMPONENT ATTRIBUTE
CENSUS
for of of basis
based of
on
for has has
has made up of PRODUCT
CLASS ATTRIBUTE
ORGANIZATION UNIT subject of
part of part of based
on
has
EXTERNAL ORGANIZATION UNIT
RATE made up of
BAND
owner of
associated
with basis
belongs basis of
has uses owned by subject of has to of
has has has
POLICY INSTANCE PRODUCT INTERNAL
GROUP HEALTH GROUP LIFE OTHER EMPLOYEE

BENEFITS

Applications
237
Applications
Group Pensions
This ERD (see Figure 105) illustrates how Siebel Financial Services supports group pension plans. The
group pensions module is designed to meet the needs of sales and service professionals, managers,
and pension administrators. Users can define group pension plans, plan classes, plan eligibility rules,
and plan funding vehicles. When a pension plan is defined, users can track eligible and enrolled
participants, participant contribution and investment allocations, and participant beneficiary
information.
Table 107. Group Pensions ERD Entities and Tables
Entity Table
Allocation S_APPLD_CVRG
Beneficiary S_FN_CVRG_ROLE
Employee Class S_FN_GRP_CLASS
Funding Vehicle S_PROD_REL
Group Pension Participant S_CONTACT, S_PARTY
Group Pension Plan S_ASSET
Group Pension Plan Contact S_ASSET_CON
Organization Unit S_BU
Pension Plan Offering S_PROD_INT
Applications
Figure 105.Group Pensions

Title : Group Pensions
PRODUCT
FUNDING
for ALLOCATION VEHICLE
BENEFICIARY of
has by
having for
of set up part of
PARTICIPANT belongs to EMPLOYEE CLASS made up of
has
part of
used for has
belong to
for has
CONTACT
ORGANIZATION UNIT PENSION

PLAN
has
for consists of uses
GROUP PENSION INSTANCE

part of
has
Applications
Health Provider and Provider Group

This ERD (see Figure 106) illustrates how Siebel Financial Services supports generation of heath-
related organizations (such as hospitals) and providers (such as physicians). A provider can be
affiliated with one or more organizations and can deliver a health product (a medical service) to a
contact or a patient during an encounter. Siebel Financial Services also stores payments made to a
provider by an organization, as well as the specialty, language, and schedule of the provider.
Table 108. Health Provider and Provider Group ERD Entities and Tables
Entity Table
Encounter S_FN_HLTH_ENCTR
Health Product S_PROD_INT
Language S_CONTACT_FNXM
Provider Group Schedule S_ORG_TIME
Provider Schedule S_CON_LOCTN
Specialty S_CONTACT_FNXM
Applications
Figure 106.Health Provider and Provider Group

Title : Health Provider/Provider Groups
ORGANIZATION
EXTERNAL ORGANIZATION UNIT
PROVIDER GROUP
subject of provides employs subject of make
belongs to
in provided by
PROVIDER GROUP
serve SCHEDULE
ENCOUNTER HEALTH
serve at PRODUCT
involves involves delivered by

made by
PROVIDER SPECIALTY LANGUAGE PAYMENT

SCHEDULE
belongs to for spoken by made to
specialized beneficiary
CONTACT part of part of subject of delivers part of in speaks of
PATIENT PROVIDER
Applications
High Tech Special Pricing Authorization

This ERD (see Figure 107) illustrates the special pricing authorization business process for Siebel
High Tech, which uses the Meet Competition Quote and Design Registration features. The quote or
design registration opportunity leads to an Agreement with Entitlements for discounts on products.
Point of sale data includes claim items, which can refer to agreed upon entitlements.
Table 109. High Tech Special Pricing Authorization ERD Entities and Tables
Entity Table
Account S_ORG_EXT
Address S_ADDR_PER
Claim Item S_POS_CLAIM_ITM
Design Registration S_OPTY_DSGN_REG
Entitlement S_ENTLMNT
Entitlement Product Price S_ENTL_PRDPRI
Meet Competition Quote S_DOC_QUOTE
Opportunity S_OPTY
Point of Sale Header S_POS
Point of Sale Item S_POS_ITEM
Product S_PROD_INT
Quote Line Item S_QUOTE_ITEM
Title : High Tech Special Pricing Authorization
POINT OF SALE ITEM for PRODUCT
subject of
OTHER POS
ITEM
ENTITLEMENT
PRODUCT PRICE
for
having
CLAIM ITEM for
having
ENTITLEMENT QUOTE LINE

ITEM
specially quoted for
referencing
subject of
Figure 107.High Tech Special Pricing Authorization
support
for
for part of
for for
made up composed
composed of of
of OPPORTUNITY
for MEET
AGREEMENT
POINT OF COMPETITION OTHER DESIGN designed
SALE associated
QUOTE OPPORTUNITY REGISTRATION for
HEADER with
subject of
initiated
by
for
associated
with
created for
ADDRESS for
for
subject of located
at subject of subject of subject of
ACCOUNT

Applications
243
Applications
Hospitality Category
This ERD (see Figure 108) illustrates how Siebel Hospitality supports the categorization for revenue.
There can be N levels of the revenue category in the hierarchy. One parent category can include one
or more categories, and one category can include one or more subcategories. The subcategory is
defined for the charge code and product, and a report is generated by category for each function and
quote. Function and quote revenue by category hierarchy supports the hierarchical category. A macro
estimate for the opportunity and quote is generated at the category level.
Table 110. Hospitality Category ERD Entities and Tables
Entity Table
Hospitality Category S_CTLG_CAT
Parent Category S_CTLG_CAT
Category S_CTLG_CAT
Subcategory S_CTLG_CAT
Category Revenue S_AVG_VAL_TNT, S_FN_CATRV_TNT, S_QUO_CATRV_TNT
Function Average Level S_AVG_VAL_TNT
Function Revenue by Category S_FN_CATRV_TNT
Quote Revenue by Category S_QUO_CATRV_TNT
Quote Macro Revenue Estimate S_QUO_MEST_TNT
Opportunity Macro Revenue S_OPTY_MEST_TNT

Estimate
Charge Code S_EVT_CHRG_LST

Function Business Type by Date S_BIZ_TP_DT_TNT
Function S_FUNC_TNT
Function Report Section S_FUNC_RPT_SECT
Property Report Section S_PROP_RPT_SECT
Report Section S_RPT_SECT_TNT
Property/Asset S_ORG_EXT
Quote S_DOC_QUOTE
Opportunity S_OPTY
Tax/Service List S_PRI_LST
Title : Hospitality Category
REPORT SECTION contain PROPERTY/ASSET

included in
FUNCTION
contain included in
charged through
INVOICE
child of
for
CATEGORY REVENUE parent of child of
subject of
FUNCTION REVENUE BY CATEGORY
for HOSPITALITY CATEGORY parent of

for
subject of
has PARENT
Figure 108.Hospitality Category
FUNCTION subject of CATEGORY

BUSINESS FUNCTION AVERAGE LEVEL
TYPE BY of
DATE
for parent of child of parent of
subject of
QUOTE QUOTE REVENUE BY CATEGORY
for
child of
subject of for
QUOTE MACRO REVENUE ESTIMATE CATEGORY
for subject of
generated from
lead to
for
subject of
OPPORTUNITY OPPORTUNITY MACRO REVENUE ESTIMATE
for subject of
parent of
child of
PRODUCT OR associated with SUB CATEGORY

SERVICE for
related with
associated with
TAX / SERVICE LIST CHARGE CODE subject of
defined for

Applications
245
Applications
Hospitality - Meeting Package

This ERD (see Figure 110) illustrates how offerings from a hospitality organization can be packaged
as a product. Products can include one or more functions, such as breakfasts, dinners, weddings,
receptions, board meetings, or share holders' meetings, as well as facilities used for the functions,
such as rooms, conference halls, and dining halls. The package can also include video and audio
equipment, and so forth.
Table 111. Hospitality - Meeting Package ERD Entities and Tables
Entity Table
Display Abbreviation S_PTY_LOV_ABBR
Meeting Function S_MTG_FNCTN
Meeting Function Item S_MTG_FNCTN_ITM
Meeting Package S_PROD_MTG_PKG, S_PROD_INT
Meeting Package Item S_MTG_PKG_ITEM
Meeting Package Room S_MTG_PKG_ROOM
Meeting Package Room Price S_MTG_PKGRM_PRI
Product S_PROD_INT
Quote/Order S_DOC_QUOTE, S_DOC_ORDER, S_QTE_MTG_PKG
Applications
Figure 109.Hospitality - Meeting Package
Title : Hospitality - Meeting Package

DISPLAY
ABBREVIATION
PRODUCT
MEETING include
PACKAGE ITEM facility or equipment for
MEETING PACKAGE MEETING include

ROOM PRICE FUNCTION ITEM
facility or
equipment
for
part of defined for for
QUOTE/ORDER
priced through composed of
MEETING MEETING
PACKAGE ROOM FUNCTION
for
included in part of
ordered through made up of made up of made up of
MEETING PACKAGE
Applications
Institutional Sales
This ERD (see Figure 110) illustrates how Siebel Financial Services supports generation of a product
or security traded in the stock market. One or more positions (such as institutional salespeople) can
cover a product. A position owns and prepares a call list containing one or more contacts, who are
the objects of the calls associated with any number of products. Siebel Financial Services also tracks
security or product line interests of a contact, as well as the securities held by an organization unit
(such as a company). Siebel Financial Services creates many-to-many relationships when storing the
literature associated with employees, activities, and products. A position can send any number of
pieces of literature to a contact within one activity.
Table 112. Institutional Sales ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Industry S_INDUST
Literature S_LIT
Product S_PROD_INT
Title : Institutional Sales
POSITION INDUSTRY ACTIVITY EMPLOYEE
owns covers covers subject uses author

of of
PRODUCT LINE
Figure 110.Institutional Sales
covers attached to authored by

object of
interest of
LITERATURE
covered
owned by by interested in about
subject
of ORGANIZATION UNIT
CALL LIST CONTACT
part EXTERNAL
of ORGANIZATION
associated interested UNIT
with in
holds issues
subject held issued

PRODUCT of object of interest of covered by subject of by by
SECURITY

Applications
249
Applications
Insurance Claims
This ERD (see Figure 111) shows the important entities in the Insurance Claim recording and
handling process. It illustrates the relationship between claims and claim elements and the various
parties to the claim. It covers the association of invoices, invoice line items, payments and recoveries
to claims. Also illustrated is the relationship between claim and insurance policy, activity, service
request, document, appraisal, and so forth. The diagram also shows the metadata that supports
claims and claim elements.
Table 113. Insurance Claims ERD Entities and Tables
Entity Table
Activity S_EVT_ACT, S_EVT_ACT_FNX
Assignment Group (Territory) S_ASGN_GRP, S_INSCLM_TERR
Claim Account S_INSCLM_ORG
Claim Appraisal S_INSCLM_APRSL
Claim Appraisal Attachment S_INSCLM_AP_ATT
Claim Contact S_INSCLM_CON, S_INSCLMCON_ORG
Claim Document S_INSCLM_DOC
Claim Element S_INSCLM_ELMNT
Claim File Attachment S_INSCLM_CL_ATT
Claim Payment S_SRCPAY_INSCLM
Claim Property S_INSCLM_PRPTY
Claim Recovery S_INSCLM_RECVRY

Contact S_CONTACT, S_PARTY, S_CONTACT_FNX
Default Coverage S_DEFAULT_ADMIN
Injury S_INSCLM_INJURY
Insurance Claim S_INS_CLAIM

S_INSCLM_FRAUD
S_INSCLM_SBRGTN
S_INSCLM_UW
Insurance Policy S_ASSET
Insurance Policy Item S_INS_ITEM
Invoice S_INVOICE, S_INVC_PAYMENT
Invoice Line Item S_INVOICE_ITEM
Loss Code S_INS_LOSS_CODE, S_LOSSCD_PLNITM
Loss Code Coverage S_INS_LOSCD_COV
Applications
Table 113. Insurance Claims ERD Entities and Tables
Entity Table
Loss Event S_INSCLM_EVT
Organization S_ORG_EXT
S_PARTY
S_ORG_EXT_FNX
Party S_PARTY
S_SRCPAYMT_CON
S_SRCPAYMT_ORG
S_INVC_PAYMENT
Reserve Code S_INS_RSRV_CODE
Service Request S_SRV_REQ, S_SRV_REQ2_FNX

Oracle
252

+ '" &$

$[N

13
+"$
Applications
3 2 26

'"
$

3
13
$
2 TT '"+

14
13

14
Figure 111.Insurance Claims

2 2

6
$>
'"+"$
14
%$
13

6 6 $%&$
2 1 $=&+ ' +"
1
'"*'
9"$ 213
$> '$"
'%% ! '" >+
'" >
! &"$
%'
9"$ 6 6 2
1 6
2 6
'"
6
>+ 14 $%&$
' +
1
!*&'
14 14 >

14
14 6
14 14 2
14 13
13 %%
$"$

&`) '%%
'" '%% %>
'"'"$ >$
%' ! 7&%T
14

13 1

6

13
14 14

14 14 14
%> ! 13

2

14 6
14 14 14
14 14
14
$%&$ '"
Applications
Insurance Policies
This ERD (see Figure 112) illustrates how Siebel Financial Services supports generation of insurance
policies and related insurance policy items. The major entities are depicted in the bottom half of the
diagram (insurance policy and insurance policy items). Insurance policies relate to households as
well as contacts. Policy coverages, discounts, payment plans, and claim summaries are also
supported.
Table 114. Insurance Policies ERD Entities and Tables
Entity Table
Claim Summary S_INS_CLAIM
Condition S_INSITEM_CNDTN
Discount S_APPLD_DISCNT
Drivers License S_DRVR_LICENSE
Household S_ORG_GROUP, S_PARTY
Household Contact S_GROUP_CONTACT
Insurance Coverages S_APPLD_CVRG
Insurance Document Item S_INS_DOC
Insurance Policy S_ASSET
Insurance Policy Item S_INS_ITEM
Insurance Policy Item Account S_INSITEM_ACCNT

License Restriction S_DL_RSTRCT
Payment Plan S_PAY_PLAN
Policy Contact S_ASSET_CON
Title : Insurance Policies
254
DISCOUNT
HOUSEHOLD CONTACT
applied to applied to
membership in membership of
Applications
LICENSE
RESTRICTION
INSURANCE POLICY ITEM

ACCOUNT applicable to
INSURANCE COVERAGE
made up of
on on
HOUSEHOLD
applied to part of
subject to
Figure 112.Insurance Policies
owner of
DRIVERS
subject of INSURANCE DOCUMENTATION LICENSE
ITEM
POLICY CONTACT
ACCOUNT
associated with associated with on issued to
for
CONDITION PAYMENT
PLAN
CLAIM
characteristic of SUMMARY
named as subject of holder of
applicable to
made against CONTACT
subject to subject of owned by

subject to
characterized by subject of subject of subject of composed of subject to subject of subject of
INSURANCE POLICY ITEM INSURANCE POLICY
POLICY INSTANCE
VEHICLE WATERCRAFT SCHEDULED
PERSONAL AUTO
PROPERTY covered by PERSONAL
subject to UMBRELLA
coverer of
DWELLING OTHER parent of LINES
INSURANCE OTHER PROPERTY
POLICY ITEM
composed of

part of
Applications
Life Insurance Policy

This ERD (see Figure 113) illustrates how Siebel Financial Services supports generation of life
insurance policies and annuities as assets. Each asset can be owned by an organization or a number
of contacts, and the owners can specify the coverage and beneficiaries under the policy. The owner
can execute a multitude of operations on the asset such as transfers, payments, withdrawals, and
surrenders.
Table 115. Life Insurance Policy ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Assessment S_ASSESS
Asset Contact S_ASSET_CON
Beneficiary S_FN_CVRG_ROLE
Beneficiary Class S_FN_BENFCLASS
Bill Account S_INS_BILLACCT
Coverage Option S_CVRG_OPTION
Financial Transaction S_FN_ACCNT_TXN
Financial Transfer S_FN_ASSET_TXFR
Holding S_FN_HLDNG
Insurance Claim S_INS_CLAIM

Insurance Coverage S_APPL_CVRG
Pay Plan S_PAY_PLAN
Product S_PROD_INT
Withdrawal/Surrender S_PAYMT_REQ
Title : Life Insurance Policy
256
ASSESSMENT
VALUE
BENEFICIARY
Applications
for
belongs of includes a component of FINANCIAL TRANSACTION
to
COVERAGE ASSESSMENT
OPTION
made up of
for for
for ORGANIZATION
subject in context of
subject SERVICE FINANCIAL
of REQUEST
has of part of responsible for TRANSFER
part of
Figure 113.Life Insurance Policy
INSURANCE undertaken for for

PERSON initiate of by
COVERAGE
requested by ACTIVITY
for contact undertake
for for
for
contact of
for for
ASSET
CONTACT associated with
associated subject of
contact with HOLDING
of INSURANCE
for CLAIM
subject PAY PLAN part of based on
of
set up
for owner of
BENEFICIARY owner of
CLASS subject of
applicable BILL WITHDRAWAL

to ACCOUNT /SURRENDER
for
subject associated
subject contact subject subject owned
of owned subject of with has
of of of subject of by includes basis of
by
FINANCIAL ACCOUNT PRODUCT
POLICY INSTANCE

LOAN
guaranteed by
based on
ANNUITY
guarantees
basis of
guaranteed by
LIFE POLICY
guarantees
Applications
Loyalty
This ERD (see Figure 114) illustrates how programs and promotions are created for customer loyalty.
Partner companies can have an association with a loyalty hosting company to create a loyalty
program. A program is the highest level entity in Siebel Loyalty. Members, tiers, promotions, point
values, and so on are all specific to a single program. The members of the loyalty program can be
individuals, households or accounts. A loyalty member can accrue or redeem points based on their
individual transactions. Pricing rule, Pricing Range, Point Subtype, Incentive Choice, and Partner
Statement entities support enhancements to features such as Post-Paid and Pre-Paid Partnership
Management, Promotion Registration Service and so on.
Accrual, redemption, promotion, enrollment, member administration, partner administration and

other functions are described in more detail as follows:
Accrual Processing. Allows unified partner point type for simplified billing. Accrual templates
are used for configurable transaction validations. Multiple partner debits for joint promotions
enable cost sharing among partners. User-defined controls and billing triggers are provided to
manage partner point balance. Allows joint rewards to benefit the organization for employees
business transactions.
Promotion. Supports range-based points calculation as well as issuing vouchers as an accrual

reward. Promotion criteria now includes product and partner attributes and leverages target lists
of members linked to marketing campaigns or generated using analytics.
Redemption. Supports distance-based zones to support air redemption pricing used by some
airlines and carriers. Multiple currency and multiple modes of payment are allowed. Automated
point loans can be assigned to members with an insufficient balance for redemption, based on
their tier status. Variable redemption pricing enables member differentiation. OOTB business
services support end-to-end redemptions from third-party interfaces. A voucher-based
redemption model supports service awards.
Member Administration. Automated tier upgrades recognize member relationships. Tier

assessment enhancements support additional models like anniversary-based, fixed-date and
rolling-period models. Tier change approvals prevent key members from automatic downgrade
of their membership status. Bulk member administration facilitates effective service recovery
through dynamic targeted rewards. User-defined membership statuses manage the membership
life cycle.
Enrollment. The member data model has been enhanced for enriched analytics and
segmentation. Batch enrollment processing has been enabled for bulk member creation and pre-
created memberships enable instant member acquisition.
Outbound Communication. Outbound communication will be triggered when certain events

occur. Content is now generated in XML format for compatibility with third-party fulfillment
applications.
Post-Paid and Pre-Paid Partnership Management. Supports both post-paid and pre-paid
partnerships. Post-paid partners are billed based on a pay-as-you-go basis. The bill frequency
can be based on time or a threshold value. Credit limits can be set for pre-paid partners; the
partners cannot reward points to the members beyond the limit. After the limit is reached, they
have to reorder for points. Partner statements can be generated.
Point sub-type related data-model enhancements. Point subtype information is captured to

aid points administration.
Applications
Points Reactivation: Enables reactivation of points. Loyalty members point balances expire
if not used for a given expiration period. Upon request by a loyalty member, these points can be
reactivated with some charges applied to the members account.
Gift Miles Service. Loyalty members are allowed to gift accrued points to other members.
Promotion Registration Service. Incentive choices are available at the promotion level.
Airport-Zone Map for Coterminal Identification. Tracks zone details of airports. Loyalty
programs can use zone details to allow members to accrue points based on zone travel.
Table 116. Loyalty ERD Entities and Tables
Entity Table
Account S_ORG_EXT
Accrual Item S_LOY_ACRL_ITM
Accrual Item Detail S_LOY_ACRL_DTL
Accrual Template S_LOY_ACRL_RULE,S_ACRL_RULE_ITM
Activity S_EVT_ACT_LOYX
Attribute Definition S_LOY_ATTRDEFN
Bucket S_LOY_BUCKET
Hosting Company S_ORG_EXT
Household S_ORG_GROUP
Incentive Choice S_LOYPR_ICHOICE
Individual S_CONTACT
Loan S_LOY_LOAN
Loyalty Program S_LOY_PROGRAM
Loyalty Program Member S_LOY_MEMBER
Loyalty Promotion S_LOY_PROMO
Loyalty Transaction S_LOY_TXN
Loyalty Transaction Log S_LOY_TXN_LOG, S_LOY_TXNEN_LOG
Membership Card S_LOY_CARD
Package Product S_LOY_TXN_ITEM
Partner Product Offering S_PGM_ORG_PROD
Partner Statement S_PROGORG_STMT
Partner Transaction S_LOY_PRT_TXN
Point Type S_LOY_ATTRDEFN
Point Subtype S_LOY_PTSUBTYP
Applications
Table 116. Loyalty ERD Entities and Tables
Entity Table
Pricing Options S_LOY_PROD_PT
Pricing Rule S_LOY_PRI_RULE
Pricing Range S_LOY_PRI_RANGE
Product S_PROD_INT
Program Partner S_ORG_EXT, S_LOY_PROG_ORG
Purchase Transfer Limits S_LOY_PURTRN_LM
Redemption Activity S_LOY_RDM_ACT
Redemption Item S_LOY_RDM_ITM
Service Product Association S_LOY_SRV_PROD
Statement S_LOY_STMT
Status Restriction S_LOY_MSTAT_PRF
Tier S_LOY_TIER
Tier Class S_LOY_TIER_CLS
Tier Reward S_LOY_REWARD
Travel Information S_LOY_TRVL_INFO
Voucher S_LOY_MEM_VCHR
TIER
REWARD
260
Title : Loyalty
for
qualified for
Applications
part of available for

made up of LOAN TIER
qualifies for
belongs to
for LOYALTY PROGRAM MEMBER
Figure 114.Loyalty
STATEMENT for
subject of defined for
part of
BUCKET LOYALTY made up of
subject of PROMOTION
qualified for
owned by
opted in by TIER CLASS
VOUCHER uses
ATTRIBUTE for
owner of used by DEFINITION
of defined for
ACCRUAL ITEM REDEMPTION

DETAIL ACTIVITY type for
POINT
BLOCK
done by of
ACTIVITY
for part of
executor of defined for uses owned by
LOYALTY PACKAGE
referred by
TRANSACTION PRODUCT
TRAVEL for LOG
INFORMATION
subject of for part of partnered with
has made of made of
owned by reference for has
MEMBERSHIP
CARD subject of
owns LOYALTY TRANSACTION
for
enrolled by enrolled by enrolled by in REDEMPTION for

ITEM
subject of child of
in in in
for
PRICING owner of involved in
OPTIONS INDIVIDUAL HOUSEHOLD ACCOUNT based on
basis for POINT
TYPE
for parent of PROGRAM PARTNER
defined for
uses ACCRUAL
ITEM subject of defined for
PRODUCT
for
in involved in
made of
HOSTING PURCHASE
ACCRUAL PARTNER COMPANY TRANSFER SERVICE
TEMPLATE PRODUCT STATUS
PARTNER TRANSACTION LIMITS
ASSOCIATION RESTRICTION
PRODUCT
OFFERING defined for
for used by
used by defined for subject of host for used by
subject of for run by subject of subject of uses subject of
uses uses uses partnered with
uses
LOYALTY PROGRAM

Applications
Loyalty Flowchart and Formula

This ERD (see Figure 115) illustrates how Loyalty Promotion flowcharts help to execute promotions
in a particular sequence. They can be used to validate the sequence of the promotions and calculate
the points awarded for a particular flow.
Loyalty Formulas are used to create and store a set of objects and operators specific to a loyalty
program. Values can be calculated based on input from third parties and then the resulting value can
be taken into account within a promotion. A formula can be available for use by a promotion only if
it is associated with the same loyalty program as that promotion. Once validated, a formula is
available for use in promotion criteria and actions. When used in promotion criteria and actions, the
object is the formula and the attributes are a list of user-defined formulas.
Table 117. Loyalty Flowchart and Formula ERD Entities and Tables
Entity Table
Attribute Definition S_LOY_ATTRDEFN
Loyalty Flow Connector S_LOY_FLW_CNCTR
Loyalty Flow Step S_LOY_FLOW_STEP
Loyalty Formula Step S_LOY_FRML_STEP
Loyalty Process Flowchart S_LOY_PROC_FLOW
Loyalty Program S_LOY_PROGRAM
Loyalty Program Formula S_LOY_PRG_FRML
Loyalty Promotion S_LOY_PROMO
Loyalty Promotion Phase S_LOY_PHASE_PRM
Program Partner S_ORG_EXT, S_LOY_PROG_ORG
Applications
Figure 115. Loyalty Flowchart and Formula

Title : Loyalty Flowchart and Formula
LOYALTY PROMOTION PHASE
for for
associated with associated with
LOYALTY ATTRIBUTE LOYALTY has refers to LOYALTY

evaluated in
FORMULA DEFINITION PROMOTION FLOW
STEP for STEP
evaluated
by of LOYALTY has from step
defined FLOW
for CONNECTOR
available for has to step
defined for
part of part of defined for
consists
of uses consists of consists of
LOYALTY PROGRAM FORMULA LOYALTY PROCESS FLOWCHART defined

for
PROGRAM
subject PARTNER
of
defined for defined for involved in
subject of subject of consists of subject of partnered with
LOYALTY PROGRAM
Applications
Managed Care
This ERD (see Figure 116) illustrates how plan design, formulary, and formulary product are used in
Siebel Life Sciences. An account contains plan designs, which have relationships to contacts. Each
plan design contains formularies, which are associated with markets that are essentially products.
Each formulary contains formulary products, which are child products for the market with which the
formulary is associated.
Table 118. Managed Care ERD Entities and Tables
Entity Table
Formulary S_INSPLN_FRMLY
Formulary Product S_PLNFRMLY_PROD
Health Care Professional S_CONTACT, S_PARTY
Managed Care Plan S_INS_PLAN
Plan Design Contact S_INSPLAN_CON
Product, Market S_PROD_INT
Applications
Figure 116.Managed Care
Title : Managed Care

child of
is PRODUCT
FORMULARY PRODUCT
for
parent to
for
contains of has
FORMULARY defined for MARKET

for
for
composed of
MANAGED CARE PLAN
accepted by provided by
acceptor of provider of
HEALTH CARE has ACCOUNT

PROFESSIONAL
associated
with
Applications
Medical Education Event Management

This ERD (see Figure 117) illustrates the significant entities related to medical education events
including plans, subplans, funds, events, sessions, products, and team members (employees).
Medical education event planning also supports the allocation and aggregation of medical education
budgets and expenditures for individual team members.
Table 119. Medical Education Event Management ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Event S_ME_EVT_LS
Event Invitee S_ME_EVT_INV_LS
Event Position S_ME_EVT_POS_LS
Fund S_MDF, S_ME_PLN_MDF_LS
Literature S_ME_SES_LIT_LS
Material S_ME_SES_MAT_LS
Period S_PERIOD
Plan S_ME_PLN_LS
Product S_ME_SES_PRD_LS, S_ME_EVT_PRD_LS, S_ME_PLN_PRD_LS, S_PROD_INT
Session S_ME_SES_LS
Session Invitee S_ME_SES_INV_LS
Title : Medical Education Event Management
266
Applications
POSITION
PRODUCT
child of parent of
FUND PLAN
allocated to PERIOD
using
in
for
allocated funds by owner of

allocating funds for promotion of owned by
child plan of
Figure 117.Medical Education Event Management
top plan for for
ACTIVITY for
EVENT
source of subject
to
promoted at team
composed of
promotion of EVENT POSITION of
to for team member for

PERSON invitee for
EVENT
INVITEE inviter of
of
EMPLOYEE
part of
for
of
composed of
SESSION to
INVITEE SESSION
inviter of MATERIAL
having
speaker at
CONTACT for
having

usage of LITERATURE
promoted at
relevant to
promotion of
Applications
Objectives
This ERD (see Figure 118) illustrates how the Siebel Consumer Goods application supports the
objective process as part of retail execution. The retail execution process begins with the creation of
an objective. Objectives are generated to help facilitate the process of accomplishing certain goals.
This model shows that an objective can be applied to many accounts, including accounts with
multiple contacts. There are generally multiple activities that belong to an objective, activities which
require follow-through to help bring the objective to fruition. The objective must be executed by
personnel who are assigned to the objective, its accounts, and activities.
Table 120. Objectives ERD Entities and Tables
Entity Table
Account S_PARTY, S_ORG_EXT
Activity Details S_EVT_ACT
Contact S_PARTY, S_CONTACT
Objective S_SRC
Position S_POSTN
Applications
Figure 118.Objectives
Title : OBJECTIVES
ACCOUNT CONTACT ACTIVITY DETAILS
target of target of has
for for subject to
OBJECTIVE
assigned to
responsible for
POSITION
Applications
Personalized Content Delivery

The Personalized Content Delivery feature allows pharmaceutical sales representatives to deliver a
sales communication to general practitioners and medical specialists using multimedia visualizations.
This ERD (see Figure 119) illustrates how a Message Plan is associated with Messages, Products
Presentation Details and Party Entities such as Account, Contact, Position and Business Unit.
Table 121. Personalized Content Delivery ERD Entities and Tables
Entity Table
Activity S_EVT_ACT, S_EVT_ACT_LSX
Assessment Template S_TMPL_PLANITEM
Business Unit S_PARTY, S_BU
Decision Issues S_ISS
Message S_LIT, S_LIT_LSX
Message Product Application S_LIT_PROD_APPL
Messaging Plan S_MSG_PLAN
Messaging Plan Item S_MSGPLAN_ITM
Objective S_SRC
Period S_PERIOD
Position S_PARTY, S_POSTN
Presentation Details S_PCD_DETAIL
Product S_PROD_INT
Title : LS Personalized Content Delivery
270
for
MESSAGING
PRODUCT
Applications
PLAN associated to
has
parent of
ASSESSMENT TEMPLATE
for
MESSAGE PRODUCT has DECISION

for for ISSUES
APPLICATION
for
has for
child of child of has has parent of
has
parent of MESSAGING PLAN MESSAGE
has ITEM for child of
for
Figure 119.Personalized Content Delivery
for
has
associated to
has for PRESENTATION ACTIVITY
OBJECTIVE for
DETAILS
for has PARTY
associated to ACCOUNT
has for
OFFER for
for has
associated to CONTACT
for for
has associated to
POSITION
has
creator of
created by
associated to
BUSINESS
for UNIT
period of

PERIOD
period for
Applications
Public Sector Benefit Case Management

This ERD (see Figure 120) illustrates how Benefit Case Management supports benefits determination
and case-information verification, specifically:
Eligibility Determination. Provides the capability to develop benefits plans that allow
caseworkers to make eligibility changes in program rules that impact benefit disbursement while
reducing the number of overpayments. The feature provides the ability to submit individual or
household profiles to a rules engine for eligibility determination. Enhancements for Siebel 8.2
include Benefits Plan History, Lock Benefits, Reassess Circumstances, and Payment History.
This ERD illustrates that a Benefit Plan is created under a Benefit Program that consists of one
or more Benefit Program Items. Benefit Program Items include one or more Products. A Benefit
Plan also consists of Benefit Plan Items that are associated with a Recipient, provided by a
Provider and associated with a Product. This ERD also shows that a Benefit Plan belongs to a Case
and that a Case can have a Change of Circumstance which might or might not be associated with
a Benefit Plan.
Effective Dating. Allows the application to capture, store and output change history for an
effective-dating enabled (ED-enabled) business component in terms of its field data as well as
its relationship to other business components. Using the change history, the system can
reconstruct data for a given point in time. Effective Dating is preconfigured for the Contact,
Household and Income Business Components.
Supporting Tasks. Helps a caseworker verify information during the intake process, where the
caseworker uses the Public Sector application to document that the information was verified, how
verification was accomplished and who verified the information. The caseworker performing
quality assurance is presented with cases based upon random selection, queued, or high-risk
profiles.
As the ERD shows, a Case Verification Template is associated with a Case and can consist of one
or more Case Verification Items. The Case Verification Template Items can be associated with a
submitter and a verifier. This feature can also help a quality-assurance worker review cases
following a checklist for adherence to standards and ensuring that each case is reviewed in the
same way.
Table 122. Public Sector Benefit Case Management ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Benefit Plan S_CASE_BNFTPLAN
Benefit Plan Item S_BNFT_PLAN_ITM
Benefit Plan Item Payment S_SRC_PAYMENT
Benefit Program S_BNFT_PGM
Benefit Program Item S_BNFT_PGM_ITM
Case S_CASE, S_CASE_PSX
Applications
Table 122. Public Sector Benefit Case Management ERD Entities and Tables
Entity Table
Case Verification Item S_ASSESS_ATTRIB
Case Verification Template S_TMPL_PLANITEM
Change of Circumstance S_CASE_CHGOFCCM
Party S_PARTY
Product S_PROD_INT
Quality Assurance Items S_ASSESS_ATTRIB
Quality Assurance Template S_TMPL_PLANITEM
User S_PARTY, S_CONTACT, S_USER
Title : PS Benefit Case Management
has BENEFIT has

BENEFIT PRODUCT BENEFIT PLAN ACTIVITY
PROGRAM PROGRAM for ITEM PAYMENT
belongs to ITEM
for for
for used by has
PARTY
associated to has payment for has

associated to
received by
CONTACT
CHANGE OF BENEFIT BENEFIT PLAN ITEM
CIRCUMSTANCEfor has recipient of
PLAN
has for provided by ACCOUNT
provider of
for belongs to
submitted by
CASE VERIFICATION ITEM USER
submitter of
verified by
verifier of
submitted by
Figure 120. Public Sector Benefit Case Management
for QUALITY
ASSURANCE submitter of
ITEMS completed by
completer of
for
has has
CASE VERIFICATION QUALITY ASSURANCE

TEMPLATE TEMPLATE
for for
has has has has
CASE

Applications
273
Applications
Public Sector Case Lead Management

This ERD (see Figure 121) illustrates how an investigative lead is related to incident and case. It
shows how a party, such as a person, organization, or group, becomes involved in the investigative
lead, and the positions of team members assigned to work on it. This ERD also shows evidence/
supporting documentation as the trigger of the investigative lead. The physical object used, location
of the investigative lead, as well as the related activity, disease, and service request are shown. This
ERD covers the features of applications received from users and their supporting documents as well
as their visibility to various organizations.
New features in 8.1 include:
Submitted applications are reviewed on the Siebel side and information uploaded from the
applications into Siebel objects such as case and contacts.
Applications received from users/citizens for benefits, visa, immigration, and so forth are taken
into account. The supporting documents for a given application, as well as any scanned images
of the application, are stored in file systems. The visibility of an application to various
organizations is also managed.
Data from the application form, as filled out by the citizen or employee, is transferred to the
Siebel application so that the agency has a historical record of the data as submitted at that point
in time. Employees will then upload the application into the system. During the upload process,
relevant data from the form(s) is imported into the appropriate Siebel contact, household and
case records.
Table 123. Public Sector Case Lead Management ERD Entities and Tables
Entity Table
INVESTIGATIVE CASE LEAD S_CASE_LEAD
PARTY S_PARTY
PERSON S_CONTACT, S_USER, S_CONTACT_PSX
ORGANIZATION/GROUP S_ORG_EXT, S_ORG_GRP_PSX
POSITION S_POSTN
ADDRESS S_ADDR_PER
SERVICE REQUEST S_SRV_REQ
ACTIVITY S_EVT_ACT
CASE S_CASE, S_CASE_PSX
PHYSICAL OBJECT S_ASSET
DISEASE S_DISEASE
EVIDENCE/SUPPORTING DOCUMENT S_EVIDENCE
INCIDENT S_INCIDENT
PERSON DESCRIPTION S_SUBJECT
Applications
Table 123. Public Sector Case Lead Management ERD Entities and Tables
Entity Table
APPLICATION S_PS_APPL
APPLICATION ATTACHMENT S_PS_APPL_ATT
APPLICATION/BUSINESS UNIT VISIBILITY S_PS_APPL_BU
Title : Public Sector Case Lead Management PERSON DESCRIPTION
276
for for for
has
for
Applications
EVIDENCE / SUPPORTING DOCUMENT

APPLICATION supported by INCIDENT
ATTACHMENT
for supported by
related to
CASE
based on basis for serviced through
ACTIVITY serviced through

related to subject for associated with subject of
the use of
conducted for
PHYSICAL OBJECT
generated by generated by relevant to
located in relevant to generated by
SERVICE REQUEST DISEASE
serviced via
address for
for location of generated by related to
ADDRESS
has
related to
Figure 121.Public Sector Case Lead Management
APPLICATION
is visible to has
associated with subject
triggered by serviced through
is related to initiation of lead to for for of
for
composed
INVESTIGATIVE LEAD of
is related to
APPLICATION related with approved by investigated by target at part of

BUSINESS UNIT
related to
subject of matching with

PARTY has visibility to involved in approver of assigned to
PERSON
ORGANIZATION/GROUP POSITION

responsibility of
AGENCY OTHER AGENT SUSPECT
OTHER SUSPICIOUS
ORGANIZATION GROUP responsible for PERSON
Applications
Public Sector Child Welfare

The Child Welfare feature addresses the intake and case management needs of social service
agencies working to provide child welfare services. Intake, Screening Decision, Assessment
Management, Court Processing Interface, and Service Plan Creation functions are included. As the
ERD (see Figure 122) depicts, a Case can have one or more Incidents and one or more Benefit Plans.
An Incident can have multiple Assessments, can be approved by one or more Positions, can have
one or more Contacts and uses an Approval Template. An Incident can also have one or more
Allegations that can be allegations on one or more Contacts associated with the Incident. A Benefit
Plan can have one or more Court Hearings and a Court Hearing can have one or more Court
Decisions.
Table 124. Public Sector Child Welfare ERD Entities and Tables
Entity Table
Allegation S_ALLEGATION
Approval Template S_APPR_TEMPLATE
Assessment S_ASSESS
Court Decision S_COURT_DECISN
Court Hearing S_EVT_ACT
Incident S_INCIDENT

Service Plan S_CASE_BNFTPLAN
Time Sheet S_TMSHT
Time Sheet Item S_TMSHT_ITEM
Time Sheet Line S_TMSHT_LN
Title : PS Child Welfare
278
Applications
refers to
TIME SHEET ITEM TIME SHEET LINE CONTACT COURT DECISION
refered in
part of
time spent on time spent on involved in involved in part of for outcome of
made up of
TIME SHEET
Figure 122. Public Sector Child Welfare
allegation on has
APPROVAL
ASSESSMENT POSITION TEMPLATE ALLEGATION COURT HEARING
for for approver of used by part related to
PLAN
has has
has has approved by uses has involves SERVICE
BENEFIT PLAN
PLAN
INCIDENT
belongs to
subject of
has has of has has
CASE

Applications
Public Sector Contact Identity

Public Sector Contact Identity (see Figure 123) allows you to track the identity of an individual,
including personal attributes, marital status changes, place of residence, and so on over time so that
the responsible organization can react swiftly to the legality of the individual. Public Sector Contact
Identity also tracks the entry and departure information of the individual into and out of the country.
Public Sector Contact Identity is used mainly for the purposes of homeland security.
Table 125. Public Sector Contact Identity ERD Entities and Tables
Entity Table
IDENTITY S_PS_IDENTITY
CREDENTIAL S_PS_CREDENTIAL
STAY S_PS_STAY_LOG
PUBLIC SECTOR CONTACT S_PS_CONTACT
ORGANIZATION/GROUP S_ORG_EXT, S_BU
PARTY, CONTACT S_PARTY, S_CONTACT
1% 3
Oracle
280
Applications
!$+ !$' %+

+ ! %% 6 >'%
!$+$&"
!$'$&"
%%&$
&$+ 613
6
>%
613
13 113 13

Figure 123.Public Sector Contact Identity

$[$0
&

%%&$

$ + 9% *$+
2

&.' % $
+

$
Applications
Public Sector Evidence Management

This ERD (show in Figure 124) illustrates how evidence and supporting documents are related to the
incident and case and acts as the trigger of the investigative lead. It shows how a party, such as a
person, organization, or group, is included in the evidence and supporting documents. The ERD
describes the positions of team members assigned to handle the incident and approve the
documents. This ERD also shows how the items are supported by the documents. The location of the
incident, physical object used in the incident, as well as the activity and service request related to
the evidence are shown.
Table 126. Public Sector Evidence Management ERD Entities and Tables
Entity Table
EVIDENCE/SUPPORTING DOCUMENT S_EVIDENCE
PARTY S_PARTY
PERSON S_CONTACT, S_USER
ORGANIZATION/GROUP S_ORG_EXT
POSITION S_POSTN
ADDRESS S_ADDR_PER
QUOTE ITEM S_QUOTE_ITEM
ORDER ITEM S_ORDER_ITEM
QUOTE S_DOC_QUOTE
ORDER S_ORDER
ACTIVITY S_EVT_ACT
INVESTIGATIVE LEAD S_CASE_LEAD
INCIDENT S_INCIDENT
CASE S_CASE
1% 2"
282
Oracle
1 %

7&" 7&
Applications
13
! 1?

!"
13 13

%>
13 7&% 2

$>%
>
2 '!
$ !$

>+
2 1
13 1

2 2 1

Figure 124.Public Sector Evidence Management
>!$ 0%&$

! &"$
13

13
6 6
1 1 213
13 13

14
!!%%
9+% '
.=

+ 2 2 2 2

1
2
6

$[$0
& %$
9
$ + 9&%9'! %$ 1
$ %&% 9%$

$[$

13
%&% &%

&
Applications
Public Sector Incident Management

This ERD (see Figure 125) illustrates how an incident is related to investigative lead and case. It
shows how a party, such as a person, organization, or group, becomes involved in the incident in
different roles such as victim, offender, witness, suspect, or owner of the incident. It includes the
offense committed and any arrest initiated by the incident or case. The physical object used in the
offense, arrest, and incident, as well as the activity and the service request related with the incident,
are also shown.
Table 127. Public Sector Incident Management ERD Entities and Tables
Entity Table
INCIDENT S_INCIDENT
PARTY S_PARTY
PERSON S_CONTACT, S_USER
ORGANIZATION/GROUP S_ORG_EXT
INCIDENT ACCOUNT S_INCIDNT_ACCNT
INCIDENT CONTACT S_INCIDENT_CON
INJURY S_INCTCON_INJRY
INCIDENT VICTIM TYPE S_INCDNT_VCTMTP
CIRCUMSTANCE S_CIRCUMSTANCE
ACTIVITY S_EVT_ACT
INVESTIGATIVE LEAD S_CASE_LEAD

CASE S_CASE
ARREST S_ARREST
ARREST FORCE S_ARREST_FORCE
OFFENSE S_OFFENSE
OFFENSE CRIMINAL ACTIVITY S_OFFENSE_ACT
1% " **$% "$' >+
284
Oracle

Applications
**$%
6

%*
$>%
>
'!
&"%$ >+
6

14 9+% '.=
$ !$ %> 6
> "+ 7&% %
%

1
13
Figure 125.Public Sector Incident Management
2

14 1 6 $=&+

$ !$
13
14
14
2 2 2 2
6
$ !$ &$ $ !$ $

$>%
$
&$ $ !$ $>%
$

9 %&%
$ 14
> " &$ $ !$ $ !$ $ !$
;$%% $ !$ &$ > " **$!
&$ %&% &%
**$! &$
& 9$ !$ $
$ !$;$%%

2 2 2 2

+

$[$0
& %$
9 %&% &%

$ + 9 %&%
$

$[$
& %$
Applications
Public Sector Service Provider and Referral

Management
The Service Provider and Referral Management feature allows social service agencies to locate
service providers and manage the referral process. Features include Service Provider Information
Management, Service Provider Contract Management, Service Provider Transaction Management,
Service Provider Portal, Service Provider Portal Resource and Inventory Control, Service Provider
Locator, Service Provider Referral and Benefits Administration.
This ERD (see Figure 126) illustrates that Service Providers can have a Profile, be the subject of
Contracts and own Assets. Contracts consist of Contract Items for Products that are made into Asset
instances. Benefit Plans with Benefit Plan Items can be associated with a Case. Benefit Plan Items
are also associated with a Product and a Service Provider who provides the Benefit. A Benefit Plan is
created under a Benefit Program that consists of Benefit Program Items. Each Benefit Plan Item is
associated with a Product and can have one or more Orders (created as part of Referral) that are
serviced by Service Providers and are composed of Order Items. Order Items are associated with the
Product, which is also associated with the related Benefit Plan Item.
Table 128. Public Sector Service Provider and Referral Management ERD Entities and Tables
Entity Table
Asset S_ASSET
Benefit Fund S_BNFT_FUND
Benefit Plan Item S_BNFT_PLAN_ITM, S_BNFT_PLNIT_XA
Benefit Plan Item Payment S_SRC_PAYMENT
Benefit Program S_BNFT_PGM

Benefit Program Item S_BNFT_PGM_ITEM
Contract Header S_DOC_AGREE
Contract Item S_AGREE_ITEM
Order S_ORDER, S_ORDER_PSX
Other Organization S_ORG_EXT, S_PARTY
Party S_PARTY
Service Provider Profile S_ORG_EXT_ATTR, S_ORG_EXT_LANG
Service Provider S_ORG_EXT, S_ORG_EXT_PSX, S_PARTY
Title : PS Svc Provider & Referral Mgmt
286

Applications
for for made into subject of provided by ordered

for
CONTRACT ITEM
has
belongs to subject of
BENEFIT BENEFIT
PROGRAM ITEM has FUND has
an instance of ORDER LINE
used for ITEM
SERVICE ASSET CONTRACT HEADER
PROVIDER part of
belongs to
PROFILE owned by for
for
has composed of
has provider of
PARTY has owns subject of
BENEFIT PROGRAM ORDER
used for services
OTHER SERVICE PROVIDER
for ORGANIZATION serviced by
has
under
Figure 126. Public Sector Service Provider and Referral Management
has for
has has has
BENEFIT PLAN BENEFIT PLAN ITEM
BENEFIT PLAN ITEM PAYMENT created for
for payment for
belongs to
has
for
for
has has

CASE
Applications
Real-Time Scheduler Integration

In a typical field service scenario, technicians are sent to a customer's location to do a job such as
performing an installation, upgrade, or repair. Real-Time Scheduler is an external application that
performs the scheduling (ERD see Figure 127). Scheduling involves matching an available service
technician with a job or service request. Each job includes a set of necessary skills. For example,
installation of a set-top box might require a skill, such as training in electrical wiring. Each technician
has a distinct set of skills. The job of the scheduler is to find the best technician who is available and
has the necessary skills to perform the job.
The following information is mastered and stored in the Siebel application:
Technician details (name, phone number, and so on.)
Technician schedule and availability
Technician skill set
Job details
Job skills (skills required to accomplish the job)
Service requests for jobs
Real-Time Scheduler can use the above information to prepare a schedule that contains a timetable
for each technician. To enable this, the Siebel application must use the Real-Time Scheduler Web
service to pass the skills needed to do the job to the Real-Time Scheduler.
Table 129. Real-Time Scheduler Integration ERD Entities and Tables
Entity Table
Address S_ADDR_PER
Buscomp S_BUSCOMP
Buscomp Field S_FIELD

Business Object S_BUSOBJ
Resource Scheduler Rule Criteria Value S_RS_CRIT_VAL
Resource Scheduler Object Link S_RS_OBJ_LNK
Resource Scheduler Object Link Relation S_RS_OBJLNK_REL
Resource Scheduler Skill Rule Criteria S_RS_RULE_CRIT
Resource Scheduler Rule Definition S_RS_RULE_DEF
Resource Schedule Item S_RS_SCHD_EVENT
Resource Scheduler Skill Item S_RS_SKILL_ITM
Resource Scheduler Skill Set S_RS_SKILL_SET
Technician S_USER
RESOURCE SCHEDULER SKILL ITEM
288
Title : Real-Time Scheduler Integration
for user of compared to
Applications
RESOURCE
SCHEDULER RULE
CRITERIA VALUE
RESOURCE SCHEDULE ITEM
specified for
has has defined for
has has
RESOURCE RESOURCE RESOURCE

SCHEDULER SCHEDULER SCHEDULER
starting ending SKILL SET SKILL RULE OBJECT LINK
location for location for
owner for CRITERIA RELATION
Figure 127. Real-Time Scheduler Integration
ADDRESS TECHNICIAN required skill evaluated uses has has

set for for
parent child source for

used
link for link for value for
for
defined for source join
RESOURCE SCHEDULER defined for target join BUSCOMP FIELD
OBJECT LINK
requires has
belongs to
RESOURCE SCHEDULER RULE

DEFINITION defined for has
source for
defined for target for BUSCOMP
used in
made up of
defined for source for
BUSINESS OBJECT

Applications
Routes and Best Call Hours

This ERD (see Figure 128) illustrates how the Siebel Consumer Goods application supports the use
of best call hours in the context of retail execution. Simply stated, each external organization or
retailer, is part of one or multiple routes which are predefined logical groupings of stores. These
routes exist for the purpose of facilitating the visit execution of a mobile field force. To coordinate
the most logical order in which these external organizations should be visited, each includes a
coordinating best call hour that specifies the time(s) at which the retailer should be visited.
Table 130. Routes and Best Call Hours ERD Entities and Tables
Entity Table
Best Call Hour S_BEST_CALL_HRS
Organization External S_ORG_EXT, S_PARTY
Route S_ACCNTRT
Applications
Figure 128.Routes and Best Call Hours
Title : Routes and Best Call Hours

part of
EXTERNAL ORGANIZATION
made up of
SYNDICATE GROUP
BEST CALL HOUR for appear on ROUTE

OTHER ORGANIZATION
have defined for
RETAILER
STORE
Applications
Sales Volume Planning

This ERD (see Figure 129) illustrates how Siebel Business applications (Consumer Goods) support
sales volume planning (SVP). A sales volume plan is the targeted sales volume (cases or currency)
for a period. This volume is calculated based on historical data within a period. Algorithms used to
calculate the SVP could be a flat percentage change over a period, or it could be a trended volume.
While planning, an authorized employee can allocate down an account, or an account product
category tree. Prior to allocating, historical data must be aggregated up these trees. After the initial
aggregation, allocation and aggregation can occur any number of times until the plan is committed
or until historical data within the plan's period is entered into the application.
Table 131. Sales Volume Planning ERD Entities and Tables
Entity Table
Authorized Product Detail S_ORG_DIST_LST
Category S_CTLG_CAT
Category Baseline S_CG_CAT_BASELN
Consumption Category S_CG_CAT_CONSUM
Employee S_CONTACT, S_PARTY
External Organization S_ORG_EXT, S_PARTY
Period S_PERIOD
Planned Volume S_PROD_BASELINE, S_CG_CAT_BASELN,

S_PROD_TARGET, S_CG_CAT_TARGET
Product Baseline S_PROD_BASELINE
Product Consumption S_PROD_CONSUME
Product Shipment S_PROD_SHIPMENT
Product Target S_PROD_TARGET
Sales Volume Planning Action S_CG_SVP_ACTION
Shipment Category S_CG_CAT_SHIP
Target Category S_CG_CAT_TARGET
Applications
Figure 129.Sales Volume Planning

part of
Title : Sales Volume Planning EXTERNAL ORGANIZATION

Author : Oracle, Confidential made up of
have
SUPPLIER
for an
at
AUTHORIZED AUTHORIZED
PRODUCT DETAIL PRODUCT subject of
for STORE
has of PRODUCT INTERNAL
subject of
RETAILER
SYNDICATE
GROUP
OTHER
PRODUCT MOVEMENT
part of ORGANIZATION
CATEGORY have MARKETING EVENT

PRODUCT
BASELINE BASELINE exist for
composed of
have CATEGORY
PRODUCT CATEGORY
SHIPMENT SHIPMENT
exist for
F-GROUP
PRODUCT CATEGORY
CONSUMPTION CONSUMPTION
PRODUCT CATEGORY
TARGET TARGET PERIOD
have
exist for
Applications
Sample Management
This ERD (see Figure 130) illustrates how product samples can be tracked in inventory. Inventory is
for a particular employee and for a specified period. All transactions involving samples such as
disbursement, shipments, and sample orders can be tracked and each active inventory period can
be reconciled after a physical inventory count.
Use of samples for product promotion by pharmaceutical companies around the world is governed
by local country legislation. The Life Science Sampling, Sample Management and Compliance feature
details requirements for sample management and compliance processes in a pharmaceutical
company to ensure that the companys processes comply with regulations. Sample Audit and
Compliance Administration functionality enables companies to adhere to government guidelines.
Table 132. Sample Management ERD Entities and Tables
Entity Table
Audit Report Attachment S_INVADTRPT_ATT
Call S_EVT_ACT
Inventory Audit Report S_INV_AUDIT_RPT
Order Item S_SMPL_TXN_ITEM
Person S_CONTACT, S_PARTY, S_USER
Product Inventory S_STOCK_EMP
Sample Order S_SAMPLE_TXN

Sample Transaction S_SAMPLE_TXN
Sample Transfer S_SAMPLE_TXN
Signature Audit S_EMP_AUDITSIGN
Stock Period S_STK_PERD_EMP
Transaction Attachment S_SMPL_TXN_ATT
Transaction Item S_SMPL_TXN_ITEM
Transfer Item S_SMPL_TXN_ITEM
Validation Result S_VALDN_RESULT
Title : Sample Management
294
PERSON
CONTACT
for
Applications
SIGNATURE
AUDIT EMPLOYEE
SAMPLE TRANSFER associated
owned by
with
own
transferred by
transfer
composed of
composed of SAMPLE ORDER
ORDER ITEM for owned by
own
Figure 130.Sample Management
transferred by
belonging to transfer
adjustment of adjusted from

for
TRANSACTION ITEM owned by
TRANSFER ITEM own
transferred by
transfer
belonging to
belonging to items of
of of of
associated composed of
with owned by
PRODUCT INVENTORY
TRANSACTION SAMPLE TRANSACTION
ATTACHMENT transferred by own
transfer
consists of
dropped at
for belonging to
AUDIT REPORT drop of
ATTACHMENT for CALL
VALIDATION
RESULT
associated with for
consists of associated with
for
INVENTORY AUDIT STOCK PERIOD owned by
REPORT
own

inventoried in subject of
INTERNAL PRODUCT
belongs to Person list factor
Applications
Special Rate List

Special Rate List (see Figure 131) is a list of phone numbers, country codes, area codes, and so on,
to be used for special rates in telephone rate plans. This list is defined for a telephone user account
in the communications industry. This special rate list is subsequently used in quotes and orders for
the customer in relation to the telephone owned by the customer.
Table 133. Special Rate List ERD Entities and Tables
Entity Table
Asset S_ASSET
Special Rate List S_SPL_RATE_LST
Special Rate List Item S_SPL_RATE_ITEM
Applications
Figure 131. Special Rate List
Title : Special Rate List

part of part of
ORDER ITEM QUOTE ITEM

composed of
composed of
has for provision of for has

ASSET
has
SPECIAL RATE LIST ITEM
for
defined for defined for has defined for
SPECIAL RATE LIST
defined for primary for
has has
ACCOUNT
Applications
Syndicated Data
This ERD (see Figure 132) illustrates how the syndicated data (sales and prescription information) is
associated with a period, plan, account, contact, postal code, territory, and area.
Table 134. Syndicated Data ERD Entities and Tables
Entity Table
Period S_PERIOD
Plan S_INS_PLAN
Postal Code S_ZIPCODE
Product S_PROD_INT
Region S_REGION
Syndicated Data S_SYND_DATA
Title : Syndicated Data
298
Applications
for AREA
SYNDICATED DATA
PERIOD subject of
for
in
SALES
Figure 132.Syndicated Data
for POSTAL CODE
subject of
PRODUCT for
of
for ACCOUNT
subject of
PLAN PRESCRIPTION
for
for CONTACT
in
subject of
POSITION
recipient of
for TERRITORY
for
subject of

Applications
Teller Administration
This ERD (see Figure 133) illustrates how Siebel Financial Services supports the administration of a
tellers activities at a financial institution branch. A set of employee, transaction, and container limits
are defined for each branch, as well as a multiple containers. Each teller is associated with a set of
containers, where they execute different activities and service requests for the customer.
Table 135. Teller Administration ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Activity Batch S_FN_ACT_BATCH
Activity Settle S_FN_ACT_SETTL
Bait S_FN_BAIT
Container S_FN_CONTAINER
Container Limits S_FNCONTNR_LMTS
Employee Teller Limits S_EMP_TLR_LMTS
Holdover S_FN_TXN_HLDVR, S_FN_HLDVR_CTF

Transaction Limits S_FN_TXN_LMTS
Title : Teller Administration
300
Applications
LIMITS
ACTIVITY
EMPLOYEE TRANSACTION CONTAINER
TELLER LIMITS LIMITS LIMITS
associated associated assoicated assoicated

includes has has generates associated with with with with with
associated associated SERVICE

Figure 133.Teller Administration
with with REQUEST LINE

ITEM
BATCH SETTLEMENT
part of
ACTIVITY
made up of HOLDOVER
subject of
includes
generated CALENDAR
by
CONTAINER SERVICE
part of
REQUEST
to
BIN VAULT BATCH DRAWER
TRANSACTION
from
from
to
for
for for
BAIT/TRAP
has
used by
PARTY from has

PERSON
CONTACT EMPLOYEE
has has
ORGANIZATION UNIT has has has has
BRANCH

Applications
Territory AlignmentQuota Assignment

This ERD (see Figure 134) shows how to set up territory alignment to determine whether the results
of quota assignments are as expected. It covers assigning quotas to alignments, breaking these
assignments down by contacts, accounts, regions, or ZIP codes and changes included in a given
alignment.
Table 136. Territory AlignmentQuota Assignment ERD Entities and Tables
Entity Table
Sales Quota S_SLS_QUOTA
Alignment Terr Quota S_ALGN_QTA_TERR
Alignment Terr/Qta Breakdown S_ALGN_QT_BRKDN
Period S_PERIOD
Alignment Quota S_TERRALGN_QTA
Territory Alignment S_TERRALGN
Contact/Terr Mapping Change S_TERRALGN_CON
Con/Quota Change S_ALGN_QTA_CON
Account/Terr Mapping Change S_TERRALGN_ACCT
Accnt/Quota Change S_ALGN_QTA_ACCT
Geo/Terr Mapping Change S_TERRALGN_REGN, S_TERRALGN_ZIP
37
Oracle
302
+ +
'
$"$ 9 9+

0"$
9$

Applications

2

&$0
"$
9$


07&
$ 0
9$

"$
9$

$07&
9$

$07&
9$

Figure 134.Territory AlignmentQuota Assignment

'
$"$7&

'
$"$07.<!;$

14 2 15 6
+

%'%7&
! '
$"$7&
2
Applications
Territory Management - Consumer Sector

This ERD (see Figure 135) shows how multiple representatives can call on the same account to carry
out different roles on a regular basis. The Territory Management module within Siebel Consumer
Goods supports a system for creating territories and modifying them to meet the needs of the
consumer goods industry.
Table 137. Territory Management - CS ERD Entities and Tables
Entity Table
Account S_ORG_EXT
Account Team Member S_ACCNT_POSTN
Account Team Role S_ACCNT_POSROLE
Activity S_EVT_ACT
Business Unit S_BU
Contact S_CONTACT
Contact Team Member S_POSTN_CON
Division S_ORG_EXT
Position S_POSTN
Position Territory Assignment S_TERR_POSITION

Position Role (LOV type TERR_POSITION_ROLE)
Territory Position Role S_TERR_POS_ROLE
3"`% %{
304
Oracle

%$+%%
$"$ +
Applications
13

14
>+ +>%$ 2

+
%$
'
2 2 +"$
14
'

+ &$

&$0 $ 0

"$
"$

14 13

Figure 135.Territory Management - Consumer Sector
&$"'
+
$ """.
9 9+

14
14 14 13

%$' &$"
"".

13
$ .&%$%%&$

1

@13
%$

13 !>%$
9!>%$ %'%*

Applications
Territory Management - Life Sciences

For Life Science companies, a key business process is territory alignment (sales force alignment).
This ERD (see Figure 136) illustrates how territory alignments can be defined encompassing
territories, sales representatives, business rules, territory roll-ups, and so on. Historical alignments
can be maintained for reference and comparison. Future alignments can be staged and analyzed
concurrently, thus facilitating simultaneous evaluation of multiple strategies for a sales force.
Table 138. Territory Management - LS ERD Entities and Tables
Entity Table
Account S_ORG_EXT
Account/Terr Mapping Change S_TERRALGN_ACCT
Asset S_ASSET
Asset/Terr Mapping Change S_TERRALGN_AST
Business Unit S_BU
Contact S_CONTACT
Contact/Terr Mapping Change S_TERRALGN_CON
Division S_ORG_EXT
Geo/Terr Mapping Change S_TERR_REGION, S_TERR_ZIP
Position S_POSTN
Position Territory Assignment Change S_TERRALGN_PSTN
Region S_REGION
Territory Alignment S_TERRALGN
Territory Alignment Condition S_TERRALGN_COND
Zipcode (None)
3"`%'%{

Oracle +
306
2
+>%$
0
%$0
Applications
%%
$"$ 13
0
9$

0"$

9$
13

9 '

[ !
$

0
%%0
"$
9$
13

%%

0
$ 0
"$
9$
13
$

0
+
Figure 136.Territory Management - Life Sciences
&$0
'
$"$ 13
"$
9$

$!$
&$

213

+9 9+
+'
$"$
2

13

.&%$%%&$

%$ 14 @13 1

13

!>%$ %'%*
9!>%$
Applications
Universal Customer Master

This ERD (see Figure 137) illustrates how Universal Customer Master works with external applications
and the Siebel application. This ERD also shows the UCM engine schematics including the
survivorship rule set and its relationship with repository-based information, UCM objects, and
operations such as deduplication, merge, and history of changes.
Table 139. Universal Customer Master ERD Entities and Tables
Entity Table
Attribute Group S_UCM_ATGP
Attribute Group Field Mapping S_UCM_ATGP_FLD
Attribute Group Rule S_UCM_ATGP_RULE
Attribute Group Update History S_UCM_CON_ATGP, S_UCM_ORG_ATGP, S_UCM_OGP_ATGP
Confidence Level S_UCM_CONF_LVL
Contact Additional Name S_CONTACT_NAME
Contact Identity S_CON_IDNTY_DOC
External Information System S_CIF_EXT_SYST
External Information System S_CIF_CON_MAP, S_CIF_ORGRP_MAP, S_CIF_ORG_MAP

Mapping
External System Privilege S_CIF_SYS_DTL
Named Hierarchy S_DYN_HRCHY
Named Hierarchy Account S_DYN_HRCHY_REL
Rule Set S_UCM_RULE_SET

UCM Address S_UCM_ADDR_PER
UCM Asset S_UCM_ASSET
UCM Child Object S_UCM_CON_CHILD, S_UCM_OGP_CHILD,

S_UCM_ORG_CHILD
UCM Decay Indicator S_UCM_CON_DECAY, S_UCM_ORG_DECAY
UCM Deduplication S_UCM_DEDUP
UCM Merge Association S_UCM_MRG_ASSOC
UCM Merge History S_UCM_CON_MERGE, S_UCM_ORG_MERGE,

S_UCM_ORGRP_MRG
UCM Merge Request S_UCM_MERGE_REQ
UCM Named Hierarchy S_UCM_HRCHY
UCM Named Hierarchy Account S_UCM_HRCHY_REL
Applications
Table 139. Universal Customer Master ERD Entities and Tables
Entity Table
UCM Object S_UCM_CONTACT, S_UCM_ORG_EXT, S_UCM_ORGGRP
UCM Party Ext S_PARTY_UCMX, S_CONTACT_UCMX
UCM Privacy S_UCM_PRIVACY
UCM Social Media Profile of S_UCM_CN_SMPROF, S_CONSMPROF_UPD,

Contacts S_CIF_SMPROFMAP
UCM Social Media Profile Attribute S_UCM_CN_SMATTR, S_CIF_SMATTRMAP

of Contacts
Title : Universal Customer Master
Author : Oracle, Confidential ATTRIBUTE GROUP
ATTRIBUTE belongs to FIELD MAPPING
RULE SET
GROUP RULE
composed of
CONFIDENCE LEVEL belongs to

associated with has
has ATTRIBUTE GROUP
has belongs to
has
for
stores
ATTRIBUTE GROUP UPDATE HISTORY points to

stores
stores
UCM MERGE REQUEST
UCM SOCIAL MEDIA
UCM ADDRESS
Figure 137.Universal Customer Master
for for UCM SOCIAL

UCM MERGE PROFILE
referenced in ASSOCIATION
UCM PROFILE referenced in
UCM ASSET PARAMETER
for
has REPOSITORY FIELD OBJECT
has
ref in for
UCM MERGE UCM DEDUP CONTACT
HISTORY ADDITIONAL
UCM
NAME belongs to
PRIVACY
belongs to of of has
for
ref in master
has duplicate of copy of REPOSITORY BUSINESS
COMPONENT
UCM OBJECT
EXTERNAL
SYSTEM
PRIVILEGE UCM PERSON UCM UCM CONTACT
ORGANIZATION HOUSEHOLD IDENTITY
UCM PARTY UCM DECAY
EXT INDICATOR
from referenced for

EXTERNAL INFORMATION to for
for
SYSTEM MAPPING
for
points to mapped for
referenced
to
used in has used in ref to ref to has used in referenced in mapped to has has has has has has has
EXTERNAL INFORMATION SYSTEM PARTY

PERSON ORGANIZATION HOUSEHOLD

Applications
309
Applications
Vehicle
This ERD (see Figure 138) illustrates how Siebel Automotive tracks the configuration and
relationships associated with a vehicle. Vehicles represent a physical asset based on a product that
can be related to one or more contacts, organizations, accounts, and positions. In addition to the
attributes inherited from the product upon which it is based, a vehicle can also have one or more
options (also products) associated with it. A vehicle's sales history, financial detail, service history
and service requests can be tracked through its life cycle.
Table 140. Vehicle ERD Entities and Tables
Entity Table
Asset S_ASSET
Dealer S_ORG_EXT, S_PARTY
Features S_PROD_SPEC
Financial Detail S_VHCL_FIN_DTL
Installed Option S_ASSET_REL
Option S_PROD_REL
Position S_POSITION, S_PARTY
Product S_PROD_INT
Product Features S_PROD_SPEC
Sales History S_VHCL_SALES
Service History S_VHCL_SRV

Specifications S_PROD_SPEC
Vehicle Product S_PROD_INT
Title : Vehicle
belong to PERSON
FINANCIAL DETAIL
owner of
of of for EMPLOYEE
of
Figure 138.Vehicle
SALES HISTORY
involved in
visible to for
Currently owned by/related to

ASSET
subject of for
subject of SERVICE HISTORY of
VEHICLE
for involved in
for performed by
of
OTHER
PERSON
Subject of SERVICE REQUEST reported by
for reporter of
composed of INSTALLED
routed to
made into OPTION
an instance of assigned to POSITION of
prefer sold by an instance of for
of
primarily PRODUCT DETAILS

PRODUCT composed of
SPECIFICATIONS
made into made into for
VEHICLE contains
OPTION
PRODUCT
belongs to
secondarily composed of FEATURES
for
involved in for for
ORGANIZATION service provider of seller of perform

have visibility to assigned to
DEALER / PARTNER
OTHER ORGANIZATION
a parent to
a report to

Applications
311
Applications
Vehicle Collection
This ERD (see Figure 139) illustrates how the Siebel application helps an automotive captive finance
company deploy collections processes. Relevant information includes that a customer's car can be
impounded by a government agency, or a customer might abandon the car during the life cycle of
vehicle ownership. Captive Finance allows the capture of multiple promises to pay (PTPs) for a given
account. When the customer breaks a promise to pay, a Service Request is created for an impound,
a repossession, or a cure process.
Table 141. Vehicle Collection ERD Entities and Tables
Entity Table
Bankruptcy S_BANKRUPTCY, S_BK_PARTY
Service Request S_SRV_REQ, S_SRV_REQ1_FNX
Promise to Pay S_CF_PTP
Party S_PARTY, S_ORG_EXT, S_CONTACT, S_USER
Asset, Financial Account S_ASSET
Vehicle Insurance S_CF_INSURANCE
BANKRUPTCY SERVICE REQUEST PROMISE TO PAY VEHICLE INSURANCE
* CASE_NUM * SEQ_NUM * EFF_START_DT
IMPOUND NOTIFICATION
insured for insured insured by

for
recorded for filed by FINANCIAL ACCOUNT
issued by insured by
associated to VEHICLE LEASE

REPOSESSION
subject of
REQUEST
Figure 139.Vehicle Collection
OTHER FINANCIAL
ACCOUNT
assigned to
insured by
ASSET
OTHER VEHICLE
ASSET
has been filed for filer of
PARTY
work on work on insure for
PERSON ORGANIZATION
REPOSESSION IMPOUND AGENCY INSURANCE COMPANY

VEHICLE LEASE
CONTACT COLLECTION AGENCY
HOLDING
AGENT
COMPANY
OTHER OTHER ORGANIZATION

PERSON

Applications
313
Applications
Vehicle Financing
Asset financing (see Figure 140) refers to the niche area of capital financing where an asset is
converted into a working cash flow in exchange for a security interest in the asset. For example, an
auto dealer might offer a customer a lease option, where the customer pays a fixed monthly charge
in exchange for using the vehicle for a predetermined period of time. In this form of leasing, the
lessee has the right to use the vehicle, but does not own the vehicle. The lessee pays an up-front
cost and pays monthly payments to get the right to use the vehicle. At the end of the lease, the
lessee usually has several options: to buy the vehicle or pay the end-of-lease cost and walk away.
The lessor must now deal with remarketing the vehicle. The lessor can lease it to another lessee or
auction the vehicle to dealers or consumers.
Table 142. Vehicle Financing ERD Entities and Tables
Entity Table
Asset S_ASSET
Financial Account State S_FN_ACCNT_STAT
Historical Auction Price S_VHCL_AUC_REF
Historical FMV Price S_VHCL_FMV_REF
Historical Residual Value S_VHCL_RSDL_REF
Product S_PROD_INT
Vehicle Consignment S_VHCL_CNSGNMNT

Vehicle Consignment Details S_VHCL_CNSGNDTL
Vehicle Consignment Fees S_VHCL_CNSGNFEE
Vehicle FMV S_VHCL_FMV
Vehicle Inspection S_VHCL_INSPCTN
Vehicle Inspection Charges S_VHCL_INSPCHRG
Vehicle Option at Lease S_FNACC_AST_OPT
Vehicle Title Log S_VHCL_TITLELOG
Vehicle Turn In S_VHCL_TURN_IN
ASSET
Title : Vehicle Financing
in context VEHICLE
SERVICE of
REQUEST subject
of
INSPECTION CHARGE
# SEQ_NUM
in context of
subject of for
VEHICLE INSPECTION performed for

CONSIGNMENT # SEQ_NUM
FEE subject
of
associated
for
Figure 140.Vehicle Financing
to VEHICLE FMV
# CALCULATION TYPE
for has
# EVALUATION DATE
for
CONSIGNMENT associated to
VEHICLE TURN IN subject
DETAIL
VEHICLE TITLE for of
LOG
for for subject
# SEQ_NUM of
subject of subject of associated to

CONTRACT
VEHICLE FINANCIAL for
VEHICLE CONSIGNMENT OTHER ACCOUNT
CONTRACT # SEQ_NUM subject of
associated LEASE
to AGREEMENT for for
consists
of based
subject of on
FINANCIAL for
associated to
ACCOUNT
VEHICLE OPTION subject of
STATE AT LEASE VEHICLE
OPTION
for
for
subject subject subject subject subject subject subject

has of
of of of of of of subject of
FINANCIAL ACCOUNT subject of

VEHICLE LEASE VEHICLE OTHER
LOAN FINANCIAL
ACCOUNT
PRODUCT
HISTORICAL FMV PRICE
HISTORICAL AUCTION PRICE subject of
HISTORICAL RESIDUAL VALUE in reference to in reference to subject of

Applications
315
Applications
Vehicle Sales
This ERD (see Figure 141) illustrates the vehicle sales process at automotive dealerships. A
prospective buyer could come into a dealership as a result of a marketing activity by the dealership
such as an advertisement campaign, direct mailer, and so on. This could result in an opportunity to
sell a vehicle to the prospective buyer. A showroom log entry is created by a sales representative to
record the visit of the prospective buyer. The sales representative could call and pursue the
opportunity with the prospect. If the vehicle is sold, the sale is recorded with the team of sales
representatives involved in the sale. The sale data could be made visible to affiliated dealerships.
Table 143. Vehicle Sales ERD Entities and Tables
Entity Table
Contact Access Log S_CON_ACCSS_LOG
Employee S_EMP_PER, S_CONTACT, S_USER
Opportunity S_OPTY, S_OPTY_ATX
Organization S_ORG_EXT, S_BU
Person S_CONTACT, S_CONTACT_ATX, S_CONTACT_BU
Showroom Log Entry S_COMM_LOG
Vehicle Sale S_VHCL_SALES, S_VHCL_SALES_BU, S_VHCL_SALE_EMP
Title : Vehicle Sales
VEHICLE SALE
made by visible to for handled by in context of
subject of
Figure 141.Vehicle Sales
for PERSON
SHOWROOM LOG
subject of OTHER
ENTRY
in context of PERSON
CONTACT
ACCESS LOG subject of participate in
# ACCESS DATE in context of
EMPLOYEE
initiator of
created by
record
result of result of
result in
target
OPPORTUNITY
subject of
result in
in context of
owner of
MARKETING EVENT OR
ACTIVITY
target
ORGANIZATION
have visibility to
involved in targeted in subject of belong to subject of
OTHER DEALER /
ORGANIZATION seller of VEHICLE
PARTNER
sold by

Applications
317
Applications
3 Siebel Physical Model
This chapter describes the Siebel physical model, which encompasses the tables, their columns, and
their indexes. It covers the following topics:
Data Model Naming Conventions
Data Model Type Definitions on page 322
Columns of Numeric Physical Type on page 326
Siebel System Fields on page 326

INTEGRATION_ID Columns on page 327
Include Only Field on page 327
Siebel Repository on page 327

Database Schema Version on page 327
Limit Checking for Data Types on page 328
Validating the Siebel Schema on page 328
Party Model Unifies Access to Data on page 328
Generating a Report about Tables on page 329
Data Model Naming Conventions

This topic describes the following conventions:
Table Naming Conventions

Index Naming Conventions on page 321
Column Naming Conventions on page 321
Abbreviations Used in the Physical Model Listings on page 322
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.
Siebel Physical Model Data Model Naming Conventions
SUFFIX A supertype name can be followed by the entity subtype. For example, the supertype
EVT (event) includes ACT (activity) as one of its subtypes. Thus, the name becomes
S_EVT_ACT.
The prefix indicates the part of the Siebel schema to which a table belongs. Table 144 provides some
of the prefixes and their descriptions.
Table 144. 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 145 provides some of the suffixes and their descriptions.
Table 145. 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.
Siebel 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-character to
four-character suffix, see Table 146.
Table 146. Standard Index Suffixes
Unique or
Suffix Value Not Unique
_F# Foreign key index. Not unique

_II Index on INTEGRATION_ID columns that are used for integrating Not unique
Siebel Business Applications with back-office applications.
_P# Primary key index. Unique
_U# Primary key index of the user. Unique
_V# Special routing visibility rule index; usually on primary child Not unique
foreign key and system foreign key columns not ordinarily
indexed (for example, primary address, primary contact, creator,
and so on).
_M# Miscellaneous index. Any index that does not fit into one of the Not unique
above categories.
CAUTION: Before modifying or deleting indexes, create a service request (SR) on My Oracle
Support. Modifying or deleting indexes can negatively affect the performance of Siebel Business
Applications and can render the applications unusable. Alternatively, you can phone Global Customer
Support directly to create a service request or get a status update on your current SR.
Column Naming Conventions

Suffixes are used to indicate columns that must contain specific values. Table 147 shows the
standard suffixes for column names and their possible values.
Table 147. 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.
Siebel Physical Model Data Model Type Definitions
Table 147. Standard Column Suffixes
Suffix Value
_NUM This column contains a number or an identifying alphanumeric value.
_TEXT This column contains text data.
_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 might use the abbreviations, see Table 148.
Table 148. 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 153 on page 326.
Data Model Type Definitions

This topic contains the following type definitions:
Table Type Definitions on page 323
Table Status Definitions on page 324
Column Type Definitions on page 325
Domain Type Definitions on page 325
Table Type Definitions

Table 149 provides descriptions of the types of tables in the Siebel database.
Table 149. Table Types in the Siebel Database
Table Type Description
Data Data (Intersection) tables contain application or end-user data. An

(Intersection) 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.
Table 149. 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 includes
properties that support external tables.
Interface Interface tables are EIM tables, which are used when moving data between
the Siebel application and external applications.
Log Log tables are used to log events. There are three Log tables:
S_DCK_INST_LOG, S_PROC_INST, and S_PROC_INST_LOG.
Repository Repository tables contain information about the Siebel Repository. Data in
some of these tables might be compiled into the 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, see Table 150.
Table Status Definitions

Table 150 provides descriptions of the types of table status in the Siebel database.
Table 150. 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 might be used by
customers.
Column Type Definitions

Table 151 provides descriptions for the types of columns in the Siebel database.
Table 151. 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 153 on
page 326.
Domain Type Definitions

Table 152 provides descriptions for the domain types of certain columns in the Siebel database.
Table 152. 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) can be associated with
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 The List of Values type against which this column is validated.
Bounded 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 Physical Model Columns of Numeric Physical Type
Table 152. Domain Types
Domain
Type Meaning Domain Contains
MLOV Multilingual List of The List of Values type against which this column is validated,
Values in multiple languages. End users must specify a value from the
list, but see the values in their preferred language.
MLS Multiple Language The name of the table in which the translation in an alternate
Support 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 153. Do not alter the contents of
these fields.
Table 153. 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.
Siebel Physical Model INTEGRATION_ID Columns
Table 153. Siebel System Fields
Column Name Description
DB_LAST_UPD Date and time the record was last changed in the database.
DB_LAST_UPD_SRC Source of the instance or operation that changed the record in the
database.
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 that is used to support integration with back-
office applications. Customers use this column to store the unique reference identifiers for
corresponding records in their back-office application. For Application Integration Architecture (AIA)
integrations, use AIA_INTEG_ID columns.
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 include 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.
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, then 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.
Siebel Physical Model Limit Checking for Data Types
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 (see Table 154). Sources of inputs include Oracles
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 154. 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.
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 155 lists the
extension tables and their corresponding EIM interface tables.
Table 155. 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
Siebel Physical Model Generating a Report about Tables
Table 155. S_PARTY Extension Tables and Corresponding EIM Interface Tables
Data Type Extension Table to S_PARTY EIM Interface Table
Organizations S_ORG_BU EIM_ORG_BU
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
Generating a Report about Tables

You can generate a report that displays selected properties of each table and lists the columns. The
name, physical type, length, comments, and various other properties are identified for each column.
To generate a table report

1 Log in to the Siebel application, and navigate to the Administration - Application screen, then
Tables view.
2 From the Menu menu, choose New Query.
3 In the Name column, enter the name of the table for which the report is to be generated, and
press Enter.
4 Click the Reports icon in the icon bar.
5 Select Tables Report from the drop-down list.
The Output Type dialog box appears.
6 Select the output format for the report from the drop-down list.
7 Click Submit to generate the report.
The File Download dialog box appears.
Siebel Physical Model Generating a Report about Tables
8 Choose to open, save or cancel the report.
NOTE: For more information about generating reports, see Siebel Reports Guide.
4 Schema Changes
This chapter lists the table, table column, and table index changes in the schema that have been
implemented in Siebel Innovation Pack 2014. It includes the following topics:
Schema Changes Implemented in Siebel Innovation Pack 2014
Schema Changes Implemented in Siebel

Innovation Pack 2014
This topic describes changes in the schema implemented in version 8.1.1.11/8.2.2.4 compared with
version 8.1.1.10. It includes the following information:
New Tables Added to Innovation Pack 2014
Changes to Table Columns Implemented in Innovation Pack 2014
Changes to Table Indexes Implemented in Innovation Pack 2014
New Tables Added to Innovation Pack 2014

Table 156 lists tables that have been added to Innovation Pack 2014. All of these new tables are
active.
Table 156. New Tables in Innovation Pack 2014
Table Type
S_CIF_SMATTRMAP Data (Public)
S_CIF_SMPROFMAP Data (Public)
S_CONSMPROF_UPD Data (Public)
S_DM_SETTING Data (Public)
S_DM_UPSYNC_QUE Data (Private)
S_KM_CHNL_CFG Data (Public)
S_MSG_RESP_ACTN Data (Public)
S_NAV_SVC_PARAM Data (Public)
S_REQ_RECO_RESP Data (Public)
S_RESPACTN_PARM Data (Public)
S_RTD_REQUEST Data (Public)
Schema Changes Schema Changes Implemented in Siebel Innovation Pack 2014
Table 156. New Tables in Innovation Pack 2014
Table Type
S_RTD_REQ_ATTR Data (Public)
S_STG_ASGN_BAR Data (Public)
S_STG_BOB Data (Public)
S_UCM_CN_SMATTR Data (Public)
S_UCM_CN_SMPROF Data (Public)
Changes to Table Columns Implemented in Innovation

Pack 2014
This topic lists the following changes to table columns that have been implemented in Innovation
Pack 2014:
New Table Columns Added to Innovation Pack 2014
Table Columns That Have Changed in Innovation Pack 2014 on page 334
New Table Columns Added to Innovation Pack 2014

Table 157 lists table columns that are new to Innovation Pack 2014. All of the tables are default
tables and all are active. Some of the column headings are abbreviated as follows:
Opt indicates optional.
Len indicates length.
Prec indicates precision.
Def indicates default.
NA in a row indicates not applicable.
Table 157. New Table Columns in Innovation Pack 2014
Data
Table Column Opt Type Len Prec Scale Def
S_ACT_SIGN SIGNATURE_IMAGE Yes CLOB 131072 NA NA NA
S_APP_KEY APP_NAME Yes Varchar 250 NA NA NA
S_BC_ENTRY_TRGT APP_NAME Yes Varchar 75 NA NA Siebel

Field
Service
S_CL_PTCL_LS ACTL_CONTRACT_AMT Yes Number 22 22 7 NA
S_CL_PTCL_LS INIT_NUM_OF_SUBJ Yes Number 22 10 0 NA
Data
S_CL_PTCL_LS PLAN_BUDGETED_AMT Yes Number 22 22 7 NA
S_CL_PTCL_LS PLN_STUDY_INTEG_ID Yes Varchar 50 NA NA NA
S_CL_PTCL_LS SEL_CL_SUBJ_PCT Yes Number 22 22 7 NA
S_CL_SUBJ_LS SDV_UPD_TYPE_CD Yes Varchar 30 NA NA NA
S_CL_SUBJ_LS SD_VERIFY_CD Yes Varchar 30 NA NA NA
S_CON_SM_PROF END_DT Yes UTC 7 NA NA NA

DateTime
S_CON_SM_PROF START_DT Yes UTC 7 NA NA NA

DateTime
S_DM_USR_CLIENT USER_ID Yes Varchar 15 NA NA NA
S_EVT_ACT_LSX CRF_PAGE_NUM Yes Varchar 250 NA NA NA
S_EVT_ACT_LSX SDV_SVT_FLG No Character 1 NA NA Y
S_EVT_ACT_LSX SD_VERIFY_FLG No Character 1 NA NA Y
S_LIT ATTCH_UNZIP_FLG No Character 1 NA NA N
S_MSGPLAN_ITM CNTNT_FILE_NAME Yes Varchar 100 NA NA NA
S_MSGPLAN_ITM DISP_SCRN_TYPE_CD Yes Varchar 30 NA NA NA
S_MSGPLAN_ITM THMBNL_FILE_NAME Yes Varchar 100 NA NA NA
S_MSGPL_ITM_REL CNTNT_FILE_NAME Yes Varchar 100 NA NA NA
S_MSGPL_ITM_REL DISP_SCRN_TYPE_CD Yes Varchar 30 NA NA NA

S_MSGPL_ITM_REL THMBNL_FILE_NAME Yes Varchar 100 NA NA NA
S_MSG_PLAN DSBL_MENU_BAR_FLG No Character 1 NA NA N
S_MSG_PLAN DSBL_MSG_RESP_FLG No Character 1 NA NA N
S_MSG_PLAN DSBL_NAV_FLG No Character 1 NA NA N
S_MSG_PLAN ENBL_DIR_LNCH_FLG No Character 1 NA NA N
S_MSG_PLAN LAST_UNCOMPRESS_DT Yes UTC 7 NA NA NA

DateTime
S_NAV_LINK BS_METHOD_NAME Yes Varchar 75 NA NA NA
S_NAV_LINK BS_NAME Yes Varchar 75 NA NA NA
S_NAV_LINK IMG_TYPE_CD Yes Varchar 30 NA NA NA
S_ORDER_ITEM PROM_UPG_PATH_ID Yes Varchar 15 NA NA NA
S_PCD_DETAIL PROD_ID Yes Varchar 15 NA NA NA
Data
S_PROD_MSG RTD_APP_NAME Yes Varchar 30 NA NA NA
S_PROD_MSG RTD_RECO_TYPE_CODE Yes Varchar 30 NA NA NA
S_PROD_MSG_RESP RTD_CHOICE_EVT_NM Yes Varchar 100 NA NA NA
S_PTCL_SITE_LS EXT_CDMS_INT_FLG No Character 1 NA NA N
S_PTCL_SITE_LS INIT_NUM_OF_SUBJ Yes Number 22 10 0 NA
S_PTCL_SITE_LS SDV_TYPE_CD Yes Varchar 30 NA NA NA
S_PTCL_SITE_LS SEL_CL_SUBJ_PCT Yes Number 22 22 7 NA
S_QUOTE_ITEM PROM_UPG_PATH_ID Yes Varchar 15 NA NA NA
S_SRC_PAYMENT BILL_ACCNT_ID Yes Varchar 15 NA NA NA
S_SRC_PAYMENT BILL_PROFILE_ID Yes Varchar 15 NA NA NA
S_TAG_OBJECT REL_FEATURE_TXT Yes Varchar 1500 NA NA NA
S_TMPL_PLANITEM CRF_PAGE_NUM Yes Varchar 250 NA NA NA
S_TMPL_PLANITEM SD_VERIFY_FLG No Character 1 NA NA Y
S_UI_FILE STATUS_CD Yes Varchar 20 NA NA NA
S_UI_OBJ_EXP_FL SEQ_NUM Yes Number 22 10 0 NA
Table Columns That Have Changed in Innovation Pack 2014

Table 158 lists table columns that have changed in Innovation Pack 2014.
Table 158. Table Columns That have Changed in Innovation Pack 2014
Type of Previous
Table Column Change Value New Value
S_ACT_CAL_RSRC ACT_APPT_RPTEND_DT Data Type Date UTC

DateTime
S_ACT_EMP ACT_APPT_RPTEND_DT Data Type Date UTC

DateTime
S_EVT_ACT APPT_REPT_END_DT Data Type Date UTC

DateTime
S_FUNC_RPTSECT COMMENTS Length 250 2000
S_MSGPL_ITM_REL LIT_ID Optional No Yes
S_MSGPL_ITM_REL LIT_NAME Optional Yes No
S_PCD_DETAIL LIT_ID Optional No Yes
Table 158. Table Columns That have Changed in Innovation Pack 2014
Type of Previous
Table Column Change Value New Value
S_PCD_DETAIL RESPONSE_CD Optional No Yes
S_PRO_CFG_ITEM ADJ_VAL_AMT Scale 0 7
S_PRO_CFG_ITEM MAX_PRI Scale 0 7
S_PRO_CFG_ITEM MIN_PRI Scale 0 7
Changes to Table Indexes Implemented in Innovation

Pack 2014
This topic lists changes to table indexes that have been implemented in Innovation Pack 2014.
New Table Indexes Added to Innovation Pack 2014
Columns Removed from Table Indexes in Innovation Pack 2014
Columns Replaced in Table Indexes in Innovation Pack 2014 on page 336
New Table Indexes Added to Innovation Pack 2014

Table 159 lists table indexes that are new to Innovation Pack 2014.
Table 159. New Table Indexes in Innovation Pack 2014
Table Index Active Unique Columns
S_AUDIT_ITEM S_AUDIT_ITEM_M5 Yes No TBL_RECORD_ID,GROUP_NUM

S_DM_USR_CLIENT S_DM_USR_CLIENT_F1 Yes No USER_ID
S_NAV_LINK S_NAV_LINK_U1 Yes Yes NAME,TASK_ACTION_CD,

CONFLICT_ID
S_ORDER_ITEM S_ORDER_ITEM_F73 Yes No PROM_UPG_PATH_ID
S_PCD_DETAIL S_PCD_DETAIL_F12 Yes No PROD_ID
S_QUOTE_ITEM S_QUOTE_ITEM_F78 Yes No PROM_UPG_PATH_ID
S_SRC_PAYMENT S_SRC_PAYMENT_F73 Yes No BILL_PROFILE_ID
S_SRC_PAYMENT S_SRC_PAYMENT_F74 Yes No BILL_ACCNT_ID
Columns Removed from Table Indexes in Innovation Pack 2014

Table 160 lists columns that were removed from existing table indexes in Innovation Pack 2014.
Table 160. Columns Removed from Table Indexes in Innovation Pack 2014
Removed
Table Index Existing Columns Column
S_BC_ENTRY_TRGT S_BC_ENTRY_TRGT_U1 VIEW_NAME,ENTRY_MODE_CD, APP_NAME

PROCESS_MODE_CD,CONFLICT_ID
Columns Replaced in Table Indexes in Innovation Pack 2014

Table 161 lists columns that were replaced in existing table indexes in Innovation Pack 2014.
Table 161. Columns Replaced in Table Indexes in Innovation Pack 2014
Table Index Existing Columns New Columns
S_MSGPL_ITM_REL S_MSGPL_ITM_REL_U1 MSG_PLAN_ITEM_ID, MSG_PLAN_ITEM_ID,

LIT_ID,TYPE_CD, LIT_NAME,TYPE_CD,
CONFLICT_ID CONFLICT_ID
Index
A about 27
account ERD diagram 28
about 18 tables 27
diagram 20 Automotive
support for Dynamic Hierarchy 18 automotive retail ERD 184
support for Global Account Views 18 dealer sales and service promotion 210
tables 18 vehicle collection ERD 312
account targeting ERD vehicle ERD 310
about 176 vehicle financing ERD 314
diagram 177 vehicle sales ERD 316
tables 176 automotive retail ERD
activity ERD about 184
about 178 diagram 185
diagram 179 tables 184
tables 178
adjustment group ERD B
about 21 banking
diagram 22 See commercial banking ERD
tables 21 See FLEXCUBE Universal Banking Integration
affiliations and best times ERD ERD
about 180 benefit case management ERD. See public
diagram 181 sector benefit case management ERD
tables 180 best call hours
agencies/agent ERD See routes and best call hours ERD
about 182 brick ERD
diagram 183 about 186
tables 182 diagram 187
agreement tables 186
See CME agreement ERD
AIA_INTEG_ID columns, about 327 C
alerts
campaign management
See CME alert ERD
See marketing campaign ERD
apparel
CG promotion planning ERD
See textile, apparel, and footwear ERD
about 29
asset management ERD
diagram 31
about 23
tables 29
diagram 24
chat
tables 23
See community/chat discussion ERD
tracking asset instances 23
child welfare ERD. See public sector child
assets
welfare ERD
See CME energy products, service, and usage
clinical study management ERD
ERD
about 188
auction ERD
diagram 190
about 25
tables 188
diagram 26
clinical study site management ERD
tables 25
about 191
auto email response generator ERD
Index D
diagram 192 compensation planning execution ERD

tables 191 about 34
CME account ERD diagram 35
about 193 tables 34
diagram 194 competency management system ERD
tables 193 about 36
CME agreement ERD diagram 37
about 195 tables 36
diagram 196 Consumer Sector
tables 195 account targeting ERD 176
CME alert ERD best hours entity 289
about 197 CG promotion planning ERD 29
diagram 198 objectives ERD 267
tables 197 sales volume planning ERD 291
CME energy products, service, and usage territory management - consumer sector
ERD ERD 303
about 199 content management ERD
CME order management ERD tables 38
about 201 content object
diagram 202 See content management ERD
tables 201 content process
columns See content management ERD
AIA_INTEG_ID columns, about 327 contract conditions ERD
domain type definitions 325 about 40
INTEGRATION_ID columns, about 327 diagram 41
naming conventions 321 tables 40
numeric physical type 326 contracts ERD
type definitions 325 about 42
commercial banking ERD diagram 43
about 203 tables 42
diagram 205 credit alerts
tables 203 See CME alert ERD
commercial insurance ERD Customer Data Item, about 44
about 206
diagram 207 D
tables 206 data (intersection) table type
Communications, Media, Energy about 323
CME account ERD 193 obsolete, table marked as 323
CME agreement ERD data (private) table type, about 323
CME alert ERD 197 data (public) table type
CME energy products, service, and usage about 323
ERD 199 obsolete, table marked as 323
CME order management ERD 201 data types
pricing comparison ERD 116 limit checking 328
community/chat discussion ERD data visibility ERD
about 208 about 44
diagram 209 diagram 46
tables 208 tables 44
compensation planning administration ERD Database Marketing, marketing program
about 32 ERD 86
diagram 33 database schema version number, finding
tables 32
Index E
and format 327 asset management, tables 23

dealer sales and service promotion ERD auction, diagram 26
about 210 auction, tables 25
diagram 211 auto email response generator,
defect tracking auto email response generator, tables 27
See product quality tracking ERD automotive retail, diagram 185
design automotive retail, tables 184
See schema brick, diagram 187
discussion brick, tables 186
See community/chat discussion ERD CG promotion planning, diagram 31
document ID and tax ID ERD CG promotion planning, tables 29
about 212 clinical study management, diagram 190
diagram 213 clinical study management, tables 188
tables 212 clinical study site management,
domain type definitions 325 diagram 192
Dun & Bradstreet integration ERD clinical study site management, tables 191
about 47 CME account, diagram 194
diagram 48 CME account, tables 193
tables 47 CME agreement, diagram 196
Dynamic Hierarchy, support by account CME agreement, tables 195
entity 18 CME alert, diagram 198
CME alert, tables 197
E CME energy products, service, and usage,
employee KPI ERD diagram 200
about 49 CME energy products, service, and usage,
tables 49 CME order management ERD, diagram 202
Employee Relationship Management CME order management ERD, tables 201
compensation planning administration commercial banking, diagram 205
ERD 32 commercial banking, tables 203
compensation planning execution ERD 34 commercial insurance, diagram 207
competency management system ERD 36 commercial insurance, tables 206
employee KPI ERD 49 community/chat discussion, diagram 209
performance review ERD 107 community/chat discussion, tables 208
employees compensation planning administration,
time sheet ERD 155 diagram 33
entitlement items, service agreement compensation planning administration,
ERD 137 tables 32
ERDs compensation planning execution,
account targeting, diagram 177 diagram 35
account targeting, tables 176 compensation planning execution,
account, diagram 20 tables 34
account, tables 18 competency management system,
activity, diagram 179 diagram 37
activity, tables 178 competency management system,
adjustment group, diagram 22 tables 36
adjustment group, tables 21 content management, diagram 39
affiliations and best times, diagram 181 content management, tables 38
affiliations and best times, tables 180 contract conditions, diagram 41
agencies/agent, diagram 183 contract conditions, tables 40
agencies/agent, tables 182 contracts, diagram 43
asset management, diagram 24 contracts, tables 42
conventions, description of 12
Index E
data visibility, diagram 46 diagram 60

data visibility, tables 44 high tech marketing development fund,
dealer sales and service promotion, tables 59
diagram 211 high tech special pricing authorization,
dealer sales and service promotion, diagram 243
tables 210 high tech special pricing authorization,
document ID and tax ID, diagram 213 tables 242
document ID and tax ID, tables 212 hospitality - meeting package,
Dun & Bradstreet integration, diagram 48 diagram 247
Dun & Bradstreet integration, tables 47 hospitality - meeting package, tables 246
employee KPI, diagram 50 hospitality category, diagram 245
employee KPI, tables 49 hospitality category, tables 244
event tax administration, diagram 215 In-Memory Next Best Action, diagram 62
event tax administration, tables 214 In-Memory Next Best Action, tables 61
exclusive arc relationship, diagram institutional sales, diagram 249
conventions 13 institutional sales, tables 248
expense reports, diagram 52 insurance claims, diagram 252
expense reports, tables 51 insurance claims, tables 250
field service inventory, diagram 54 insurance policies, diagram 254
field service inventory, tables 53 insurance policies, tables 253
field service scheduler, diagram 56 invoiceable charges, diagram 65
field service scheduler, tables 55 invoiceable charges, tables 63
financial account application, diagram 219 invoices, diagram 67
financial account application, tables 218 invoices, tables 66
financial account origination, diagram 221 lead management, diagram 70
financial account origination, tables 220 lead management, tables 68
financial account, diagram 217 life insurance policy, diagram 256
financial account, tables 216 life insurance policy, tables 255
financial investments, diagram 223 loyalty flowchart and formula,
financial investments, tables 222 diagram 262
financial products, diagram 225 loyalty flowchart and formula, tables 261
financial products, tables 224 loyalty, diagram 260
financial services events, diagram 228 loyalty, tables 258
financial services events, tables 226 managed care, diagram 264
fleet management - location, diagram 233 managed care, tables 263
fleet management - location, tables 232 marketing budget request, diagram 72
fleet management, diagram 231 marketing budget request, tables 71
fleet management, tables 229 marketing campaign, diagram 74
FLEXCUBE Universal Banking Integration, marketing campaign, tables 73
diagram 235 marketing collaboration, diagram 76
FLEXCUBE Universal Banking Integration, marketing collaboration, tables 75
tables 234 marketing encyclopedia, diagram 78
forecasts, diagram 58 marketing encyclopedia, tables 77
forecasts, tables 57 marketing event driven dialogue,
general diagram conventions 12 diagram 80
group insurance policies, diagram 237 marketing event driven dialogue, tables 79
group insurance policies, tables 236 marketing events, diagram 83
group pensions, diagram 239 marketing events, tables 81
group pensions, tables 238 marketing plans, diagram 85
health provider and provider group, marketing plans, tables 84
diagram 241 marketing program, diagram 88
health provider and provider group, marketing program, tables 86
tables 240 marketing resource management: document,
high tech marketing development fund, diagram 90
Index E
marketing resource management: document, tables 271

tables 89 public sector case lead management,
medical education event management, diagram 276
diagram 266 public sector case lead management,
medical education event management, tables 274
tables 265 public sector child welfare, diagram 278
objectives, diagram 268 public sector child welfare, tables 277
objectives, tables 267 public sector contact identity, diagram 280
opportunity management, diagram 92 public sector contact identity, tables 279
opportunity management, tables 91 public sector evidence management,
order and promotion, diagram 94 diagram 282
order and promotion, tables 93 public sector evidence management,
order life cycle, diagram 96 tables 281
order life cycle, tables 95 public sector incident management,
orders, diagram 98 diagram 284
orders, tables 97 public sector incident management,
partner collaboration, diagram 100 tables 283
partner collaboration, tables 99 public sector service provider and referral
partner program registration, diagram 102 management, diagram 286
partner program registration, tables 101 public sector service provider and referral
party model, diagram 104 management, tables 285
party model, tables 103 real-time scheduler integration,
payments, diagram 106 diagram 288
payments, tables 105 real-time scheduler integration, tables 287
performance review, diagram 109 recursive relationship, diagram
performance review, tables 107 conventions 14
personal account, diagram 111 revenue, diagram 132
personal account, tables 110 revenue, tables 131
personal financial review, diagram 113 revision table 15, 173
personal financial review, tables 112 routes and best call hours, diagram 290
personalized content delivery, routes and best call hours, tables 289
diagram 270 sales hierarchy and credit assignment,
personalized content delivery, tables 269 diagram 134
pricing comparison, diagram 117 sales hierarchy and credit assignment,
pricing comparison, tables 116 tables 133
pricing, diagram 115 sales portfolio management, diagram 136
pricing, tables 114 sales portfolio management, tables 135
product promotion, diagram 119 sales volume planning, diagram 292
product promotion, tables 118 sales volume planning, tables 291
product quality tracking, diagram 121 sample management, diagram 294
product quality tracking, tables 120 sample management, tables 293
product recommendation and offer, service agreement, diagram 138
diagram 123 service agreement, tables 137
product recommendation and offer, service calendars and work shifts,
products or services, diagram 125 service calendars and work shifts,
products or services, tables 124 tables 139
professional services, diagram 127 service request, diagram 142
professional services, tables 126 service request, tables 141
promotion group, diagram 130 shipment, diagram 144
promotion group, tables 128 shipment, tables 143
public sector benefit case management, Siebel Assistant, diagram 146
diagram 273 Siebel Assistant, tables 145
public sector benefit case management, social media, diagram 148
Index F
social media, tables 147 diagram 215

special rate list, diagram 296 tables 214
special rate list, tables 295 exclusive arc relationship
syndicated data, diagram 298 about 13
syndicated data, tables 297 diagram conventions 13
teller administration, diagram 300 expense reports ERD
teller administration, tables 299 about 51
territory alignment - quota assignment diagram 52
territory alignment - quota assignment, extension (Siebel) table type
tables 301 about 323
territory management - consumer sector, obsolete table marked as 323
diagram 304 extension table type, about 323
territory management - consumer sector,
tables 303 F
territory management - life sciences, field service inventory ERD
territory management - life sciences, diagram 54
territory management, diagram 150 field service scheduler ERD
territory management, tables 149 about 55
territory quota rollup, diagram 152 diagram 56
territory quota rollup, tables 151 tables 55
textile, apparel, and footwear, financial account application ERD
textile, apparel, and footwear, tables 153 diagram 219
time sheet, diagram 156 tables 218
time sheet, tables 155 financial account ERD
trade promotions, diagram 158 about 216
trade promotions, tables 157 diagram 217
training curriculum course, diagram 160 tables 216
training curriculum course, tables 159 financial account origination ERD
training test engine, diagram 162 about 220
training test engine, tables 161 diagram 221
universal customer master, diagram 309 tables 220
universal customer master, tables 307 financial accounts
vehicle collection, diagram 313 financial account application ERD 218
vehicle collection, tables 312 financial account ERD 216
vehicle financing, diagram 315 financial account origination ERD 220
vehicle financing, tables 314 personal account ERD 110
vehicle sales, diagram 317 financial investments ERD
vehicle sales, tables 316 about 222
vehicle, diagram 311 diagram 223
vehicle, tables 310 tables 222
versioned object definition, diagram 164 financial products ERD
versioned object definition, tables 163 about 224
warranty claim, diagram 170 diagram 225
warranty claim, tables 168 tables 224
warranty, diagram 167 financial review
warranty, tables 165 See personal financial review ERD
work order, diagram 172 Financial Services
work order, tables 171 agencies/agent ERD 182
event tax administration ERD commercial banking ERD 203
about 214
Index G
commercial insurance ERD 206 about 238

financial account application ERD 218 diagram 239
financial account ERD 216 tables 238
financial account origination ERD 220
financial investments ERD 222 H
financial products ERD 224 health provider and provider group ERD
financial services events ERD 226 about 240
FLEXCUBE Universal Banking Integration diagram 241
ERD 234 tables 240
group insurance policies ERD 236 high tech marketing development fund ERD
group pensions ERD 238 about 59
health provider and provider group diagram 60
ERD 240 tables 59
institutional sales ERD 248 high tech special pricing authorization ERD
insurance claims ERD 250 about 242
insurance policies ERD 253 diagram 243
life insurance policy ERD 255 tables 242
teller administration ERD 299 Hospitality
financial services events ERD event tax administration ERD 214
about 226 hospitality - meeting package ERD
fleet management - location ERD tables 246
about 232 hospitality category ERD
fleet management ERD tables 244
about 229
diagram 231
tables 229 I
FLEXCUBE Universal Banking Integration Include Only field 327
ERD index column fields 327
about 234 index naming conventions 321
diagram 235 In-Memory Next Best Action ERD
tables 234 about 61
footwear diagram 62
See textile, apparel, and footwear ERD tables 61
forecasts ERD institutional sales ERD
about 57 about 248
fraud alerts insurance
See CME alert ERD commercial insurance ERD 206
group insurance policies ERD 236
insurance claims ERD 250
G insurance policies ERD 253
generating table report 329 life insurance policy ERD 255
Global Account Views, support by account personal account ERD 110
entity 18 insurance claims ERD
group insurance policies ERD about 250
tables 236 insurance policies ERD
group pensions ERD about 253
Index L
diagram 254 M
tables 253 managed care ERD
INTEGRATION_ID columns, about 327 about 263
invoiceable charges ERD diagram 264
about 63 tables 263
diagram 65 Marketing
tables 63 CG promotion planning ERD 29
invoices ERD Dun & Bradstreet integration ERD 47
about 66 forecasts ERD 57
diagram 67 high tech marketing development fund
tables 66 ERD 59
lead management ERD 68
L marketing budget request ERD 71
lead management ERD marketing campaign ERD 73
about 68 marketing collaboration ERD 75
diagram 70 marketing encyclopedia ERD 77
tables 68 marketing event driven dialogue ERD 79
life insurance policy ERD marketing events ERD 81
about 255 marketing plans ERD 84
diagram 256 marketing program ERD 86
tables 255 marketing resource management: document
Life Sciences ERD 89
activity ERD 178 marketing budget request ERD
affiliations and best times ERD 180 about 71
brick ERD 186 diagram 72
clinical study management ERD 188 tables 71
clinical study site management ERD 191 marketing campaign ERD
community/chat discussion ERD 208 about 73
managed care ERD 263 diagram 74
medical education event management tables 73
ERD 265 marketing collaboration ERD
personalized content delivery ERD 269 about 75
sample management ERD 293 diagram 76
syndicated data ERD 297 tables 75
territory management - life sciences marketing development funds
ERD 305 See CG promotion planning ERD
limit checking for data types 328 marketing encyclopedia ERD
loans, commercial banking entity 203 about 77
logical model diagram 78
ERD conventions 12 tables 77
ERD descriptions 15 marketing event driven dialogue ERD
ERD descriptions for Siebel Industry about 79
Applications 173 diagram 80
loyalty ERD tables 79
about 257 marketing events ERD
loyalty flowchart and formula ERD tables 81
about 261 marketing plans ERD
tables 84
marketing program ERD
Index N
about 86 about 95
tables 86 tables 95
marketing resource management: document orders ERD
ERD about 97
about 89 diagram 98
tables 89
Master Data Item, about 44 P
MDFs partner collaboration ERD
See CG promotion planning ERD about 99
MedEd event management diagram 100
See medical education event management tables 99
ERD partner program registration ERD
medical education event management ERD about 101
tables 265 party model ERD
mini brick about 103
See brick ERD diagram 104
tables 103
N party model, about 328
naming conventions party, defined 103
columns 321 payments ERD
indexes 321 about 105
physical model listings, abbreviations diagram 106
used 322 tables 105
table names 319 performance review ERD
table prefixes 320 about 107
table suffixes 320 diagram 109
non-Siebel application products, caution tables 107
about inserting or updating personal account ERD
data 12 about 110
normalized, defined 11 diagram 111
tables 110
O personal financial review ERD
objectives ERD about 112
tables 267 personalized content delivery ERD
opportunity management ERD about 269
tables 91 physical model
Oracle Applications AIA_INTEG_ID columns, about 327
about use of AIA_INTEG_ID columns 327 column naming conventions 321
about use of INTEGRATION_ID column type definitions 325
columns 327 columns of numeric physical type 326
order and promotion ERD database schema version number, finding and
about 93 format 327
diagram 94 domain type definitions 325
tables 93 Include Only field 327
order life cycle ERD index naming conventions 321
Index R
INTEGRATION_ID columns, about 327 tables 271

limit checking for data types 328 public sector case lead management ERD
party model, about 328 about 274
physical model listings, abbreviations diagram 276
used 322 tables 274
Siebel repository tables, about 327 public sector child welfare ERD
Siebel system fields 326 about 277
table naming conventions 319 diagram 278
table report, about 329 tables 277
table status definitions 324 public sector contact identity ERD
table type definitions 323 about 279
validating Siebel Schema 328 diagram 280
physicians tables 279
See health provider and provider group ERD public sector evidence management ERD
prescription information about 281
See syndicated data ERD 297 diagram 282
pricing comparison ERD tables 281
about 116 public sector incident management ERD
pricing ERD tables 283
about 114 public sector service provider and referral
diagram 115 management ERD
product promotion ERD diagram 286
about 118 tables 285
diagram 119
tables 118 R
product quality tracking ERD real-time scheduler integration ERD
about 120 about 287
product recommendation and offer ERD recursive relationship
about 122 about 14
diagram 123 diagram conventions 14
tables 122 report about tables
products or services ERD generating 329
about 124 repository, about Siebel repository 327
diagram 125 revenue ERD
professional services ERD 126 diagram 132
diagram 127 routes and best call hours ERD
promotion group ERD diagram 290
diagram 130
tables 128
protocols S
See clinical study management ERD Sales
See clinical study site management ERD Dun & Bradstreet integration ERD 47
public sector benefit case management ERD forecasts ERD 57
about 271 high tech special pricing authorization
diagram 273 ERD 242
Index T
In-Memory Next Best Action ERD 61 about 139

lead management ERD 68 diagram 140
marketing encyclopedia ERD 77 tables 139
opportunity management ERD 91 service provider and referral management
routes and best call hours ERD 289 See public sector service provider and referral
sales hierarchy and credit assignment ERD management ERD
sales portfolio management ERD 135 service region
territory alignment - quota assignment See field service scheduler ERD
ERD 301 service request ERD
territory management - life sciences about 141
ERD 305 diagram 142
territory management ERD 149 tables 141
territory quota rollup ERD 151 service requests
sales hierarchy and credit assignment ERD See CME account ERD
about 133 services
diagram 134 See CME energy products, service, and usage
tables 133 ERD
Sales Hierarchy Module shipment ERD
See sales hierarchy and credit assignment about 143
ERD diagram 144
sales portfolio management ERD tables 143
about 135 Siebel Assistant ERD
sales volume planning ERD tables 145
about 291 Siebel Industry Applications
diagram 292 ERD descriptions 173
tables 291 Siebel repository, about 327
sample management ERD Siebel SAP R/3 Connector, about use of
about 293 INTEGRATION_ID columns 327
diagram 294 Siebel system fields 326
tables 293 social media ERD
schema about 147
database schema version number, finding and diagram 148
format 327 tables 147
defined 11 special ERD conventions
validating Siebel Schema 328 exclusive arc relationship 13
Service recursive relationship 14
field service inventory ERD 53 special rate list ERD
field service scheduler ERD about 295
invoiceable charges ERD 63 diagram 296
invoices ERD 66 tables 295
products or services ERD 124 syndicated data ERD
service agreement ERD 137 about 297
service calendars and work shifts ERD 139 diagram 298
service request ERD 141 tables 297
territory management - consumer sector system fields 326
ERD 303
warranty ERD 165 T
service agreement ERD table columns
about 137 changed in Innovation Pack 2014 334
diagram 138 new in Innovation Pack 2014 332
tables 137 table indexes
service calendars and work shifts ERD
Index U
added to Innovation Pack 2014 335 training curriculum course ERD

columns removed from Innovation Pack about 159
2014 336 diagram 160
columns replaced in Innovation Pack tables 159
2014 336 training test engine ERD
tables about 161
generating report 329 diagram 162
naming conventions 319 tables 161
new in Innovation Pack 2014 331 trouble tickets
prefix naming conventions 320 See CME account ERD
suffix naming conventions 320
table status definitions 324 U
types of 323 universal customer master ERD
tax ID about 307
See document ID and tax ID ERD diagram 309
teller administration ERD tables 307
about 299
diagram 300
tables 299 V
territory alignment - quota assignment ERD validating Siebel Schema 328
about 301 vehicle collection ERD
territory management - consumer sector tables 312
ERD vehicle ERD
about 303 about 310
territory management - life sciences ERD vehicle financing ERD
about 305 about 314
territory management ERD vehicle sales ERD
about 149 about 316
territory quota rollup ERD versioned object definition ERD
about 151 about 163
tests
See training test engine ERD W
textile, apparel, and footwear ERD warranty claim ERD
about 153 about 168
time sheet ERD warranty ERD
about 155 about 165
trade promotions ERD work order ERD
about 157 about 171
Index W
work shifts workflow process

See service calendars and work shifts ERD See content management ERD
Index W

DMR2014 PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

DMR2014 PDF

Transféré par

Droits d'auteur :

Formats disponibles

Siebel Data Model

Access to Oracle Support

Siebel Data Model Reference 1

Chapter 1: Whats New in This Release

Chapter 2: Siebel Logical Model

Siebel Data Model Reference Siebel Innovation Pack 2014, Rev. A 3

4 Siebel Data Model Reference Siebel Innovation Pack 2014, Rev. A

Training Test Engine 161

Siebel Data Model Reference Siebel Innovation Pack 2014, Rev. A 5

Insurance Policies 253

Chapter 3: Siebel Physical Model

6 Siebel Data Model Reference Siebel Innovation Pack 2014, Rev. A

Domain Type Definitions 325

Chapter 4: Schema Changes

Siebel Data Model Reference Siebel Innovation Pack 2014, Rev. A 7

8 Siebel Data Model Reference Siebel Innovation Pack 2014, Rev. A

Whats New in Siebel Data Model Reference, Siebel Innovation Pack

Whats New in Siebel Data Model Reference, Siebel Innovation Pack

Siebel Data Model Reference Siebel Innovation Pack 2014, Rev. A 9

Schema Changes Implemented in Siebel Removed topic.

Schema Changes Implemented in Siebel Removed topic.

What's New in Siebel Data Model Reference Version 8.1/8.2

Schema Changes Implemented in Modified topic. A listing of the schema changes

Schema Changes Implemented in Modified topic. A listing of the schema changes

10 Siebel Data Model Reference Siebel Innovation Pack 2014, Rev. A

The information on ERDs is organized as follows:

Overview of Siebel Data Model

Entity Relationship Diagram Conventions

Overview of Siebel Data Model

Siebel Data Model Reference Siebel Innovation Pack 2014, Rev. A 11

NOTE: The Siebel Bookshelf is available on Oracle Technology Network (http://www.oracle.com/

Entity Relationship Diagram

Relationships between entities

This topic describes entity relationship diagram conventions, as follows:

General Entities on page 12

Exclusive Arc Relationship on page 13

Recursive Relationship on page 14

12 Siebel Data Model Reference Siebel Innovation Pack 2014, Rev. A

Figure 1. General Entity Relationship Diagram Conventions

Exclusive Arc Relationship

Siebel Data Model Reference Siebel Innovation Pack 2014, Rev. A 13

Figure 2. Exclusive Arc Relationship Diagram Convention Example

Entity Relationship Example:

1) Each activity may by made up of one or more activities.

Figure 3. Recursive Relationship Diagram Convention Example

14 Siebel Data Model Reference Siebel Innovation Pack 2014, Rev. A

Entity Relationship Diagrams and

Table 4. Entity Relationship Diagrams for Siebel Cross-Industry Applications

Figure Num. and

Account Figure 4 on page 20 General

Adjustment Group Figure 5 on page 22 General

Asset Management Figure 6 on page 24 General

Auction Figure 7 on page 26 General

Auto Email Response Generator Figure 8 on page 28 General

CG Promotion Planning Figure 9 on page 31 Marketing

Compensation Planning Administration Figure 10 on page 33 ERM

Compensation Planning Execution Figure 11 on page 35 ERM

Competency Management System Figure 12 on page 37 ERM

Content Management Figure 13 on page 39 General

Contract Conditions Figure 14 on page 41 General

Dun & Bradstreet Integration Figure 17 on page 48 Sales and Marketing

Employee KPI Figure 18 on page 50 ERM

Expense Reports Figure 19 on page 52 General