DMR2014

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 errorfree. 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
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
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
89
Contents
Training Test Engine 161

Versioned Object Definition
Warranty 165
Warranty Claim 168
Work Order 171
163
Entity Relationship Diagrams and Descriptions for Siebel Industry Applications

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
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
173
193
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
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
285
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
Data Model Type Definitions
322
322
Table Type Definitions 323

Table Status Definitions 324
Column Type Definitions 325
Contents
Domain Type Definitions
325
Columns of Numeric Physical Type

Siebel System Fields
326
INTEGRATION_ID Columns
Include Only Field
Siebel Repository
326
327
327
327
Database Schema Version
327
Limit Checking for Data Types

Validating the Siebel Schema
328
328
Party Model Unifies Access to Data

Generating a Report about Tables
328
329
Chapter 4: Schema Changes

Schema Changes Implemented in Siebel Innovation Pack 2014
New Tables Added to Innovation Pack 2014 331
Changes to Table Columns Implemented in Innovation Pack 2014
Changes to Table Indexes Implemented in Innovation Pack 2014
331
332
335
Index
Contents
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

2014 on page 331
Modified topic. A listing of the new tables that have been

added to Siebel Innovation Pack 2014.
Changes to Table Columns

Implemented in Innovation Pack 2014
on page 332
Modified topic. A listing of the table columns that have

changed in Siebel Innovation Pack 2014.
Changes to Table Indexes Implemented

in Innovation Pack 2014 on page 335
Modified topic. A listing of the table indexes that have

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

Innovation Pack 2014 on page 331
Modified topic. A listing of the schema changes

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

CRM Version 8.1.1.11/8.2.2.4 Compared
with Version 8.1.1.10.
Removed topic.

CRM Version 8.1.1.11/8.2.2.4 Compared
with Version 8.2.2.3.
Removed topic.
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

page 188
Modified topic. Added two new entities: Contract and

Exception Activity.
Schema Changes Implemented in

Siebel CRM Version 8.1.1.11/8.2.2.4
Compared with Version 8.1.1.10 on
page 329

implemented in version 8.1.1.11/8.2.2.4 compared with
version 8.1.1.10.
Schema Changes Implemented in

Siebel CRM Version 8.1.1.11/8.2.2.4
Compared with Version 8.2.2.3 on
page 361

implemented in version 8.1.1.11/8.2.2.4 compared with
version 8.2.2.3.
10
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:
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

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.
11
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.
12
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.
13
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.
14
Recursive Relationship Diagram Convention Example
Entity Relationship Diagrams and Descriptions for Siebel CrossIndustry 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
ERD Name
Figure Num. and

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
Figure 9 on page 31
Marketing
Compensation Planning Administration
Figure 10 on page 33
ERM
Compensation Planning Execution
ERM
Competency Management System
ERM
Content Management
General
Contract Conditions
General
Contracts
General
Data Visibility
General
Dun & Bradstreet Integration
Sales and Marketing
Employee KPI
ERM
Expense Reports
General
Field Service Inventory
Service
Field Service Scheduler
Service
Forecasts
Sales and Marketing
High Tech Marketing Development Fund
Marketing
In-Memory Next Best Action
Marketing
Invoiceable Charges
Service
Invoices
Service
15

Industry Applications
Table 4.
Entity Relationship Diagrams and Descriptions for Siebel Cross-
ERD Name
Figure Num. and

Page
Functional Area
Lead Management
Sales and Marketing
Marketing Budget Request
Marketing
Marketing Campaign
Marketing
Marketing Collaboration
Marketing
Marketing Encyclopedia
Sales and Marketing
Marketing Event Driven Dialogue
Marketing
Marketing Events
General
Marketing Plans
Marketing
Marketing Program
Marketing
Marketing
Opportunity Management
Sales
Order and Promotion
General
Order Life Cycle
General
Orders
General
Partner Collaboration
General
Partner Program Registration
General
Party Model
General
Payments
General
Performance Review
ERM
Personal Account
Industry-Specific
Personal Financial Review
Industry-Specific
Pricing
General
Pricing Comparison
Energy
Product Promotion
General
Product Quality Tracking
General
Product Recommendation and Offer
General
Products or Services
Service
Professional Services
General
Promotion Group
General
Revenue
General
16
Table 4.
ERD Name
Figure Num. and

Page
Functional Area
Sales Hierarchy and Credit Assignment
Sales
Sales Portfolio Management
Sales
Service Agreement
Service
Service Calendars and Work Shifts
Service
Service Request
Service
Shipment
General
Siebel Assistant
General
Social Media
General
Territory Management
Sales
Territory Quota Rollup
Sales
Textile, Apparel, and Footwear
Consumer Sector
Time Sheet
General
Trade Promotions
General
Training Curriculum Course
General
Training Test Engine
General
General
Warranty
Service
Warranty Claim
Service
Work Order
Service
17

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
18
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
19
20
part of
PAYMENT TERM
default payment term for
composed of
a parent of
user of
applicable to
a report to
POSITION
held by
responsibility of
access to
EMPLOYEE / AGENT
target of
current price
list for
holders
of
SALES OR SERVICE
TEAM MEMBER
responsible for
PRICE LIST
participant in
ASSIGNMENT
GROUP
(TERRITORY)
user characteristics for
described in
OTHER PERSON
PERSON
contact of
pay or payed by
target of
belong to
for
MARKET
SEGMENT
addressed to
participate in
action for
ACTIVITY
type of
OTHER
PARTY
for
DECISION
ISSUES
responsibility of
constrained to use
responsible for
ACCOUNT
known as
for
ADDRESS
located at
acessible to
NAMED HIERARCHY
made up of
of
BUSINESS UNIT
PARTY
made visible through
for
a parent of
another name for
CORRESPONDENCE
classification for
CHARACTERISTIC
Figure 4.
NAMED HIERARCHY
ACCOUNT
a report to
ACCOUNT SYNONYM
INDUSTRY

Account
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
21
22
for
# MTRX_RULE_NUM
STANDARD TRAINING PRICING MATRIX RULE
# MTRX_RULE_NUM
STANDARD PRODUCT PRICING MATRIX RULE
# MTRX_RULE_NUM
STANDARD ENTITLEMENT PRICING MATRIX

RULE
# MTRX_RULE_NUM
for
for
for
PRODUCT PROMOTION PRICING MATRIX RULE for
# MTRX_RULE_NUM
for
contain
contain
contain
contain
contain
contain

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

Adjustment Group
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 upperright 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

Competitive Metric
S_CMPT_MTRC
Competitive Product Feature
S_CMPT_PROD_FEA
Contact
S_CONTACT, S_PARTY
Employee
External Product
S_PROD_EXT
Internal Product
S_PROD_INT
Opportunity
S_OPTY
Opportunity Asset
S_OPTY_ASSET
Person
S_CONTACT, S_PARTY
Personal Address
S_ADDR_PER
Product Instance (Asset)
S_ASSET
Service Request
S_SRV_REQ
23
24
initiated by
for
of
ASSET
RELATIONSHIP
ACTIVITY PART
MOVEMENT
of
moved by
ASSET
FEATURE
of
COMPETITIVE
PRODUCT
FEATURE
a component of
an assembly of
of
of
subject of
subject of
moved by
use of
NON-SERIALIZABLE
PRODUCT
INTERNAL PRODUCT
PRODUCT
involved in
parent of
EXTERNAL
PRODUCT
child of
vendor of
VENDOR
OTHER EXTERNAL
ORGANIZATION
ACCOUNT
SERIALIZABLE
PRODUCT
made into
produced by
owner of
EXTERNAL
ORGANIZATION
associated with
associated with
associated with
EMPLOYEE
currently possessed by
possessor of
owner of
currently owned by
use of
to
to
to
OPPORTUNITY
currently owned byCONTACT
PERSON
ASSET CONTACT RELATIONSHIP
instance of
involved in
ASSET
MODIFICATION
for
modified by
initiated by
ASSET EMPLOYEE RELATIONSHIP
ASSET EXTERNAL ORGANIZATION
for
of
subject
of
subject of
located at
subject of
initiator of
subject of
subject of
for
NOTE
for
of
classification for
COMPETITIVE
of
METRIC
classification for
of
for
subject of
for
PRODUCT INSTANCE (ASSET)
associated with
associated with
subject of
subject of
defined for
for problems with

subject of
for problems with
SERVICE
REQUEST
made up of
defined for
initiator of
performed on
made up of
BUSINESS
ADDRESS
OPPORTUNITY
ASSET
Figure 6.
part of
ACTIVITY
part of
PERSONAL
ADDRESS
ADDRESS

Asset Management
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 Siebelowning 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
25
26
OTHER PARTY
PARTY

OTHER PERSON
USER
lister of
listed by
AUCTION ITEM
placer of
subject of
featured in
PERSON
for
for
fulfilled as
fulfillment of
placed by
AUCTION ITEM BID
AUCTION ITEM
PROMOTION
ORDER
composed of
part of
ORDER ITEM
for
for
subject of
subject of
pricing
mechanism
for
ASSET
creator of
for
AUCTION ITEM WATCH
alerted by
for
represented by
TRIGGERED AUCTION ITEM ALERT
priced by
displayed as
PRODUCT
displayed as
represented by
priced by
pricing
mechanism
for
created from
for
creator of
subject of
made by
applicable to
made up of
rating of
creator of
created by
AUCTION ALERT
DEFINITION
subject of
AUCTION LISTER/BIDDER
RATING
genesis of
created
from
CATALOG
owner of
owner of
CATALOG CATEGORY
part of
Figure 7.
represented as
CATALOG CATEGORY ITEM
accessed
via

Auction

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
Catalog Category
S_CTLG_CAT
Category Usage Notification
S_COMM_CTG_NTFY
Communication Template Usage Notification
S_COMMTMPL_NTFY
Person
S_CONTACT, S_PARTY
Problem Resolution Document
S_RESITEM
Template Communication Response
S_DMND_CRTN_PRG
27
28
subject of
for usage of
PERSON
target of
COMMUNICATION TMPL USAGE

NOTIFICATION
OUTBOUND RESPONSE
INBOUND COMMUNICATION
PROBLEM
RESOLUTION
DOCUMENT
to notify
categorized within
target of
to notify
CATEGORY
USAGE
NOTIFICATION
classification of
default response for
subject of
for usage of
classification for
categorized under
classification for
made up
part of
CATALOG
made up of
CATALOG CATEGORY
part of
Figure 8.
TEMPLATE COMMUNICATION RESPONSE
ACTIVITY

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
Account
S_ORG_EXT, S_PARTY
Authorized Product
S_ORG_PROD
Fund Allocation
S_MDF_ALLOC
Marketing Development Fund
S_MDF
Marketing Event or Activity
S_SRC
MDF Accrual
S_MDF_ACCRUAL
Payment
S_SRC_PAYMENT
Period
S_PERIOD
Person
S_CONTACT, S_PARTY
Position
S_POSTN, S_PARTY
Price List
S_PRI_LST
Price List Item
S_PRI_LST_ITEM
Product Internal
S_PROD_INT
Product Line
S_PROD_LN
Product Structure
S_PROD_REL or S_PROD_ITEM
Promotion Plan
S_SRC
Promotion
S_SRC
Promotion Account
S_SRC
Promotion Product
S_SRC
29

Table 10.
CG Promotion Planning ERD Entities and Tables
Entity
Table
Promotion Category
S_SRC
Promotion Account Product
S_SRC
30
of
subject of
MIXED FUND
FIXED FUND
ACCRUAL
FUND
MARKETING
part of DEVELOPMENT
FUND
made up of
sub allocated to
sub allocation of

defined for
for
funded through
for promotion of
for promotion of
AUTHORIZED
PRODUCT
designated to
responsible for
assigned to
responsible for
assigned to
approved by
requested by
to
covered by
earned in
earned by
earned by
PRICE LIST ITEM
subject of
relation of
earner of
subject of
of
for
ACCOUNT
OTHER PERSON
EMPLOYEE / AGENT
PERSON
target of
related to
MDF ACCRUAL
of
at
POSITION
approver of
requestor of
for
OTHER PAYMENT
PROMOTION PAYMENT
PAYMENT
subject of
subject of
subject of
PRODUCT LINE
PERIOD
earner of
part of
subject of
subject of
subject of
of
of
hierarchy child of
hierarchy parent of
INTERNAL PRODUCT OR
SERVICE
a component of
promoted via
an assembly of
subject of
basis for
for
PRODUCT
STRUCTURE
defined for
OTHER MARKETING EVENT OR

ACTIVITY
PROMOTION ACCOUNT PRODUCT
PROMOTION PRODUCT
PROMOTION CATEGORY
PROMOTION ACCOUNT
PROMOTION
user of
composed of
based on
PRICE LIST
used by
available to
defined for
part of
made of
recipient of
applicable to
subject to
target of
subject of
composed of
for
PROMOTION PLAN
MARKETING EVENT OR ACTIVITY
Figure 9.
FUND
ALLOCATION

Oracle

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
32
used by
BUSINESS UNIT
have
budget for
COMPENSATION BUDGET DEFINITION
container for
used by
EMPLOYEE ELIGIBILITY
(PDQ)
type for
defined for
constrained by
COMPENSATION TYPE
type for
defined for
subject of type of
valid date for
container for
used in
defined for
QUARTERLY PERIOD
ANNUAL PERIOD
PERIOD
used in
defined for
used in
2 factor
defined
in
have
defined in
SALARY GRADE
composed of
sub-org of
for
JOB
FAMILY
support
POSITION
defined for
employer of
for
JOB
CATEGORY
category for
employed by
salary
grade
defined
in
part of
grouping for
categorized
in
manage by
salary plan for
have
has
job code for

JOB CODE
salary plan
grade defined
in
SALARY PLAN FOR

SALARY GRADE
salary grades for
component of
period for
have
for
SALARY PLAN
component of
1 factor
defined
in
defined defined
for
for
COMPENSATION
REGION
COMPENSATION
GUIDELINE
FACTOR
used in
subject of
COMPENSATION PLANNING PERIOD
container for
have
compensation location for
values for
salary
defined
in
located in
EMPLOYEE / AGENT
COMPENSATION GUIDELINE
DEFINITION
has
COMPENSATION GUIDELINE TABLE
defined for
COMPENSATION
GUIDELINE SET
user of
subject of
type of
defined for
defined for constrained by
COMPENSATION BUDGET ITEM
has
have
COMPENSATION
CHANGE EFFECTIVITY
DATE
allocated for
COMPENSATION CYCLE PLANNING PERIOD
budget allocation for
COMPENSATION BUDGET
ITEM FOR EMPLOYEE
Title : Compensation Planning Administration

Author : Oracle, Confidential

Figure 10. Compensation Planning Administration
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
34
"$%$
&!'$.'
2
2
"$%$
&!'$
!*$$

1

14

3

"$%$
'$'
13
2
2

14
14
"$%$
.&!

!*$$
13
14

1

6
2
.&%$%%
&$
313
"'+0

$
3

!

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

21

613
513
2
1

6

313
213
113

"$%$
'$

"$%$'$*"'+
"$%$'$$$

!
"$%$
.&!
"
3

3
"$%$+

"$%$
&!'$%
2

"$%$
'$ ""$%
3
14

"$%$
+ ''$$$

!

3

"$%$'$"*"'+

Oracle

Figure 11. Compensation Planning Execution
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

Category
S_CMPTNCY
Educational Qualification
S_PER_EDU_QUAL
Employee Competency
S_EMP_CMPTNCY
Employee Competency Change
S_EMP_CMPT_CHG
Employee/Agent
S_EMP_PER
Honors And Awards
S_PER_AWARD
Job Code
S_JOB
Job Profile
S_JOB_PROFILE, S_JOBPRFL_CMPT
Past Work Experience
S_PER_WRK_EXP
Person
S_USER, S_CONTACT
Professional Membership
S_PER_PROF_MBR
Professional Qualification
S_PER_PROF_CERT
Review Rating
S_PERF_RATING
Review Rating Scale
S_PERF_RTNG_SCL
Team Competency
S_TEAM_CMPTNCY
Training Course
S_PROD_INT_CRSE
36

=.*'
?

13
2
9

2

313

13
=. !

26
14
14

13

3
6 5 6
3

2613
>;$
% '

>;$

"'+ "$ +

9$

513
" "$ +
%;<8$
*%%$'"".%9
"'+ &$ "$ +

@
"$ +

+
3

9$%$!;!%
!& $'7&'* $
*%%$' * $
7&'* $8$
"$ +

+

?

$$
&%

?

"$ +
3"%3
Oracle
"'+
0
$
%$
9
%$

Figure 12. Competency Management System
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
Person
S_CONTACT, S_PARTY
Position
S_POSTN, S_PARTY
Product
S_PROD_INT
38
CONTENT
PROJECT
ITEM
picked via
picked via
owned by
used by
owner of
responsible
for
responsibility
of
managed by
for managing
changes to
an example of
Title : Content Management

OTHER MASTER
DATA ITEM
holder of
followed by
controlled by
producer of
produced by
held by
generally
controlled
by
used by
WORKFLOW PROCESS
generally followed
by
PERSON
generally the responsibility of
generally responsible for
PICK APPLET
CONTENT
PROJECT
POSITION
PRODUCT
LITERATURE
MASTER DATA ITEM
type for
VIEW
used by
based on
used by
picked via
used by
used by
published via
EAI
INTEGRATION
OBJECT
used by
BUSINESS
OBJECT
basis for
picked via
CONTENT OBJECT
viewed via
used by
made
up of
part of
used by
viewed via
picked via
picked via
CONTENT ITEM
TYPE
PICK LIST

Figure 13. Content Management
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
Product Line
S_PROD_LN
Template Benefit
S_ENTL_BNFTTMPL
Template Condition
S_ENTL_CONDTMPL
Template Term
S_AGR_TERM_TMPL
Term
S_AGR_TERM_DESC
40
AGREEMENT
used by
correspond to
comprise
applicable to
ENTITLEMENT
# NAME
governed by
in reference to
comprise
used by
OTHER
CONTRACT
TEMPLATE TERM
# TERM_NUM
dependent upon
used by
in reference to
belong to
basis for
subject of
subject of
subject of
subject of
subject of
in reference to
comprise
in reference to
ENTITLEMENT TEMPLATE
# NAME
composed of
TEMPLATE BENEFIT
# SEQ_NUM
in context of
TEMPLATE CONDITION
# SEQ_NUM
used in
composed of
in reference to
based on
applicable to
based on
BENEFIT
# SEQ_NUM
governed by
applicable to
applicable to
CONDITION
# SEQ_NUM
subject of
in reference to
applicable to
based on
in reference to
CONDITION COMPLIANCE
# COMPL_NUM
subject of
CONTRACT
subject of
applicable to
TERM
Title : Contract Lifecycle Management

CATEGORY
OBJECT CLASS
PRODUCT LINE
PRODUCT
CONTRACT CONDITION
OBJECT

Figure 14. Contract Conditions
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
Account
S_ORG_EXT, S_PARTY
Asset
S_ASSET
Business Unit
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
Payment Term
S_PAYMENT_TERM
Person
S_CONTACT, S_PARTY
Position
S_POSTN, S_PARTY
Price List
S_PRI_LST
42
BUSINESS UNIT
responsible for
ORDER
PERSON
primary contact for
responsibility of
POSITION
responsible for
responsibility of
OTHER CONTRACT
AGREEMENT
CONTRACT
composed of
part of
QUOTE
ORDER LINE ITEM
for
priced by
pricing for
ASSET
subject of
default pricing for
subject of
part of
composed of
priced by
for
for
involved by
for
DELETED CONTRACT ITEM
subject of
QUOTE LINE ITEM
composed of
OTHER CONTRACT LINE ITEM
AGREEMENT LINE
ITEM
CONTRACT LINE ITEM
part of
Title : Contracts
employed at
ACCOUNT
subject to
employer of
for
subject to
pricing
method for
subject of
for
PAYMENT
TERM
for
subject to
priced by
INTERNAL
PRODUCT OR
SERVICE
subject of
made into
an instance of
applicable to
PRICE LIST
subject of
for

Figure 15. Contracts
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
Agreement
S_DOC_AGREE
Business Unit
Catalog
S_CTLG
Category
S_CTLG_CAT
Dynamic Account Hierarchy
S_DYN_HRCHY
Dynamic Account Hierarchy Node
S_DYN_HRCHY_REL
Employee/Agent
Group
S_PARTY
Internal/Partner Organization Unit
S_ORG_EXT
Literature Item
S_LIT
Opportunity
S_OPTY
44
Table 17.
Data Visibility ERD Entities and Tables
Entity
Table
Order
S_ORDER
Organization Unit
S_ORG_EXT, S_PARTY
Party
S_PARTY
Position
S_POSTN, S_PARTY
Price List
S_PRI_LST
Product
S_PROD_INT
Quote
S_DOC_QUOTE
Service Request
S_SRV_REQ
45

Figure 16. Data Visibility

!>13
Oracle
"%!"
&%"!"

@
'%
&$+
7&
%>
7&%
>+
!

"$

+

'&"
1
9 &%"
!"

9"%
!"
'
613
13
13

+

%$
"'+0
$
1

%%
&
9%$

9+
1

&

$[$&$

%$
9
$[$&$

$$'0$
$[$&$
6

6
6
46

9
$$'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
Organization Unit
S_ORG_EXT, S_PARTY
Prospect
S_PRSP_CONTACT
47
48
CALL LIST
created from
for
CALL LIST D&B

ORGANIZATION
ORGANIZATION UNIT
classified within
classifier of
composed of
of
global parent of
domestic parent of
parent of
equivalent to
INDUSTRY
ORGANIZATION INDUSTRY CLASSIFICATION
Title : Dun & Bradstreet Integration

member in
source of
global child of
domestic child of
child of
equivalent to
direct
child of
classification for
specifier of
OTHER
PROSPECT
PROSPECT
affiliated with
domestic
child of
domestic
parent of
global
parent of
primarily a
banking
customer of
D&B CONTACT
composed of
classified
within
D&B ORGANIZATION
direct
parent of
classifier of
bearer of
D&B STANDARD INDUSTRY

CLASSIFICATION
classification for
specifier of
for
D&B MANAGEMENT
RESPONSIBILITY TYPE
assigned to
of
D&B CONTACT RESPONSIBILITY
global child
of
a bank for
D&B ORGANIZATION INDUSTRY CLASSIFICATION

Figure 17. Dun & Bradstreet Integration
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
MEASUREMENT
S_EMP_PERF_MEAS
GROUP, ACCESS GROUP
S_PARTY
KEY PERFORMANCE INDICATOR

DEFINITION
S_KPI, S_KPI_AGRP
KPI VALUE FOR EMPLOYEE
S_EMP_KPI
KPI VALUE FOR OBJECTIVE
S_PERF_MITM_KPI
KPI VALUE HISTORY
S_EMPKPI_SNPSHT
ORGANIZATION UNIT, DIVISION
S_ORG_EXT
PERFORMANCE MEASUREMENT ITEM
S_PERF_MEAS_ITM
PERSON, EMPLOYEE/AGENT, OTHER

PERSON
S_CONTACT, S_EMP_PER, S_USER
49

Figure 18. Employee KPI

Title : Employee KPI
KPI VALUE
FOR
OBJECTIVE
PERFORMANCE
MEASUREMENT
ITEM
contain value for

measured in
contain value for
objective for
KPI VALUE FOR EMPLOYEE

user of
defined for
KPI VALUE HISTORY

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

measurement
of
approved by
accessed by
approver of
parent visibility node of

PARTY
child visibility node of
ORGANIZATION UNIT
GROUP
have access to
PERSON
has
have
subject of
EMPLOYEE / AGENT
DIVISION
ACCESS GROUP
OTHER PERSON
50
OTHER
PARTY
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
Employee
Expense Item
S_EXP_ITEM
Expense Item Type
S_EXP_ITM_TYPE
Expense Report
S_EXP_RPT
Expense Report Approval
S_EXP_RPT_APPR
Opportunity
S_OPTY
Organization Unit
S_ORG_EXT, S_PARTY
Party
S_PARTY
Person
S_CONTACT, S_PARTY
Project
S_PROJ
51

Figure 19. Expense Reports

Title : Expense Reports
EXPENSE ITEM
incurred for
PROJECT
subject of
incurred for
OPPORTUNITY
for
ACTIVITY
subject of
source of
incurred during
for
source of
subject of
EXPENSE ITEM TYPE
of
classification for
made up of
PARTY
part of
incurred for
ORGANIZATION UNIT
subject of
involver of
involved in
PERSON
OTHER
ORGANIZATION UNIT
incurred by
incurrer of
EMPLOYEE /
AGENT
OTHER
PERSON
EXPENSE REPORT
APPROVAL
by
reported on
provider of
of
composed
of
subject of
INTERNAL
ORGANIZATION /
PARTNER
reported for
EXPENSE REPORT
the reporting period for
PERIOD
reported by
accounting approval by
reporter of
approver of
charged to
charged with
52
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
Address

Asset
S_ASSET
Business Unit
Inventory Location
S_INVLOC
Inventory Transaction
S_INV_TXN
Organization Unit
S_ORG_EXT, S_PARTY
Party
S_PARTY
Person
S_CONTACT, S_PARTY
Position
S_POSTN, S_PARTY
Product Inventory
S_PROD_INV
Product Inventory Category
S_PROD_INV_CAT
Product Inventory Location
S_PROD_INVLOC
Product or Service
S_PROD_INT
53
54
currently in
inventory at

stored in
NON-SERIALIZABLE
PRODUCT
PRODUCT INTERNAL
PRODUCT OR SERVICE
is made into
a component of
an assembly of
PRODUCT
INVENTORY
CATEGORY
for
are counted via
located at
type of
INVENTORY
LOCATION TYPE
SERIALIZABLE
PRODUCT
of
at
composed of
for
INTERNAL/PARTNER
ORGANIZATION
ORGANIZATION UNIT
composed
of
OTHER
ORGANIZATION
located at
supplier
of
for
from
visible
to
part of
composed of
sub-org
of
BUSINESS
UNIT
accessor of
responsibility
of
OTHER INVENTORY
LOCATION
VIRTUAL INVENTORY
LOCATION
made up
responsible
for
located
at
replenished
ADDRESS
for
accessed by
responsibility of
PERSONAL (TRUNK)
INVENTORY LOCATION
WAREHOUSE
INVENTORY LOCATION
replenishment
source for
INVENTORY
TRANSACTION TYPE
responsible responsible
for
for
POSITION
held by
for
replenished from
of
holder of
type of
affiliated
with
PERSON
for
stores
defines movement
from
NON-SERIALIZED
TRANSACTION
is affected by
counts product for
PRODUCT INVENTORY
LOCATION
type of
for
SERIALIZED
TRANSACTION
INVENTORY TRANSACTION
defines
is affected movement to
by
participates in
PRODUCT INVENTORY
status of
is a
ASSET (PRODUCT
INSTANCE)
Title : Field Service Inventory


Figure 20. Field Service Inventory

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
Address

Employee
Employee Exceptional Work Hours
S_EMP_EXCPT_HRS
Scheduler Cost Function
S_SCH_CSTFN
Scheduler Cost Function Variable
S_SCH_CSTFN_VAR
Scheduler Parameter
S_SCH_PARAM
Scheduler Parameter Set
S_SCH_PARAM_SET
Scheduler Rule
S_SCH_RULE
Scheduler Rule Node
S_SCH_RULENODE
Scheduler Rule Set
S_SCH_RLST
Scheduler Time Map
S_SCH_TMMAP
Scheduler Time Map Duration
S_SCH_TMMAP_DUR
Service Activity
S_EVT_ACT
Service Region
S_SRV_REGN
Service Request
S_SRV_REQ
Timezone
S_TIMEZONE
Work Shift
S_SCHED_CAL
Work Shift Exception
S_EXCPT_CAL
Work Shift Exception Hour
S_EXCPT_CAL_HRS
Work Shift Hour
S_SCHED_CAL_HRS
Zipcode
S_ZIPCODE
55

Figure 21.
Title : Field Service Scheduler

above
under
within
for
made up of
subject of
SERVICE
ACTIVITY
SERVICE
REQUEST
for
SCHEDULER
RULE SET
SCHEDULER RULE
SCHEDULER RULE NODE
user of
SERVICE REGION
in
used by
for
subject of
SCHEDULER COST
FUNCTION
VARIABLE
assigned to
owner of
assigned to
defined for
EMPLOYEE
assigned with
subject of
user of
used by
EMPLOYEE
EXCEPTIONAL
WORK HOURS
for
SCHEDULER COST
FUNCTION
at
with
for
starting
SCHEDULER TIME
MAP DURATION
in
for
for
WORK SHIFT
EXCEPTION HOUR
ending at
defined for
subject of
ADDRESS
user of
used by
defined for
in
in
for
in
SCHEDULER
TIME MAP
user of
for
defined for
WORK SHIFT HOUR
defined by
with
defined by
with
in
within
for
WORK SHIFT EXCEPTION
56
SCHEDULER
PARAMETER
WORK SHIFT
for
for
TIMEZONE
for
for
ZIPCODE
made up of
used by
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
Agreement
S_DOC_AGREE
Forecast
S_FCST
Forecast Item Detail
S_FCST_ITEM_DTL
Forecast Period
S_FCSTSER_DATE
Forecast Series
S_FCSTSER
Forecasted Item
S_FCST_ITEM
Marketing Event
S_SRC
Opportunity
S_OPTY
Organization Unit
S_ORG_EXT, S_PARTY
Person
S_CONTACT, S_PARTY
Position
S_POSTN, S_PARTY
Product Line
S_PROD_LN
Product or Service
S_PROD_INT
Project
S_PROJ
Quote
S_DOC_QUOTE
Revenue Item
S_REVN
Service Request
S_SRV_REQ
57
58
OPPORTUNITY
attributed to
for
for
for
PROJECT
attributed to
AGREEMENT
attributed to
for
REVENUE ITEM
summary of
SERVICE REQUEST
attributed to
MARKETING
EVENT OR
ACTIVITY
attributed to
for
FORECASTED ITEM
member of
Title : Forecasts
QUOTE
FORECAST SERIES
aggregated by
applicable to
a report to
governed by
INTERNAL
ORGANIZATION
UNIT
OTHER
ORGANIZATION
UNIT
defined for
AGGREGATE
DIMENSION
attributed to
for
manager of
POSITION
for
owner of
submitted by
submitter of
subject of
original forecast of
subject of
valid period for
FORECAST PERIOD
period for
participant of
owned by
submitted for
manager's forecast of
FORECAST
subordinator's forecast of
ORGANIZATION UNIT
partner attributed to
OTHER PERSON
EMPLOYEE /
AGENT
PERSON
account attributed to
for
for
author of
defined by
for
member of
PRODUCT OR
SERVICE
PRODUCT LINE
for
for
FORECAST ITEM DETAIL
subject of
attributed to
attributed to
for
forecasted via
generated for

Figure 22. Forecasts
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
Fund Allocation
S_MDF_ALLOC
General Fund
S_MDF
S_PROD_INT
Market Segment
S_MKT_SEG
S_MDF
S_SRC
MDF Snapshot
S_MDF_PERIOD
MDF Transaction
S_MDF_TXN
Partner Event Activity
S_SRC
Partner Program
S_PRTNR_PROG
Partner Program Application
S_PRTNRPRG_APPL
Partner Specific Fund
S_MDF
Position
S_POSTN
59
60
for
has
MDF
SNAPSHOT
for
PARTNER
PROGRAM
belongs to
for
for
MARKET
SEGMENT
belongs to
PARTNER
for
PROGRAM
APPLICATION
belongs to
POSITION
has
to
to
GENERAL
FUND
PARTNER
SPECIFIC
FUND
for promotion of
for promotion of
for
funded through
DEBIT
defined for
subject of
belongs to
subject of
part of
CREDIT
OTHER PAYMENT
.
MDF TRANSACTION
EVENT ITEM
OTHER
ACCOUNT
target of
belongs
for
has
CLAIM
PAYMENT
subject of
target of
PARTNER
ACCOUNT
MARKETING
DEVELOPMENT
FUND
designated to
subject of
of
FUND ALLOCATION
Title : High Tech Marketing Development Fund

earned by
part of
subject of
earner of
earned by
has
CLAIM ITEM
PRODUCT
LINE
for
subject of
part of
hierarchy child of
hierarchy parent of
INTERNAL PRODUCT OR
SERVICE
of
OTHER MARKETING
EVENT OR ACTIVITY
promoted via
composed of
earner of
basis for
PARTNER EVENT
ACTIVITY
MARKETING EVENT OR
ACTIVITY
has
available to
defined for
recipient of
part of
made of

Figure 23. High Tech Marketing Development Fund

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
61

Figure 24.
Title : In Memory Next Best Action

Author : Oracle Confidential
REQUEST PARAMETER
REQUEST
carry
sent with
for
has
RECOMMENDATION TYPE
RECOMMENDATION
for
refer to
may have
against
RESPONSE
RESPONSE TYPE
for
belongs to
can have
for
ACTION PARAMETER
ACTION
may have
belongs to
62
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
Address

Agreement
S_DOC_AGREE
Agreement Entitlement
S_ENTLMNT
Agreement Line Item
S_AGREE_ITEM
Asset
S_ASSET
Auction Item
S_AUC_ITEM
Expense Item
S_EXP_ITEM
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
Payment
S_SRC_PAYMENT
Payment Term
S_PAYMENT_TERM
Product or Service
S_PROD_INT
Project Item
S_PROJITEM
Project Team Role
S_PROJ_RSRC
Service Request
S_SRV_REQ
63

Table 26.
Invoiceable Charges ERD Entities and Tables
Entity
Table
Shipment
S_SHIPMENT
Time Sheet Item
S_TMSHT_ITEM
64
for
INVOICE
made up of
part of
billed to
for
for
ADDRESS
made for
fulfilled by
PAYMENT
part of
composed of
invoiced into
INVOICE ITEM for

INVOICEABLE
subject of
CHARGE
INVOICE ITEM
subject of
for
subject of
for
ACCOUNT
contact of
OTHER
ORGANIZATION
UNIT
charged via
PARTY
for
ORGANIZATION UNIT
billed to
located at
for
billed to
INVOICEABLE CHARGE
charged via
based on
for
for
PERSON
for
for
SHIPMENT
charged via
ORDER
PRODUCT OR
SERVICE
object for
composed of
part of
composed of
ordered on
part of
of
charged via
of
ORDER
PART
MOVEMENT
PAYMENT TERM
ORDER LINE
ITEM
fulfilled by
PROJECT
TEAM ROLE
primary billing contact of
OTHER
PARTY
billed to
for
charged via
for
PROJECT
ITEM
ACTIVITY
PART
MOVEMENT
AGREEMENT
AUCTION ITEM
made up of
part of
charged via
AGREEMENT
LINE ITEM
basis for
based on
made up of
part of
SERVICE
REQUEST
EXPENSE ITEM
charged via
charged via
AGREEMENT
ENTITLEMENT
PART MOVEMENT
charged via
ASSET
charged via
charged via
ACTIVITY
basis of
charged via
TIME SHEET ITEM
PART REPAIR
charged via
FINANCIAL ACCOUNT
charged via
charged via
charged via
charged via
for
for
for
for
for
for
based on
for
for
for
for
for
for
Figure 25.
INVOICE ITEM
DETAIL
INVOICE ITEM
RECONCILIATION ENTRY
Title : Invoiceable Charges


Invoiceable Charges
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
Agreement
S_DOC_AGREE
Expense
S_EXP_ITEM
Invoice
S_INVOICE
Invoice Attachment
S_INVOICE_ATT
Invoice Item
S_INVOICE_ITEM
Order
S_ORDER
Order Item
S_ORDER_ITEM
Part Movement
S_ORDPART_MVMT
Part Repair
S_PART_RPR
Payment
S_SRC_PAYMENT
Period
S_PERIOD
Product
S_PROD_INT
Project
S_PROJ
Service Request
S_SRV_REQ
Shipment
S_SHIPMENT
66
composed
of
for
for
for
for
for
for
for
for
for
for
for
billed via
OTHER INVOICE
INVOICE ITEM
part of
INVOICE
Title : Invoices
billed via
billed via
PRODUCT
billed via
fulfillment for
fulfilled by
part of
billed via
reason for
generated
for
object for
SHIPPED PART
for
billed via
part of
ORDER
composed
of
composed of
PART MOVEMENT
billed via
reason for
PART REPAIR
reason for
generated
for
PERIOD
generated
for
PAYABLE INVOICE
fulfilled by
made for
PAYMENT
SERVICE REQUEST
reason for
generated
for
ACTIVITY
ordered on
of
ORDER ITEM
EXPENSE
billed via
detail for
for
reason for
generated
for
AGREEMENT
UNIT OF
LABOR
billed via
billed via
billed via
PROJECT
reason for
generated for
RECEIVABLE INVOICE
source for
for
INVOICE ATTACHMENT
for
based on
SHIPMENT
reason for
PAYMENT
TERM
generated
for

Figure 26. Invoices
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
68
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
69
70
subject
of
subject
of
subject of
generated
for
generated
for
ACTIVITY
RESPONSE
LEAD NOTE
attached
to
LEAD
considered
on
consideration
of
for
created
via
imports
discovered
from
generated
by
generates
generated
from
generates
for
turns
into
for
creates
PROSPECT
CONTACT
primary for
OPPORTUNITY
generated
from
DEMAND
CREATION
PROGRAM
CAMPAIGN
CONTACT
source
for
LEAD
SOURCE
MARKETING
IMPORT TASK
primary for
PRODUCT
Title : Lead Management

Author : Oracle ,Confidential
for
creates
CONTACT
responsible
for
belongs
to
owns
involved
in
belongs
to
assigned
to
reponsible
for
referred
by
refers
PARTNER
ASSIGNED
EXTERNAL
INTERNAL
OTHER ORGANIZATION
involver of
ACCOUNT
owns
BUSINESS
UNIT
under
POSITION
PARTY

Figure 27. Lead Management
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
S_MDF
Marketing Plan
S_SRC
Marketing Fund
S_MDF
Marketing Tactics
S_SRC
Tactics Expense
S_SRC_COST
Purchase Request Line Item
S_ORDER_ITEM
71
72

14
.&%$%%&$

14

13
14
"<$
%

1
& 9%7&%

& 9%
7&%'$
"

$>
14
%8$%

1
2

2
1
!& '$
14
!
2

"<$
!>'"$*&$!
!&
14
$!&%+
14
%$

"<$

*&$!

14
1 13

13
"<$
'$
14
13
.&!
7&%
"5.?
Oracle

$
1

Figure 28. Marketing Budget Request
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
S_CALL_LST
Call List Member
S_CALL_LST_CON
Campaign Call List
S_CAMP_CALL_LST
Campaign Contact
S_CAMP_CON
Fulfillment Recipient
S_FUL_RECIP
Fulfillment Request
S_EVT_FUL_REQ
Fulfillment Request Item
S_FUL_REQ_ITEM
Literature Item
S_LIT
Marketing Event
S_SRC
Opportunity
S_OPTY
Opportunity Contact
S_OPTY_CON
Order
S_ORDER
Organization Unit
S_ORG_EXT, S_PARTY
Person
S_CONTACT, S_PARTY
Position
S_POSTN, S_PARTY
Prospective Contact
S_PRSP_CONTACT
Response
S_COMMUNICATION
Territory
S_ASGN_GRP
73
74
OTHER PERSON
recipient of
PERSON
POSITION
for
for
subject of
made up
of
ORDER
composed of
for
initiator of
originator of
originator of
originator of
associated with
generated by
made
of
of
part of
used in
subject
of
PURCHASED
LIST
CAMPAIGN CALL LIST
for
user of
MARKETING
SEGMENT
CALL LIST
in
of
of
of
subject
of
of
subject of
subject
of
of
subject of
CALL LIST
MEMBER
primarily from
source of
made up of
targeted at
PROSPECTIVE CONTACT
a parent
to
a report to
OTHER
MARKETING
EVENT OR
ACTIVITY
responsibility of
MARKETING CAMPAIGN
introduction to
for
CAMPAIGN CONTACT
responsible for
made up of
part of
managed within
subject of
promoted via
subject of
conducted as
focus of
relevant to
part of
RESPONSE
generated by
ORGANIZATION UNIT
assigned to
TERRITORY
NOTE
LITERATURE
ITEM
FULFILLMENT
REQUEST
initiated by
generated by
assigned to sell in
assigned to
assigned to
role played by
assigned to
CAMPAIGN
TEAM MEMBER
of
for
OPPORTUNITY CONTACT
OPPORTUNITY
targeted at
part of
of
part of
FULFILLMENT
REQUEST ITEM
addressed to
FULFILLMENT
RECIPIENT
ACTIVITY
Title : Marketing Campaign

Author :Oracle, Confidential

Figure 29. Marketing Campaign
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
S_SRC
Opportunity
S_OPTY
Order
S_ORDER
Organization Unit, Other Organization Unit
S_ORG_EXT, S_PARTY
Partner Organization
S_BU, S_PARTY
Party, Other Party
S_PARTY
Quote
S_DOC_QUOTE
Response
S_COMMUNICATION
75

Figure 30. Marketing Collaboration

Title : Marketing Collaboration
PARTY
ORGANIZATION UNIT
responsible for
ORDER
responsibility of
collaborating on
PARTNER
ORGANIZATION
INTERNAL /
PARTNER
ORGANIZATION
item of collaboration for

generated from
based on
basis for
responsible for
QUOTE
responsibility of
collaborating on

generated from
lead to
responsible for
OPPORTUNITY
responsibility of
collaborating on

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

responsibility of
collaborating on
responsible for
OTHER ORGANIZATION UNIT
OTHER PARTY
76
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
Literature Item
S_LIT
Organization Unit
S_ORG_EXT, S_PARTY
Product Comparison
S_PROD_CMP
Product Detail
S_PROD_SPEC
Product External
S_PROD_EXT
Product Internal
S_PROD_INT
Product Literature
S_PROD_LIT
77
78
for
characterized by
PRODUCT
DETAIL
INTERNAL PRODUCT
OR SERVICE
of
to
produced by
subject of
COMPETITIVE COMPANY METRIC
INTERNAL / PARTNER
ORGANIZATION UNIT
reference to
usage of
about
subject of subject of
usage of
COMPANY
LITERATURE
for
COMPETITIVE
COMPANY
FEATURE
classification for
EXTERNAL ORGANIZATION UNIT
LITERATURE ITEM
reference to
about
PRODUCT
LITERATURE
ORGANIZATION UNIT
vendor of
EXTERNAL
PRODUCT
competitor of
PRODUCT COMPARISON
competitor of
subject of
COMPETITIVE PRODUCT METRIC
COMPETITIVE METRIC
classification for
of
relevant to
DECISION
ISSUE
PRODUCT OR SERVICE
subject of
of
COMPETITIVE
PRODUCT
FEATURE
Title : Marketing Encyclopedia

of

Figure 31. Marketing Encyclopedia
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
Call List
S_CALL_LST
Campaign Contact
S_CAMP_CON
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
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
Response
S_COMMUNICATION
79
80
for
associated
with
MARKETING STAGE
MARKETING PROGRAM
vehicle
promoted
MARKETING
EVENT OR
ACTIVITY
source of
LEAD SOURCE
for
of
from
target of
subject of
EVENT
TRIGGER
related by
for
subject of
for
EVENT
TRIGGER
MAPPING
associated with
EVENT TRIGGER HISTORY
subject of
of
created for
RESPONSE
CAMPAIGN CONTACT
Title : Marketing Event-Driven Dialogue

OFFER
belongs to
subject of
for
MARKETING
STAGE WAIT
for
part of
of
of
subject of
belongs to
for
subject of
made up
belongs to
MARKETING
CAMPAIGN
subject of
MARKETING
PROGRAM ACTION
consists of
ACTION LIST
attached
CALL LIST
PROSPECT
CONTACT
OTHER PERSON
PERSON
POSITION
subject of
subject of
PARTY

Figure 32. Marketing Event Driven Dialogue
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
Literature Item
S_LIT
Location Room
S_EVTLOC_ROOM
S_SRC
Order
S_ORDER
Organization Unit
S_ORG_EXT, S_PARTY
Parent Event
S_SRC_EVT, S_SRC
Position
S_POSTN, S_PARTY
Price List
S_PRI_LST
Product or Service
S_PROD_INT
Quote
S_DOC_QUOTE
Room Avail Equipment
S_EVTLOC_RM_EQP
Travel Participant
S_EVT_TRVL_PER
81

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
82
for
VENUE
EVENT LOCATION
used by
use
ORGANIZATION
UNIT
parent company of
of
subject of
location of
OTHER LOC
supplier of
in
LOCATION ROOM
held at
EVENT
SESSION
location of
available in
ROOM EQUIPMENT
AVAILABILITY
OTHER MARKETING
EVENT OR ACTIVITY
PRICE
LIST
auction
price list
for
uses
relevant to
have
for
inviter of
staffed by
created for
participate
have
EVENT PRODUCT
for
for
PERSON
OTHER
CONTRACT
QUOTE
ORDER
CONTRACT
subject of
composed of
OTHER PRODUCT OR
SERVICE
CONTRACT LINE ITEM
PRODUCT OR SERVICE
subject of
for
recipient of
CANCELLED
REGISTRANT
WAIT LIST
ATTENDEE
for
invited to
on staff for
reviewer of
classified as
TRAVEL
PARTICIPANT a member of
reviewer of
EVENT
REGISTRATION
ordered by
subject of
subject of
PARENT
EVENT
promoted via
LITERATURE
ITEM
responsible for
POSITION
incur
incurred by
composed of
for
responsibility of
EVENT
required by
EQUIPMENT
REQUIREMENT
incur
TRAVEL PLAN
associated with
serviced by
service
reviewed by
EVENT COST
incur
in need of
composed of
for
for
ACTIVITY
subject of
held at
for
subject of
reviewed by incurred by
for
for
VENDOR
REVIEW
subject of
offered by
VENDOR
SERVICE
provider of
VENUE
REVIEW
offered by
equipped with
EVENT VENUE
subject of
VENUE
SERVICE
provider of
VENUE
OFFER
offered at
belong to
provider of
offered by
VENDOR
OFFER
Figure 33.
EVENT VENDOR
Title : Marketing Event


Marketing Events
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
Call List
S_CALL_LST
S_MDF
Marketing Event Cost
S_SRC_COST
Marketing Event or Activity, Marketing Plan, Other Marketing Plan

or Activity
S_SRC
Marketing Goal
S_SRC_GOAL
Period
S_PERIOD
Planned Marketing Development Fund Allocation
S_MDF_ALLOC
Product or Service, Product Line, Other Product or Service
S_PROD_INT, S_PROD_LN
Product Promotion
S_PROD_INT_SRC
84
used for
for
defined for
valid in
reserved from
MARKETING
DEVELOPMENT
FUND
source of
defined for
GOAL
uses
BUDGET
REQUEST
defined for
PERIOD
part of
INVOICE
made up of
INVOICE ITEM
estimated for
valid in
PLANNED
attributed to
MARKETING
DEVELOPMENT
MARKETING
FUND ALLOC
Title : Marketing Plans

source of
created from
CALL LIST
FOR
belong to
type of
SUBJECT OF
valid in
user of
requirer of
created for
owner for
compose of
defined for the budget of
CAMPAIGN
CALL LIST
launched in
PRODUCT OR SERVICE
created for
incur
consists of
source of
created from
attributed to
PRODUCT
PROMOTION
promotion item for
basis of
defined for launch of
has
based on
MARKETING
EVENT COST
has
OTHER
MARKETING
EVENT OR
ACTIVITY
MARKETING
PLAN
MARKETING EVENT
OR ACTIVITY

Figure 34. Marketing Plans
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
Call List
S_CALL_LST
Campaign Allocation
S_CAMP_CALL_LST
Campaign Contact
S_CAMP_CON
Campaign Load
S_CAMP_LD_WAVE
Campaign Offer
S_SRC_OFFR
Campaign Wave
S_DD_CAMP_WAVE
Contact
S_CONTACT, S_PARTY
Contact Status
S_ SRCDCP_CONSTA
Deal
S_DEAL
Filter
S_DD_FILTER
Filter Clause
S_DD_FILTER_DTL
Load Wave
S_CAMP_LD_WAVE
86
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
Response
S_COMMUNICATION
87
88
**
2

6
1

2

.&%$%%&$

14

"
$
;>
!& %>

13
"
$'%
!%.&$
'

"
$**
**"! <

3
"
$'!

'!;>

"
$ $
%
"$
& 9%!
'%
'''%

"<$

%

"<$

'$

"<$

"
+
14
%& !
*"

%& !
'"$
"5

Oracle

$[$
&$
% >
$
9
%$
%$
%$
14

1 2

14
2
14

14
1
14
2
2
"<$

>$

"<$
"
$
'!%&
14

"
%
"$


Figure 35. Marketing Program

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
Event Location
S_EVTLOC
Region
S_REGION
Material Fulfillment Request
S_EVT_FUL_REQ
Material Fulfillment Item
S_FUL_REQ_ITEM
Mat Fulfill Request Attachment
S_NOTE_FUL_REQ
Vendor Bidding
S_FUL_REQ_BID
Vendor Bidding Item
S_FR_BID_LITM
External Organization
S_ORG_EXT
Offer Media Package
S_DMND_CRTN_PRG
Offer Document
S_OFFR_CBAST
Lead Source
S_SRC
Lead Source Document
S_SRC_CBAST
Project
S_PROJ
Project Document
S_PROJ_CBAST
89
90

**"!
<

2
**
! &"$

2

'!%&

2

"*&'*''
7&%
9"$
=

2
=
! &"$

3

14

"'
*&'*''"$"
14
"'*&'*IL'"$7&%

13
'!%& ! &"$
1
13

>$!.!!$
2

>$!.!!$
"

8$'

$[$

33

** "
$
1
>$
' $

6
3

"<$
"'

$
2
1
"'$>$+.+' $
""! "
Oracle

Figure 36. Marketing Resource Management: Document
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
Address

Agreement
S_DOC_AGREE
Contact
S_CONTACT, S_PARTY
Employee
Event
S_EVT_ACT
External Organization Unit
S_ORG_EXT, S_PARTY
Issue
S_ISS
Opportunity
S_OPTY
Opportunity Relationship
S_OPTY_REL
Organization Unit
S_ORG_EXT, S_PARTY
Person
S_CONTACT, S_PARTY
Product
S_PROD_INT
Quote
S_DOC_QUOTE
Sales Stage
S_STG
Source
S_SRC
Territory
S_ASGN_GRP
91
92
driver of
OPPORTUNITY
for
classified in
for
part of
considered on
PRODUCT OR
SERVICE
consideration of
ADDRESS
source of
basis for
based on
ISSUE
relevant as
relevant to
subject to
within
subject to
made up of
TERRITORY
consideration on
relevance of
part of
affiliated with
part of
for
OPPORTUNITY
RELATIONSHIP
collection of
of
responsible for
owned by
performer of
performed by
subject of
targeted at
resource for
CORRESPONDENCE
EVENT ACTIVITY
AGREEMENT
composed of
owned by
located at
for
OPPORTUNITY ISSUE
subject of
for
QUOTE
SALES DOCUMENT
vendor of
a collection of
produced by
of
PRODUCT
STRUCTURE
made up of
SALES
STAGE
a parent to
OTHER ORGANIZATION UNIT
a report to
a component of
composed of
classification of
driven by
SALES
METHODOLOGY
initiator of
initiated by
involver of
a partner to
MARKETING EVENT OR
ACTIVITY
involved on
INTERNAL / PARTNER
ORGANIZATION UNIT
ORGANIZATION UNIT
in partnership with
Title : Opportunity Management

on
a report to
EMPLOYEE /
AGENT
manager of
involver of
OTHER
PERSON
PERSON
located at
for

Figure 37. Opportunity Management
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
Order Item
S_ORDER_ITEM
Product Promotion
S_PROD_INT
Product Promotion Item
S_PROM_ITEM
Product Promotion Operation
S_PROM_OPER
Quote Item
S_QUOTE_ITEM
93

Figure 38.
Order and PromotionOrder Life Cycle
Title : Order and Promotion

ORDER ITEM
for
uses
QUOTE ITEM
for
has
ASSET
has
uses
used by
PRODUCT PROMOTION ITEM
has
for
used by
PRODUCT PROMOTION
OPERATION
for
made up
has
defined for
PRODUCT
associated to
contain
associated to
has
associated to
PRODUCT PROMOTION
94
for
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
Account
S_ORG_EXT, S_PARTY
Invoice
S_INVOICE
Invoice Item
S_INVOICE_ITEM
Opportunity
S_OPTY
Opportunity Product
S_REVN
Order
S_ORDER
Order Item
S_ORDER_ITEM
Order Part Movement
S_ORDPART_MVMT
Product or Service
S_PROD_INT
Quote
S_DOC_QUOTE
Quote Item
S_QUOTE_ITEM
Shipment
S_SHIPMENT
95
96
target of
part of
for
lead to
PRODUCT OR SERVICE
of
has
ordered on
base item for
original item for
composed of
has
part of
part of
of
billed via
fulfilled by
for
billed via
for
composed of
has
target of
ORDER ITEM
original item for
backup order for
has
created from
ORDER
taken for
composed of has
part of
composed of
for
lead to
receiver of
QUOTE ITEM
for
QUOTE
prepared for
quoted for purchase on
for
has
base item for
composed of
considered for purchase on
of
OPPORTUNITY
PRODUCT
for
lead to
lead to
consideration of purchase of
OPPORTUNITY
of
ACCOUNT
Title : Order Life Cycle

for
INVOICE ITEM
billed via
for
INVOICE
part of
of
from
ALLOCATION
RECEIPT
MVMT
SHIP
MVMT
preceded by followed by
OTHER PART
MOVEMENT
ORDER PART MOVEMENT

on
subject of
SHIPMENT
made up of
vehicle for fulfillment of
delivered by
a step toward the

fulfillment of
billed via
for
composed of
generated for
reason for
original order for
for
billed via

Figure 39. Order Life Cycle
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 Location
S_INVLOC
Inventory Transaction
S_INV_TXN
Inventory Transaction Type
S_INV_TXN_TYPE
Order
S_ORDER
Order Item
S_ORDER_ITEM
Order Type
S_ORDER_TYPE
Part Movement
S_ACTPART_MVMT, S_ORDPART_MVMT
Part Movement Type
S_PARTMVMT_TYPE
Party
S_PARTY, S_ORG_EXT, S_POSTN, S_CONTACT
Product
S_PROD_INT
97
98
ORDER
composed of
SALES ORDER
part of
composed of
part of
result of
OTHER ORDER
RMA
for
composed of
part of
for
for
proceded by
for
for
PARTY
primary contact for
of
source of
related to
ORGANIZATION UNIT
PERSON
POSITION
responsible for
destination of
ACTIVITY
subject of
for
ACTIVITY PART
MOVEMENT
to
source of
OTHER ORGANIZATION
OTHER
PARTY
from
OTHER PART
MOVEMENT
INTERNAL/PARTNER ORGANIZATION
INVENTORY LOCATION
related to
PART
MOVEMENT
TYPE
for
destination of
ORDER TYPE
responsible for
customer of
responsibility of
for
responsibility of
to
from
of
subject of
of
followed by
an instance of
moved on
PRODUCT
ASSET
made into
subject of
subject to
of
ORDER PART MOVEMENT
PART MOVEMENT
ORDER ITEM
fulfilled by
cause of
PURCHASE ORDER
SERVICE ORDER
INVENTORY
TRANSACTION
TYPE
for
of
INVENTORY
TRANSACTION
Title : Orders

Figure 40. Orders
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
99
100
"%%

9"%%

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

1
14

313
9+

1

9
$[O$
&$
$$'0$

$[$
3

$[$&$
313
.&%$%%$%^%$%.'

$[$
''.$
%$
+
3
.&%$%%$%^%$%.'
%$
.&%$%%$% $""".

''.$%9!%&
.&%$%%$% $
1

Oracle,

Figure 41. Partner Collaboration
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
101
102

2
''
% &$

2
' $
9"$
%$

6

' $
>'"

2
13
$
.&%$%%&$

$;'%

'
.'+'%

>''%

''% 9
"<
%
"$
!& '$
'&"
'$
&

$
""".%9
113
3 1
1

$
"' $

' $
7&%$
$%;

Oracle,
14

14
14
14
14
6
6

14
14

""
1

'

+

6
'
$
"
&

'

+
"
d

.%
"
!!$!
"
$
"

Figure 42. Partner Program Registration
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
Access Group
S_PARTY
Account
S_ORG_EXT, S_PARTY
Business Address

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

S_PARTY_REL (Siebel Industry Applications)
Organization Unit
S_ORG_EXT, S_PARTY
Party
S_PARTY
Party Relationship
S_PARTY_REL
Person
S_CONTACT, S_PARTY
Person Relationship
S_PARTY_REL or S_CONTACT_REL
Personal Address
S_ADDR_PER
Position
S_POSTN, S_PARTY
User List
S_PARTY
User Login
S_USER
103

Figure 43. Party Model

3"
Oracle
+'$%9
%$'$%9
!!%%
%$'!!%%
.&%$%%!!%%

$[$'$%9
9'$%9

6

+

&
%$

9&%9'!
"'+0

$

%%
&
&%'%

1
%$
9
&

1

$[$&$

9
%$
&$

9+
9
$[$&$

&%'
$
104
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
Address

Invoice
S_INVOICE
Order
S_ORDER
Organization Unit
S_ORG_EXT, S_PARTY
Party
S_PARTY
Payment
S_SRC_PAYMENT
Person
S_CONTACT, S_PARTY
Prepayment Balance
S_PREPAY_BAL
105

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
source of
OUTBOUND PAYMENT
PREPAYMENT
BALANCE
ADDRESS
addressed to
available to
used in
paid to
addressed to
for
located at
receiver of
PARTY
entitled to
PERSON
source for
receiver of
ORGANIZATION UNIT
OTHER
ORGANIZATION
106
ACCOUNT
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
Employee/Agent
Evaluation Script
S_CS_PATH, S_CS_PATH_SCPT
Evaluation Script Answer
S_CS_RUN, S_CS_RUN_ANSWR
Job Family
S_JOB_FAMILY
Organization Unit
S_ORG_EXT, S_PARTY
Party
S_PARTY
Performance Measurement Item
S_PERF_MEAS_ITM
Performance Review
S_EMP_PERF_MEAS
Period
S_PERIOD
Person
S_CONTACT, S_PARTY
Position
S_POSTN, S_PARTY
Review Component
S_PERF_RVW_CMP
Review Component Language
S_RVW_COMP_LANG
Review For Skill Item
S_PERF_CMPTNCY
107

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
108
14
14
13
313

9%$
2

3
!

3
1

.&%$%%&$

$[$&$

1

9
$[$
$$'0$

$[$

1
9>;+
! >;
1
"$$
+
>; "$$
>;
"$$
'$
&

=.*"'+

1
*"$
>;"

2
$$&'>;

!+

".
1
*"$
.= >
>;"

>;$

% '

>;"'

>;"' "$$
"$ +
26
>;*%<''"
14

>;
$
14
1
1
%$
14
2
"'+ &%"

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

"%&"$
3

142
*"$ "%&"$"
1 313
"'+

`!7{

>'&$%
"'+0
$
2

%$
+
6
213
?
|}~>'&$
2
>'&$%
$%;
26
Oracle

Figure 45. Performance Review
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
Account
S_ORG_EXT, S_PARTY
Activity
S_EVT_ACT
Contact
S_CONTACT, S_PARTY
Opportunity
S_OPTY
Organization Unit
S_ORG_EXT, S_PARTY
Personal Account
S_ASSET
Personal Account Contact
S_ASSET_CON
Personal Address
S_ADDR_PER
Product
S_PROD_INT
Service Request
S_SRV_REQ
110
Figure 46. Personal Account

Title : Personal Account
PERSONAL
ADDRESS
PERSONAL ACCOUNT CONTACT

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

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
S_CONTACT, S_PARTY
Contact Relationship
S_CONTACT_REL
Financial Need
S_FN_NEED
Financial Recommendation
S_FN_RCMD
Household/Account
Income (Expense)
S_FN_INCM_EXP
Income (Expense) Contact
S_FN_INCM_EXP_CON
Need Contact
S_FN_NEED_CON
Opportunity
S_OPTY
Organization Unit
S_ORG_EXT, S_PARTY
Product
S_PROD_INT
Product Instance
S_ASSET
Product Instance Contact
S_ASSET_CON
Received Product Instance
S_FN_RCMD_ASSET
Recommendation Contact
S_FN_RCMD_CON
112
source of
for
with
of
affects
made of
from
is addressed by
subject of
of
owned by
for
of
is a
subject of
is a
ASSET LIAB.
CONTACT
NEED CONTACT
PROD. INST.
CONTACT
on
has a
ASSET (LIABILITY)
with
source of
for
regarding
to understand
to review
reported during
to review
ACTIVITY
incurred by
FINANCIAL
REVIEW
PROCESS
part of
location of
reported during
INCOME (EXPENSE)
located at
has
CONTACT
is primarily incurred by
associated to
owns
has
primary subject of
jointly has
associated to
from
of
ORG MEMBER
member of
in
owns
made up of
because of
source of
with
with
with
source of
of
managed by
owned by
associated with
RECOMMENDATION CONTACT
of
of
of
of
vendor of
ORGANIZATION UNIT
associated with
owned by
owns
vendor of
ACTIVITY PROD.
INST.
with
subject of
recommended during
ADDRESSED NEED
of
of
subject of
addresses
communicated during
of
of
subject of
produced by
PRODUCT INSTANCE
made up of
part of
FINANCIAL NEED
part of
because of
RCIVD PROD. INST.
source of
OPPORTUNITY
consideration of
considered on
FINANCIAL RECOMMENDATION
for
subject of
PRODUCT OR SERVICE
Title : Personal Financial Review

INC. EXP.
CONTACT
involves
in
made up of
has
for
located at
to
ACTIVITY CONTACT
PERSONAL ADDRESS
of
with
has
has
of
CONTACT
RELATIONSHIP
member of
made up of
in
participates in
head of
defined for
HOUSEHOLD/
ACCOUNT
subject of

Figure 47. Personal Financial Review
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
S_VOD, S_VOD_VER
Object Class Extended Attribute
S_XA_ATTR
Price List
S_PRI_LST
Price List Item
S_PRI_LST_ITEM
Pricing Factor Item
S_PRIFCTR_ITM
Pricing Factor Item Attrib
S_PRIFCTITM_ATR
Pricing Matrix
S_PRI_MTRX
Pricing Matrix Attribute
S_PRI_ATTR
Pricing Matrix Item
S_PRI_MTRX_ITEM
Pricing Matrix Value
S_PRI_MTRX_VAL
Pricing Model
S_PRIMDL
Pricing Model Factor
S_PRIMDL_FCTR
Product Extended Attribute
S_PROD_INT_XA
Product or Service
S_PROD_INT
Product or Service Structure
S_PROD_ITEM
114
used by
PRICING MATRIX
made up of
part of
PRICING MATRIX
ITEM
configured via
based on
for
constraint for
made up of
for
PRICING MODEL
FACTOR
made up of
for
PRICING FACTOR ITEM
constrained by
of
for
basis of
the subject of
OBJECT CLASS
EXTENDED
ATTRIBUTE
have types
OBJECT CLASS
classification for
classified as
INTERNAL
PRODUCT OR
SERVICE
subclass of
described by
for
parent class of
described by
for
referenced by
subject of
a component of
an assembly of
based on
PRODUCT
EXTENDED
ATTRIBUTE
defined for
PRODUCT OR
SERVICE
STRUCTURE
PRICING FACTOR
ITEM ATTRIB
PRICING MODEL
of object class
used by
PRICING MATRIX
ATTRIBUTE
subject of
for
PRICING MATRIX
VALUE
PRICE LIST
an adjustment for
composed of
for
of
adjusted via
priced via
PRICE LIST
ITEM
for
COMPONENT PRICE
ADJUSTMENT
Title : Pricing

Figure 48. Pricing
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
S_VOD, S_VOD_VER
Object Class Extended Attribute
S_XA_ATTR
Opportunity
S_OPPTY
Price List
S_PRI_LST
Price List Item
S_PRI_LST_ITEM
Pricing Matrix
S_PRI_MTRX
Pricing Matrix Item
S_PRI_MTRX_ITEM
Product Extended Attribute
S_PROD_INT_XA
Product or Service
S_PROD_INT
Product or Service Structure
S_PROD_ITEM
Quote
S_DOC_QUOTE
Quote Item
S_QUOTE_ITEM
Quote Item Extended Attribute
S_QUOTE_ITEM_XA
Tier Price Value
S_VDISCNT_ITEM
Tier Pricing
S_VOL_DISCNT
116
Figure 49. Pricing Comparison

Title : Pricing Comparison
for
PRICE LIST ITEM
subject of
part of
COMPETITOR
ITEM
PRODUCT OR
SERVICE
composed of
QUOTE ITEM
EXTENDED
ATTRIBUTE
QUOTE ITEM
for
quotation for
described
by
subject of
comparison for
for
compared to
composed of
INTERNAL
ITEM
QUOTE
OPPORTUNITY
COMPETITOR
COMPARISON
for
subject
of
priced via
priced via
for
for
PRODUCT OR
SERVICE
STRUCTURE
used by
composed of
PRICE LIST
of
INTERNAL PRICE
LIST
COMPETITOR
PRICE LIST
assembly
of
component
of
PRODUCT
EXTENDED
ATTRIBUTE
TIER PRICE VALUE
for
described by
subject of
for
based on
classified as
TIER PRICING
subclass of
basis of
subject of
for
OBJECT CLASS
EXTENDED
ATTRIBUTE
PRICING MATRIX ITEM
used by
classification
for
OBJECT CLASS
for
described
by
based on
for
PRICING MATRIX
parent class of
for
have types
of
117

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
118
has
has
PRODUCT PROMOTION
has
PRODUCT
define for
contain
ADJUSTMENT
GROUP
has
define for
PRODUCT
PROMOTION TERM
DESCRIPTION
PRODUCT PROMOTION
TERM
define for
PRODUCT PROMOTION
PRICING MATRIX RULE for
define for
associate to
root of
define for
child of
contain
made up
has
child of
define for

ATTRIBUTE
has

ATTRIBUTE VALUE
has
define for
uses
has
defined for
PRODUCT
PROMOTION
OPERATION
has
associated
to
PRODUCT PROMOTION
OPERATION COMPONENT
uses
parent of
applicable
to
applies
used by
used by
associate by
CONDITIONAL
CHARGE
PRORATA PLAN
Figure 50.
PRODUCT PROMOTION
CHARGE
Title : Product Promotion


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
Employee/Agent
Organization Unit
S_ORG_EXT, S_PARTY
Product or Service
S_PROD_INT, S_PROD_EXT
Product Quality Item
S_PROD_DEFECT
Project
S_PROJ
Project Item
S_PROJITEM
Resolution Item
S_RESITEM
Service Request
S_SRV_REQ
120
handled via
INTERNAL PRODUCT VERSION
INTERNAL PRODUCT OR SERVICE
actual fix for
OTHER PERSON
produced in
version of
EXTERNAL PRODUCT
part of
primarily by
reported by
relation
of
owner of
owned by
primary of
owner of
owned by
reported via
solution to
resolved by
defined for
INTERNAL PRODUCT
OTHER ACTIVITY
made up of
OTHER INTERNAL PRODUCT

OR SERVICE
an assembly of
owner of
owned by
a component of
OTHER
ORGANIZATION
UNIT
INTERNAL /
PARTNER
ORGANIZATION
UNIT
ORGANIZATION UNIT
caused by
part of
part of
reporter of
reported by
SERVICE REQUEST
made up of
resolved by
solution to
SERVICE REQUEST ACTIVITY
RESOLUTION ITEM
QUALITY ENHANCEMENT
ACTIVITY
ACTIVITY
EMPLOYEE / AGENT
fixed via
PRODUCT
RELEASE
PROJECT
OTHER
PROJECTS
PROJECT
PERSON
reporter of
in environment of
actually fixed in
reported for planned to

be fixed in
related to
based on
includes
belong to
PRODUCT PATCH /
ENHANCEMENT
REQUEST
basis for
REQUIRED
FEATURE
OTHER PRODUCT QUALITY ITEM
PRODUCT DEFECT
exhibition of
PRODUCT QUALITY ITEM
defined for
QA TEST
PROJECT ITEM
PRODUCT OR SERVICE
target
afflicted
fix for
with
duplicate
of
duplicated
as
observed for
DEFECT
SYMPTOM
Title : Product Quality Tracking


Figure 51. Product Quality Tracking
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 or Service
S_PROD_INT
Product Recommendation
S_PROD_RECMNDTN
122
PRODUCT
OFFER
RESPONSE
ACTION
PARAMETER
for
for
has
parameter for
subject of
for
refer to
has
upgrade
product for
PRODUCT
OFFER
RESPONSE
PRODUCT
OR
SERVICE
PRODUCT
MESSAGE
VARIABLE
user of
PRODUCT
root product for
OFFER
user of
RESPONSE
ACTION
component for
offer
recommendation for
recommended by
COMMUNICATION
actual
response for
displayed by
have
user of
PRODUCT
RECOMMENDATION
Title : Product Recommendation and Offer

for
user of
has
for base
product
composed
of
part of
user of
have
PRODUCT
MESSAGE
RESPONSE
for
PRODUCT
MESSAGE
PRODUCT OFFER
used by
PRODUCT
LINE
template for
defined for

Figure 52. Product Recommendation and Offer
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
Catalog Category
S_CTLG_CAT
Class Attribute
S_XA_ATTR
Class of Product or Service
S_VOD, S_VOD_VER
Language
S_LANG
Price List
S_PRI_LST
Price List Item
S_PRI_LST_ITEM
Product Assembly Port
S_PROD_ITEM
Product Line
S_PROD_LN
Product or Service
S_PROD_INT or S_PROD_EXT
Product or Service Attribute
S_PROD_INT_XA
Product Structure
S_PROD_ITEM, S_PROD_REL
Product User Defined Attribute
S_PROD_USRDEFATR
Vendor
S_ORG_EXT, S_PARTY
124
CATALOG
made up of
for
has
EXTERNAL PRODUCT OR SERVICE
of
part of
part of
a
collection
of
described via
PRODUCT
LINE
composed of
for
grouped
by
constrained by
a
component
of
for
translated into
translation for
PRODUCT ASSEMBLY PORT
PRODUCT
STRUCTURE
valid for
translation for
an assembly
of
translated into
categorized in
parent to
part of
child of
translation for
CATALOG
CATEGORY
translated into
PRODUCT OR SERVICE
for
PRODUCT
USER
DEFINED
ATTRIBUTE
LANGUAGE
Title : Products or Services

for
subject of
subject of
PRICE
LIST
composed of
of
PRICE LIST ITEM
defined for
of
translated into
of
translated into
translation for
VENDOR
a report to
a parent to
CLASS OF PRODUCT OR
SERVICE
producer of
produced by
classified in
a classification for
subject of
CLASS ATTRIBUTE
basis for
based on
PRODUCT OR SERVICE
ATTRIBUTE
translation for

Figure 53. Products or Services
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
Address

Billing Rate List
S_PRI_LST
Employee/Agent
Internal/Partner Organization
S_ORG_EXT, S_PARTY
Invoice
S_INVOICE
Lead Source
S_SRC
Opportunity
S_OPTY
Organization Unit
S_ORG_EXT, S_PARTY
Person
S_CONTACT, S_PARTY
Position
S_POSTN, S_PARTY
Potential Project Resource
S_PROJ_PTL_RSRC
Project
S_PROJ
Project Contact
S_PROJ_CON
Project Issue
S_PROJ_ISS
Project Team Role
S_PROJ_RSRC
Skill
S_PROJRSRC_SKL
126
to track work on
the outcome of
for
assigned to
for
for
of
for
sent to
accessible to
responsible for
a partner for
responsibility of
located at
for
billed for
composed of
EMPLOYEE /
AGENT
OTHER
PERSON
INTERNAL/PARTNER
ORGANIZATION
ORGANIZATION UNIT
billed in
involved in
the client of
ADDRESS
for
of
for
filled by
PERSON
assigned to fill
BILLING RATE
LIST
defined as
subcontracted to
for
for
required by
located at
billed by
billed for
INVOICE
PROJECT CONTACT
targeted at
subject of
because of
source of
LEAD
SOURCE
requirer of
subject of
requirer of
POTENTIAL PROJECT
RESOURCE
defined for
PROJECT TEAM ROLE
assigned to
PROJECT ISSUE
subject of
subject of
PROFESSIONAL SERVICE PROJECT
requirer of
subject of
source of
OPPORTUNITY
subject of
for the resolution of
defined by
ACTIVITY
required by
SKILL
Title : Professional Services

accessor of
OTHER
ORGANIZATION
UNIT
employed by
SERVICE
BILLING
POSITION
TYPE
POSITION
billed as
billing type for
held by
occupant of
billing type for
billed as
billed via

Figure 54. Professional Services
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
Order Item
S_ORDER_ITEM
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
128
Table 56.
Promotion Group ERD Entities and Tables
Entity
Table
Promotion Group Term Description
S_PROD_TRM_DESC
Quote Item
S_QUOTE_ITEM
129
130
has
has
has
user of
defined
for
has
related
to
has
has
defined for
for for
has
ADJUSTMENT
GROUP
PROMOTION GROUP
has
has
defined for
COMMUNICATION
TEMPLATE
used by
defined for
PROMOTION GROUP
NOTIFICATION
defined for
PRODUCT MEMBERSHIP COMPATIBILITY
PROMOTION GROUP
MEMBER
has
PRODUCT
for
PROMOTION CONFIGURATION ITEM
has
for
has
for
has
has
associated to
for
has
for
has
for
has
notify
associated
to
for
has
for
has
contains
has
defined for
CONDITIONAL
CHARGE
PRORATA
PLAN
has
defined for
PROMOTION
GROUP TERM
DESCRIPTION
associate
by
associate
to
used by
PROMOTION
GROUP
CHARGE
made up of
uses
related to
PROMOTION
GROUP ITEM
owned by
owner of
notified by
ACCOUNT
owner of
ORDER ITEM
owned by
has
associated
to
for
QUOTE
ITEM
ASSET
defined for
belongs to
defined
for
PROMOTION
GROUP
ACCESS
applies to
PRODUCT COMPATIBILITY MATRIX
Figure 55.
for
PROMOTION GROUP
PRICING MATRIX RULE
Title : Product Promotion Group


Promotion Group
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
S_DOC_AGREE
Agreement Item
S_AGREE_ITEM
Invoice
S_INVOICE
Invoice Item
S_INVC_ITEM
Marketing Event
S_SRC
Opportunity
S_OPTY
Organization Unit
S_ORG_EXT, S_PARTY
Person
S_CONTACT, S_PARTY
Position
S_POSTN, S_PARTY
Product Line
S_PROD_LN
Product or Service
S_PROD_INT
Project
S_PROJ
Revenue Item
S_REVN
Revenue Template
S_REVN_TMPL
Revenue Template Item
S_REVN_TMPL_ITM
Service Request
S_SRV_REQ
131
132
detailed item of
REVENUE ITEM
revenue plan for
Title : Revenue

subject of
part of
REVENUE TEMPLATE
ITEM
details of
consist of
template for
part of
subject of
attributed to
subject of
made up of
subject of
attributed to
attributed to
attributed to
REVENUE TEMPLATE
PRODUCT OR SERVICE
OPPORTUNITY
AGREEMENT
INVOICE
MARKETING EVENT OR
ACTIVITY
SERVICE REQUEST
attributed to
EMPLOYEE / AGENT
PERSON
PROJECT
attributed to
occupant of
attributed to
held by
belongs to
manager of
composed of
CONTRACT ITEM
PRODUCT LINE
attributed to
INVOICE ITEM
owner of
attributed to
template item for
based on
based on
for
for
for
for
for
for
for
for
for
for
for
for
for
POSITION
a report to
OTHER
ORGANIZATION
UNIT
INTERNAL /
PARTNER
ORGANIZATION
UNIT
ORGANIZATION UNIT
OTHER PERSON

Figure 56. Revenue
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
S_POSTN, S_PARTY
Position Territory Assignment
S_SLSTERR_POSTN
Sales Hierarchy
S_SLS_HIER
Sales Territory
S_SLS_TERR
133
134
validated by
SALES HIERARCHY
RULE TYPE
subject of
categoried by
VALIDATION RULE
CREDIT RULE CRITERIA
characterized by
subject of
parent of
version of
recipient of
recipient of
recipient of
approve
approved by
approve
approve
assigned territory
of
assigned to
OTHER PARTY
POSITION
PARTY
approved by approve
approved by
HIERARCHY
VERSION
versioned by
composed of
part of
assignment of
POSITION TERRITORY ASSIGNMENT
HIERARCHY VERSION
TERRITORY
assigned to
transfer to
rollup to
allocated to
approved
by
consists of
applicable to
version of
belongs to
subordinate to
consists of
allocation of
CREDIT ASSIGNMENT
RULE
subject of
CREDIT ALLOCATION
SALES TERRITORY
characterized by
defined for
applied to
defined for
CREDIT RULE CRITERIA

VALUE
Title : Sales Hierarchy and Credit Assignment


Figure 57. Sales Hierarchy and Credit Assignment
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
135
136
!&
**$
14
14

2

1
*'

+

@

*'
$
"

14

13
9
&$
$

$[$
"

$[$
&$

$[$&$
14
*'.&%$%%
!>
*'%&. &$
14

*'
$
*'
&$
9"$
*'.&%$%%
$>
*' &$
14
2
6
*'
9"$
%'%*'

*'!&
**$

&$!
**$
"
$
22
*' &$ "

$
% "
Oracle

Figure 58. Sales Portfolio Management
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
Account
S_ORG_EXT, S_PARTY
Agreement
S_DOC_AGREE
Agreement Entitlement
S_ENTLMNT
Agreement Line Item
S_AGREE_ITEM
Asset
S_ASSET
Contact
S_CONTACT, S_PARTY
Entitled Product or Asset
S_ENTLMNT_ITEM
Entitled Service
S_ENTL_ACT_TYPE
Expense Type
S_EXP_ITEM_TYPE
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
Service Request
S_SRV_REQ
Work Type
S_PROJ
137
138
billed for
billable to
billed for
billable to
billed for
billable to

agreement to provide
part of
measured by
measurement for
basis for granting
granted because of
basis for granting
for
basis for
ACTION
TYPE
applicable to
for
covered by
used by
constrained by
for
for
SERVICE
CALENDER
EMPLOYEE/C
AGREEMENT
part of
subject
of
of
covered by
employer of
with
ACCOUNT
subject of
ASSET
subject of
employed at
for
covered in
FAULT/TROUBLE
CODE
AGREEMENT LINE
ITEM
include
made up of
made up of
part of
basis for
based on
include
covered in
LABOR OPERATION
CODE
ENTITLED PRODUCT OR ASSET
defined for
PRICE ADJUSTMENT
AGREEMENT ENTITLEMENT
subject of
of
defined for
ENTITLED
SERVICE
granted because of
PREVENTIVE
MAINTENANCE
PLAN ITEM
SERVICE
METRIC
ORDER
SERVICE
REQUEST
MATERIAL
WORK
TYPE
EXPENSE
TYPE
Title : Agreement Entitlement


Figure 59. Service Agreement
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
Person
S_CONTACT, S_PARTY
Schedule Calendar
S_SCHED_CAL
Schedule Calendar Hours
S_SCHED_CAL_HRS
Service Calendar
S_SCHED_CAL
Work Shift
S_SCHED_CAL
139

Figure 60. Service Calendars and Work Shifts

Title : Service Calendars and Work Shifts
SCHEDULE
CALENDAR
HOURS
EXCEPTION
CALENDAR
HOURS
EMPLOYEE
EXCEPTION
HOURS
worked by
for
for
of
of
contributor of
SCHEDULE CALENDAR
PERSON
OTHER PERSON
EXCEPTION
CALENDAR
SERVICE CALENDAR
for
EMPLOYEE /
AGENT
assigned to
WORK SHIFT
worked by
manager of
140
a report to
of
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
Service Region
S_SRV_REGN
141
142
EXTERNAL
PRODUCT
PRESENCE
part of
profile of
at
in
environment
of
made up of
EXTERNAL
PRODUCT OR
SERVICE
PRODUCT OR SERVICE
part of
profile of
subject of
of
in
environment
of
SERVICE REQUEST
part of
Title : Service Request

for
manufactured into
subject of
an instance of
ASSET (PRODUCT
INSTANCE)
subject of
for problems
with
OTHER PERSON
OTHER ORGANIZATION
UNIT
INTERNAL / PARTNER
ORGANIZATION UNIT
ORGANIZATION UNIT
OTHER PARTY
responsible for
subject of
responsibility of
EMPLOYEE / AGENT
responsible for
PERSON
PARTY
responsible for
owner of
part of
OTHER ACTIVITY
responsibility of
reporter of
SERVICE
REGION
responsible for
responsible for
owned by
responsibility of
reported by
responsibility of
responsibility of
SERVICE REQUEST ACTIVITY
for problems
with
subject of
ACTIVITY
made up of

Figure 61. Service Request
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
Inventory Location
S_INVLOC
Order
S_ORDER, S_ORDER_SHIP
Order Item Delivery Request
S_ORDPART_REQ
Order Line Item
S_ORDER_ITEM
Order Part Movement
S_ORDPART_MVMT, S_SHIPMENT_MVMT
Part Movement Type
S_PARTMVMT_TYPE
Product Internal
S_PROD_INT
Quote
S_DOC_QUOTE, S_DOC_ORDER
Quote Item Delivery Promise
S_QTE_ITM_DLVRQ
Quote Item Delivery Request
S_QTE_ITM_DLVRQ
Quote Line Item
S_QUOTE_ITEM
Shipment
S_SHIPMENT
143
144

13

1

3
1
1
1

7&

7&'$"

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

3
613
!"
!'>+7&%
!'$"
13
9">"$
!"!'>+"%
232
$>$+' $
!
213
%9"$

%9"$'$"
!">"$

%
Oracle

!&
$$'


Figure 62. Shipment
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
Account
S_ORG_EXT, S_PARTY
Activity
S_EVT_ACT
Activity Plan
S_EVT_ACT
Activity Plan Template
S_TMPL_PLANITEM
Assessment Template
S_TMPL_PLANITEM
Assessment
S_ASSESS
Assessment Attribute
S_ASSESS_ATTRIB
Assessment Attribute Valid Value
S_ASSESS_ATTVAL
Assessment Value
S_ASSESS_VAL
Employee/Agent
Opportunity
S_OPTY
Opportunity Stage
S_OPTY_STG
Person
S_CONTACT, S_PARTY
Sales Methodology
S_SALES_METHOD
Sales Stage
S_STG
Stage Plan Item
S_STG_PLANITEM
Stage Recommendation
S_STG_RECOMMEND
Template Activity
S_EVT_ACT
145
146
subject of
ACCOUNT
subject of
of
ASSESSMENT
a component of
for
of
OTHER
PERSON
OPPORTUNITY
for
EMPLOYEE /
AGENT
for
ASSESSMENT
TEMPLATE
planned by
created during
PERSON
of
for
SALES PLANNING ITEM
container of
ASSESSMENT ATTRIBUTE
validated via
defined for
made up of
for
of
OPPORTUNITY STAGE
ACTIVITY PLAN TEMPLATE
of
of
at
for
SALES
METHODOLOGY
composed of
for
STAGE
RECOMMENDATION
SALES STAGE
of
for
governor of
for
for
for
governed by
currently at
for
STAGE PLAN ITEM
instance of
ACTIVITY
PLAN
instantiated as
for
TEMPLATE
ACTIVITY
OTHER ACTIVITY
ACTIVITY
part of
made up of
ASSESSMENT ATTRIBUTE
VALID VALUE
defined for
created from
assesed via
subject of
ASSESSMENT VALUE
Title : Siebel Assistant


Figure 63. Siebel Assistant
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
Service Request
S_SRV_REQ
147

Figure 64. Social Media

Title : Social Media
CONTACT SOCIAL
MEDIA PROFILE
ATTRIBUTE
SOCIAL MEDIA DATA
defined for
SERVICE
REQUEST
PARTY
based on
source for
has
LOYALTY
TRANSACTION
based on
source for
authored by
author of
LEAD
PERSON
CONTACT
SOCIAL
MEDIA
PROFILE
owned by
OTHER
PERSON
owner of
based on
source for
listened by
posted on
EMPLOYEE /
AGENT
publisher for
SOCIAL MEDIA CHANNEL
administered by
primary administrator for
accessed by
listener for
accessor of
SOCIAL MEDIA DATA
SOURCE
administered by
administrator for
OTHER PARTY
148
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
S_TERR_POSITION
Region
S_REGION
Territory
S_TERRITORY
Territory Hierarchy
S_TERR_HIER
Territory Version
S_TERRHIER_NODE
Zipcode
(None)
149
150
%$
13
%%

$
13
&$

13
13

%%"
"".
&$""".

$ 0
"$
+"$
$ """.

%$+
%%
$"$
3"
Oracle

!>%$

$

9!>%$

13

1
%'%*

.&%$%%&$

+
9 9+

2

@13

9 '
[ !
+
>%$

0
"$

%%0
"$

&$0
"$
13
+


Figure 65. Territory Management
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
S_TERRITORY
Territory Quota
S_TERR_QUOTA
Account/Quota
S_QUOTA_ACCNT
Contact/Quota
S_QUOTA_CON
Geo/Quota
S_QUOTA_REGN, S_QUOTA_ZIP
Quota Assignment Breakdown
S_QTA_ACC_PD, S_QTA_CON_PD,
S_QTA_REGN_PD, S_QTA_ZIP_PD
S_TERR_CON
S_TERR_ACCNT
Geo/Terr Mapping
S_TERR_REGION, S_TERR_ZIP
Terr/Qta/Geo
S_TERR_QTA_REGN, S_TERR_QTA_ZIP
Terr/Qta/Con
S_TERR_QTA_CON
Terr/Qta/Accnt
S_TERR_QTA_ACCT
Accnt Quota Credit
S_TRQT_ACC_CRDT
Contact Quota Credit
S_TRQT_CON_CRDT
Geo Quota Credit
S_TRQT_REGNCRDT, S_TRQT_ZIP_CRDT
Period Quota
S_QTA_PD_BRKDN
Terr Quota Breakdown
S_TRQT_PD_BRKDN
151
152
2

!
7&
1
%'%7&
14
1
!
2

14
6

&$07&

&$

&$0
"$
+"$

7&%%
$"$
14

$

$
0
"$

0
"$

07&

[ !

+
37

Oracle

$

070

7&
!

9 '

070 $

$ 7&
!
$ 07&

070 $
15 6
7&%%
$"$
.<!;$
3
2
2

$7&
!
+7&"$
7&"$

.<!;$
15 6
213
7&
.<!;$

+7&

Figure 66. Territory Quota Rollup
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
Order Item
S_ORDER_ITEM
Organization External
S_ORG_EXT
Period
S_PERIOD
Period Relationship
S_PERIOD_REL
Product Attribute Type
S_LST_OF_VAL
Product Attribute Value
S_LST_OF_VAL
Product Option Mix Preference
S_PROD_OPT_MIX
Product Option Mix Proportion
S_PROD_OPT_PCT
Product Option Range
S_PROD_OPTION
Product Option Range Member
S_PROD_OPT_VAL
Quote
S_DOC_QUOTE
Quote Item
S_QUOTE_ITEM
153
154
primarily composed of
lead to
defined for
ASSORTMENT
PLAN
PERIOD RELATIONSHIP
delivery period for
defined
for
for
of
for
composed
of
billed to
for
delivery period for
to
of
MARKETING
the target of
SEGMENT
part of
made up
of
WEEK
subject of
PERIOD
subject of
scope of
specific to
items within
a collection of
subject of
LINE OF BUSINESS
composed of
defined for
OTHER PERIOD TYPES
SEASON
composed
of
defined for
CATEGORY
applicable
to
in
secondary
domain for
COLOR PALETTE
SEASONAL
SIZE RUN
NON-SEASONAL
PRODUCT OPTION RANGE
primarily
defined by secondarily
defined by
primary
domain
for
PRODUCT
ATTRIBUTE
TYPE
the domain
for
a value
of
includer
of
Title : Textile, Apparel and Footwear

defined for
secondarily
manufactured in
in
defined for
primarily
manufactured in
parent to
collection
of
for
PRODUCT OPTION
RANGE MEMBER
secondarily
of
collection of
subject of
secondary defined by
primarilly
of
subject
of
COLOR
FAMILY
relevant to
collection of
STYLE/COLOR/DIMENSION
launched
in
COLOR
OTHER ATTRIBUTE VALUE
SHOE SIZE
PRODUCT ATTRIBUTE VALUE
primary defined by
subject of
subject of
subject of
PRODUCT INTERNAL
recommended to be ordered in
debut season for
targetted at
for
the
default
mix for
RECOMMENDED
MIX
ordered on belonging to
specific to
ACCOUNT
SPECIFIC
MIX
OTHER
ORGANIZATION
STORE
ACCOUNT
ORGANIZATION
EXTERNAL
subject of
subject of
for
secondarily of
primarily of
PRODUCT OPTION MIX PREFERENCE

(SPREAD)
subject of
applicable to
PRODUCT OPTION
MIX PROPORTION
definer of
primarily specified
on
ASSORTMENT specify
PLAN ITEM
secondarily specified
specify
on
for
scheduled
by
of
ASSORTMENT PLAN ITEM

SCHEDULED DELIVERY
QUOTE ITEM
secondarily composed of
created from
of
QUOTE
defined
for
ORDER
composed
of
for
ORDERED
ASSORTMENT
PLAN ITEM
of
split into
ORDERED
ASSORTMENT
PLAN ITEM
PROPORTION
ORDER ITEM

Figure 67. Textile, Apparel, and Footwear
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
Organization Unit
S_ORG_EXT, S_PARTY
Period
S_PERIOD
Person
S_CONTACT, S_PARTY
Project
S_PROJ
Project Team Role
S_PROJ_RSRC
Service Request
S_SRV_REQ
Time Unit
S_TMSHT_ITEM
Timesheet
S_TMSHT
Timesheet Approval
S_TMSHT_APPR
Timesheet Line
S_TMSHT_LN
Work Type
S_PROJ
155
156
TIME SHEET
made up of
for
approved
reported by
for
reported for
PERIOD
NON-PROJECT
WORK TYPE
WORK TYPE
report of time
worked on
PROJECT TASK
for
reported by
belongs to
PROJECT
require
PERSON
reporter of
based
basis for
affiliated with
owner of
EMPLOYEE/AGENT
OTHER PERSON
approver
reporter of
composed of
targeted at
OTHER
ORGANIZATION
UNIT
subject of
owned by
ACTIVITY
INTERNAL
ORGANIZATION UNIT
ORGANIZATION UNIT
have ownership of
OPPORTUNITY
subject of
for
referenced by
defined for
PROJECT TEAM ROLE
subject of
made up
classification for
classified as
WORK TIME UNIT
subject of
submitted for
SERVICE
REQUEST
subject of
reported via
part of
adjustment
TIME ADJUSTMENT
TIME SHEET LINE
made up of
TIME UNIT
adjusted
Title : Time Sheet

contact for
owned by associated with

Figure 68. Time Sheet
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
Account
S_ORG_EXT, S_PARTY
Contract
S_D0C_AGREE, S_DOC_QUOTE, S_ORDER
Contract Item
S_AGREE_ITEM, S_QUOTE_ITEM, S_ORDER_ITEM
Fund Allocation
S_MDF_ALLOC
Internal Product Presence
S_ORG_PROD
S_MDF
S_SRC, S_SRC_CHNL
Note
S_NOTE_SRC
Order
S_ORDER
Other Contract
S_DOC_AGREE, S_DOC_QUOTE
Person
S_CONTACT, S_PARTY
Product
157
158

?13
14

14
!& $$'
!&

9"<$

>$ >+
"$ &$
"$
&$!&
"$'$
14
213

2
2

!& 8$'

"$
"$
!&
13
?
"<$
!>'"$*&$!
"<$
>$ >+

*&$!
'' $

13
!"

Oracle
$
%$

14

6
&$

14
9
$
!
$

3


Figure 69. Trade Promotions
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
Catalog Category
S_CTLG_CAT
Access Group
S_PARTY
Employee Course
S_EMP_CRSE
Employee Course Status
S_EMP_CRSE_STAT
159
160
composed of
offered in

categorized into
OTHER PRODUCT OR SERVICE
TRAINING COURSE
path
for
provide training for
for
for
belongs to
for
CURRICULUM
CATEGORY
basis of
based on
PERSON
instructor of
instructed by
in need of
enrolled in
registered by
TRAINING COURSE OFFERING
OTHER MARKETING EVENT OR

ACTIVITY
for
subject of
certification of
CURRICULUM
PERSON
certified for
subject of
granted access to
ACCESS GROUP
accessed by
needed by
EMPLOYEE COURSE
tracked by
of
EMPLOYEE COURSE STATUS
subject of
LITERATURE
for
subject of
satisfied by
JOB PROFILE
satisfied by
categorized into
target of
CURRICULUM
TARGET AUDIENCE
targeted at
provide training for
composed of
part of
TRAINING
CURRICULUM STEP
TRAINING CURRICULUM
composed of
CATALOG CATEGORY
available for
COURSE
AVAILABLE
LANGUAGE
part of
part of
PRODUCT OR SERVICE
subject of
of
TRAINING
CURRICULUM
STEP COURSE
Title : Training Curriculum Course


Figure 70. Training Curriculum Course
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
Event Location
S_EVTLOC
Individuals Test
S_CRSE_TSTRUN
Individuals Test Answer
S_CRSE_TSTRUN_A
Individuals Test Category
S_TSTRUN_CATSTS
Individuals Test Question
S_CRSE_TSTRUN_Q
S_SRC
Pool Question
S_POOL_QUES
Product or Service
S_PROD_INT
Question/Possible Answer
S_CRSE_TST_ANSR
Question/Question Pool, Question Pool, Question
S_TST_QUES
Question Category
LOV
Test Available Language
S_CRSE_TST_LANG
Test Question
S_CRSE_TST_QUES
Topic/Objective
S_CRSE_TOPIC
Training Course
S_PROD_INT_CRSE, S_PROD_INT
Training Course Offering
S_SRC_EVT, S_SRC
Training Test
S_CRSE_TST
161
162
13
2

9"<$
>$ >+
$$
&%**$

>$' $

3
"<$
>$ >+
14

213
$!>!&'%%

+
$!>!&'%%

$!>!&'%%
7&%$
14
$!>!&'%
%$%;

Oracle
14
13

1
6
1
&%0 &%**$
%
14
6
7&%$

+
9!& %>
$$
&%
1

0.= >

@
!& %>
14
21
7&%$

7&%$
'
14

7&%$07&%$'
14

13
14
%>'.'
'$
&

6
$$
%
%7&%$

7&%$0%%.'$%;
'7&%$

Figure 71. Training Test Engine

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
163
164
locally
defined
for
for
have

have
PRODUCT DEFINITION
for
OBJECT DEFINITION
child for
parent of
PRODUCT HEADER
DEFINITION
have
VERSIONED OBJECT DEFINITION
PRODUCT
ATTRIBUTE
OBJECT ATTRIBUTE
have
for
PRODUCT ATTRIBUTE VALUE
OBJECT ATTRIBUTE VALUE
Title : Versioned Object Definition

have
for
PRODUCT TEMPLATE
DEFINITION
have
for
PRODUCT TEMPLATE HEADER

DEFINITION
have
locally
defined
for
PRODUCT TEMPLATE
ATTRIBUTE
have
for
PRODUCT TEMPLATE
ATTRIBUTE VALUE
ATTRIBUTE DEFINITION
for
have
have
grouped in
for
VERSIONED OBJECT
DEFINITION VERSION
for
have
OTHER VERSIONED OBJECT HEADER

DEFINITION
ATTRIBUTE VALUE
for
ATTRIBUTE HEADER DEFINITION
for
globally defined via
JOINT WORKSPACE
ITEM
for
have
JOINT WORKSPACE

Figure 72. Versioned Object 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
S_LAB_OPER_CODE, S_CVRGLST_LABOP
Labor Operation Time
S_LAB_OPER_TM
Order
S_ORDER
Order Item
S_ORDER_ITEM
Organization Unit
S_ORG_EXT, S_PARTY
Partner Labor Rate
S_PRTNR_LAB_RATE
Position
S_POSTN
Product
S_PROD_INT, S_CVRGLST_PART
Product Line
S_PROD_LN
Product Line Warranty Coverage
S_PRDLN_WRNTY
Product Warranty Coverage
S_PROD_WRNTY
User
S_USER
165

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
166
WARRANTY
SERVICE
PROVIDER
WARRANTY
COVERAGE
ATTACHMENT
OTHER ORDER
for
made
up of
for
subject of
USER
ORGANIZATION UNIT
POSITION
for
approver of
holder of
for
for
for
has
specified for
LABOR OPERATION
TIME
for
subject to
PRODUCT
parent of
warrantor of
provided by
for
LABOR OPERATION associated to

CODE
for
associated
to
assigned to
associated
to
for
associated
to
has
made into
AGREEMENT
LINE ITEM
FAULT/TROUBLE
CODE
related to
for
PERSON
as instance of
associated to
ASSET
EXCLUSION
subject
of
policy holder for
approved by
WARRANTY COVERAGE
has
for
by
of
provided to
held by
provided by
has
for
dealer
of
PARTNER
LABOR RATE
applicable to
has
ACCOUNT
policy
holder of
role played by
of
for
SERVICE ORDER
ORDER
composed of
part of
applied to
claimed against
ASSET
WARRANTY
COVERAGE
for
a part of
by
PRODUCT
LINE
WARRANTY
COVERAGE
of
vended by
vendor of
made up of
made up of
by
PRODUCT
WARRANTY
COVERAGE
of
subject of
subject of
PRODUCT
LINE
made up of
associated
to
COVERAGE LIST
for
part of
composed of
belongs to
Figure 73.
ORDER LINE
ITEM
Title : Warranty

Warranty
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
Agreement
S_DOC_AGREE
Asset
S_ASSET
S_ASSET_WRNTY
Business Unit
S_BU
Campaign
S_SRC
Contact
S_CONTACT
Event Activity
S_EVT_ACT
Exclusion
S_EXCLUSION
Fault/Trouble Code
S_FAULT_CODE
S_LAB_OPER_CODE
Order
S_ORDER
Order Item
S_ORDER_ITEM
Partner Labor Rate
S_PRTNR_LAB_RATE
Position
S_POSTN
Product
S_PROD_INT
Service Request
S_SRV_REQ
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
168
Table 75.
Warranty Claim ERD Entities and Tables
Entity
Table
Warranty Claim Item
S_WRNTY_CLM_IT
Warranty Claim Part
S_WRNTY_IT_PROD
169
170
has
WARRANTY CLAIM
ATTACHMENT
SOURCE PAYMENT
EXCLUSION
BUSINESS UNIT
EVENT ACTIVITY
ORDER
composed of
for
ORDER ITEM
for
uses
for
for
has
for
for
associated to
for
original
part for
has
has
has
has
for
for
for
has
for
has
associated to
for
for
has
WARRANTY CLAIM
prewarranty
authorization for
has
WARRANTY CLAIM ITEM
consists of
prewarranty
authorization for
AGREEMENT
PRODUCT
has
used
for
for
associated
to
SOURCE ASSET
has
has
prewarranty
authorization
for
for
has
for
associated to
assigned to
has
assigned to
for
vendor of
vended by
has
partner of
for
filer of
approver of
submitter for
approver of
submitter for
claimed against
SERVICE REQUEST
ASSET
POSITION
ACCOUNT
CONTACT
USER
for
claimed against
FAULT/TROUBLE CODE
PARTNER LABOR RATE
CAMPAIGN
LABOR OPERATION CODE
trouble code for
fault code for
used by
recall campaign for
subject of
for
filed by
has
approved by
submitted by
approved by
submitted by
has
has
has
uses
has
has
for
ASSET
WARRANTY
COVERAGE
VALIDATION
MESSAGE
Figure 74.
WARRANTY
CLAIM PART
SOURCE PAYMENT ITEM
Title : Warranty Claim


Warranty Claim
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 repairrelated 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
S_ASSET_WRNTY
Business Unit
S_BU, S_WRK_ORDR_BU
Contact
S_CONTACT
Event Activity
S_EVT_ACT
Exclusion
S_EXCLUSION
Fault and Related Operation
S_FLT_LABOPER
Fault and Related Trouble
S_FLT_TRBL_REL, S_FAULT_CODE
Fault/Trouble Code
S_FAULT_CODE
S_LAB_OPER_CODE
Order Item
S_ORDER_ITEM
Position
S_POSTN, S_WRKORDR_POSTN
Product
S_PROD_INT
Service Request
S_SRV_REQ
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
171
172
associated to
for
for
for
has
has
for
has
has
associated to
PRODUCT original part for
for
EVENT ACTIVITY
WORK ORDER
ATTACHMENT
EXCLUSION
BUSINESS UNIT
ORDER ITEM
for
associated to
for
WORK ORDER
consists of
for
WORK ORDER ITEM
for
approved by
for
CONTACT
ASSET
USER
for
for
partner for
prewarranty
authorization for
approver of
submitter for
POSITION
associated to
associated to
created for
has
has
has
has
has
assigned to
submitted by
for
assigned to
assigned to
submitter for
approver of
approved by
prewarranty
authorization for
submitted by
has
trouble code for
has
FAULT/TROUBLE
CODE
ASSET
WARRANTY
COVERAGE
SERVICE REQUEST
ACCOUNT
WARRANTY CLAIM
consists of
for
WARRANTY CLAIM
ITEM
for
LABOR OPERATION CODE
fault code for
for
has
has
has
Figure 75.
has
WORK ORDER PART
Title : Work Order


Work Order
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
Consumer Sector
Activity
Life Sciences
Affiliations and Best Times
Life Sciences
Agencies/Agent
Financial Services
Automotive Retail
Automotive
Brick
Life Sciences
Clinical Study Management
Life Sciences
Clinical Study Site Management
Life Sciences
Communications, Media, and Energy (CME)

Account
CME
CME Agreement
CME
CME Alert
CME
CME Energy Products, Service, and Usage
CME
CME Order Management
CME
Commercial Banking
Financial Services
Commercial Insurance
Financial Services
Life Sciences
Dealer Sales and Service Promotion
Automotive
Document ID and Tax ID
Handheld
Event Tax Administration
Hospitality
Financial Account
Financial Services
Financial Account Application
Financial Services
173

Applications
Table 77.
ERD Name
Functional Area
Financial Account Origination
Financial Services
Financial Investments
Financial Services
Financial Products
Financial Services
Financial Services Events
Financial Services
Fleet Management
Financial Services
Fleet Management - Location
Financial Services
FLEXCUBE Universal Banking Integration
Financial Services
Group Insurance Policies
Financial Services
Group Pensions
Financial Services
Health Provider and Provider Group
Financial Services
High Tech Special Pricing Authorization
Sales
Hospitality Category
General
Hospitality - Meeting Package
General
Institutional Sales
Financial Services
Insurance Claims
Financial Services
Insurance Policies
Financial Services
Life Insurance Policy
Financial Services
Loyalty
General
Loyalty Flowchart and Formula
General
Managed Care
Life Sciences
Life Sciences
Objectives
Consumer Sector
Personalized Content Delivery
Life Sciences
Public Sector Benefit Case Management
Public Sector
Public Sector Case Lead Management
Public Sector
Public Sector Child Welfare
Public Sector
Public Sector Contact Identity
Public Sector
Public Sector Evidence Management
Public Sector
Public Sector Incident Management
Public Sector
Public Sector Service Provider and Referral

Management
Public Sector
174
Table 77.

Applications
ERD Name
Functional Area
Real-Time Scheduler Integration
Service
Routes and Best Call Hours
Sales
Sales Volume Planning
Consumer Sector
Sample Management
Life Sciences
Special Rate List
Communications
Syndicated Data
Life Sciences
Teller Administration
Financial Services
Territory AlignmentQuota Assignment
Sales
Territory Management - Consumer Sector
Service
Territory Management - Life Sciences
Sales
Universal Customer Master
General
Vehicle
Automotive
Vehicle Collection
Automotive
Vehicle Financing
Automotive
Vehicle Sales
Automotive
175

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
Account
S_ORG_EXT, S_PARTY
Criteria
S_CG_QUERY_ITEM
Employee
S_CONTACT, S_PARTY
Objective
S_SRC
Query
S_CG_QUERY
Route
S_ACCNTRT
176

Applications
Figure 76. Account Targeting

OBJECTIVE
EMPLOYEE
ACCOUNT
ROUTE
created from
created from
applied to
applied to
consist of
QUERY RESULT SET
combine
appear on
combined by
returned by
return
submit
QUERY
submitted by
have
belong to
CRITERIA
177

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
Account
S_ORG_EXT, S_PARTY
Activity
S_EVT_ACT
Contact
S_CONTACT
Employee
Indication
S_PROD_APPLCTN
Issue
S_PROD_ISS
Person
S_CONTACT, S_PARTY
Product
S_PROD_INT
178
INDICATION
for
Title : Activity
contains
SAMPLE
DETAIL
PROMOTIONAL ITEM
PRODUCT
consideration on
subject to
sampled at
discussed at
dropped at
belong to
ISSUE
subject to
consideration on
sampling of
discussion of
for
ACTIVITY
ATTENDEE / INVITEE
MEETING
ACCOUNT CALL
have
belongs
ATTENDEE CALL
CONTACT CALL
invite/attend
subject of
subject of
for
for
for
captured for
contain
CONTACT
EMPLOYEE
affiliated with
composed of
invited to/attend
ACCOUNT
subject of
SIGNATURE
responsible for
responsibility of
personal list of
PERSON

Applications
Figure 77. Activity
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
S_CONTACT, S_PARTY
Person Position
S_POSTN_CON
Position
S_POSTN, S_PARTY
Type
S_PARTY_PER_DTL
180

Applications
Figure 78. Affiliations and Best Times

ADDRESS USAGE
for
located at
PERSON POSITION
POSITION
composed of
belong to
for
composed of
having
for
BEST TIMES
(CONTACT
ADDRESS)
located at
for
for
ADDRESS
BEST TIMES
(ACCOUNT)
TYPE
BEST TIMES
(ACCOUNT
AFFILIATION)
belong to
of
defined by
belong to
having
ACCOUNT AFFILIATION
located at
composed of
having
ORGANIZATION
for
located at
for
for
composed of
CONTACT
181

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
Contact
S_CONTACT, S_PARTY
Organization Unit
S_ORG_EXT, S_PARTY
Product Line
S_PROD_LN
182

Applications
Figure 79. Agencies/Agent
AGENCY LINE OF
BUSINESS
based on
for
PRODUCT LINE
AGENT LINE OF
BUSINESS
based on
for
for
for
subject of
subject of
ORGANIZATION UNIT
AGENCY DETAIL
contracted by
deals with
AGENT DETAIL
INTERNAL
ORGANIZATION UNIT
deals
with
contracted
by
for
CONTACT
EXTERNAL
ORGANIZATION UNIT
has
AGENT
for
AGENCY
has
employs
works for
183

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
184
SALES STEP
used by
used in
of
OPPORTUNITY
SALES STEP
for
subject of
involver of
owner of
EMPLOYEE
owner of
in
for
has
presented
has trade-in of
presented in
VEHICLE
set
traded in
responsibility of
OTHER ASSET
visibility of
DEALER/PARTNER
visible to
handled
by
ORGANIZATION
set by
STORE BUDGET/FORECAST
responsible
for
ASSET
owner of
POSITION
owned
by
of
defined for
OPPORTUNITY
on
has
of
assigned to
SHOWROOM LOG
ENTRY
submitted by
EMPLOYEE
BUDGET/FORECAST
submitter of
subject of
assigned to
OTHER
PERSON
PERSON
in context of
instance of
SALES STEP
GOAL
of
for
source of
for
ACTIVITY
responsible for
for
set up
subject of
defined for
subject of
OTHER
ORGANIZATION
PERIOD

Applications
Figure 80. Automotive Retail
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
Contact
S_CONTACT, S_PARTY
Organization
S_ORG_EXT, S_PARTY
Position
S_POSTN
Region
S_REGION
Syndicated Data
S_SYND_DATA
186
BRICK
source of
ACTIVITY
for
REGION
POSITION
held by
holders of
SYNDICATED DATA
for
subject of
CONTACT
located at
parent of
located at
assigned to
OTHER REGION
child of
ORGANIZATION
for
ACCOUNT ADDRESS
for
assigned to
for
defined by
parent of
ADDRESS
child of

Applications
Figure 81. Brick
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
Account
S_ORG_EXT, S_PARTY
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
Contact
S_CONTACT, S_PARTY
Contract
S_DOC_AGREE
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
188
Table 84.

Applications
Clinical Study Management ERD Entities and Tables
Entity
Table
Template Visit
S_TMPL_PLANITEM
Trip Report
S_EVT_ACT
Visit
S_EVT_ACT
189

Applications
Figure 82. Clinical Study Management
190

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
Account
S_ORG_EXT, S_PARTY
Activity
S_EVT_ACT
Address
S_ADDR_PER_S_CON_ADDR
Affiliation
S_PTCL_ST_CON_LS
Contact
S_CONTACT, S_PARTY
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
191
192
has
VISIT
LOG for
PROTOCOL
VISIT
TRIP
REPORT
ACTIVITY
composed of
applied to
having
conducted at
for
for
participant of
has
for
has
used for
for
SITE STATUS
SUMMARY
REGION
user of
organization
for
has
PROTOCOL
ORGANIZATION
ACCOUNT
organization
for
has
has
site for
PROTOCOL SITE ORGANIZATION
participating in
for primary
investigator
SUBJECT
TEMPLATE
associated with
composed of
having
using
used by
for
for
located at
ADDRESS
for
PROTOCOL SITE
participant at
type for
having
TEMPLATE VERSION
for
TEMPLATE
VISIT
involved in
source of
affiliated to
AFFILIATION
having
subject of
SUBJECT
has
CONTACT
study conducted by
VISIT TYPE
SUBJECT for
STATUS
have
made by
made for
for
Title : Clinical Study Site Management


Applications
Figure 83. Clinical Study Site Management

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
Contact
S_CONTACT, S_PARTY
Exemption Profile
S_SUBSIDY
Financial Profile
S_FINAN_PROF
Trouble Ticket
S_SRV_REQ
193

Applications
Figure 84. Communications, Media, and Energy (CME) Account

ADDRESS
PREMISE
SERVICE ADDR
for
for
for
for
FINANCIAL
PROFILE
EXEMPTION
PROFILE
for
for
described
by
for
associated
with
child of
ACCOUNT
described
by
parent of
CUSTOMER
ACCT
located at
PREMISE ACCT
located at
mailed to
associated with
SERVICE ACCT
BILLING PROFILE
INVOICE
CONTACT
for
for
STATEMENT
described by
has
associated with
BILLING ACCT
associated with
tracked by
tracked by
for
problems
with
TROUBLE TICKET
made
up of
part of
associated
with
ACTIVITY
194

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
S_DOC_AGREE
Agreement Note
S_NOTE_AGR_CUT
Agreement Terms
S_AGREE_TERMS
Event Activity
S_EVT_ACT
Parameter
S_QUOTE_ITEM_XA
Quote
S_DOC_QUOTE
Quote Item
S_QUOTE_ITEM
Solution Set
S_QUOTE_ITEM
195
196
AGREEMENT
governs
bound by
QUOTE
has
belongs to
QUOTE ITEM
for
Title : CME AGREEMENTS

Author : Oracle. Confidential
part of
AGREEMENT
TERMS
consists of
for
associated
with
AGREEMENT
NOTE
tracked
by
associated
with
EVENT ACTIVITY
subject of
parent of
child of
parent of
associated
with
has a
ACCOUNTS
child of

Applications
Figure 85. CME Agreement

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
Account
S_ORG_EXT, S_PARTY
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
197

Applications
Figure 86. CME Alert

Title : CME Alert
child of
ACCOUNT
for
FRAUD PROFILE
parent of
described by
child of
for
parent of
INVOICE LINE
ITEMS
associated with
has
has
subject
for
generated by
BILLING
PROFILE
created for
ALERT
for
has
ENERGY CONSUMPTION
USAGE
ALERT ATTACHMENT
for
for
consists
BILL
generates
subject of
made up of
on
for
attached to
part of
ASSET
ACTIVITY
EQUIPMENT
METER
for
attached to
OTHER
198

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
Account
S_ORG_EXT, S_PARTY
Address
S_ADDR_PER
Asset
S_ASSET
External Product Presence
S_ORG_PRDEXT
Invoice
S_INVOICE
Invoice Adjustment
S_INVOICE_ADJ
Invoice Item
S_INVOICE_ITEM
Payment
S_SRC_PAYMENT
Period
S_PERIOD
Product: External
S_PROD_EXT
Product: Internal
S_PROD_INT
Service Instance
S_ASSET
Usage
S_USAGE
199
200
CUSTOMER
ACCOUNT
subject of
at
ASSET
EXTERNAL PRODUCT
PRESENCE
at
service
SERVICE INSTANCE
made up of
of
OTHER
EQUIPMENT
displayer
of
recorded
for
for
for
SERVICE
used
by
subject of
made by
PAYMENT
for
for
responsible for
for
BILLING
subject of
PERIOD
recorded
in
for
subject
of
INVOICE
ADJUSTMENT
line item of
INVOICE
made
of
recorded
in
for
consumer
of
USAGE
INVOICE ITEM
associated
with
subject
of
is made into
METER
is a
subject of
EXTERNAL PRODUCT
INTERNAL PRODUCT
of
PRODUCT
Title : CME Energy Products, Services, and Usage


Applications
Figure 87. CME Energy Products, Service, and Usage

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
Account
S_ORG_EXT, S_PARTY
Asset
S_ASSET
Asset Attribute
S_ASSET_XA
Order
S_ORDER
Order Item
S_ORDER_ITEM
Order Item Attribute
S_ORDER_ITEM_XA
Product or Service
S_PROD_INT
Quote
S_DOC_QUOTE
Quote Item
S_QUOTE_ITEM
Quote Item Attribute
S_QUOTE_ITEM_XA
Failed Service Order
S_SRV_ORD_FAIL
Service Request
S_SRV_REQ
201

Applications
Figure 88. CME Order Management

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

instance of
subject of
subject of
of
FAILED SERVICE
ORDER
for
part of
subject of
of
composed of
ORDER ITEM
of
part of
QUOTE ITEM
composed of
associated
to
for
associated
to
subject of
for
for
for provision of
subject of
subject of
of
for
subject of
ASSET
has
SERVICE
REQUEST
an instance of
ordered on
quoted for purchase on
made into
PRODUCT OR SERVICE
composed of
composed of
associated to
ORDER
QUOTE
created from
leads to
billed by
associated with
ACCOUNT
serviced by
serviced by
billed by
associated with
SERVICE ACCOUNT
associated with
associated with
BILLING ACCOUNT
202
OTHER
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
Employee
Exception
S_OPTY_ORG_FNXM
Facility
S_REVN
Facility Detail
S_OPTY_PROD_FNXM
Facility Organization
S_OPTYPRD_ORG
Fee
S_FN_OFFR_FEE
Financial Account
S_ASSET
Note
S_NOTE_OPTY
Opportunity
S_OPTY
Opportunity Detail
S_OPTY_DTL
Organization
S_ORG_EXT, S_PARTY
Person
S_CONTACT, S_PARTY
Portfolio Type
S_MKT_SEG
Product
S_PROD_INT
Rating
S_OPTY_ORG_FNXM
Revenue
S_REVN
Revenue
S_REVN
203

Applications
Table 91.
Commercial Banking ERD Entities and Tables
Entity
Table
Trailing Document
S_OPTY_DOC
Underwriting Standard
S_MKT_SEG_VAL
204
of
ORGANIZATION
applied as
BORROWER
subject of
for
EXCEPTION
OPPORTUNITY
subject of
of
NOTE
represented by
has
for
RATING
subject of
has
of
subject of
participated as
of
subject
of
subject of
a parent to
GUARANTOR
a report to
owned by
owner of
has
for
PRODUCT
FINANCIAL ACCOUNT
generated by
issues of
issued by
APPROVAL
LEVEL
associated
with
has
APPROVAL
STAGE
APPROVAL
part of
EMPLOYEE
need for
required by
subject to
part of
subject to
UNDERWRITING
STANDARD
belongs to
made up of
of
DECISION
KEY CREDIT
ISSUES
PORTFOLIO TYPE
for
SYNDICATE
generates
FACILITY ORGANIZATION
participated in
has
associated
with
based
on
ACTIVITY
for
has
generates
REQUEST POLICY
EXCEPTION
UNDERWRITING
STANDARD
OPPORTUNITY DETAIL
includes
FACILITY
part of
for
TRAILING
DOCUMENT
subject to
subject
of
for
for
represented by
COVENANT
POLICY
PRICE
FACILITY DETAIL
of
CORRESPONDENCE
COLLATERAL
FEE
ATTACHMENT
Title : Commercial Banking

made up
of

Applications
Figure 89. Commercial Banking
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
206

Applications
Figure 90. Commercial Insurance

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

Applications
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
Contact
S_CONTACT, S_PARTY
Discussion Post
S_MESG_BRD_LS
Product
S_PROD_INT
Registration
S_TOPIC_CON_LS
Topic
S_TOPIC_LS
208

Applications
Figure 91. Community/Chat Discussion

Title : Community Chat/Discussion
CONTACT
of
REGISTRATION
registered for
for
registration of
TOPIC
authored by
author of
for
subject of
PRODUCT
subject of
about
involving
DISCUSSION POST
posted to
209

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
S_CALL_LST
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
S_CAMP_CON
Campaign Contact Vehicle
S_CAMP_CON_AST
S_SRC
Person
S_CONTACT, S_CONTACT_ATX
Vehicle
210

Applications
Figure 92. Dealer Sales and Service Promotion

Title : eDealer Sales and Service Promotion
CAMPAIGN CONTACT
owner of
target of
in context of
belong to
for
CAMPIAGN CONTACT VEHICLE
VEHICLE
subject of
for
CALL LIST CONTACT VEHICLE
subject of
in context of
belong to
subject of
CAMPAIGN CALL LIST
CALL LIST CONTACT
created
from
in context of
belong to
in context of
subject of
owner of
subject of
PERSON

OTHER EVENT
target
CAMPAIGN
subject of
source
of
subject of
CALL LIST
211

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
Account
S_ORG_EXT, S_PARTY
Authorized Product
S_ORG_PROD
Document Mask Component
S_DOC_NUM_SEG
Document Types
S_DOC_NUM
Document Values
S_DOC_NUM_VAL
Invoice
S_INVOICE
Order
S_ORDER
Order Item
S_ORDER_ITEM
Price List
S_PRI_LST
Price List Item
S_PRI_LST_ITEM
212

Applications
Figure 93. Document ID and Tax ID

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

COMPONENTS
have
DOCUMENT
TYPES
have
composed of
exists for
exists for
PRICE LIST
213

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

Applications
Figure 94. Event Tax Administration

Title : Event- Tax Administration
EVENT/FUNCTION
FUNCTION
TAX CODE/SERVICE CODE
EVENT LOCATION ROOM
held at
location of
belongs to
for
contains
TAX CODE
composed of
held at
PROPERTY
EVENT
holds
responsible for
TEAM
MEMBER
has
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
PRICE LIST
ITEM
for
PRICE LIST
composed of
for
CHARGE
CODE
composed of
for
subject of
child of
child of
for
PRODUCT
parent to
for
subject of
CATEGORY
categorized in
parent to
for
215

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
S_CONTACT, S_PARTY
Contact Profitability
S_CON_PRFTBLTY
Fee
S_FN_ACCNT_FEE
Financial Account
S_ASSET
Financial Account Contact
S_ASSET_CON
Financial Transaction
S_FN_ACCNT_TXN
Note
S_NOTE_ASSET
Organization Unit
S_ORG_EXT, S_PARTY
Product
S_PROD_INT
Schedule
S_FN_ACCNT_SCHD
Service Request
S_SRV_REQ
216
defined for
ATTACHMENT
FEE
SCHEDULE
SERVICE
REQUEST
for
for
of
subject
subject of
subject of
subject of
subject of
EXTERNAL ACCOUNT
INTERNAL ACCOUNT
FINANCIAL ACCOUNT of
associated associated
with
with
for
ASSET
RELATIONSHIP
for problems with
for
for problems with
subject of
PRODUCT
subject of
ACTIVITY
Title : Financial Account

for
NOTE
subject of
for
for
target of
associated
with
for
owner
of
currently owned
by
subject of
CONTACT
INTERNAL
ORGANIZATION
UNIT
EXTERNAL
ORGANIZATION
UNIT
of
ACCOUNT
PROFITABILITY
subject of
ORGANIZATION UNIT
owner of
currently owned by
uses
of
CONTACT
PROFITABILITY
subject of
for
AUTHORIZATION
used by
ACCOUNT
AGGREGATION
SERVICE
FINANCIAL
TRANSACTION
subject of
for
BALANCE
HISTORY
subject of
for
FINANCIAL ACCOUNT CONTACT
participant in
ASSIGNMENT
GROUP(TERRITORY)
ACCOUNT
ANALYSIS
subject of
located
at
for
BUSINESS
ADDRESS
PERSONAL
ADDRESS
ADDRESS

Applications
Figure 95. Financial Account
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
Assessment Value
S_ASSESS_VAL
Asset Liab Contact
S_FN_ASTLB_CON
Asset Liability
S_FN_ASSET_LIAB
Collateral
S_FN_OFFR_COLT
Contact
S_CONTACT, S_PARTY
Credit Report
S_FN_CRDT_RPT
Credit Report Item
S_CRDT_RPT_ITEM
Fee
S_FN_OFFR_FEE
Financial Account
S_ASSET
Inc. Exp. Contact
S_FN_INCEXP_CON
Income/Expense
S_FN_INCM_EXP
Note
S_NOTE_OPTY
Organization
S_ORG_EXT, S_PARTY
Product
S_PROD_INT
Quote
S_DOC_QUOTE
Sales Stage
S_STG
Trailing Document
S_OPTY_DOC
218
FINANCIAL
ACCOUNT
used by
FEE
for
subject of
based
on
contain
belong
to
for
for
uses
PRODUCT
DISCLOSURE
has
associated
with
for
a component of
for
ASSESSMENT
VALUE
acknowledger of
subject of
located at
located at
for
ADDRESS
LENDER
for
for
subject
has
of
CONTACT
for
has
APPLICANT
APPLICATION CONTACT
acknowledged by
SALES
STAGE
associated
with
ORGANIZATION
has
associated
with
has
subject
to
ASSESSMENT
OTHER ACTIVITY
to review
reported in
INCOME/EXPENSE
reported in
STATEMENT
ACTIVITY
to review
TRAILING
DOCUMENT
in reference to
CREDIT
REPORT ITEM
# SEQ_NUM
CREDIT REPORT
in support
of
has
based
on
for
for
APPROVAL
NOTE
APPLICATION
based
on
for
QUOTE
part of
for
supported
by
generates
based on
PRODUCT
generates
generates
for
subject of
COLLATERAL
APPLICATION PRODUCT
subject of
generated
by
uses
ASSET LIABILITY
Title : Financial Account Application

incurred
by
associated
with
has a
with
ASSET LIAB.
CONTACT
of
associated
to
has
with
INC.EXP.
CONTACT
of
has
for
for
on

Applications
Figure 96. Financial Account Application
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
S_ORDER_ITEM
Order Item Document
S_ORDERITM_DOC, S_ORDITMDOC_LI
Quote
S_DOC_QUOTE, S_DOC_ORDER
Quote Item
S_QUOTE_ITEM
220

Applications
Figure 97. Financial Account Origination

Title : Financial Account Origination
LITERATURE
QUOTE ITEM
included in
made up of
ORDER ITEM
DOCUMENT
for
for
for
included in
ORDER
made up of DOCUMENT
has
composed of
for ORDER ITEM

for
has composed of
APPLICANT GROUP referenced in
ORDER
CONTACT
IDENTITY
refer to
serviced thro' for serviced thro'
QUOTE
child of parent to
for
for
PARTY
serviced
thro'
serviced
thro'
GROUP
made up of
for
APPLICANT GROUP
child of
ORGANIZATION UNIT
parent of
ACCOUNT
included in
composed of
has
APPLICANT GROUP
CONTACT
included in
affiliated with
made up of
composed of
member of
PERSON
contact for
OTHER PERSON
applicant for
OTHER PARTY
221

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
Contact
S_CONTACT,S_PARTY
Distribution
S_FNSEC_DSTRBTN
S_ORG_EXT, S_PARTY
Earning
S_FNSEC_ERNG
Financial Account
S_ASSET
Holding
S_FN_HLDNG
Industry
S_INDUST
Literature
S_LIT
Security
S_PROD_INT
Transaction
S_FN_ACCNT_TXN
222

Applications
Figure 98. Financial Investments

Title : Financial Investments
DISTRIBUTION
EXTERNAL ORGANIZATION
for
HOLDING
LITERATURE
TRANSACTION
INSTITUTIONAL
INVESTOR
for
for
for
for
PUBLIC COMPANY
made against
subject of
INDUSTRY
EARNING
for
FINANCIAL ACCOUNT
DIVIDEND
subject of
part of
for
for
CAPITAL GAINS
FINANCIAL INSTITUTION
made up of
subject of
CONTACT
for
for
subject of
subject of
subject of
made against
subject of
subject of
SECURITY
STOCK
invested by
FUND
INTERNAL
investor of
EXTERNAL
BOND
223

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
Product Line
S_PROD_LN
Rate
S_PROD_RATE
224

Applications
Figure 99. Financial Products

Title : Financial Products
BENEFIT
CONDITION
for
for
for
subject of
subject of
RATE
FEE
for
contain
PRODUCT LINE
subset
FEATURE
within
composed of
part of
of
has
subject of
of
of
has
has
PRODUCT INTERNAL
made up of
part of
225

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
Literature Item
S_LIT
Location Room
S_EVTLOC_ROOM
S_SRC
Organization Unit
S_ORG_EXT, S_PARTY
Person
Position
S_POSTN
Product
S_PROD_INT
Product Line
S_PROD_LN
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
226

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
227
228
VENUE
EVENT LOCATION
for
held at
subject of
location of
for
OTHER LOC
supplier of
in
LOCATION ROOM
OTHER
ORGANIZATION
UNIT
part of
subject of
has
REVENUE
COST
participates
deals with
subject of
subject of
inviter of
staffed by
deals with
subject of
INDUSTRY
has
REGION
EVENT COST
associated with
PRODUCT
deals with
has
PARENT EVENT
associated with
LITERATURE
ITEM
INVESTING
COMPANY
PRODUCT LINE
composed
of
part of
responsibility of
responsible
for
for
TRAVEL PLAN
POSITION
serviced by
required by
promoted
via
in need of
relevant to
deals with
services
reviewed by
EQUIPMENT
REQUIREMENT
composed
of
SUB EVENT
for
ACTIVITY
subject
of
part of
subject of
held at
EVENT SESSION
location of
available
in
ROOM AVAIL
EQUIPMENT
for
reviewed by
equipped
with
of
EVENT VENUE
subject of
VENUE
REVIEW
for
VENDOR
REVIEW
subject of
offered by
VENDOR
SERVICE
provider of
offered by
VENDOR
OFFER
provider of
offered at
VENUE
SERVICE
provider of
offered at
VENUE
OFFER
subject of
has
ORGANIZATION UNIT
participated
as
from
VENDOR
Title : Financial Services Events

for
includes
CANCELLED
REGISTRANT
WAIT LIST
ATTENDEE
reviewer of
subject of
for
invited to
on staff for
member of
includes
EVENT
REGISTRATION
TRAVEL
PARTICIPANT
reviewer of
PERSON

Applications
Figure 100.Financial Services Events

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
S_ORDER_ITEM
Order Item Stop
S_ORDITEM_STOP
Order Stop
S_ORDER_STOP
Order Stop Action
S_ORDSTOP_ACTN
Order Stop Detail
S_ORDERSTOP_DTL
229

Applications
Table 103. Fleet Management ERD Entities and Tables

Entity
Table
Quote
S_DOC_QUOTE
Quote Item
S_QUOTE_ITEM
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
230
OTHER
ORDER
ORDER
for
has
for
QUOTE
composed of
for
QUOTE
ITEM
FLEET MANAGEMENT ORDER
has
for
RATING
SOLUTION
has
for
RATING
SOLUTION
DETAIL
has
RATING
SOLUTION
DETAIL
PRICING
Title : Fleet Management

has
for
has
for
has
ORDER ITEM
composed of
FAVORITE
PRODUCT ITEM
for
FAVORITE
PRODUCT
ACTION
has
for
for
for
has
has
primary for
FLEET
MANAGEMENT
ORDER DETAIL
for
has
has
placed by
for
has
has
has
FLEET MANAGEMENT
ORDER HISTORY
for
belongs to
for
primary for
has
has
owner for
has
owner of
primary for
associated
to
primary for
for
owned by
has
has
has
for
associated
to
has
TARGETED LANE
FLEET
MANAGEMENT
LOCATION ROLE
FLEET
MANAGEMENT
LOCATION
for
has
primary stop for
destination
for
origin for
has
for
ORDER
STOP DETAIL
ORDER STOP
to
to
for
ORDER ITEM STOP
ORDER STOP ACTION
ACCOUNT
ADDRESS
CONTACT
BUSINESS
UNIT

Applications
Figure 101. Fleet Management
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
232

Applications
Figure 102. Fleet Management - Location

Title : Fleet Management - Location
PARTY
LOCATION
has
CONTACT
primary contact for
LOCATION primary role for

ROLE
defined for
general location for

located in
has
has
parent of
ADDRESS
container for
located in
child of
for
has
ACCOUNT
general location for

located in
has
primary account for
233

Applications

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
Offer
S_DMND_CRTN_PRG
Party
S_PARTY
Product
S_PROD_INT
234
sub-limit for
FINANCIAL
LIMIT
part of
specified for
FINANCIAL
MANDATE
available to
for
subject of
for
associated to
issued by
Title : Flexcube Universal Banking Integration

FINANCIAL
ACCOUNT
owned by
held at
owned by
associated to
OFFER
for
for
for
maker of
made by
PRODUCT
FINANCIAL GOAL
FINANCIAL PLAN
for
for
BRANCH
subject to
subject of
owner of
owner of
issuer of
has
has
has
ACCOUNT
CONTACT
PARTY

Applications
Figure 103. FLEXCUBE Universal Banking Integration
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
Contact
S_CONTACT,S_PARTY
Coverage Role
S_FN_CVRG_ROLE
Employee Class
S_FN_GRP_CLASS
Instance Attribute
S_ASSET_ITEM_XA
Organization Unit
S_ORG_EXT, S_PARTY
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
Product Internal
S_PROD_INT
Rate Band
S_PROD_RATE
236
of
beneficiary of
made up
of
subject of
subject of
for
GROUP HEALTH
POLICY INSTANCE
has
for
for
under
for
GROUP LIFE
uses
owned by
for
part of
part of
made up of
subject of
OTHER EMPLOYEE
BENEFITS
owner of
subject of
made up of
for
CENSUS
has
for
CENSUS
DETAIL
ORGANIZATION UNIT
has
for
part of
made up of
available for
PRODUCT CLASS
EMPLOYEE
CLASS
has
has
belongs
to
used for
has
belongs to
PRODUCT FOR
MEMBERS
part of
PRODUCT
ENROLLMENT
benefits
PRIMARY POLICY MEMBER
primary of
CONTACT
subject of
for
COVERAGE ROLE
Title : Group Insurance Policy

has
part
of
has
has
of
has
part of
basis
of
based
on
basis
of
PRODUCT
ATTRIBUTE
basis
based of
on
made up of
has
has
of
associated
with
belongs
to
has
RATE
BAND
based on
CLASS
ATTRIBUTE
basis of
PRODUCT INTERNAL
has
of
CLASS
has
for
PRODUCT
COMPONENT
part of
of
PRODUCT
INSTANCE
for
INSTANCE ATTRIBUTE
based on
subject to
applied to
PRODUCT CLASS RATE
based on

Applications
Figure 104.Group Insurance Policies
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
Person
S_CONTACT, S_PARTY
238

Applications
Figure 105.Group Pensions

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

Applications
Health Provider and Provider Group

This ERD (see Figure 106) illustrates how Siebel Financial Services supports generation of heathrelated 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
Contact
S_CONTACT,S_PARTY
Encounter
S_FN_HLTH_ENCTR
Health Product
S_PROD_INT
Language
S_CONTACT_FNXM
Organization
S_ORG_EXT, S_PARTY
Payment
S_SRC_PAYMENT
Provider Group Schedule
S_ORG_TIME
Provider Schedule
S_CON_LOCTN
Specialty
S_CONTACT_FNXM
240

Applications
Figure 106.Health Provider and Provider Group

Title : Health Provider/Provider Groups
ORGANIZATION
PROVIDER GROUP
subject of
provides
employs
make
subject of
belongs to
in
provided by
PROVIDER GROUP
SCHEDULE
serve
ENCOUNTER
serve at
involves
HEALTH
PRODUCT
delivered by
involves
made by
SPECIALTY
PROVIDER
SCHEDULE
for
belongs to
CONTACT part of
PATIENT
part of
subject of
delivers
part of
specialized
in
LANGUAGE
PAYMENT
spoken by
speaks
made to
beneficiary
of
PROVIDER
241

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
Agreement
S_DOC_AGREE
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
242
subject of
for
ADDRESS
located
at
ACCOUNT
for
POINT OF
SALE
HEADER
composed
of
for
CLAIM ITEM
OTHER POS
ITEM
POINT OF SALE ITEM
referencing
for
support
for
having
subject of
for
AGREEMENT
made up
of
for
ENTITLEMENT
for
ENTITLEMENT
PRODUCT PRICE
Title : High Tech Special Pricing Authorization

for
for
for
associated
with
subject of
subject of
OTHER
OPPORTUNITY
OPPORTUNITY
specially quoted for
associated
with
initiated
by
MEET
COMPETITION
QUOTE
composed
of
part of
QUOTE LINE
ITEM
created for
DESIGN
REGISTRATION
designed
for
subject of
subject of
having
subject of
PRODUCT

Applications
Figure 107.High Tech Special Pricing Authorization
243

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

Estimate
S_OPTY_MEST_TNT
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
Product or Service
S_PROD_INT
Tax/Service List
S_PRI_LST
244
TAX / SERVICE LIST
PRODUCT OR
SERVICE
OPPORTUNITY
generated from
FUNCTION
BUSINESS
TYPE BY
DATE
lead to
QUOTE
for
has
FUNCTION
Title : Hospitality Category

child of
QUOTE REVENUE BY CATEGORY
parent of
FUNCTION AVERAGE LEVEL
FUNCTION REVENUE BY CATEGORY
CHARGE CODE
related with
for
for
child of
subject of
for
subject of
parent of
SUB CATEGORY
child of
CATEGORY
child of
parent of
PARENT
CATEGORY
HOSPITALITY CATEGORY
INVOICE
PROPERTY/ASSET
subject of
subject of
for
for
included in
OPPORTUNITY MACRO REVENUE ESTIMATE
defined for
associated with
child of
contain
QUOTE MACRO REVENUE ESTIMATE
for
of
for
associated with
for
subject of
for
subject of
subject of
subject of
subject of
parent of
REPORT SECTION
CATEGORY REVENUE
contain
charged through
included in
parent of

Applications
Figure 108.Hospitality Category
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
246

Applications
Figure 109.Hospitality - Meeting Package

Title : Hospitality - Meeting Package
DISPLAY
ABBREVIATION
PRODUCT
MEETING
PACKAGE ITEM
include
facility or equipment for
MEETING PACKAGE
ROOM PRICE
MEETING
include
FUNCTION ITEM
facility or
equipment
for
for
defined for
part of
QUOTE/ORDER
priced through
composed of
MEETING
PACKAGE ROOM
MEETING
FUNCTION
for
included in
ordered through
made up of
made up of
part of
made up of
MEETING PACKAGE
247

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
Call List
S_CALL_LST
Contact
S_CONTACT, S_PARTY
Employee
Industry
S_INDUST
Literature
S_LIT
Organization Unit
S_ORG_EXT, S_PARTY
Position
S_POSTN, S_PARTY
Product
S_PROD_INT
Product Line
S_PROD_LN
248
object of interest of
interested in
subject
of
CONTACT
covered
by
object of
interest of
PRODUCT LINE
interested
in
part
of
subject
of
covers
associated
with
owned by
owns
SECURITY
PRODUCT
CALL LIST
POSITION
Title : Institutional Sales

covered by
covers
subject of
about
LITERATURE
covers
subject
of
INDUSTRY
held
by
holds
issued
by
issues
EXTERNAL
ORGANIZATION
UNIT
authored by
author
of
EMPLOYEE
ORGANIZATION UNIT
attached to
uses
ACTIVITY

Applications
Figure 110.Institutional Sales
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
250

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
Payment
S_SRC_PAYMENT
S_SRCPAYMT_CON
S_SRCPAYMT_ORG
S_INVC_PAYMENT
Position
S_POSTN, S_PARTY
Reserve Code
S_INS_RSRV_CODE
Service Request
S_SRV_REQ, S_SRV_REQ2_FNX
251
252
14
$%&$ '"
14

'"
%'
14

6
'"
%'
9"$
'"*'
9"$

'"+"$
14
+"$

Oracle

2
13

6

14

14 14

2

'"'"$
14

13
2
13
!*&'
>

14

TT
14

6
%>
7&%T

6
'"
! &"$
$=&+

13
14

'"
$

13
2

213

14

'%%
>$
14
$%&$
' +
%%
$"$
&`)

6
>+
$%&$
' +"
14
2 2

'"+

'" &$
14

14
14

13

14 6
14
14

1

'%%
!
1

2

%> !

13
1

'%% !
>

2

%$
6

13

2 26

$[N
$
3

3

14
14

6
14
13
14

1

'"
>+

6
6
$> '$"
1

6
$>

+

Applications
Figure 111.Insurance Claims

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
Account
S_ORG_EXT, S_PARTY
Claim Summary
S_INS_CLAIM
Condition
S_INSITEM_CNDTN
Contact
S_CONTACT,S_PARTY
Discount
S_APPLD_DISCNT
Drivers License
S_DRVR_LICENSE
Household
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
253
254
subject of
on
WATERCRAFT
OTHER
INSURANCE
POLICY ITEM
DWELLING
associated with
part of
subject to
OTHER
POLICY INSTANCE
INSURANCE POLICY
named as
for
PERSONAL
UMBRELLA
LINES
subject of
CONTACT
parent of
subject to
subject of
made against
PROPERTY
AUTO
subject to
on
CLAIM
SUMMARY
owned by
applicable to
PAYMENT
PLAN
owner of
HOUSEHOLD
made up of
membership of
POLICY CONTACT
HOUSEHOLD CONTACT
membership in
subject of
applied to
composed of
associated with
coverer of
composed of
covered by
subject to
SCHEDULED
PERSONAL
PROPERTY
subject of
part of
INSURANCE DOCUMENTATION
ITEM
applied to
INSURANCE COVERAGE
applied to
DISCOUNT
subject of
VEHICLE
INSURANCE POLICY ITEM
characterized by
characteristic of
CONDITION
ACCOUNT
subject of
on
INSURANCE POLICY ITEM

ACCOUNT
Title : Insurance Policies

subject of
holder of
issued to
DRIVERS
LICENSE
subject to
applicable to
LICENSE
RESTRICTION

Applications
Figure 112.Insurance Policies

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
Assessment Value
S_ASSESS_VAL
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 Account
S_ASSET
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
Organization
S_ORG_EXT, S_PARTY
Pay Plan
S_PAY_PLAN
Person
S_CONTACT, S_PARTY
Product
S_PROD_INT
Service Request
S_SRV_REQ
Withdrawal/Surrender
S_PAYMT_REQ
255
256
subject
of
for
contact
LOAN
for
subject
of
for
set up
for

guaranteed by
guaranteed by
owned
by
subject of
owned
by
associated
with
has
owner of
guarantees
LIFE POLICY
ANNUITY
for
basis of
based on
includes
part of
PRODUCT
basis of
based on
associated with
for
HOLDING
for
FINANCIAL
TRANSFER
FINANCIAL TRANSACTION
ORGANIZATION
POLICY INSTANCE
guarantees
subject of
for
WITHDRAWAL
/SURRENDER
INSURANCE
CLAIM
subject of
for
ACTIVITY
undertaken
by
responsible for
in context of
undertake
for
subject
of
for for
BILL
ACCOUNT
owner of
subject of
requested by
made up of
for
ASSESSMENT
VALUE
a component of
SERVICE
REQUEST
initiate of
subject
of
part of
for
ASSESSMENT
includes
PERSON
part of
associated
with
PAY PLAN
contact
of
ASSET
CONTACT
contact of
contact
has
for
COVERAGE
OPTION
FINANCIAL ACCOUNT
subject
of
applicable
to
BENEFICIARY
CLASS
subject
of
of
INSURANCE
COVERAGE
subject
of
belongs
to
BENEFICIARY
Title : Life Insurance Policy


Applications
Figure 113.Life Insurance Policy

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 precreated 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.
257

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

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
259
260
used by
LOYALTY PROGRAM
uses
PARTNER
PRODUCT
OFFERING
made of
in
PRODUCT
in
subject of
ACCRUAL
TEMPLATE
ACCOUNT
defined for subject of
for
for
enrolled by
PARTNER
TRANSACTION
enrolled by
HOUSEHOLD
enrolled by
in
made up of
LOYALTY PROGRAM MEMBER
INDIVIDUAL
in
owns
owned by
subject of
for
executor of
done by
owner of
defined for
PRICING
OPTIONS
MEMBERSHIP
CARD
TRAVEL
INFORMATION
uses
subject of
owned by
ACTIVITY
VOUCHER
STATEMENT
for
part of
Title : Loyalty
in
run by
uses
for
has
made of
defined for
made of
part of
uses
parent of
child of
uses
uses
used by
involved in
partnered with
involved in
defined for
TIER CLASS
part of
subject of
made up of
TIER
qualified for
partnered with
LOYALTY
PROMOTION
for
qualifies for
PROGRAM PARTNER
owner of
owned by
of
opted in by
subject of
defined for
available for
POINT
BLOCK
STATUS
RESTRICTION
defined for
POINT
TYPE
for
of
type for
for
BUCKET
defined for uses
ATTRIBUTE
DEFINITION
used by
subject of
SERVICE
PRODUCT
ASSOCIATION
part of
subject of
for
used by
REDEMPTION
ACTIVITY
PACKAGE
PRODUCT
LOYALTY TRANSACTION
PURCHASE
TRANSFER
LIMITS
subject of
for
host for
HOSTING
COMPANY
ACCRUAL
ITEM
basis for
for
for
has
for
ACCRUAL ITEM
DETAIL
LOYALTY
TRANSACTION
LOG
subject of
based on
REDEMPTION
ITEM
subject of
reference for
referred by
uses
qualified for
belongs to
LOAN
for
TIER
REWARD

Applications
Figure 114.Loyalty

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

Applications
Figure 115. Loyalty Flowchart and Formula

Title : Loyalty Flowchart and Formula
LOYALTY PROMOTION PHASE
for
for
associated with
associated with
LOYALTY
evaluated in
FORMULA
STEP
evaluated
ATTRIBUTE
DEFINITION
LOYALTY
PROMOTION
for
of
by
has
defined for
part of
consists
of
LOYALTY
FLOW
STEP
has from step

LOYALTY
FLOW
CONNECTOR
defined
for
available for
refers to
has
to step
defined for
part of
consists of
uses
LOYALTY PROGRAM FORMULA
consists of
LOYALTY PROCESS FLOWCHART
defined
for
subject
of
defined for
defined for
subject of
subject of
consists of
subject of
involved in
partnered with
LOYALTY PROGRAM
262
PROGRAM
PARTNER

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
Account
S_ORG_EXT, S_PARTY
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
263

Applications
Figure 116.Managed Care

Title : Managed Care
child of
is
FORMULARY PRODUCT
PRODUCT
for
parent to
for
of
contains
defined for
FORMULARY
has
MARKET
for
for
composed of
MANAGED CARE PLAN
accepted by
provided by
acceptor of
provider of
HEALTH CARE
PROFESSIONAL
has
ACCOUNT
associated
with
264

Applications

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
Person
S_CONTACT, S_PARTY
Plan
S_ME_PLN_LS
Position
S_POSTN, S_PARTY
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
265
266
PRODUCT
FUND
ACTIVITY

promoted at
CONTACT
EMPLOYEE
PERSON
promoted at
allocated to
using
speaker at
of
of
for
EVENT
INVITEE
SESSION
INVITEE
invitee for
for
allocating funds for promotion of

child plan of
allocated funds by
Title : Medical Education Event Management

promotion of
having
inviter of
to
inviter of
to
promotion of
parent of
SESSION
composed of
EVENT
top plan for
source of
PLAN
child of
part of
for
relevant to
usage of
having
for
of
LITERATURE
MATERIAL
subject
to
team
composed of
EVENT POSITION
for
for
owner of
in
PERIOD
team member for
owned by
POSITION

Applications
Figure 117.Medical Education Event Management

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
267

Applications
Figure 118.Objectives
Title : OBJECTIVES
ACCOUNT
CONTACT
target of
target of
for
ACTIVITY DETAILS
for
has
subject to
OBJECTIVE
assigned to
responsible for
POSITION
268

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
Account
S_PARTY, S_ORG_EXT
Activity
S_EVT_ACT, S_EVT_ACT_LSX
Assessment Template
S_TMPL_PLANITEM
Business Unit
S_PARTY, S_BU
Contact
S_PARTY, S_CONTACT
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
Offer
S_DMND_CRTN_PRG
Period
S_PERIOD
Position
S_PARTY, S_POSTN
Presentation Details
S_PCD_DETAIL
Product
S_PROD_INT
269
270
child of
parent of
MESSAGING
PLAN

period for
period of
associated to
for
for
for
parent of
creator of
for
has
has
has
for
Title : LS Personalized Content Delivery

has
PERIOD
OFFER
OBJECTIVE
for
for
MESSAGING PLAN
ITEM
child of
has
has
has
has
for
has
for
for
has
PRODUCT
has
associated to
associated to
associated to
associated to
for
for
created by
has
for
for
for
parent of
MESSAGE PRODUCT
APPLICATION
MESSAGE
PRESENTATION
DETAILS
for
has
for
ASSESSMENT TEMPLATE
associated to
for
BUSINESS
UNIT
POSITION
CONTACT
ACCOUNT
PARTY
ACTIVITY
child of
has
DECISION
ISSUES

Applications
Figure 119.Personalized Content Delivery

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
Account
S_PARTY, S_ORG_EXT
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
271

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
Contact
S_PARTY, S_CONTACT
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
272
CASE
has
for
CHANGE OF
CIRCUMSTANCEfor
has
for
has
belongs to
for
for
has
has
for
CASE VERIFICATION
TEMPLATE
has
for
for
has
for
submitter of
provider of
provided by
recipient of
received by
completer of
submitter of
completed by
verifier of
submitted by
has
for
ACTIVITY
QUALITY ASSURANCE
TEMPLATE
has
for
QUALITY
ASSURANCE
ITEMS
verified by
submitted by
has
BENEFIT PLAN
ITEM PAYMENT
payment for
PRODUCT
CASE VERIFICATION ITEM
BENEFIT PLAN ITEM
associated to
used by
has
BENEFIT
PROGRAM
belongs to ITEM
has
BENEFIT
has
PLAN
associated to
BENEFIT
PROGRAM
Title : PS Benefit Case Management

USER
ACCOUNT
CONTACT
PARTY

Applications
Figure 120. Public Sector Benefit Case Management
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
274

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
275
276
for
has visibility to
related to
OTHER
ORGANIZATION
SUSPICIOUS
GROUP
triggered by
generated by
AGENCY
approver of
related with
initiation of
relevant to
involved in
basis for
conducted for
ACTIVITY
associated with
related to
location of
INVESTIGATIVE LEAD
ORGANIZATION/GROUP
PARTY
APPLICATION
BUSINESS UNIT
is related to
has
ADDRESS
address for
located in
is related to
is visible to
APPLICATION
has
subject for
based on
EVIDENCE / SUPPORTING DOCUMENT
PHYSICAL OBJECT
for
related to
APPLICATION
ATTACHMENT
Title : Public Sector Case Lead Management

POSITION
assigned to
approved by
OTHER
PERSON
PERSON
for
AGENT
target at
for
for
subject of
related to
DISEASE
lead to
subject of
serviced via
responsible for
responsibility of
investigated by
serviced through
relevant to
generated by
INCIDENT
associated with
the use of
supported by
serviced through
CASE
generated by
SERVICE REQUEST
generated by
serviced through
for supported by
for
has
SUSPECT
for
composed
of
matching with
part of
subject
of
related to
for
PERSON DESCRIPTION

Applications
Figure 121.Public Sector Case Lead Management

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
Benefit Plan
S_CASE_BNFTPLAN
Case
S_CASE, S_CASE_PSX
Contact
S_CONTACT, S_PARTY
Court Decision
S_COURT_DECISN
Court Hearing
S_EVT_ACT
Incident
S_INCIDENT
Position
S_POSTN, S_PARTY
Service Plan
S_CASE_BNFTPLAN
Time Sheet
S_TMSHT
Time Sheet Item
S_TMSHT_ITEM
Time Sheet Line
S_TMSHT_LN
277
278
CASE
has
has
has
of
has
for
INCIDENT
for
ASSESSMENT
time spent on
TIME SHEET ITEM
Title : PS Child Welfare

subject of
approved by
uses
used by
APPROVAL
TEMPLATE
TIME SHEET
part of
has
involves
part
ALLEGATION
has
involved in involved in part of
CONTACT
allegation on
TIME SHEET LINE
made up of
approver of
POSITION
time spent on
refered in
refers to
has
has
belongs to
SERVICE
PLAN
related to
BENEFIT PLAN
PLAN
has
outcome of
COURT HEARING
has
for
COURT DECISION

Applications
Figure 122. Public Sector Child Welfare

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
279
280
$
+
&.' % $
2
13
!$+$&"
!$+
1% 3

Oracle

>%
%%
13

%%&$

$ +

6
6

$[$0
&
113

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

>'%

613
613
%+


Applications
Figure 123.Public Sector Contact Identity

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
PHYSICAL OBJECT
S_ASSET
QUOTE ITEM
S_QUOTE_ITEM
ORDER ITEM
S_ORDER_ITEM
QUOTE
S_DOC_QUOTE
ORDER
S_ORDER
SERVICE REQUEST
S_SRV_REQ
ACTIVITY
S_EVT_ACT
INVESTIGATIVE LEAD
S_CASE_LEAD
INCIDENT
S_INCIDENT
CASE
S_CASE
281
282
13
9

$[$

%&% &%
&
9&%9'!

%$
2
6
13
1

$
%&%
2 2
13
13
%
9%$
13
1
1
2
$ !$
13

6
%$
1

13
1
13
$>%
>
'!
2
2
2

>+

1?

1 1 213
13
9+% '
.=
14
6

$ +
2 2

$[$0
&
+
!!%%

>!$ 0%&$

! &"$
%>
7&%
!
1

7&
2

!"

13
7&"
1% 2"

Oracle

Applications
Figure 124.Public Sector Evidence Management

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
SERVICE REQUEST
S_SRV_REQ
ACTIVITY
S_EVT_ACT
INVESTIGATIVE LEAD
S_CASE_LEAD
CASE
S_CASE
PHYSICAL OBJECT
S_ASSET
ARREST
S_ARREST
ARREST FORCE
S_ARREST_FORCE
OFFENSE
S_OFFENSE
OFFENSE CRIMINAL ACTIVITY
S_OFFENSE_ACT
283
284
14
+
9

$[$

$[$0
&
;$%%
&$
%&% &%
&
$ !$
%&% &%
&
$>%
$
&$
2 2

>+

2
%>
7&%
2 2
**$! &$
> " &$
$ !$ &$
14
$ !$
&"%$
$ !$
> "+

**$%
1% "

Oracle

$ +
9
$ !$
&$

1
%
14
$>%
>
'!

$ !$
**$!
9
%$
%$

$

13

14
13
$>%
$

$

9$ !$ $
$ !$
%&%
%&%
2 2
$ !$;$%%
$ !$
> "

14
$=&+

%

6
6
2 2

$ !$ $
6
6
1

%*
6
9+% '.=

**$% "$' >+

Applications
Figure 125.Public Sector Incident Management

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
S_CASE_BNFTPLAN
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
Case
S_CASE, S_CASE_PSX
Contract Header
S_DOC_AGREE
Contract Item
S_AGREE_ITEM
S_PROD_INT
Order
S_ORDER, S_ORDER_PSX
Order Line Item
S_ORDER_ITEM
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
285
286
CASE
has
belongs to
BENEFIT PLAN
under
for
BENEFIT PROGRAM
has
belongs to
BENEFIT
PROGRAM ITEM
has
for
has
has
has
used for
used for
for
Title : PS Svc Provider & Referral Mgmt

owns
for
has
belongs to
subject of
owned by
payment for
has
has
subject of
provider of
BENEFIT PLAN ITEM

PAYMENT
for
CONTRACT HEADER
SERVICE PROVIDER
OTHER
ORGANIZATION
PARTY
has
for
for
CONTRACT ITEM
has
made into
ASSET
an instance of
SERVICE
PROVIDER
PROFILE
BENEFIT PLAN ITEM
has
BENEFIT
FUND
for
has
services
provided by
for
created for
has
serviced by
part of
for
ORDER
composed of
ORDER LINE
ITEM
subject of
ordered

Applications
Figure 126. Public Sector Service Provider and Referral Management

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
287
288
ADDRESS
starting
location for
has
requires
required skill
set for
RESOURCE
SCHEDULER
SKILL SET
has
for
has
parent
link for
uses
has
child
link for
RESOURCE
SCHEDULER
OBJECT LINK
RELATION
has
RESOURCE SCHEDULER
OBJECT LINK
used
for
evaluated
for
RESOURCE
SCHEDULER
SKILL RULE
CRITERIA
has
specified for
RESOURCE
SCHEDULER RULE
CRITERIA VALUE
RESOURCE SCHEDULER SKILL ITEM
RESOURCE SCHEDULER RULE

DEFINITION
owner for
defined for
TECHNICIAN
ending
location for
has
RESOURCE SCHEDULE ITEM
Title : Real-Time Scheduler Integration

source for
target for
source for
defined for
defined for
target join
source join
defined for
defined for
defined for
source for
user of
made up of
used in
BUSINESS OBJECT
BUSCOMP
has
belongs to
BUSCOMP FIELD
value for
compared to

Applications
Figure 127. Real-Time Scheduler Integration

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
289

Applications
Figure 128.Routes and Best Call Hours

Title : Routes and Best Call Hours
part of
made up of
SYNDICATE GROUP
BEST CALL HOUR
for
OTHER ORGANIZATION
have
appear on
ROUTE
defined for
RETAILER
STORE
290

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
S_ORG_PROD
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
S_ORG_EXT, S_PARTY
Internal Product
S_PROD_INT
Marketing Event
S_SRC
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 Line
S_PROD_LN
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
291

Applications
Figure 129.Sales Volume Planning

part of
Title : Sales Volume Planning

made up of
have
AUTHORIZED
PRODUCT
AUTHORIZED
PRODUCT DETAIL
SUPPLIER
for an
at
subject of
STORE
for
PRODUCT INTERNAL
of
has
subject of
RETAILER
SYNDICATE
GROUP
PRODUCT MOVEMENT
PRODUCT
BASELINE
PRODUCT
SHIPMENT
part of
CATEGORY
BASELINE
CATEGORY
SHIPMENT
have
MARKETING EVENT
exist for
composed of
CATEGORY
have
exist for
F-GROUP
PRODUCT
CONSUMPTION
CATEGORY
CONSUMPTION
PRODUCT
TARGET
CATEGORY
TARGET
PERIOD
have
exist for
292
OTHER
ORGANIZATION

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
Contact
S_CONTACT, S_PARTY
Employee
Internal Product
S_PROD_INT
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
293
294
of

belongs to
belonging to
owned by
VALIDATION
RESULT
consists of
associated
with
adjusted from
TRANSACTION
ATTACHMENT
belonging to
STOCK PERIOD
for
of
subject of
for
associated with
for
SAMPLE ORDER
composed of
TRANSACTION ITEM
adjustment of
INVENTORY AUDIT
REPORT
consists of
AUDIT REPORT
ATTACHMENT
INTERNAL PRODUCT
inventoried in
for
transferred by
owned by
belonging to
ORDER ITEM
PRODUCT INVENTORY
of
belonging to
TRANSFER ITEM
for
composed of
SAMPLE TRANSFER
Title : Sample Management

items of
CALL
associated with
for
drop of
for
Person list factor
own
transfer
own
transfer
own
transfer
own
transfer
associated
with
own
transferred by
owned by
transferred by
owned by
dropped at
SAMPLE TRANSACTION
composed of
transferred by
owned by
SIGNATURE
AUDIT
EMPLOYEE
CONTACT
PERSON

Applications
Figure 130.Sample Management

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
Account
S_ORG_EXT, S_PARTY
Asset
S_ASSET
Order Item
S_ORDER_ITEM
Quote Item
S_QUOTE_ITEM
Special Rate List
S_SPL_RATE_LST
Special Rate List Item
S_SPL_RATE_ITEM
295

Applications
Figure 131. Special Rate List

Title : Special Rate List
part of
part of
QUOTE ITEM
ORDER ITEM
composed of
composed of
has
for provision of
for
subject of
has
subject of
ASSET
has
SPECIAL RATE LIST ITEM
for
defined for
defined for
has
defined for
SPECIAL RATE LIST
defined for
has
primary for
has
ACCOUNT
296

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
Account
S_ORG_EXT, S_PARTY
Contact
S_CONTACT, S_PARTY
Period
S_PERIOD
Plan
S_INS_PLAN
Position
S_POSTN, S_PARTY
Postal Code
S_ZIPCODE
Product
S_PROD_INT
Region
S_REGION
Syndicated Data
S_SYND_DATA
Territory
S_ASGN_GRP
297
298
POSITION
PLAN
PRODUCT
PERIOD
Title : Syndicated Data

recipient of
for
for
for
for
of
in
in
PRESCRIPTION
SALES
SYNDICATED DATA
for
for
for
for
for
subject of
subject of
subject of
subject of
subject of
TERRITORY
CONTACT
ACCOUNT
POSTAL CODE
AREA

Applications
Figure 132.Syndicated Data

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
Contact
S_CONTACT, S_PARTY
Container
S_FN_CONTAINER
Container Limits
S_FNCONTNR_LMTS
Employee
Employee Teller Limits
S_EMP_TLR_LMTS
Holdover
S_FN_TXN_HLDVR, S_FN_HLDVR_CTF
Organization Unit
S_ORG_EXT, S_PARTY
Person
S_CONTACT, S_PARTY
Service Request
S_SRV_REQ
Transaction Limits
S_FN_TXN_LMTS
299
300
part of
for
has
for
BRANCH
has
has
used by
DRAWER
BAIT/TRAP
BATCH
SETTLEMENT
associated
with
ORGANIZATION UNIT
has
PARTY
BIN
VAULT
subject of
CONTAINER
made up of
has
BATCH
ACTIVITY
associated
with
includes
ACTIVITY
Title : Teller Administration

PERSON
to
from
from
to
generated
by
from
CONTACT
SERVICE
REQUEST
includes
part of
SERVICE
REQUEST LINE
ITEM
generates
associated with
EMPLOYEE
has
has
has
has
assoicated
with
TRANSACTION
LIMITS
with
with
EMPLOYEE
TELLER LIMITS
LIMITS
has
for
TRANSACTION
CALENDAR
HOLDOVER
assoicated
with
CONTAINER
LIMITS

Applications
Figure 133.Teller Administration

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
Territory
S_TERRITORY
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
301
302
%'%7&
14

'
$"$7&

07&
9$

$07&
9$

2

2

+

+
9 9+

2

+
'
$"$
'
$"$7&
15 6
'
$"$07.<!;$
$07&
9$

$ 0
"$
9$

!
&$0
"$
9$

0"$
9$

37

Oracle

Applications
Figure 134.Territory AlignmentQuota Assignment

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
S_TERR_ACCNT
Activity
S_EVT_ACT
Business Unit
S_BU
Catalog Category
S_CTLG_CAT
Contact
S_CONTACT
Contact Team Member
S_POSTN_CON
S_TERR_CON
Division
S_ORG_EXT
Position
S_POSTN
S_TERR_POSITION
Position Role
(LOV type TERR_POSITION_ROLE)
Territory
S_TERRITORY
Territory Hierarchy
S_TERR_HIER
Territory Position Role
S_TERR_POS_ROLE
Territory Version
S_TERRHIER_NODE
303
304

14

13

&$
&$"
"".
14

&$"'
%$'
%$

14

>+
'

+
2 2
+
%$
'
14
14

14
%$+%%
$"$
3"`% %{
Oracle


13

9!>%$

%'%*
1

.&%$%%&$

13

+

+
9 9+

2
@13
!>%$
$
13
$ 0
"$
+>%$
$ """.
&$0
"$
+"$

13


Applications
Figure 135.Territory Management - Consumer Sector

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
S_TERRITORY
Territory Alignment
S_TERRALGN
Territory Alignment Condition
S_TERRALGN_COND
Territory Hierarchy
S_TERR_HIER
Territory Version
S_TERRHIER_NODE
Zipcode
(None)
305
306
%$

+
'
$"$
$!$

13

0
9!>%$

13
13
13
13
13

1

.&%$%%&$

%'%*
13

+
+9 9+
@13
2

&$

!>%$
14

$
$
%%
[ !

2

9 '

0
&$0
"$
9$

$ 0
"$
9$

+>%$

0
0
%%0
"$
9$

0"$

9$

213
0
+'
$"$

%$0
%%
$"$
9$

3"`%'%{
Oracle


Applications
Figure 136.Territory Management - Life Sciences

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

Mapping
S_CIF_CON_MAP, S_CIF_ORGRP_MAP, S_CIF_ORG_MAP
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
307

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

Contacts
S_UCM_CN_SMPROF, S_CONSMPROF_UPD,
S_CIF_SMPROFMAP
UCM Social Media Profile Attribute

of Contacts
S_UCM_CN_SMATTR, S_CIF_SMATTRMAP
308
used in
for
EXTERNAL
SYSTEM
PRIVILEGE
has
ref to
referenced
to
ref in
UCM
PRIVACY
ref to
ref in
UCM ASSET
referenced in
UCM ADDRESS
stores
has
belongs to
ATTRIBUTE GROUP UPDATE HISTORY
EXTERNAL INFORMATION SYSTEM
used in
for
CONFIDENCE LEVEL
Title : Universal Customer Master

from
UCM
ORGANIZATION
belongs to
points to
for
mapped to
master
copy of
of
PARTY
mapped for
has
referenced
to
UCM
HOUSEHOLD
of
stores
has
has
for
PERSON
has
has
has
for
CONTACT
IDENTITY
for
ORGANIZATION
has
for
UCM PARTY
EXT
belongs to
HOUSEHOLD
has
for
UCM DECAY
INDICATOR
REPOSITORY BUSINESS
COMPONENT
has
REPOSITORY FIELD OBJECT
points to
ATTRIBUTE GROUP
FIELD MAPPING
referenced in
stores
belongs to
CONTACT
ADDITIONAL
NAME
UCM PROFILE
PARAMETER
UCM SOCIAL
PROFILE
UCM SOCIAL MEDIA
has
ATTRIBUTE GROUP
RULE SET
UCM DEDUP
has
EXTERNAL INFORMATION
SYSTEM MAPPING
UCM PERSON
UCM OBJECT
has
UCM MERGE
HISTORY
has
for
has
duplicate of
associated with
composed of
belongs to
UCM MERGE
ASSOCIATION
used in referenced in
for
UCM MERGE REQUEST
has
ATTRIBUTE
GROUP RULE

Applications
Figure 137.Universal Customer Master
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
Contact
S_CONTACT, S_PARTY
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
Service Request
S_SRV_REQ
Specifications
S_PROD_SPEC
Vehicle
Vehicle Product
S_PROD_INT
310
involved in
of
VEHICLE
for
service provider of
OTHER ORGANIZATION
DEALER / PARTNER
for
of
ASSET
visible to
SALES HISTORY
ORGANIZATION
have visibility to
of
FINANCIAL DETAIL
Title : Vehicle
prefer
subject of
seller of
for
VEHICLE
PRODUCT
made into
PRODUCT
sold by
of
belong to
belongs to
contains
an instance of
OPTION
made into
made into
composed of
Subject of
subject of
POSITION
for
of
for
for
for
FEATURES
assigned to
SPECIFICATIONS
perform
reported by
routed to
SERVICE REQUEST
PRODUCT DETAILS
for
assigned to
secondarily composed of
primarily
composed of
an instance of
INSTALLED
OPTION
for
SERVICE HISTORY
Currently owned by/related to

for
reporter of
performed by
involved in
of
involved in
owner of
for
a parent to
a report to
of
OTHER
PERSON
EMPLOYEE
PERSON

Applications
Figure 138.Vehicle
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
312
OTHER
PERSON
CONTACT
PERSON
PARTY
has been filed for
COLLECTION
AGENT
recorded for
BANKRUPTCY
* CASE_NUM
filer of
issued by
work on
REPOSESSION
AGENCY
work on
assigned to
REPOSESSION
REQUEST
OTHER ORGANIZATION
VEHICLE LEASE
HOLDING
COMPANY
ORGANIZATION
filed by
insured for
ASSET
subject of
associated to
insure for
VEHICLE
INSURANCE COMPANY
OTHER
ASSET
insured by
OTHER FINANCIAL
ACCOUNT
VEHICLE LEASE
insured
for
VEHICLE INSURANCE
* EFF_START_DT
insured by
FINANCIAL ACCOUNT
PROMISE TO PAY
* SEQ_NUM
IMPOUND AGENCY
IMPOUND NOTIFICATION
SERVICE REQUEST
insured by

Applications
Figure 139.Vehicle Collection
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
Contract
S_DOC_AGREE
Financial Account
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
Service Request
S_SRV_REQ
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
314
subject
of
VEHICLE LEASE
subject
of
for
in reference to
subject
of
subject
of
for
for
for
subject of
subject of
based
on
PRODUCT
subject of
VEHICLE
OPTION
consists
of
VEHICLE
ASSET
subject of
for
subject of
subject of
for
subject
of
subject
of
has
subject
of
subject
of
OTHER
FINANCIAL
ACCOUNT
in reference to
VEHICLE
LOAN
subject of
VEHICLE OPTION
AT LEASE
subject of
for
# SEQ_NUM
VEHICLE FINANCIAL
ACCOUNT
associated to
# SEQ_NUM
VEHICLE TITLE
LOG
for
HISTORICAL FMV PRICE

in reference to
subject
of
associated to
LEASE
AGREEMENT
OTHER
CONTRACT
CONTRACT
HISTORICAL AUCTION PRICE
for
VEHICLE TURN IN
subject
of
associated to
for
performed for
# CALCULATION TYPE
# EVALUATION DATE
VEHICLE FMV
subject
of
# SEQ_NUM
associated
to
HISTORICAL RESIDUAL VALUE
FINANCIAL ACCOUNT
has
for
FINANCIAL
ACCOUNT
STATE
subject of
# SEQ_NUM
INSPECTION CHARGE
in context
of
VEHICLE INSPECTION
in context of
SERVICE
REQUEST
associated
to
VEHICLE CONSIGNMENT
subject of
for
CONSIGNMENT
DETAIL
subject of
for
CONSIGNMENT
FEE
Title : Vehicle Financing


Applications
Figure 140.Vehicle Financing
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
S_SRC
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
Vehicle Sale
S_VHCL_SALES, S_VHCL_SALES_BU, S_VHCL_SALE_EMP
316
OTHER
ORGANIZATION
DEALER /
PARTNER
involved in
made by
VEHICLE SALE
ORGANIZATION
Title : Vehicle Sales

seller of
have visibility to
visible to
sold by
OPPORTUNITY
result in
result of
VEHICLE
target
in context of
subject of
subject of
in context of
target
subject of
record
initiator of
CONTACT
ACCESS LOG
subject of
# ACCESS DATE in context of
created by
for
MARKETING EVENT OR
ACTIVITY
targeted in
result in
result of
SHOWROOM LOG
ENTRY
belong to
owner of
EMPLOYEE
participate in
OTHER
PERSON
PERSON
subject of
for
subject of
handled by
in context of

Applications
Figure 141.Vehicle Sales
317

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

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.
319
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.
320
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

Suffix
Value
Unique or
Not Unique
_F#
Foreign key index.
Not unique
_II
Index on INTEGRATION_ID columns that are used for integrating

Siebel Business Applications with back-office applications.
Not unique
_P#
Primary key index.
Unique
_U#
Primary key index of the user.
Unique
_V#
Special routing visibility rule index; usually on primary child

foreign key and system foreign key columns not ordinarily
indexed (for example, primary address, primary contact, creator,
and so on).
Not unique
_M#
Miscellaneous index. Any index that does not fit into one of the
above categories.
Not unique
CAUTION: 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.
321
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.

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
322
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
(Intersection)
Data (Intersection) tables contain application or end-user data. An

intersection table implements a many-to-many relationship between two data
tables. The name of an intersection table is usually composed by
concatenating the two table names, abbreviated if needed. For example
S_OPTY_POSTN is the intersection table between tables S_OPTY and
S_POSTN. Intersection tables cannot be extended using extension tables, but
can be extended using extension columns, subject to database restrictions.
Data (Private)
Data (Private) tables contain application administration or system data.

Private tables cannot be extended using extension tables or extension
columns.
Data (Public)
Data (Public) tables contain application or end-user data. Public data tables
can be extended using extension tables and, subject to database restrictions,
extension columns.
Database View
Database View objects appear as tables with regular columns. These tables
represent database views. Objects of this table type are not created by the
ddlimp Siebel database utility. Underlying views are created by SQL scripts
during install and upgrade.
Dictionary
S_APP_VER is the only table in this category. This table has only one row and
contains information about the application such as major and minor version,
application name, unicode flag, and so on. This table contains information
about the data dictionary.
Extension
Extension tables implement a one-to-one relationship with a data table to

provide additional columns to the data table. These tables are named with an
_X suffix and contain generic columns with the ATTRIB_ prefix, which are
useful to define customized fields in a business component. These tables can
be further extended using extension columns, subject to database
restrictions.
Note that there are also tables that implement a many-to-one relationship to
a data table. Those tables have an _XM suffix and their columns have generic
names with the ATTRIB_ prefix. However, they are not considered extension
tables. Their type is Data (Public).
Extension (Siebel)
Extension (Siebel) tables also implement a one-to-one relationship with a

data table to provide additional columns to the data table. However, these
columns are configured in advance in Siebel Business Applications. Do not use
extension tables for any other purpose. These tables can be extended using
extension columns, subject to database restrictions, but cannot be extended
through extension tables.
323
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.
324
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
Bounded
The List of Values type against which this column is validated.

In the LOVB case, end users must specify a value from the list,
whereas in the LOV case, the user can enter a value not
contained in the list.
325
Table 152. Domain Types

Domain
Type
Meaning
Domain Contains
MLOV
Multilingual List of
Values
The List of Values type against which this column is validated,

in multiple languages. End users must specify a value from the
list, but see the values in their preferred language.
MLS
Multiple Language
Support
The name of the table in which the translation in an alternate

language can be found.
DNRM
Denormalized
The path to the original column, used by the Object Manager to

synchronize the values, in the form of [foreign key
column].[original column]. For example, the ACCNT_NAME
column of table S_ACCNT_POSTN is denormalized; its domain
is [OU_EXT_ID].[NAME]. In other words, the contents of
column NAME of the table referenced by OU_EXT_ID
(S_ORG_EXT) are replicated into column ACCNT_NAME of table
S_ACCNT_POSTN. Denormalization is used to improve query
performance.
(blank)
There is no domain specified for this column.

Columns of 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.
326
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.
Many tables contain a column called INTEGRATION_ID that is used to support integration with backoffice 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.
327

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

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.
From the Menu menu, choose New Query.
In the Name column, enter the name of the table for which the report is to be generated, and
press Enter.
Click the Reports icon in the icon bar.
Select Tables Report from the drop-down list.

The Output Type dialog box appears.
Select the output format for the report from the drop-down list.
Click Submit to generate the report.

The File Download dialog box appears.
329
Choose to open, save or cancel the report.
NOTE: For more information about generating reports, see Siebel Reports Guide.
330
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:

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)
331
Schema Changes
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

Table
Column
Opt
Data
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
NA
S_CL_PTCL_LS
INIT_NUM_OF_SUBJ
Yes
Number
22
10
NA
332
Schema Changes

Table
Column
Opt
Data
Type
Len
Prec
Scale
Def
S_CL_PTCL_LS
PLAN_BUDGETED_AMT
Yes
Number
22
22
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
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
DateTime
NA
NA
NA
S_CON_SM_PROF
START_DT
Yes
UTC
DateTime
NA
NA
NA
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
NA
NA
S_EVT_ACT_LSX
SD_VERIFY_FLG
No
Character
NA
NA
S_LIT
ATTCH_UNZIP_FLG
No
Character
NA
NA
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
NA
NA
S_MSG_PLAN
DSBL_MSG_RESP_FLG
No
Character
NA
NA
S_MSG_PLAN
DSBL_NAV_FLG
No
Character
NA
NA
S_MSG_PLAN
ENBL_DIR_LNCH_FLG
No
Character
NA
NA
S_MSG_PLAN
LAST_UNCOMPRESS_DT
Yes
UTC
DateTime
NA
NA
NA
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
333
Schema Changes

Table
Column
Opt
Data
Type
Len
Prec
Scale
Def
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
NA
NA
S_PTCL_SITE_LS
INIT_NUM_OF_SUBJ
Yes
Number
22
10
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
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
NA
NA
S_UI_FILE
STATUS_CD
Yes
Varchar
20
NA
NA
NA
S_UI_OBJ_EXP_FL
SEQ_NUM
Yes
Number
22
10
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
Table
Column
Type of
Change
Previous
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
334
New Value
Schema Changes
Table 158. Table Columns That have Changed in Innovation Pack 2014
Table
Column
Type of
Change
Previous
Value
New Value
S_PCD_DETAIL
RESPONSE_CD
Optional
No
Yes
S_PRO_CFG_ITEM
ADJ_VAL_AMT
Scale
S_PRO_CFG_ITEM
MAX_PRI
Scale
S_PRO_CFG_ITEM
MIN_PRI
Scale
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
335
Schema Changes
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
Column
Table
Index
Existing Columns
S_BC_ENTRY_TRGT
S_BC_ENTRY_TRGT_U1
VIEW_NAME,ENTRY_MODE_CD,
PROCESS_MODE_CD,CONFLICT_ID
APP_NAME
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,
LIT_ID,TYPE_CD,
CONFLICT_ID
MSG_PLAN_ITEM_ID,
LIT_NAME,TYPE_CD,
CONFLICT_ID
336
Index
A
account ERD
about
18
diagram
20
support for Dynamic Hierarchy
18
support for Global Account Views
18
tables
18
account targeting ERD
about
176
diagram
177
tables
176
activity ERD
about
178
diagram
179
tables
178
adjustment group ERD
about
21
diagram
22
tables
21
affiliations and best times ERD
about
180
diagram
181
tables
180
agencies/agent ERD
about
182
diagram
183
tables
182
agreement
See CME agreement ERD
AIA_INTEG_ID columns, about
327
alerts
See CME alert ERD
apparel
See textile, apparel, and footwear ERD
asset management ERD
about
23
diagram
24
tables
23
tracking asset instances
23
assets
See CME energy products, service, and usage
ERD
auction ERD
about
25
diagram
26
tables
25
auto email response generator ERD
about
27
diagram
28
tables
27
Automotive
automotive retail ERD
184
dealer sales and service promotion
vehicle collection ERD
312
vehicle ERD
310
vehicle financing ERD
314
vehicle sales ERD
316
automotive retail ERD
about
184
diagram
185
tables
184
210
B
banking
See commercial banking ERD
See FLEXCUBE Universal Banking Integration
ERD
benefit case management ERD. See public
sector benefit case management ERD
best call hours
See routes and best call hours ERD
brick ERD
about
186
diagram
187
tables
186
C
campaign management
See marketing campaign ERD
CG promotion planning ERD
about
29
diagram
31
tables
29
chat
See community/chat discussion ERD
child welfare ERD. See public sector child
welfare ERD
clinical study management ERD
about
188
diagram
190
tables
188
clinical study site management ERD
about
191
337
Index
diagram
192
tables
191
CME account ERD
about
193
diagram
194
tables
193
CME agreement ERD
about
195
diagram
196
tables
195
CME alert ERD
about
197
diagram
198
tables
197
CME energy products, service, and usage
ERD
about
199
diagram
200
tables
199
CME order management ERD
about
201
diagram
202
tables
201
columns
327
domain type definitions
325
INTEGRATION_ID columns, about
327
naming conventions
321
numeric physical type
326
type definitions
325
commercial banking ERD
about
203
diagram
205
tables
203
commercial insurance ERD
about
206
diagram
207
tables
206
Communications, Media, Energy
CME account ERD
193
CME agreement ERD
CME alert ERD
197
CME energy products, service, and usage
ERD
199
CME order management ERD
201
pricing comparison ERD
116
community/chat discussion ERD
about
208
diagram
209
tables
208
compensation planning administration ERD
about
32
diagram
33
tables
32
338
compensation planning execution ERD

about
34
diagram
35
tables
34
competency management system ERD
about
36
diagram
37
tables
36
Consumer Sector
account targeting ERD
176
best hours entity
289
29
objectives ERD
267
sales volume planning ERD
291
territory management - consumer sector
ERD
303
content management ERD
about
38
diagram
39
tables
38
content object
See content management ERD
content process
contract conditions ERD
about
40
diagram
41
tables
40
contracts ERD
about
42
diagram
43
tables
42
credit alerts
See CME alert ERD
Customer Data Item, about
44
D
data (intersection) table type
about
323
obsolete, table marked as
323
data (private) table type, about
323
data (public) table type
about
323
obsolete, table marked as
323
data types
limit checking
328
data visibility ERD
about
44
diagram
46
tables
44
Database Marketing, marketing program
ERD
86
database schema version number, finding
Index
and format
327
dealer sales and service promotion ERD
about
210
diagram
211
tables
210
defect tracking
See product quality tracking ERD
design
See schema
discussion
See community/chat discussion ERD
document ID and tax ID ERD
about
212
diagram
213
tables
212
325
Dun & Bradstreet integration ERD
about
47
diagram
48
tables
47
Dynamic Hierarchy, support by account
entity
18
E
employee KPI ERD
about
49
diagram
50
tables
49
Employee Relationship Management
compensation planning administration
ERD
32
compensation planning execution ERD
34
competency management system ERD
36
employee KPI ERD
49
performance review ERD
107
employees
time sheet ERD
155
entitlement items, service agreement
ERD
137
ERDs
account targeting, diagram
177
account targeting, tables
176
account, diagram
20
account, tables
18
activity, diagram
179
activity, tables
178
adjustment group, diagram
22
adjustment group, tables
21
affiliations and best times, diagram
181
affiliations and best times, tables
180
agencies/agent, diagram
183
agencies/agent, tables
182
asset management, diagram
24
asset management, tables

23
auction, diagram
26
auction, tables
25
auto email response generator,
diagram
28
auto email response generator, tables
27
automotive retail, diagram
185
automotive retail, tables
184
brick, diagram
187
brick, tables
186
CG promotion planning, diagram
31
CG promotion planning, tables
29
clinical study management, diagram
190
clinical study management, tables
188
clinical study site management,
diagram
192
clinical study site management, tables
191
CME account, diagram
194
CME account, tables
193
CME agreement, diagram
196
CME agreement, tables
195
CME alert, diagram
198
CME alert, tables
197
CME energy products, service, and usage,
diagram
200
CME energy products, service, and usage,
tables
199
CME order management ERD, diagram
202
CME order management ERD, tables
201
commercial banking, diagram
205
commercial banking, tables
203
commercial insurance, diagram
207
commercial insurance, tables
206
community/chat discussion, diagram
209
community/chat discussion, tables
208
compensation planning administration,
diagram
33
compensation planning administration,
tables
32
compensation planning execution,
diagram
35
compensation planning execution,
tables
34
competency management system,
diagram
37
competency management system,
tables
36
content management, diagram
39
content management, tables
38
contract conditions, diagram
41
contract conditions, tables
40
contracts, diagram
43
contracts, tables
42
conventions, description of
12
339
Index
data visibility, diagram

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

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

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

206
218
216
220
financial investments ERD
222
financial products ERD
224
financial services events ERD
226
ERD
234
group insurance policies ERD
236
group pensions ERD
238
health provider and provider group
ERD
240
institutional sales ERD
248
insurance claims ERD
250
insurance policies ERD
253
life insurance policy ERD
255
teller administration ERD
299
financial services events ERD
about
226
diagram
228
tables
226
fleet management - location ERD
about
232
diagram
233
tables
232
fleet management ERD
about
229
diagram
231
tables
229
ERD
about
234
diagram
235
tables
234
footwear
See textile, apparel, and footwear ERD
forecasts ERD
about
57
diagram
58
tables
57
fraud alerts
See CME alert ERD
G
generating table report
329
Global Account Views, support by account
entity
18
about
236
diagram
237
tables
236
group pensions ERD
about
238
diagram
239
tables
238
H
health provider and provider group ERD
about
240
diagram
241
tables
240
high tech marketing development fund ERD
about
59
diagram
60
tables
59
high tech special pricing authorization ERD
about
242
diagram
243
tables
242
Hospitality
event tax administration ERD
214
hospitality - meeting package ERD
about
246
diagram
247
tables
246
hospitality category ERD
about
244
diagram
245
tables
244
I
Include Only field
327
index column fields
327
index naming conventions
321
In-Memory Next Best Action ERD
about
61
diagram
62
tables
61
institutional sales ERD
about
248
diagram
249
tables
248
insurance
206
236
250
253
255
110
about
250
diagram
252
tables
250
about
253
343
Index
diagram
254
tables
253
invoiceable charges ERD
about
63
diagram
65
tables
63
invoices ERD
about
66
diagram
67
tables
66
M
327
L
lead management ERD
about
68
diagram
70
tables
68
about
255
diagram
256
tables
255
Life Sciences
activity ERD
178
affiliations and best times ERD
180
brick ERD
186
clinical study management ERD
188
clinical study site management ERD
191
community/chat discussion ERD
208
managed care ERD
263
medical education event management
ERD
265
personalized content delivery ERD
269
sample management ERD
293
syndicated data ERD
297
territory management - life sciences
ERD
305
limit checking for data types
328
loans, commercial banking entity
203
logical model
ERD conventions
12
ERD descriptions
15
ERD descriptions for Siebel Industry
Applications
173
loyalty ERD
about
257
diagram
260
tables
258
loyalty flowchart and formula ERD
about
261
diagram
262
tables
261
344
managed care ERD

about
263
diagram
264
tables
263
Marketing
29
47
forecasts ERD
57
high tech marketing development fund
ERD
59
lead management ERD
68
marketing budget request ERD
71
marketing campaign ERD
73
marketing collaboration ERD
75
marketing encyclopedia ERD
77
marketing event driven dialogue ERD
79
marketing events ERD
81
marketing plans ERD
84
marketing program ERD
86
marketing resource management: document
ERD
89
marketing budget request ERD
about
71
diagram
72
tables
71
marketing campaign ERD
about
73
diagram
74
tables
73
marketing collaboration ERD
about
75
diagram
76
tables
75
marketing development funds
See CG promotion planning ERD
about
77
diagram
78
tables
77
marketing event driven dialogue ERD
about
79
diagram
80
tables
79
marketing events ERD
about
81
diagram
83
tables
81
marketing plans ERD
about
84
diagram
85
tables
84
marketing program ERD
Index
about
86
diagram
88
tables
86
marketing resource management: document
ERD
about
89
diagram
90
tables
89
Master Data Item, about
44
MDFs
See CG promotion planning ERD
MedEd event management
See medical education event management
ERD
medical education event management ERD
about
265
diagram
266
tables
265
mini brick
See brick ERD
N
naming conventions
columns
321
indexes
321
physical model listings, abbreviations
used
322
table names
319
table prefixes
320
table suffixes
320
non-Siebel application products, caution
about inserting or updating
data
12
normalized, defined
11
O
objectives ERD
about
267
diagram
268
tables
267
opportunity management ERD
about
91
diagram
92
tables
91
Oracle Applications
about use of AIA_INTEG_ID columns
about use of INTEGRATION_ID
columns
327
order and promotion ERD
about
93
diagram
94
tables
93
order life cycle ERD
327
about
diagram
tables
orders ERD
about
diagram
tables
95
96
95
97
98
97
P
partner collaboration ERD
about
99
diagram
100
tables
99
partner program registration ERD
about
101
diagram
102
tables
101
party model ERD
about
103
diagram
104
tables
103
party model, about
328
party, defined
103
payments ERD
about
105
diagram
106
tables
105
performance review ERD
about
107
diagram
109
tables
107
about
110
diagram
111
tables
110
personal financial review ERD
about
112
diagram
113
tables
112
personalized content delivery ERD
about
269
diagram
270
tables
269
physical model
327
column naming conventions
321
column type definitions
325
columns of numeric physical type
326
database schema version number, finding and
format
327
325
Include Only field
327
index naming conventions
321
345
Index

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

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

335
columns removed from Innovation Pack
2014
336
columns replaced in Innovation Pack
2014
336
tables
generating report
329
naming conventions
319
new in Innovation Pack 2014
331
prefix naming conventions
320
suffix naming conventions
320
table status definitions
324
types of
323
tax ID
See document ID and tax ID ERD
teller administration ERD
about
299
diagram
300
tables
299
territory alignment - quota assignment ERD
about
301
diagram
302
tables
301
ERD
about
303
diagram
304
tables
303
territory management - life sciences ERD
about
305
diagram
306
tables
305
territory management ERD
about
149
diagram
150
tables
149
territory quota rollup ERD
about
151
diagram
152
tables
151
tests
See training test engine ERD
textile, apparel, and footwear ERD
about
153
diagram
154
tables
153
time sheet ERD
about
155
diagram
156
tables
155
trade promotions ERD
about
157
diagram
158
tables
157
348
training curriculum course ERD

about
159
diagram
160
tables
159
training test engine ERD
about
161
diagram
162
tables
161
trouble tickets
See CME account ERD
U
universal customer master ERD
about
307
diagram
309
tables
307
V
328
vehicle collection ERD
about
312
diagram
313
tables
312
vehicle ERD
about
310
diagram
311
tables
310
vehicle financing ERD
about
314
diagram
315
tables
314
vehicle sales ERD
about
316
diagram
317
tables
316
versioned object definition ERD
about
163
diagram
164
tables
163
W
warranty claim ERD
about
168
diagram
170
tables
168
warranty ERD
about
165
diagram
167
tables
165
work order ERD
about
171
diagram
172
tables
171
Index
work shifts
See service calendars and work shifts ERD
workflow process
349
Index
350

DMR2014

Uploaded by

Copyright:

Available Formats

DMR2014

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DMR2014

Uploaded by

Copyright:

Available Formats

Siebel Data Model

Siebel Data Model Reference 1

Chapter 1: Whats New in This Release

Entity Relationship Diagram Conventions

Entity Relationship Diagrams and Descriptions for Siebel Cross-Industry Applications

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

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

Training Test Engine 161

Entity Relationship Diagrams and Descriptions for Siebel Industry Applications

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

Insurance Policies 253

Chapter 3: Siebel Physical Model

Table Naming Conventions 319

Data Model Type Definitions

Table Type Definitions 323

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

Domain Type Definitions

Columns of Numeric Physical Type

Database Schema Version

Limit Checking for Data Types

Party Model Unifies Access to Data

Chapter 4: Schema Changes

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

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

Whats New in This Release

Whats New in Siebel Data Model Reference, Siebel Innovation Pack

New Tables Added to Innovation Pack

Modified topic. A listing of the new tables that have been

Changes to Table Columns

Modified topic. A listing of the table columns that have

Changes to Table Indexes Implemented

Modified topic. A listing of the table indexes that have

Whats New in Siebel Data Model Reference, Siebel Innovation Pack

In-Memory Next Best Action on page 61

New topic. Organizations can provide contextual

Universal Customer Master on page 307

Modified topic. Added two new entities: UCM Social

Schema Changes Implemented in Siebel

Modified topic. A listing of the schema changes

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

Whats New in This Release

Schema Changes Implemented in Siebel

Schema Changes Implemented in Siebel

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

New Product Features in Siebel Data Model Reference, Version 8.1/8.2

Clinical Study Management on

Modified topic. Added two new entities: Contract and

Schema Changes Implemented in

Modified topic. A listing of the schema changes

Schema Changes Implemented in

Modified topic. A listing of the schema changes

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

Siebel Logical Model

Overview of Siebel Data Model

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

Siebel Logical Model

Entity Relationship Diagram Conventions

Entity Relationship Diagram

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

Siebel Logical Model