DMR

Siebel Data Model
Reference
Version 8.1
November 2008
Copyright 2005, 2008, Oracle. All rights reserved.

The Programs (which include both the software and documentation) contain proprietary information;
they are provided under a license agreement containing restrictions on use and disclosure and are also
protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering,
disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability
with other independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems
in the documentation, please report them to us in writing. This document is not warranted to be errorfree. Except as may be expressly permitted in your license agreement for these Programs, no part of
these Programs may be reproduced or transmitted in any form or by any means, electronic or
mechanical, for any purpose.
PRODUCT MODULES AND OPTIONS. This guide contains descriptions of modules that are optional and
for which you may not have purchased a license. Siebels Sample Database also includes data related to
these optional modules. As a result, your software implementation may differ from descriptions in this
guide. To find out more about the modules your organization has purchased, see your corporate
purchasing agent or your Oracle sales representative.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs
on behalf of the United States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS. Programs, software, databases, and related documentation and technical
data delivered to U.S. Government customers are "commercial computer software" or "commercial
technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific
supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the
Programs, including documentation and technical data, shall be subject to the licensing restrictions set
forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set
forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle USA,
Inc., 500 Oracle Parkway, Redwood City, CA 94065.
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently
dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup,
redundancy and other measures to ensure the safe use of such applications if the Programs are used for
such purposes, and we disclaim liability for any damages caused by such use of the Programs.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be
trademarks of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from third
parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites.
You bear all risks associated with the use of such content. If you choose to purchase any products or
services from a third party, the relationship is directly between you and the third party. Oracle is not
responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of
the agreement with the third party, including delivery of products or services and warranty obligations
related to purchased products or services. Oracle is not responsible for any loss or damage of any sort
that you may incur from dealing with any third party.
Contents
Siebel Data Model Reference 1
Chapter 1: Whats New in This Release

Chapter 2: Data Model Overview
Chapter 3: Logical Model
Entity Relationship Diagram Conventions
11
General Entities 12
Exclusive Arc Relationship 12
Recursive Relationship 13
Entity Relationship Diagrams and Descriptions
14
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
Invoicable Charges 61
Invoices 63
Lead Management 65
Marketing Budget Request 68
Marketing Campaign
70
Siebel Data Model Reference Version 8.1
Contents
Marketing Collaboration 72
Marketing Encyclopedia 74
Marketing Event Driven Dialogue 76
Marketing Events 78
Marketing Plans 81
Marketing Program 83
Marketing Resource Management: Document
Opportunity Management 88
Order Life Cycle 90
Orders 92
Partner Collaboration 94
Partner Program Registration 96
Party Model 98
Payments 100
Performance Review 102
Personal Account 105
Personal Financial Review 107
Pricing Comparison 109
Pricing 111
Product Promotion 113
Product Quality Tracking 115
Product Recommendation 117
Products or Services 119
Professional Services 121
Revenue 123
Sales Hierarchy and Credit Assignment 125
Sales Portfolio Management 127
Service Agreement 129
Service Calendars and Work Shifts 131
Service Request 133
Shipment 135
Siebel Assistant 137
Territory Management 139
Territory Quota Rollup 141
Textile, Apparel, and Footwear 143
Time Sheet 145
Trade Promotions 147
Training Curriculum Course 149
Training Test Engine 151
Versioned Object Definition 153
Warranty 155
86
Contents
Chapter 4: Physical Model

Data Model Naming Conventions
157
Table Naming Conventions 157

Index Naming Conventions 159
Column Naming Conventions 159
Abbreviations Used in the Physical Model Listings
Data Model Type Definitions
160
160
Table Type Definitions 161

Table Status Definitions 162
Column Type Definitions 163
Domain Type Definitions 163
Columns of Numeric Physical Type

Siebel System Fields
164
164
INTEGRATION_ID Columns
Include Only Field
165
Siebel Repository
165
Database Schema Version
165
166
Limit Checking for Data Types

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

Generating a Report about Tables
167
167
Chapter 5: Schema Changes

Table Changes in This Version
169
New Tables in This Version 169

Changed Tables in This Version 171
Table Column Changes in This Version
172
New Table Columns in This Version 172

Changed Table Columns in This Version 181
Table Index Changes in This Version
181
New Table Indexes in This Version 181

Changed Table Indexes in This Version 183
Table Indexes That Were Deleted from This Version
183
Index
Contents
Whats New in This Release
Whats New in Siebel Data Model Reference, Version 8.1

Table 1 lists changes described in this version of the documentation to support release 8.1 of the
software.
Table 1.
Whats New in Siebel Data Model Reference, Version 8.1
Topic
Description
Lead Management on page 65.
Lead management is a new addition to Siebel Marketing that

provides an explicit lead-management process within Customer
Relationship Management. It improves the alignment between
marketing and sales processes.
Marketing Event Driven

Dialogue on page 76
This new feature is designed to enable timely communication

with customers and deliver sales, marketing, and services
planned for their specific needs.

on page 169.
A listing of the table changes in this schema, including the new

tables and changes to the existing table definitions.
Table Column Changes in This

Version on page 172.
A listing of the column changes in this schema, including the

new columns and changes to the existing column definitions.
Table Index Changes in This

Version on page 181.
A listing of the index changes in this schema, including the new

indexes, deleted indexes, and changes to the existing index
definitions.
Whats New in This Release
Data Model Overview
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 products you have purchased. You
are not entitled to use any portion of the Siebel Data Model to support Siebel products for which you
have not purchased the required licenses.
The Siebel Data Model is designed for speed and performance in data entry, running limited scope
queries, and managing processes like call scripting. These tasks are considered transactions, and the
database used is called an online transaction processing (OLTP) database.
Optimizing a database used for these purposes requires a design, or schema, that puts each unit of
information in a single location in the database. This allows you to update the data efficiently, since
you do not have to update the same unit of data in several different locations. Most tables in an OLTP
database have links, or join paths, to other tables, sometimes to many other tables.
The database design used in an OLTP database is usually normalized. There are several levels of
database normalization, ranging from first to fifth normal form. The Siebel database is in third
normal form.
The information in this reference is intended as an aid in configuring and using Siebel Business
Applications.
CAUTION: Do not attempt to insert or update data in the Siebel Business Applications tables
through non-Siebel application products. Doing so can render your Siebel database unusable;
additionally, you limit the ability of Oracle to provide you with quality support.
To learn how to configure an application to insert, update, and delete data interactively, read the
Siebel Developers Reference. To learn how to insert, update, and delete data in large quantities, see
Siebel Enterprise Integration Manager Administration Guide.
NOTE: The Siebel Bookshelf is available on Oracle Technology Network (OTN) and Oracle E-Delivery.
It might also be installed locally on your intranet or on a network location.
Data Model Overview
10
Logical Model
The Siebel logical model represents the following in Siebel Business Applications:
Entities
Relationships between entities
This information is represented in entity relationship diagrams (ERDs).

Oracle has made and continues to make a significant investment in modeling the business functions
of sales, marketing, and service organizations. The entity relationship diagrams included in this
chapter represent the logical model for the current release of Siebel Business Applications. In some
areas, the model extends beyond the current implementation. Published entities, therefore, might
appear in the logical model that may not be implemented in the physical model at the present time.
The ERDs included in this publication are those that are the most useful to individuals involved in
implementing or integrating Siebel Business Applications. These diagrams cover the application
areas that are most relevant to a functional understanding of the application.
The information on ERDs is organized as follows:
Entity Relationship Diagram Conventions
Entity Relationship Diagrams and Descriptions on page 14
Entity Relationship Diagram

Conventions
This topic describes entity relationship diagram conventions, as follows:
General Entities on page 12
Exclusive Arc Relationship on page 12
Recursive Relationship on page 13
11
Logical Model Entity Relationship Diagram Conventions
General Entities
Figure 1 shows the diagram conventions for general entities used in this publication.
Figure 1.
General Entity Relationship Diagram Conventions
Exclusive Arc Relationship

Figure 2 illustrates an example of the exclusive arc relationship. An exclusive arc is an arc across two
or more relationship ends; you can read each exclusive arc relationship as follows:
12
Logical Model Entity Relationship Diagram Conventions
Each [entity] must be [relationship name] either to one and only one [entity] or [relationship name]
to one and only one [entity]. For example, each Product Comparison must be to either one and only
one Product Internal or to one and only one Product External as shown in Figure 2.
Figure 2.
Exclusive Arc Relationship Diagram Convention Example
Recursive Relationship
Figure 3 illustrates an example of the recursive relationship. A recursive relationship is one in which
an entity has a relationship to itself. For example, each activity might be part of one and only one
activity, or each activity might be made up of one or more activities, as shown in Figure 3.
Recursive relationships are almost always optional, and either one-to-many or many-to-many.
Part of
Activity
Made up of
Entity Relationship Example:

1) Each activity may by made up of one or more activities.
2) Each activity may be part of one and only one activity.
Figure 3.
Recursive Relationship Diagram Convention Example
13
Logical Model Entity Relationship Diagrams and Descriptions
Entity Relationship Diagrams and

Descriptions
ERDs represent the significant entities and relevant relationships in a functional area. To enhance
their readability, the diagrams do not include every relationship and subtype. Some many-to-many
relationships have also been preserved instead of showing them as one-to-many relationships
around intersection tables in the logical model.
Table 2 provides a list of ERDs in alphabetic order.
Table 2.
Entity Relationship Diagrams
ERD Name
Figure Num.
and Page
Functional Area
Revised
in 8.1
New
in 8.1
Account
Figure 4 on
page 20
General
No
No
Adjustment Group
Figure 5 on
page 22
General
No
No
Asset Management
Figure 6 on
page 24
General
No
No
Auction
Figure 7 on
page 26
General
No
No
Auto Email Response Generator
Figure 8 on
page 28
General
No
No
Figure 9 on
page 31
Marketing
No
No
Compensation Planning Administration
Figure 10 on
page 33
ERM
No
No
Compensation Planning Execution
Figure 11 on
page 35
ERM
No
No
Competency Management System
Figure 12 on
page 37
ERM
No
No
Content Management
Figure 13 on
page 39
General
No
No
Contract Conditions
Figure 14 on
page 41
General
No
No
Contracts
Figure 15 on
page 43
General
No
No
Data Visibility
Figure 16 on
page 46
General
No
No
Dun & Bradstreet Integration
Figure 17 on
page 48
Sales/Marketing
No
No
14
Table 2.
ERD Name
Figure Num.
and Page
Functional Area
Revised
in 8.1
New
in 8.1
Employee KPI
Figure 18 on
page 50
ERM
No
No
Expense Reports
Figure 19 on
page 52
General
No
No
Field Service Inventory
Figure 20 on
page 54
Service
No
No
Field Service Scheduler
Figure 21 on
page 56
Service
No
No
Forecasts
Figure 22 on
page 58
Sales/Marketing
No
No
High Tech Marketing Development Fund
Figure 23 on
page 60
Marketing
No
No
Invoicable Charges
Figure 24 on
page 62
Service
No
No
Invoices
Figure 25 on
page 64
Service
No
No
Lead Management
Figure 26 on
page 67
Sales/Marketing
No
Yes
Marketing Budget Request
Figure 27 on
page 69
Marketing
No
No
Marketing Campaign
Figure 28 on
page 71
Marketing
No
No
Marketing Collaboration
Figure 29 on
page 73
Marketing
No
No
Marketing Encyclopedia
Figure 30 on
page 75
Sales/Marketing
No
No
Marketing Event Driven Dialogue
Figure 31 on
page 77
Marketing
No
Yes
Marketing Events
Figure 32 on
page 80
General
No
No
Marketing Plans
Figure 33 on
page 82
Marketing
No
No
Marketing Program
Figure 34 on
page 85
Marketing
No
No
Marketing Resource Management:

Document
Figure 35 on
page 87
Marketing
No
No
15
Table 2.
ERD Name
Figure Num.
and Page
Functional Area
Revised
in 8.1
New
in 8.1
Opportunity Management
Figure 36 on
page 89
Sales
No
No
Order Life Cycle
Figure 37 on
page 91
General
No
No
Orders
Figure 38 on
page 93
General
No
No
Partner Collaboration
Figure 39 on
page 95
General
No
No
Partner Program Registration
Figure 40 on
page 97
General
No
No
Party Model
Figure 41 on
page 99
General
No
No
Payments
Figure 42 on
page 101
General
No
No
Performance Review
Figure 43 on
page 104
ERM
No
No
Personal Account
Figure 44 on
page 106
Industry-Specific
No
No
Personal Financial Review
Figure 45 on
page 108
Industry-Specific
No
No
Pricing Comparison
Figure 46 on
page 110
Energy
No
No
Pricing
Figure 47 on
page 112
General
No
No
Product Promotion
Figure 48 on
page 114
General
No
No
Product Quality Tracking
Figure 49 on
page 116
General
No
No
Product Recommendation
Figure 50 on
page 118
General
No
No
Products or Services
Figure 51 on
page 120
Service
No
No
Professional Services
Figure 52 on
page 122
General
No
No
Revenue
Figure 53 on
page 124
General
No
No
16
Table 2.
ERD Name
Figure Num.
and Page
Functional Area
Revised
in 8.1
New
in 8.1
Sales Hierarchy and Credit Assignment
Figure 54 on
page 126
Sales
No
No
Sales Portfolio Management
Figure 55 on
page 128
Sales
No
No
Service Agreement
Figure 56 on
page 130
Service
No
No
Service Calendars and Work Shifts
Figure 57 on
page 132
Service
No
No
Service Request
Figure 58 on
page 134
Service
No
No
Shipment
Figure 59 on
page 136
General
No
No
Siebel Assistant
Figure 60 on
page 138
General
No
No
Territory Management
Figure 61 on
page 140
Sales
No
No
Territory Quota Rollup
Figure 62 on
page 142
Sales
No
No
Textile, Apparel, and Footwear
Figure 63 on
page 144
Consumer Sector
No
No
Time Sheet
Figure 64 on
page 146
General
No
No
Trade Promotions
Figure 65 on
page 148
General
No
No
Training Curriculum Course
Figure 66 on
page 150
General
No
No
Training Test Engine
Figure 67 on
page 152
General
No
No
Versioned Object Definition
Figure 68 on
page 154
General
No
No
Warranty
Figure 69 on
page 156
Service
No
No
17
Account
Figure 4 shows the Account ERD. The account entity is a key entity in the Siebel Data Model. The
account entity appears in many diagrams in this publication, and is often referred to as an
organization unit.
The account entity is a subtype of party composed of one or more people or contacts. An account is
any organization or subset of an organization that can be sold to or serviced. An account might
represent a company, a site, a subsidiary, a division, or any other subset of an organization. An
account might also represent a governmental agency, club, or other formal or informal group of
individuals. Each account might be accessible at one or more addresses.
The account entity supports Global Account Views and Dynamic Hierarchy. This allows a universal
view of all customer interactions. The Global Account Views present accounts in the context of a
customizable hierarchy, allowing navigation to parent and child accounts. Roll-up and roll-down
functionality gives users access to account-specific information, and aggregate information including
child accounts, activities, contacts, opportunities, and the account team.
Dynamic Hierarchy allows the Global Account Views to display a different hierarchy depending on the
business unit of the user. Each custom account hierarchy is represented completely in a relationship
table. The relationships are then denormalized into a separate table to be used for roll-up support.
Table 3 lists the entities in this ERD and their corresponding tables.
Table 3.
Account ERD Entities and Tables
Entity
Table
Account
S_ORG_EXT, S_PARTY
Account Synonym
S_ORG_SYN
Activity
S_EVT_ACT
Address
S_ADDR_ORG
Assignment Group (Territory)
S_ASGN_GRP
Business Unit
S_BU, S_ORG_EXT, S_PARTY
Characteristics
S_CHRCTR
Dynamic Account Hierarchy
S_DYN_HRCHY
Dynamic Account Hierarchy Node
S_DYN_HRCHY_REL
Employee/Agent
S_EMP_PER, S_CONTACT, S_PARTY
Industry
S_INDUST
Market Segment
S_MKT_SEG
Party
S_PARTY
Payment Term
S_PAYMENT_TERM
Person
S_CONTACT, S_PARTY
Position
S_POSTN, S_PARTY
18
Table 3.
Account ERD Entities and Tables
Entity
Table
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
Figure 5 shows the Adjustment Group ERD. This ERD illustrates the system for managing the various
matrices for pricing, compatibility, eligibility, product promotions, and so on. It allows the user to
define a matrix, its dimensions, and all of its rules. This new infrastructure allows the adjustment to
be any value, not just a price amount.
Table 4.
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
Figure 6 shows the Asset Management ERD. This ERD illustrates how Siebel Business Applications
track instances of assets. Moving counter-clockwise from the lower-right corner, the diagram shows
how internal products can be made into assets and associated with an account or a contact to register
ownership. Additional relationships between assets and accounts, contacts, and employees are
illustrated in the upper-right corner. Additional information such as the related opportunities, the
current business or personal address location of the asset, notes, and related assets are shown
across the top of the diagram. The left side of the diagram shows the relationships with service
requests, activities, and related part movements.
Table 5.
Asset Management ERD Entities and Tables
Entity
Table
Activity
S_EVT_ACT
Activity Part Movement
S_ACTPART_MVMT
Asset Contact Relationship
S_ASSET_CON
Asset Employee Relationship
S_ASSET_EMP
Asset External Organization
S_ASSET_ACCNT
Asset Feature
S_ASSET_FEA
Asset Modification
S_ASSET_TXN
Asset Relationship
S_ASSET_REL
Business Address
S_ADDR_ORG
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
Figure 7 shows the Auction ERD. This ERD illustrates how the Siebel Data Model represents the
auctioning of goods or services to bidders. An auction item may be a stand-alone offering, or may
be a specific instance of an offering of a quantity of product or of a particular asset for sale. An
auction item must be listed by a corporate or individual user, but that user may be either internal to
or external to the Siebel-owning company. Auction items are displayed to bidders through one or
more categories in a catalog. Fulfillment of an auction item to the winning bidders may be tracked
through one or more order items. Finally, users may set up watched items, may define alerts, and
may rate fellow listers or bidders.
Table 6.
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

Figure 8 shows the Auto Email Response Generator ERD. This ERD illustrates the data model for the
automatic generation of a response to an inbound communication. Incoming messages (inbound
communications) are compared against a database of previously categorized messages to categorize
them in one or more categories. The categories are associated with predefined template
communication responses, used to generate a default response to each category of message. A
notification mechanism can be defined to alert a person whenever the usage of a category or
template exceeds a predefined limit.
Table 7.
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
Figure 9 shows the CG Promotion Planning ERD. This ERD illustrates how Siebel Business Applications
support the funding of trade promotions in channel management and the Consumer Goods (CG)
industry. Marketing development funds (MDFs) are defined for an account, for a product line or
product category, and for an accounting period. An MDF can be a fixed sum of money, an accrual
fund, or a mixture of the two. The value of the accrual fund is typically determined based on an
accrual rate multiplied by either the number of units sold, or the revenue in a given period from one
or more specific products that are representative of the product line or category of the fund. Planned
expenses for the various tactics involved in the planning and execution of product promotions can
be allocated to one or more MDFs. Allocations that have not yet been approved are considered fund
requests. One or more such MDF allocations may be covered by a single payment to the partner
account.
Advanced Planning is a feature designed to address the process used by CG organizations to plan
sales volume and sales revenue at key accounts. Advanced Planning is part of a broader process
called Trade Marketing. Trade Marketing includes planning, executing, and analyzing sales.
Table 8.
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
29
Table 8.
CG Promotion Planning ERD Entities and Tables
Entity
Table
Promotion Product
S_SRC
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

Figure 10 shows the Compensation Planning Administration ERD. The administration activities of
compensation planning involve setting up salary structures such as salary plan, salary grades, and
job codes. In addition to salary structures, an organization sets up compensation budgets,
compensation types such as merit increase, bonus, promotion, and stock options, planning periods,
budget calculation and eligibility rules, guidelines and calculation of budget allocations for
employees.
Table 9.
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

Figure 11 shows the Compensation Planning Execution ERD. In the execution phase of compensation
planning, a workbook is created for each of the authorized managers with the list of employees who
report to them. The manager goes through the planning process and decides on the merit, bonus,
promotion, and stock option changes that he may grant to his employees. Authorized persons such
as managers, or HR personnel approve the plans. Totals are maintained for each manager and
organization.
Table 10.
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

Figure 12 shows the Competency Management System ERD. An organization can define a set of
competencies that employees can have or acquire over a period of time and an evaluation of
employees' skill levels in those competencies, In addition, information about an employee's past
work experience, merits, honors, professional memberships and education qualifications can be
maintained. An organization can also define a list of courses and related skills which can be
associated with an employee when they complete those courses.
Table 11.
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
Figure 13 shows the Content Management ERD. This ERD illustrates how the Siebel Data Model
supports the process of creating and maintaining content through projects. A content project is made
up of one or more content project items that represent an item of master data, such as a product
definition or an item of literature. Each content project item is an instance of a content item type
that is part of a content object. A content object is based on a business object and is published to
the production system through an EAI integration object. A workflow process governs the flow of the
items in a content project from conception through publication. Each item may be the responsibility
of, reviewed by, or approved by one or more Positions.
Table 12.
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
Figure 14 shows the Contract Conditions ERD. This ERD illustrates the usage of templates to create
agreements. An agreement could comprise one or more entitlements. A contracts administrator may
define template entitlements, template benefits and template conditions in addition to template
terms. Template benefits and conditions could be for a specific product or product line or product
class or category. An entitlement could be created using the entitlement template and this would
create the corresponding benefits and conditions based on the corresponding template benefits and
conditions. The terms governing the agreement could be based on template terms.
Table 13.
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
Figure 15 shows the Contracts ERD. This ERD illustrates the significant entities related to general
business contracts (quotes, orders, agreements, and others). A contract is an agreement between
two parties, usually to deliver goods or services in exchange for payment. For example, a quote is
an agreement between a company and a customer to guarantee a price for a particular set of items
if acted on within a specified timeframe. The customer is usually an account, but may be a person.
The party on the other side of the contract is an internal or partner organization (or business unit).
A contract is composed of contract line items that specify the internal products, services, or assets
to be covered under the terms of the contract.
Table 14.
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
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
for
priced by
priced by
for
for
involved by
composed of
QUOTE
ORDER LINE ITEM
QUOTE LINE ITEM
part of
OTHER CONTRACT LINE ITEM
AGREEMENT LINE
ITEM
CONTRACT LINE ITEM
Title : Contracts
subject of
default pricing for
pricing for
subject of
employed at
ACCOUNT
subject to
employer of
applicable to
for
subject to
PAYMENT
TERM
for
subject to
priced by
INTERNAL
PRODUCT OR
SERVICE
pricing
method for
subject of
made into
an instance of
composed of
PRICE LIST
ASSET
part of
Figure 15. Contracts
43
Data Visibility
The main business entities represented (shown in Figure 16) in the Siebel Data Model fall into one of
two super-types: Master Data Item or Customer Data Item. A Master Data Item represents data set
up and administered by the company using Siebel Business Applications such as products, literature,
and price Lists. Master Data Items are often categorized to make information more accessible. A user
gains visibility to this data either through the person's association with a business unit (multiple
organization visibility) or through the person's access to items in a catalog (access control). Access
to items in a catalog is provided by making the category public, or by granting access to the category
to one or more access groups. Each access group may be made up of smaller access groups and may
be made up of one or more groups of users. Categories granted to a parent access group are
automatically granted to all of its child access groups, but categories granted to a child are not
granted to its parents.
A Customer Data Item represents transactional data collected during the normal course of doing
business such as opportunities, quotes, orders, agreements, service requests, and activities. A user
gains visibility to this data either through the person's association with a business unit (multiple
organization visibility) or more commonly through a direct assignment of the person or the person's
position to the item. A Customer Data Item is usually accessible to one business unit, but is
occasionally accessible to two or more business units. Each business unit may be made up of smaller
business units. A given type of customer data item is usually assigned to employees through position
or directly to the employee, but rarely both. Managers can be granted access to customer data items
assigned to their subordinates.
Table 15.
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 15.
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 (shown in Figure 17) illustrates how Siebel Business Applications integrate with Dun &
Bradstreet Organization information. A D & B organization may be classified as doing business in one
or more industries, may provide information about contacts at the organization and their
management responsibilities. In addition, a D & B organization may indicate its direct parent
organization, its ultimate domestic parent, and its ultimate global parent. A Siebel organization unit
(for example, an account) can be related to its equivalent D & B organization and its associated
parent organizations. Contact information from one or more D & B organizations can be used to
create one or more call lists.
Table 16.
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 (shown in Figure 18) illustrates that Key Performance Indicators (KPI) can be defined and
associated with the objectives of an employee so that the employee and the manager of the
employee manager can measure achievement or current values against the goals set in the
objectives of the employee.
Table 17.
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
EMPLOYEE / AGENT
DIVISION
ACCESS GROUP
OTHER PERSON
50
subject of
OTHER
PARTY
Expense Reports
This ERD (shown in Figure 19) illustrates how Siebel Business Applications track employee expense
reports. Employees (for example, sales representatives, field service engineers, and professional
services personnel) can track expense items incurred for business purposes. These expenses can be
associated with an account, an opportunity, or a project, and may be related to an activity. Other
employees or contacts involved in the expense can be associated with the expense. The expenses in
a specified reporting period can then be reported on an expense report for reimbursement.
Table 18.
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 (shown in Figure 20) illustrates how Siebel Business Applications track field service parts
inventory. Parts may be tracked in inventory as serialized assets or as nonserialized quantities of
products. An instance of product inventory defines a quantity of product in a given location with a
given status and availability. Inventory quantities cannot be modified directly. Instead, they are
modified through inventory transactions that reflect each movement of parts between locations,
statuses, and availabilities. Inventory locations may be located at a third-party provider, as well as
within the internal organization. They may also be related to other inventory locations for the
purposes of replenishment or fulfillment.
Table 19.
Field Service Inventory ERD Entities and Tables
Entity
Table
Address
S_ADDR_ORG
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
Field Service Scheduler

This ERD (shown in Figure 21) illustrates how the Siebel Data Model supports the scheduling of
employees to perform service activities within configured service regions. A service region
corresponds to one or more ZIP codes or other geographical representation, but may only be
associated with a single time zone. The service region defines a number of parameters, time duration
maps, cost functions, and rule sets that constrain the scheduling of resources within the region. A
given service request or activity is assigned to a service region and then to an employee, based on
the employee's working hours and current schedule.
Table 20.
Field Service Scheduler ERD Entities and Tables
Entity
Table
Address
S_ADDR_ORG
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. Field Service Scheduler

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
for
TIMEZONE
for
ZIPCODE
used by
made up of
SCHEDULER PARAMETER SET
Forecasts
This ERD (shown in Figure 22) illustrates the process of generating forecasts. A forecast series
defines a set of forecast periods in which forecasts must be submitted, and describes the appropriate
number of periods to forecast into the future for each forecast period. One or more positions are then
assigned to submit forecasts under the defined forecast series. When a forecast series is accessible
to the public, it means the forecast series can be shared across organizations. Each participant
submits a forecast each period that is made up of forecast items. Each forecast item may be
attributed to different kinds of business transactions, and may be defined at any of a number of
levels based on business rules. These forecast items may be generated based on known revenue
items. Forecasts that managers make can contain items from the forecasts of their subordinates.
Table 21.
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 (shown in Figure 23) illustrates how Siebel Business Applications support the funding of
trade promotions in the high technology industry. Marketing Development Fund (MDF) is a pool of
money made available to partners for the organization of marketing activities (campaigns, events,
and so on). An MDF may be a partner-specific fund or general fund. MDFs (Programs) provide the
brand owner with the ability to make marketing funds available to partners in a programmatic way.
Partner Specific funds are child funds of Programs. Within each Partner Specific fund, the partner
accrues funds under the given program. The partner creates a partner event activity (pre-approval)
with several associated event items. Event Items add granularity to the partner event activity.
Partners create claims to redeem the money in their partner-specific funds for marketing activities
that were pre-approved by the brand owner.
Table 22.
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
Internal Product or Service
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
Invoicable Charges
This ERD (shown in Figure 24) illustrates how financial transactions, such as charges and credits, are
handled. Any charge or credit that could be invoiced is added to this table. This is based on defined
consolidation plan rules to consolidate charges and credits into invoice and invoice items.
Table 23.
Invoicable Charges ERD Entities and Tables
Entity
Table
Activity
S_EVT_ACT
Address
S_ADDR_ORG
Agreement
S_DOC_AGREE
Agreement Entitlement
S_ENTLMNT
Agreement Line Item
S_AGREE_ITEM
Asset
S_ASSET
Auction Item
S_AUC_ITEM
Expense Item
S_EXP_ITEM
Invoicable Charge
S_INVOICE_CHRG
Invoice
S_INVOICE
Invoice Item
S_INVOICE_ITEM
Invoice Item Reconciliation Entry
S_INVC_ITM_DTL
Order
S_ORDER
Order Line Item
S_ORDER_ITEM
Part Movement
S_ACTPART_MVMT, S_ORDPART_MVMT
Part Repair
S_PART_RPR
Party
S_PARTY, S_ORG_EXT, S_CONTACT, S_USER, S_BU
Payment
S_SRC_PAYMENT
Payment Term
S_PAYMENT_TERM
Product or Service
S_PROD_INT
Project Item
S_PROJITEM
Project Team Role
S_PROJ_RSRC
Service Request
S_SRV_REQ
Shipment
S_SHIPMENT
Time Sheet Item
S_TMSHT_ITEM
61
62
for
INVOICE
made up of
part of
for
ADDRESS
billed to
for
made for
fulfilled by
PAYMENT
INVOICE ITEM
subject of
invoiced into
for
INVOICE ITEM for
INVOICABLE
subject of
CHARGE
INVOICE ITEM
DETAIL
INVOICE ITEM
RECONCILIATION ENTRY
Title : Invoicable Charges

subject of
for
ACCOUNT
contact of
OTHER
ORGANIZATION
UNIT
charged via
PARTY
for
ORGANIZATION UNIT
billed to
located at
for
billed to
INVOICABLE CHARGE
for
for
for
for
for
for
for
PERSON
primary billing contact of
for
AGREEMENT
charged via
ORDER
PRODUCT OR
SERVICE
object for
composed of
SHIPMENT
AUCTION ITEM
part of
composed of
ordered on
part of
of
charged via
of
ORDER
PART
MOVEMENT
PAYMENT TERM
ORDER LINE
ITEM
fulfilled by
for
ACTIVITY
PART
MOVEMENT
made up of
part of
charged via
AGREEMENT
LINE ITEM
based on
made up of
part of
SERVICE
REQUEST
EXPENSE ITEM
charged via
charged via
AGREEMENT
ENTITLEMENT
basis for
charged via
TIME SHEET ITEM
PART REPAIR
charged via
PART MOVEMENT
PROJECT
TEAM ROLE
charged via
based on
for
for
charged via
for
PROJECT
ITEM
charged via
charged via
ASSET
ACTIVITY
basis of
charged via
charged via
charged via
based on
for
for
for
for
composed of
for
charged via
OTHER
PARTY
billed to
part of
Figure 24. Invoicable Charges
Invoices
This ERD (shown in Figure 25) illustrates the invoicing and payment processes. An invoice may be
considered a receivable or a payable for the company. It may be generated to bill for an order, a
project, a part repair, an agreement, a service request, an activity, or a period of time for products
or services delivered within a specific period of time. Items on the invoice may be reconciled with
one or more other entities as well. A payment may be made for one or more Invoices, and an invoice
may be paid through one or more payments.
Table 24.
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
63
64
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 25. Invoices
Lead Management
This ERD (shown in Figure 26) 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 may be converted into an Opportunity. A lead may be generated as a result of a marketing
campaign, a marketing offer or other marketing activities. A lead may 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 system.
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 which 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 25.
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
65
Table 25.
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
66
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 26. Lead Management
67
Marketing Budget Request

This ERD (shown in Figure 27) 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 26.
Marketing Budget Request ERD Entities and Table
Entity
Table
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
68

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 27. Marketing Budget Request
69
Marketing Campaign
This ERD (shown in Figure 28) illustrates campaign management, execution, and evolution.
Campaign management may involve the focus of the campaign on a territory, as well as the
responsibility of the various internal divisions and teams for successful execution. Execution may
include the production and distribution of literature to the appropriate campaign contacts. Campaign
evolution tracks the usage of call lists to identify campaign contacts and generate leads. Campaign
contacts may include prospective contacts purchased on a call list. If a prospective contact is not
promoted to a customer before the call list that names them expires, they are typically deleted from
the database.
Table 27.
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
70
OTHER PERSON
recipient of
PERSON
POSITION
for
for
subject of
made up
of
ORDER
composed of
for
initiator of
originator of
originator of
originator of
associated with
generated by
made
of
part of
used in
subject
of
PURCHASED
LIST
CAMPAIGN CALL LIST
for
user of
MARKETING
SEGMENT
CALL LIST
in
of
of
of
subject
of
of
subject of
subject
of
of
subject of
CALL LIST
MEMBER
primarily from
source of
made up of
targeted at
PROSPECTIVE CONTACT
a parent
to
a report to
OTHER
MARKETING
EVENT OR
ACTIVITY
responsibility of
MARKETING CAMPAIGN
introduction to
for
CAMPAIGN CONTACT
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 28. Marketing Campaign
71
Marketing Collaboration
Collaborative marketing (shown in Figure 29) assists marketers in maintaining the balance between
the need for consistent customer management among partners and effective brand building with
local expertise. It consists of two features. Marketing program collaboration allows companies to
develop marketing programs in a more collaborative environment, resulting in reduced costs. It
encourages collaboration on programs through the sharing of information with key action groups
(internal and external). Partner marketing enhancements provides the ability to associate and track
partner participation in marketing programs and campaigns to measure and report on opportunities,
orders, and ROI. It also closes the loop by providing the ability to track partner sources for
responses/opportunities orders.
Table 28.
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
72
Figure 29. 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
73
Marketing Encyclopedia
This ERD (shown in Figure 30) illustrates how Siebel Business Applications track competitive
information about products and companies. A standard set of metrics may be defined against which
competitive organizations and their products can be rated in comparison with the internal
organization and products, respectively. Detailed product specifications can be recorded. In addition,
competitive literature may be associated both with organizations and with products. The relevance
of key decision issues to the various competitive metrics may be defined.
Table 29.
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
74
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 30. Marketing Encyclopedia
75
Marketing Event Driven Dialogue

The Event Driven Dialogue feature enables timely sales and services to be 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 (shown in Figure 31)
illustrates the various relationships between Marketing Program, Stage, and Event Triggers. The wait
period between stages is also tracked.
Table 30.
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
76
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

Author : Oracle ,Confidential
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 31. Marketing Event Driven Dialogue
77
Marketing Events
This ERD (shown in Figure 32) illustrates how Siebel Business Applications support marketing events
and activities planning. A marketing event may be composed of one or more sessions, held at one
or more venues such as a hotel or convention center. The room for each session of an event may be
chosen based on the size and equipment requirements of the session matched to the size and
available equipment of each room. Users can also create travel plans for customers attending the
events. Event vendors and sponsors can be tracked as well as the various offers or services they
provide. The event staff can be planned and attendees invited. Attendees may then register for the
event or even for specific sessions. Attendees may be quoted registration prices through a quote and
purchase tickets to the event through an order.
Table 31.
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
Product or Service
S_PROD_INT
Quote
S_DOC_QUOTE
Room Avail Equipment
S_EVTLOC_RM_EQP
Travel Participant
S_EVT_TRVL_PER
Travel Plan
S_EVT_TRVL_PLAN
78
Table 31.
Marketing Events ERD Entities and Tables
Entity
Table
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
79
80
>$&
>$' $
13

$[$
&$
3
>$>$&
14
14
14
9'

>$
%$
2

14
>$!&
9!&

%>
%$
9
$
7&
!
$
14
2

26

$ ''!

%$
;'%
$!
>$

%$
13
14
2
13
26
>'
$ 1
$ '$"
14
$
>$
2

2

!& %>
'&
"
2
13

?13
13

>''$
6
213
7&"$
7&"$

1

>$%%%$

' $"
?6
21
"7&"$
>'.'+
9"<$

>$ >+
>+

2
2613
>$ %
2613 13
"<$
>$ >+

14
>$&
>;
13
>$&
%>
>$!
>;
14
13
>$!
%>
2
13
>$!
**
2
2
>$&
**

1
>$>$!
"52
Oracle
Figure 32. Marketing Events
Marketing Plans
This ERD (shown in Figure 33) illustrates how marketing plans are used in conjunction with the
financial modeler for the purposes of financial planning. Marketing plans are multilevel groupings of
plan elements (campaigns) or sub-plans. Financial goals and costs can be forecasted for each level
of the plan, tracked against actual achievement after campaign execution, and rolled up to the toplevel plan. Funds can also be allocated for different plans in different periods and used as inputs for
accounting purposes or in financial calculations.
Table 32.
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
81
82
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 33. Marketing Plans
Marketing Program
This ERD (shown in Figure 34) illustrates how Siebel Business Applications support the more complex
program planning and execution used for Database Marketing. Marketing segments are dynamic lists
of people defined by a set of database criteria and available to marketing programs. These criteria
may be defined on measures and attributes based on complex mathematical scores, ratios, and
formulas applied to customer demographics or behavior data sourced from the Siebel database or
from external applications such as a data warehouse.
After a data dictionary describing the external data store has been defined, segment definitions can
be created and attached to one or more campaigns, together with purchased lists. Filters allow the
exclusion of segment members based on predefined clauses. Segment prioritization and
deduplication make sure that individuals qualified for more than one segment do not receive
conflicting messages from more than one campaign. Waves can be generated as a subset of the
qualifying people within the targeted segments.
Recurring marketing programs can be defined in which each stage may be based on customer
response behavior or any other event. Marketers can define customer hierarchies, so that campaigns
can be driven by data summarized from any level of the hierarchy (for example household level and
customer level). People to be contacted are listed as campaign contacts for a specific campaign or
wave.
Each campaign may be presented with one or more offers. An offer is a type of demand creation
program that is directly presented to a target audience. It is intended to generate awareness of or
demand for one or more products. Responses are tracked through Communications.
Table 33.
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
83
Table 33.
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
84
**
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 34. Marketing Program
85
Marketing Resource Management: Document

This ERD (shown in Figure 35) 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 34.
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
86

**"!
<

2
**
! &"$

2

'!%&

2

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

2
=
! &"$

3

14

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

13
'!%& ! &"$
1
13

>$!.!!$
2

>$!.!!$
"

8$'

$[$

33

** "
$
1
>$
' $

6
3

"<$
"'

$
2
1
"'$>$+.+' $
""! "
Oracle
Figure 35. Marketing Resource Management: Document
87
Opportunity Management
This ERD (shown in Figure 36) illustrates the significant entities related to an opportunity (or lead),
including relationships to contacts, employees (generally sales representatives), products, accounts,
and so on.
Table 35.
Opportunity Management ERD Entities and Tables
Entity
Table
Address
S_ADDR_ORG
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
88
driver of
OPPORTUNITY
for
classified in
for
part of
considered on
PRODUCT OR
SERVICE
consideration of
ADDRESS
source of
basis for
based on
ISSUE
relevant as
relevant to
subject to
within
subject to
made up of
TERRITORY
consideration on
relevance of
part of
affiliated with
part of
for
OPPORTUNITY
RELATIONSHIP
collection of
of
responsible for
owned by
performer of
performed by
subject of
targeted at
resource for
CORRESPONDENCE
EVENT ACTIVITY
AGREEMENT
composed of
owned by
located at
for
OPPORTUNITY ISSUE
subject of
for
QUOTE
SALES DOCUMENT
vendor of
a collection of
produced by
of
PRODUCT
STRUCTURE
made up of
SALES
STAGE
a parent to
OTHER ORGANIZATION UNIT
a report to
a component of
composed of
classification of
driven by
SALES
METHODOLOGY
initiator of
initiated by
nvolver of
a partner to
MARKETING EVENT OR
ACTIVITY
involved on
INTERNAL / PARTNER
ORGANIZATION UNIT
ORGANIZATION UNIT
in partnership with
Title : Opportunity Management

on
a report to
EMPLOYEE /
AGENT
manager of
involver of
OTHER
PERSON
PERSON
located at
for
Figure 36. Opportunity Management
89
Order Life Cycle

This ERD (shown in Figure 37) illustrates how orders are tracked through their full life cycle by Siebel
Business Applications. The cycle starts with an opportunity that tracks the consideration of purchase
of one or more products. This opportunity leads to one or more quotes, composed of one or more
quoted product items. A quote may then lead to one or more orders. An order is composed of one
or more ordered product items. Fulfillment of the order can be tracked through a set of part
movements of various types, culminating in a shipment of products to the customer, and the
invoicing for shipped goods.
Table 36.
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
90
target of
part of
for
lead to
PRODUCT OR SERVICE
part of
of
ORDER
taken for
composed of
ordered on
part of
of
billed via
billed via
for
for
for
part of
of
from
ALLOCATION
RECEIPT
MVMT
SHIP
MVMT
preceded by followed by
OTHER PART
MOVEMENT
ORDER PART MOVEMENT

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

fulfillment of
billed via
for
INVOICE
billed via
composed of
generated for
reason for
INVOICE ITEM
fulfilled by
for
billed via
for
composed of
target of
ORDER ITEM
part of
created from
composed of
composed of
for
lead to
receiver of
QUOTE ITEM
for
QUOTE
prepared for
quoted for purchase on
for
composed of
considered for purchase on
of
OPPORTUNITY
PRODUCT
for
lead to
lead to
consideration of purchase of
OPPORTUNITY
of
ACCOUNT
Title : Order Life Cycle

Figure 37. Order Life Cycle
91
Orders
This ERD (shown in Figure 38) illustrates the relationships between orders and significant entities
related to orders such as assets, products, inventory locations, part movements, inventory
transactions, activities, and parties. Orders include sales orders, service orders, purchase orders,
and return material authorizations (RMAs) among others. The fulfillment of an order results in one
or more part movements according to the instructions of the order. Each part movement results in
one or more inventory transactions. Each order is usually the responsibility of a single internal or
partner organization, but sometimes two or more. An order may be assigned or credited to one or
more positions.
Table 37.
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
92
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 38. Orders
93
Partner Collaboration
Partner collaboration (shown in Figure 39) allows the brand owner's partner companies to give other
partners visibility to their data. With this functionality, partners can more easily collaborate with
other partners, without any required intervention from the brand owner company. Partner companies
can start collaborations and invite other partners of the brand owner to join their collaborations.
Once the invitation is accepted, individual partner companies who are now part of the collaboration
can pledge resources (Positions) to the collaboration, making the resources available to all partners
in the collaboration who may want to add the resource to a project or an opportunity.
Table 38.
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
94
"%%

9"%%

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

1
14

313
9+

1

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

$[$
3

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

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

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

Oracle,
Figure 39. Partner Collaboration
95
Partner Program Registration

Partner Program Registration (shown in Figure 40) 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 39.
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
96

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 40. Partner Program Registration
97
Party Model
This ERD (shown in Figure 41) illustrates the structure of the party entity, its significant subtypes,
and relationships. A party is either a person or some grouping of people such as an organization, a
household, a position or a list of users. A person may be an employee or agent of the company using
Siebel Business Applications. A person may also be considered a user if he or she has been granted
user login credentials. An access group is a type of party that is made up of one or more groups.
Addresses may be tracked for a person, a household, or an organization.
Table 40.
Party Model ERD Entities and Tables
Entity
Table
Access Group
S_PARTY
Account
S_ORG_EXT, S_PARTY
Business Address
S_ADDR_ORG
Employee/Agent
Group
S_PARTY
Household
S_ORG_GROUP, S_PARTY
Organization Relationship
S_ORG_REL
Organization Unit
S_ORG_EXT, S_PARTY
Party
S_PARTY
Party Relationship
S_PARTY_REL
Person
S_CONTACT, S_PARTY
Person Relationship
S_PARTY_REL or S_CONTACT_REL
Personal Address
S_ADDR_PER
Position
S_POSTN, S_PARTY
User List
S_PARTY
User Login
S_USER
98
Figure 41. Party Model

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

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

6

+

&
%$

9&%9'!
"'+0

$

%%
&
&%'%

1
%$
9
&

1

$[$&$

9
%$
&$

9+
9
$[$&$

&%'
$
99
Payments
This ERD (shown in Figure 42) illustrates the support for payments provided in the Siebel Data Model.
The payment entity supports payments made by customers to the company, as well as payments
made by the company to customers, vendors, or others. A payment may be made to directly settle
an order or to settle one or more Invoices. An invoice may be paid through one or more payments.
A payment may be taken as a deduction from a prepayment balance available to the paying party.
Table 41.
Payments ERD Entities and Tables
Entity
Table
Address
S_ADDR_ORG
Invoice
S_INVOICE
Order
S_ORDER
Organization Unit
S_ORG_EXT, S_PARTY
Party
S_PARTY
Payment
S_SRC_PAYMENT
Person
S_CONTACT, S_PARTY
Prepayment Balance
S_PREPAY_BAL
100
Figure 42. Payments

Title : Payments
Author :Oracle, Confidential
INVOICE
PAYMENT
in settlement of
paid by
generated for
INBOUND PAYMENT
billed via
in settlement of
ORDER
paid by
received from
debited from
source of
OUTBOUND PAYMENT
PREPAYMENT
BALANCE
ADDRESS
addressed to
available to
used in
paid to
addressed to
for
located at
receiver of
PARTY
entitled to
PERSON
source for
receiver of
ORGANIZATION UNIT
OTHER
ORGANIZATION
ACCOUNT
10 1
Performance Review
This ERD (shown in Figure 43) illustrates how the Siebel Data Model supports employee performance
reviews. Review templates of various types (such as annual review, periodic review, customer
satisfaction, MBO, KSO, and service level) can be specified to contain one or more Components (such
as shared objectives, training plan, rollup, 360-degree evaluation, individual objectives, and skills).
Components may be made up of standard review metrics. The performance review can then be
created for a given employee and employee-specific objectives can be defined. At the end of the
review period, the performance review can be completed and ratings given for assigned objectives
and for the standard review metrics. Different rating scales can be defined and used for different
types of reviews. Review templates can be specified for different job families and internal
organizations. An employee may optionally be separately reviewed for performance in each of his or
her assigned Positions.
This diagram also illustrates how the Siebel Data Model supports employee performance review by
other employees within an organization. These employees can be employees at the same level, a
higher level, or a lower level who may provide performance reviews for an employee to the manager
of that employee. A set of evaluation questions can be defined and associated with different sets of
employees. The reviewers answer the questions to evaluate the performance of the employee.
Table 42.
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
102
Table 42.
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
10 3
104

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 43. Performance Review
Personal Account
This ERD (shown in Figure 44) 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 43.
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
10 5
Figure 44. 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
106
Personal Financial Review

This ERD (shown in Figure 45) illustrates the information captured during the process of reviewing
the financial status of an individual customer. The financial review process itself is tracked as an
activity and becomes the source of the rest of the personal financial information of the contact,
including assets, liabilities, income, expenses, and financial needs (such as retirement savings).
When the financial needs of the contact are not fully addressed by his or her current financial product
holdings, assets, or liabilities, the salesperson makes one or more financial recommendations. When
a financial recommendation leads to a purchased product, such as a savings account or mortgage,
the product instance can be associated with the recommendation that led to it. Assets may be located
at a personal address and may be a source of income. Similarly, a liability, such as a mortgage, may
be secured by an associated asset and may have periodic expenses associated with the liability.
Table 44.
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
S_ORG_GROUP, S_PARTY
Income (Expense)
S_FN_INCM_EXP
Income (Expense) Contact
S_FN_INCM_EXP_CON
Need Contact
S_FN_NEED_CON
Opportunity
S_OPTY
Organization Unit
S_ORG_EXT, S_PARTY
Product
S_PROD_INT
Product Instance
S_ASSET
Product Instance Contact
S_ASSET_CON
Received Product Instance
S_FN_RCMD_ASSET
Recommendation Contact
S_FN_RCMD_CON
10 7
108
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 45. Personal Financial Review
Pricing Comparison
This ERD (shown in Figure 46) 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 45.
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
10 9
Figure 46. 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

based on
used by
for
for
have types
of
110
classification
for
OBJECT CLASS
described
by
for
PRICING MATRIX
parent class of
Pricing
This ERD (shown in Figure 47) illustrates the pricing capabilities of Siebel Business Applications,
including price lists, pricing matrices, and pricing models, and how they are related to simple and
complex products or services to be priced. A price list is made up of price list items, each of which
tracks the price for a given product or service. The list prices may be adjusted for certain extended
attributes as defined in a specified pricing matrix. They may be adjusted based on changes to a
customizable product through component price adjustments. They may also be modified through a
specified pricing model made up of pricing factors.
Table 46.
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
11 1
112
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 47. Pricing
Product Promotion
Product Promotion (shown in Figure 48) 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 47.
Product Promotion ERD Entities and Tables
Entity
Table
Conditional Charge Prorate Plan
S_AGR_PR_PLAN
Product Promotion
S_PROD_INT
Product Promotion Charge
S_PROM_CHRG
Product Promotion Item
S_PROM_ITEM
Product Promotion Item Attribute
S_PROM_ITEM_XA
Product Promotion Item Attribute Value
S_PROMITM_VAL
Product Promotion Pricing Matrix Rule
S_PROM_PMTRX
Product Promotion Term
S_PROMITM_TRMS
Product Promotion Term Description
S_PROD_TRM_DESC
11 3
114
child of
has
parent of
contain
PRODUCT PROMOTION
PRODUCT
made up
PRODUCT PROMOTION ITEM
root of
define for
PRODUCT PROMOTION ITEM ATTRIBUTE
has
define for
PRODUCT PROMOTION ITEM ATTRIBUTE

VALUE
Title : PRODUCT PROMOTION

child of
has
has
has
define for
PRODUCT PROMOTION TERM
define for
PRODUCT PROMOTION CHARGE
define for
contain
associate by
associate to
PRODUCT PROMOTION PRICING MATRIX RULE for
has
define for
PRODUCT PROMOTION TERM

DESCRIPTION
CONDITIONAL CHARGE
PRORATA PLAN
ADJUSTMENT GROUP
Figure 48. Product Promotion
Product Quality Tracking

This ERD (shown in Figure 49) illustrates the significant entities related to product defect tracking.
Defects can be associated with service requests and may have associated activities defined to fix the
defect. Associations may be defined with various product or product versions to record which are
affected by the defect, which are planned to fix the defect, and which actually fix the defect.
Additional relevant associations with external products may be recorded. Defects may be associated
with other, related defects.
Table 48.
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
11 5
116

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 49. Product Quality Tracking
Product Recommendation (shown in Figure 50) provides a system for managing product
recommendations for up-sell or cross-sell. Product Recommendation allows the user to clearly define
the messages, the set of possible responses, and the recommendation itself.
Table 49.
Product Recommendation ERD Entities and Tables
Entity
Table
Communication
S_COMMUNICATION
Product Message
S_PROD_MSG
Product Message Response
S_PROD_MSG_RESP
Product Message Variable
S_PROD_MSG_VAR
Product or Service
S_PROD_INT
S_PROD_RECMNDTN
11 7
Figure 50. Product Recommendation

Title : Product Recommendation
PRODUCT
recommendation for
RECOMMENDATION
PRODUCT OR SERVICE
recommended via
for
subject of
displayed via
PRODUCT MESSAGE
template for
PRODUCT MESSAGE
VARIABLE
defined for
utilize
have
for
COMMUNICATION
have
actual response for
118
PRODUCT MESSAGE
RESPONSE
Products or Services
This ERD (shown in Figure 51) 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 50.
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
Vendor
S_ORG_EXT, S_PARTY
11 9
120
a collection of

CATALOG
made up of
for
EXTERNAL PRODUCT OR SERVICE
categorized in
PRODUCT OR SERVICE
part of
child of
translation for
parent to
a
component
of
for
described
via
of
constrained
by
PRODUCT
STRUCTURE
valid for
translation for
subject
of
for
of
translated
into
translated
into
translation
for
VENDOR
a report to
a parent to
CLASS OF PRODUCT OR
SERVICE
producer of
produced by
classified in
a classification for
subject of
of
translation for
CLASS ATTRIBUTE
basis for
based on
PRODUCT OR SERVICE
ATTRIBUTE
subject
of
PRICE
LIST
composed of
of
PRICE LIST ITEM
defined for
PRODUCT ASSEMBLY
PORT
translated into
translation for
an
assembly
of
translated into
part of
CATALOG CATEGORY
translated into
composed of
PRODUCT
LINE
part of
LANGUAGE
Title : Products or Services

Figure 51. Products or Services
Professional Services
This ERD (shown in Figure 52) 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 51.
Professional Services ERD Entities and Tables
Entity
Table
Activity
S_EVT_ACT
Address
S_ADDR_ORG
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
12 1
122
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 52. Professional Services
Revenue
This ERD (shown in Figure 53) illustrates how revenue items are tracked and analyzed in Siebel
Business Applications. Revenue Items may be defined for any number of confirmed or likely business
transactions such as opportunities, accounts, projects, marketing events or activities, agreements,
invoices, and so on. Revenue is generally attributed to a product, service, product line, or some
description of the product or service offering. Credit for the revenue can be spread across sales team
members by breaking the revenue into a line for each sales team member with their credit amounts.
Recurring or incoming revenues over a period of time (weeks, months, or years) can be shown by
using the revenue schedule capabilities. A revenue template with detailed items can be created for
this purpose.
Table 53.
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
12 3
124
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 53. 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 (shown in
Figure 54) 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 54.
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
12 5
126
validated by
SALES HIERARCHY
RULE TYPE
subject of
categoried by
VALIDATION RULE
CREDIT RULE CRITERIA
characterized by
subject of
parent of
version of
recipient of
recipient of
recipient of
approve
approved by
approve
assigned to
approve
assigned territory
OTHER PARTY
POSITION
PARTY
approved by approve
approved by
HIERARCHY
VERSION
versioned by
composed of
part of
assignment of
POSITION TERRITORY ASSIGNMENT
HIERARCHY VERSION
TERRITORY
assigned to
transfer to
rollup to
allocated to
approved
consists of
applicable to
version of
belongs to
subordinate to
consists of
allocation of
CREDIT ASSIGNMENT
RULE
subject of
CREDIT ALLOCATION
SALES TERRITORY
characterized by
defined for
applied to
defined for
CREDIT RULE CRITERIA

VALUE
Title : Sales Hierarchy and Credit Assignment

Figure 54. Sales Hierarchy and Credit Assignment
Sales Portfolio Management

This ERD (shown in Figure 55) 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 55.
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
12 7
128
!&
**$
14
14

2

1
*'

+

@

*'
$
"

14

13
9
&$
$

$[$
"

$[$
&$

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

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

*'!&
**$

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

$
% "
Oracle
Figure 55. Sales Portfolio Management
Service Agreement
This ERD (shown in Figure 56) illustrates how Siebel Business Applications support service
agreements. A service agreement is a contract that entitles one or more contacts at one or more
organizations to service or support on one or more items through entitlements. Entitlement items
define coverage of products or specified instances of a product. The entitlement can be constrained
by a service calendar (to indicate 24x7 coverage, for example), and may be subject to one or more
metrics (that describe a guaranteed two-hour response, for example).
Table 56.
Service Agreement ERD Entities and Tables
Entity
Table
Account
S_ORG_EXT, S_PARTY
Agreement
S_DOC_AGREE
Agreement Entitlement
S_ENTLMNT
Agreement Item
S_AGREE_ITEM
Asset
S_ASSET
Contact
S_CONTACT, S_PARTY
Entitled Product or Asset
S_ENTLMNT_ITEM
Entitled Service
S_ENTL_ACT_TYPE
Expense Type
S_EXP_ITEM_TYPE
Material
S_PROD_INT
Order
S_ORDER
Preventive Maintenance
S_PM_PLNITM
Price Adjustment
S_ENTL_PRDPRI
Product
S_PROD_INT
Service Calendar
S_SCHED_CAL
Service Metric
S_SVC_METRIC
Service Request
S_SRV_REQ
Work Type
S_PROJ
12 9
130

basis for
entitled by
basis for
entitled by
basis for
based on
for
of
basis for
ACTION
TYPE
for
basis
for
covered by
used by
constrained by
for
for
made up of
part of
covered by
with
subject of
made
into
an
instance
of
subject of
for
subject of
ACCOUNT
subject of
employer of
employed at
for
for
ASSET
subject of
subject of
for
SERVICE
CALENDER
CONTACT
AGREEMENT
part of
AGREEMENT
ITEM
AGREEMENT
ITEM RENEWAL
TERM
made up of
basis for
based on
based on
ENTITLED PRODUCT OR ASSET
based on
PRICE ADJUSTMENT
AGREEMENT ENTITLEMENT
defined for
ENTITLED
SERVICE
suject of
basis for
based on
billable as
billable for
billable as
billable for
billable as
billable for
PREVENTIVE
MAINTENANCE
SERVICE
METRIC
ORDER
SERVICE
REQUEST
MATERIAL
WORK
TYPE
EXPENSE
TYPE
Title : Agreement Entitlement

PRODUCT
Figure 56. Service Agreement
Service Calendars and Work Shifts

This ERD (shown in Figure 57) 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 57.
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
13 1
Figure 57. 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
SERVICE CALENDAR
EMPLOYEE /
AGENT
assigned to
WORK SHIFT
worked by
manager of
132
EXCEPTION
CALENDAR
a report to
for
of
Service Request
This ERD (shown in Figure 58) 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 58.
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
13 3
134
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 58. Service Request
Shipment
This ERD (shown in Figure 59) 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 59.
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
13 5
136

13

1

3
1
1
1

7&

7&'$"

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

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

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

%
Oracle

!&
$$'

Figure 59. Shipment
Siebel Assistant
This ERD (shown in Figure 60) 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 60.
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
13 7
138
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 60. Siebel Assistant
Territory Management
This ERD (shown in Figure 61) 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 61.
Territory Management ERD Entities and Tables
Entity
Table
Account
S_ORG_EXT
Account Team Member
S_ACCNT_POSTN
Account/Terr Mapping
S_TERR_ACCNT
Asset
S_ASSET
Asset Team Member
S_ASSET_POSTN
Asset/Terr Mapping
S_TERR_ASSET
Business Unit
S_BU
Contact
S_CONTACT
Contact/Terr Mapping
S_TERR_CON
Contact Team Member
S_POSTN_CON
Division
S_ORG_EXT
Geo/Terr Mapping
S_TERR_ZIP, S_TERR_REGION
Position
S_POSTN
Position Territory Assignment
S_TERR_POSITION
Region
S_REGION
Territory
S_TERRITORY
Territory Hierarchy
S_TERR_HIER
Territory Version
S_TERRHIER_NODE
Zipcode
(None)
13 9
140
%$
13
%%

$
13
&$

13
13

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

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

%$+
%%
$"$
3"
Oracle

!>%$

$

9!>%$

13

1
%'%*

.&%$%%&$

+
9 9+

2

@13

9 '
[ !
+
>%$

0
"$

%%0
"$

&$0
"$
13
+

Figure 61. Territory Management
Territory Quota Rollup

This ERD (shown in Figure 62) 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 62.
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
Contact /Terr Mapping
S_TERR_CON
Account / Terr Mapping
S_TERR_ACCNT
Geo/Terr Mapping
S_TERR_REGION, S_TERR_ZIP
Terr/Qta/Geo
S_TERR_QTA_REGN, S_TERR_QTA_ZIP
Terr/Qta/Con
S_TERR_QTA_CON
Terr/Qta/Accnt
S_TERR_QTA_ACCT
Accnt Quota Credit
S_TRQT_ACC_CRDT
Contact Quota Credit
S_TRQT_CON_CRDT
Geo Quota Credit
S_TRQT_REGNCRDT, S_TRQT_ZIP_CRDT
Period Quota
S_QTA_PD_BRKDN
Terr Quota Breakdown
S_TRQT_PD_BRKDN
14 1
142
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 62. Territory Quota Rollup
Textile, Apparel, and Footwear

This ERD (shown in Figure 63) illustrates how Siebel Business Applications support the assortment
planning process in the textile, apparel, and footwear industries. A retailer can define the products
that are sold in each season, then associate each product with one or more market segments to
define recommended product assortments. Rather than complicating the assortment by specifying
product entries for each combination of one or two attributes in which a style is manufactured (such
as size or color), the attributes can be specified through a seasonal or nonseasonal product option
range (for example, a shirt size range of S, M, L, and XL). The retailer can then further specify
recommended product option mixes that indicate the proportion of each product option attribute
value to deliver when ordering a style (for example, a mix preference of 20% S, 30% M, 30% L, and
20% XL), or each retail customer can create its own mix preferences. When creating an assortment
plan for a season, the retail customer chooses the styles from the recommended product assortment
for the season, modifies the assortment to fit its customers, and chooses the desired product option
mix for each product option. The total ordered quantity of each style is then further broken down
into the quantity to be delivered in each subperiod within the season (for example, each week in the
season). This assortment plan can then serve as a guideline for ordering throughout the season or
even facilitate the generation of orders in each delivery period in the season.
The shaded subtypes in this diagram indicate examples of the types of data that may be found within
a supertype. They are not intended to indicate strict subtypes.
Table 63.
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
14 3
144
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 63. Textile, Apparel, and Footwear
Time Sheet
This ERD (shown in Figure 64) 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 64.
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
14 5
146
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 64. Time Sheet
Trade Promotions
This ERD (shown in Figure 65) 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 65.
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
14 7
148

?13
14

14
!& $$'
!&

9"<$

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

2
2

!& 8$'

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

*&$!
'' $

13
!"

Oracle
$
%$

14

6
&$

14
9
$
!
$

3

Figure 65. Trade Promotions
Training Curriculum Course

This ERD (shown in Figure 66) illustrates the entities and relationships relevant to the training
business function. A training curriculum is made up of one or more training courses, which are
offered through one or more course offerings. Both courses and curriculums target one or more
audience types and have literature associated with them. A person can be registered for one or more
course offerings. Tests that may be defined for one or more course offerings, including test questions
and possible answers. Tests taken by an Individual contain the answer given by that person to each
question and the score achieved by that person for each question.
Table 66.
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
14 9
150

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 66. Training Curriculum Course
Training Test Engine

This ERD (shown in Figure 67) illustrates the entities and relationships relevant to the training test
engine business function. Tests may be defined for one or more course offerings, or for one or more
courses, including test questions and possible answers, and may be available in one or more
languages. Each test question can be either determined in advance or pulled from a question pool at
run time. Tests taken by an Individual contain the exact question presented to the individual, the
individual's answer to each question, and the score achieved by that person for each question. It also
keeps track whether the question has been attempted.
Table 67.
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
15 1
152
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 67. Training Test Engine
Versioned Object Definition

Versioned Object Definition (shown in Figure 68) 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 68.
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
15 3
154
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 68. Versioned Object Definition
Warranty
This ERD (shown in Figure 69) illustrates how Siebel Business Applications tracks product warranty
coverages. Warranty coverage is provided by an organization (often the vendor of the product) and
covers one or more products that are part of a covered product line. The products covered under the
warranty coverage may be specified directly through product warranty coverage entries or indirectly
through product line warranty coverages (which specifies coverage for the products that compose
the product line). Warranty service may be provided by one or more authorized service providers.
The various warranty coverages applicable to an asset throughout its life are tracked, and may be
applied to fully or partially compensate the service provider for service requested in a service order.
Table 69.
Warranty ERD Entities and Tables
Entity
Table
Asset
S_ASSET
Asset Warranty Coverage
S_ASSET_WRNTY
Order
S_ORDER
Order Item
S_ORDER_ITEM
Organization Unit
S_ORG_EXT, S_PARTY
Product
S_PROD_INT
Product Line
S_PROD_LN
Product Line Warranty Coverage
S_PRDLN_WRNTY
Product Warranty Coverage
S_PROD_WRNTY
Warranty Coverage
S_WRNTY_CVRG
Warranty Service Provider
S_WRNTY_SRV_ORG
15 5
156
part of
provided by
subject of
role played by
of
OTHER ORDER
ORGANIZATION UNIT
by
PRODUCT
WARRANTY
COVERAGE
subject of
made up of
of
WARRANTY COVERAGE
by
ASSET
WARRANTY
COVERAGE
made up of
applied to
claimed against
SERVICE ORDER
WARRANTY SERVICE
PROVIDER
ORDER
composed of
ORDER ITEM
Title : Warranty
by
warrantor of
provided by
of
subject of
made into
PRODUCT LINE
WARRANTY
COVERAGE
an instance of
made up of
of
ASSET
subject of
part of
made up of
PRODUCT
LINE
composed of
PRODUCT
a part of
vendor of
vended by
Figure 69. Warranty
Physical Model
The Siebel physical model encompasses the tables, their columns, and their indexes. This chapter
covers the following topics.
Data Model Naming Conventions on page 157
Data Model Type Definitions on page 160
Columns of Numeric Physical Type on page 164
Siebel System Fields on page 164
INTEGRATION_ID Columns on page 165
Include Only Field on page 165
Siebel Repository on page 165
Database Schema Version on page 166
Limit Checking for Data Types on page 166
Validating the Siebel Schema on page 166
Party Model Unifies Access to Data on page 167
Generating a Report about Tables on page 167
Data Model Naming Conventions

This topic describes:
Table Naming Conventions
Index Naming Conventions on page 159
Column Naming Conventions on page 159
Abbreviations Used in the Physical Model Listings on page 160
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.
15 7
Physical Model Data Model Naming Conventions
SUFFIX
A supertype name may be followed by the entity subtype. For example, the supertype
EVT (event) has ACT (activity) as one of its subtypes. Thus, the name becomes
S_EVT_ACT.
The prefix indicates the part of the Siebel schema to which a table belongs. Table 70 provides some
of the prefixes and their descriptions.
Table 70.
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 71 provides some of the suffixes and their descriptions.
Table 71.
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.
158
Physical Model Data Model Naming Conventions
Index Naming Conventions

Indexes are named the same as the table on which they are created plus a one- to four-character
suffix as shown in Table 72.
Table 72.
Standard Index Suffixes
Suffix
Value
Unique or
Not Unique
_F#
Foreign key index.
Not unique
_P#
Primary key index.
Unique
_U#
Primary key index of the user.
Unique
_V#
Special routing visibility rule index; usually on primary child

foreign key and system foreign key columns not ordinarily
indexed (for example, primary address, primary contact, creator,
and so on).
Not unique
_M#
Miscellaneous index. Any index that does not fit into one of the
above categories.
Not unique
CAUTION: Before modifying or deleting indexes, create a service request (SR) on OracleMetaLink 3.
Modifying or deleting indexes can negatively affect the performance of Siebel Business Applications
and may render it unusable.
Alternatively, you can phone Global Customer Support directly to create a service request or get a
status update on your current SR. Support phone numbers remain the same and are listed on
OracleMetaLink 3.
Column Naming Conventions

Suffixes are used to indicate columns that must contain specific values. Table 73 shows the standard
suffixes for column names and their possible values.
Table 73.
Standard Column Suffixes
Suffix
Value
_AMT
This column contains a currency amount.
_CD
The column value is based on the contents of the List of Values (LOV).
_DT
This column contains a date or datetime value.
_FLG
This column contains a Boolean value where Y indicates Yes or True; N indicates No
or False.
_ID
This column contains ROW_ID values.
_NUM
This column contains a number or an identifying alphanumeric value.
15 9
Physical Model Data Model Type Definitions
Table 73.
Standard Column Suffixes
Suffix
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 may use the abbreviations shown in Table 74.
Table 74.
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 79 on page 164.
Data Model Type Definitions

This topic contains the following type definitions:
Table Type Definitions on page 161
Table Status Definitions on page 162
Column Type Definitions on page 163
Domain Type Definitions on page 163
160
Table Type Definitions

Table 75 provides descriptions of the types of tables in the Siebel database.
Table 75.
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.
16 1
Table 75.
Table Types in the Siebel Database
Table Type
Description
External
External tables are tables that reside outside the Siebel database. The Siebel
object manager provides some support for accessing data in these tables
through business components. In Siebel Tools, the Table object type has
properties that support external tables.
Interface
Interface tables are EIM tables, which are used when moving data between
the Siebel application and external applications.
Log
Log tables are used to log events. There are three Log tables:
S_DCK_INST_LOG, S_PROC_INST, and S_PROC_INST_LOG.
Repository
Repository tables contain information about the Siebel Repository. Data in

some of these tables may get compiled into the SRF files.
Virtual Table
Virtual tables represent database tables or data in an operating system file

that resides outside the Siebel database. Virtual business components are
defined on these tables.
Warehouse
Warehouse tables are used by Oracle Business Analytics in the Oracle

Business Analytics Warehouse table. These tables have names starting with
'W_'.
NOTE: Tables of the following types: Data(Public), Data(Intersection), Extension(Siebel), and

Extension are designed to hold user data. These tables, as well as some of their columns, are
occasionally marked as obsolete in the comments whenever they are no longer used by the current
version of Siebel Business Applications. The status of the table or column indicates the support that
will be provided for it in future versions of the Siebel database schema, as shown in Table 76.
Table Status Definitions

Table 76 provides descriptions of the types of table status in the Siebel database.
Table 76.
Table Status Definitions
Table Status
Description
Active
Actively used and supported in Siebel Business Applications.
Inactive
Dropped or removed from Siebel Data Model and no longer supported.

Customers must remove every reference to these tables or columns in their
configurations.
EOL
End of Life. Supported as is in this release but will be dropped in a future release
of Siebel Business Applications. Use alternate active tables or columns.
Not Used
Not currently used by Siebel Business Applications, but may be used by

customers.
162
Column Type Definitions

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

Table 78 provides descriptions for the domain types of certain columns in the Siebel database.
Table 78.
Domain Types
Domain
Type
Meaning
Domain Contains
FK
Foreign Key column
The name of the table referenced by this Foreign Key column.
PC
Primary Child
The name of the table in which the Primary Child is found. For
example, an account (S_ORG_EXT) may be associated to
multiple industries (S_INDUST) through the intersection table
S_ORG_INDUST. One of these industries is the primary industry
of the account: column S_ORG_EXT.PR_INDUST_ID points to
the foreign key column INDUST_ID of the primary child table
S_ORG_INDUST (the column S_ORG_INDUST.INDUST_ID is a
foreign key to the base table S_INDUST and so it points to
S_INDUST.ROW_ID).
LOV
List of Values
The intended List of Values type for this column. List of values
types are defined in the table S_LST_OF_VAL accessible
through Siebel Tools: Screens > System Administration > List
of Values.
LOVB
List of Values
Bounded
The List of Values type against which this column is validated.

In the LOVB case, end users must specify a value from the list,
whereas in the LOV case, the user can enter a value not
contained in the list.
16 3
Physical Model Columns of Numeric Physical Type
Table 78.
Domain
Type
Domain Types
Meaning
Domain Contains
MLOV
Multilingual List of
Values
The List of Values type against which this column is validated,

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

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

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

Columns of a numeric physical type must have the properties Precision and Scale set, for example:
Number (22, 7), or Number (10, 0). The first value (22 and 10, in these examples) represents the
precision, which is the total length of the column including the decimal places. The second number
(7 and 0, in these examples) represents the scale, which are the decimal places after the decimal
point. Siebel Tools sets the Length property to 22 by default; Length is a required column in Siebel
Tools, but this property does not play any role in columns of a numeric physical type.

Every Siebel table contains the system fields described in Table 79. Do not alter the contents of these
fields.
Table 79.
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.
164
Physical Model INTEGRATION_ID Columns
Table 79.
Column Name
Description
DB_LAST_UPD
Date and time the record was last changed in the database.
DB_LAST_UPD_SRC
Source of the instance or operation that changed the record in the

database.
LAST_UPD
Date and time the record was last changed.
LAST_UPD_BY
User who last changed record (foreign key to S_USER).
MODIFICATION_NUM
Internally incremented number used for locking and to identify

records for incremental updates of the Siebel Business Data
Warehouse.
ROW_ID
Unique row identifier.
INTEGRATION_ID Columns
Many tables contain a column called INTEGRATION_ID for back office integration. Normally,
customers use this column to store the unique reference identifiers for corresponding records in the
back office application. These columns are currently used by the Siebel SAP R/3 Connector.
The S_ADDR_ORG.INTEGRATION2_ID and INTEGRATION3_ID columns have been created for
integration with Oracle back office applications. The INTEGRATION2_ID column is used to store the
Oracle BILL TO SITE ID, and the INTEGRATION3_ID column is used to store the Oracle SHIP TO SITE
ID.
Include Only Field

Include Only is an index column field, and is either blank or checked. It applies only to DB2. When
checked, it adds the column into the leaf pages of the unique index. This avoids access to table pages
when the column is the only other piece of data retrieved from the table other than the indexed
columns. Included columns do not contribute to the unique constraint.
Siebel Repository
Siebel Business Applications includes a set of tables referred to as the Siebel repository tables. These
tables store the full definition of a given configuration of Siebel Business Applications, including the
database schema and the client configuration. As with other Siebel tables, do not manipulate
information in the Siebel repository tables directly. Instead, use Siebel Tools. For more information
on how to use Siebel Tools, see Using Siebel Tools. To learn more about the information stored in the
repository, see Siebel Object Types Reference.
16 5
Physical Model Database Schema Version
Database Schema Version

Each Siebel Business Applications database installation is stamped with a database schema version.
You can learn the schema version of a Siebel installation by choosing Help > Technical Support from
your Siebel client. The schema version is listed in the format 41.XX.YY.ZZ, where XX, YY, and ZZ are
one or two digit integers.
Limit Checking for Data Types

The Object Manager imposes limit checking on data of specific types to make sure that every input,
regardless of its source, is within specified limits (shown in Table 80). 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 80.
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.
166
Physical Model Party Model Unifies Access to Data
Party Model Unifies Access to Data

The party model is a means of unifying all access to data about relationships. This covers
relationships between your company and people (contacts, employees, partner employees, users)
and other businesses (accounts, divisions, organizations, partners). The base table for all such
access is S_PARTY. Related tables are implicitly joined as extension tables. Table 81 lists the
extension tables and their corresponding EIM interface tables.
Table 81.
S_PARTY Extension Tables and Corresponding EIM Interface Tables
Data Type
Extension Table to S_PARTY
EIM Interface Table
Accounts
S_ORG_EXT
EIM_ACCOUNT
Business Units
S_BU
EIM_BU
Contacts
S_CONTACT
EIM_CONTACT
Employees
S_CONTACT
EIM_EMPLOYEE
Groups
S_ORG_GROUP
EIM_GROUP
Organizations
S_ORG_BU
EIM_ORG_BU
Positions
S_POSTN
EIM_POSITION
Users
S_USER
EIM_USER
Because the extension tables are implicitly joined to S_PARTY, you do not need to configure anything
to access them through S_PARTY. Some data types have a many-to-many relationship. For example,
any contact can be associated with multiple accounts or partners. To model these relationships there
are preconfigured intersection tables: S_PARTY_PER and S_PARTY_REL. Use S_PARTY_REL to
implement relationships between parties in the S_PARTY table. In this case, records in S_PARTY are
both parent (PARTY_ID) and child (PERSON_ID).
Use S_PARTY_PER to implement relationships between members:
Access groups and members
Accounts and contacts
Employees and positions
User lists and users
Generating a Report about Tables

You can generate a report that displays selected properties of each table and lists the columns. The
name, physical type, length, comments, and various other properties are identified for each column.
16 7
Physical Model Generating a Report about Tables
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.
Choose to open, save or cancel the report.
NOTE: For more information about generating reports, see Siebel Reports Administration Guide.
168
Schema Changes
This chapter lists the table, table column and table index changes in this version of the schema:
Table Column Changes in This Version on page 172
Table Index Changes in This Version on page 181

This topic lists the following changes to tables that have been implemented in this version of the
schema:
New Tables in This Version
Changed Tables in This Version on page 171

Table 82 lists tables that are new in this version.
Table 82.
Table
Type
Active
S_ACC_VIEW_APPL
Data (Private)
Yes
S_BR_ACTION
Data (Public)
Yes
S_BR_ACTN_SET
Data (Public)
Yes
S_BR_EXCPTN
Data (Public)
Yes
S_BR_INST
Data (Public)
Yes
S_BULK_REQ
Data (Public)
Yes
S_CHAT_KB_VSTD
Data (Public)
Yes
S_CHAT_LANG_MAP
Data (Public)
Yes
S_CHAT_PARAM
Data (Public)
Yes
S_CHAT_ROUTE
Data (Public)
Yes
S_CHRCTR_IMPT
Data (Public)
Yes
S_COMM_IMPT
Data (Public)
Yes
S_COMM_SVY_LOG
Data (Public)
Yes
16 9
Schema Changes Table Changes in This Version
Table 82.
Table
Type
Active
S_CONTACT_IMPT
Data (Public)
Yes
S_DOC_QUOTE_SPA
Extension (Siebel)
Yes
S_INT_OBJ_DATA
Data (Private)
Yes
S_INT_OBJ_DPLOY
Data (Private)
Yes
S_LEAD
Data (Public)
Yes
S_LEAD_BU
Data (Intersection)
Yes
S_LEAD_IMPT
Data (Public)
Yes
S_LEAD_OPTY
Data (Intersection)
Yes
S_LEAD_POSTN
Data (Intersection)
Yes
S_LEAD_PROD
Data (Intersection)
Yes
S_LEADPROD_IMPT
Data (Public)
Yes
S_LEADRESP_IMPT
Data (Public)
Yes
S_MKT_EVT_TRG
Data (Public)
Yes
S_MKT_IMPRT_TSK
Data (Public)
Yes
S_MKT_IMPT_MAP
Data (Public)
Yes
S_MKT_SRVY
Data (Public)
Yes
S_MKT_STGWAIT
Data (Public)
Yes
S_MKT_STGWT_REL
Data (Public)
Yes
S_MKTEVTRG_HST
Data (Public)
Yes
S_MKTEVTRG_MAP
Data (Intersection)
Yes
S_MKTIMP_CHRCTR
Data (Intersection)
Yes
S_MKTIMPMAP_ITM
Data (Public)
Yes
S_MKTIMPTSK_ARG
Data (Public)
Yes
S_MKTIMPTSK_LOG
Data (Public)
Yes
S_MKTPRG_ACTN
Data (Public)
Yes
S_MKTPRGACT_LST
Data (Intersection)
Yes
S_MKTSVY_A_LANG
Data (Intersection)
Yes
S_MKTSVY_ANSW
Data (Public)
Yes
S_MKTSVY_Q_LANG
Data (Intersection)
Yes
S_MKTSVY_QUES
Data (Public)
Yes
S_MKTSVY_SCTN
Data (Public)
Yes
170
Schema Changes Table Changes in This Version
Table 82.
Table
Type
Active
S_MKTSVYST_QUES
Data (Public)
Yes
S_NOTE_LEAD
Data (Public)
Yes
S_OPTY_DSGN_REG
Extension (Siebel)
Yes
S_ORDER_ACTNSET
Data (Intersection)
Yes
S_ORG_EXT_IMPT
Data (Public)
Yes
S_ORG_RL_PROF
Extension (Siebel)
Yes
S_POS
Data (Public)
Yes
S_POS_BU
Data (Public)
Yes
S_POS_CLAIM_ITM
Extension (Siebel)
Yes
S_POS_ITEM
Data (Public)
Yes
S_PRSPCON_IMPT
Data (Public)
Yes
S_QUOTE_ITM_SPA
Extension (Siebel)
Yes
S_TIMEZONE_DTL
Data (Private)
Yes
S_WEB_SITE
Data (Public)
Yes
S_WEB_SITE_LANG
Data (Public)
Yes
S_WEBSITE_CNTNT
Data (Public)
Yes
S_WEBST_TMPL_RL
Data (Public)
Yes
S_XMLP_REP_IOBJ
Data (Public)
Yes
S_XMLP_REP_TMPL
Data (Public)
Yes
S_XMLP_REPOUTPT
Data (Public)
Yes
S_XMLP_RPT_LANG
Data (Intersection)
Yes
S_XMLP_RPT_VIEW
Data (Intersection)
Yes
Changed Tables in This Version

Table 83 lists a table whose type has changed in this version.
Table 83.
Table with Changed Type
Table
Previous Type
New Type
S_TIMEZONE
Data (Public)
Data (Private)
17 1
Schema Changes Table Column Changes in This Version
Table Column Changes in This Version

This topic lists the following changes to columns that have been implemented in this version of the
schema:
New Table Columns in This Version
Changed Table Columns in This Version on page 181

Table 84 lists table columns that are new in this version. Some column headings are abbreviated as
follows.
Optional = Opt
Length = Len
Precision = Prec
Default = Def
LOV Bound = LOV Bnd
172

COST_CURCY_CD
RESP_VALUE_CD
LEAD_ID
MKT_SRVY_ID
APPROVAL_STATUS_CD
EMAIL_STATUS_CD
LST_EMLADR_UPD_TS
S_COMMUNICATION
S_COMMUNICATION
S_COMMUNICATION
S_COMMUNICATION
S_CONTACT
S_CONTACT
S_CONTACT
NUM_HARD_BNCE
COST_AMT
S_COMMUNICATION
S_CONTACT
ACCNT_REVN_AMT
KEYWORD_STRNG
S_COMM_DTL
S_COMM_IMPT
CURRENT_URL
S_COMM_DTL
ACCNT_POSTN_ID
CLIENT_IP_ADDR
S_COMM_DTL
S_COMM_IMPT
BANNER_AD_STRNG
S_COMM_DTL
REFERRER_USERNAME
CTRL_GRP_FLG
S_CAMP_CON
S_COMM_DTL
ADDRESSEE
S_ADDR_PER
REFERRER_URL
ACTIVE_FLG
S_ADDR_PER
S_COMM_DTL
ADDRESSEE
S_ADDR_ORG
MKT_SRVY_LANG_ID
Column
Table
S_COMM_DTL
Table 84.
Opt
Number
UTC
DateTime
Varchar
Varchar
Varchar
Varchar
Varchar
Varchar
Number
Number
Varchar
Varchar
Varchar
Varchar
Varchar
Varchar
Varchar
Varchar
Char
Varchar
Char
Varchar
Data
Type
22
30
30
15
15
30
20
22
22
15
100
200
100
200
100
100
100
100
Len
10
22
22
Prec
Scale
Def
EMAIL_STATUS
APPROVAL_STATUS
LOV Type
LOV
Bnd
173

Column
NUM_SOFT_BNCE
LOCK_FLG
LOCK_FLG
RULE_SET_TYPE_CD
ALLOCATED_CNT
ALLOCATED_PCT
CTRL_GRP_PCT
PCT_ALLOC_FLG
LAND_SITE_ID
RELAY_EMBED_ID_FLG
ACT_APPT_DURTN_MIN
ACT_CAL_TYPE_CD
ACT_COMMENTS
ACT_COMMENTS_LONG
ACT_DONE_FLG
ACT_OWNER_PER_ID
ACT_PLAN_END_DT
ACT_PLAN_START_DT
ACT_PRIORITY_CD
ACT_PRIV_FLG
ACT_STAT_CD
ACT_TODO_CD
Table 84.
Table
S_CONTACT
1 74
S_CT_APLT_RLST
S_CT_RULE_SET
S_CT_RULE_SET
S_DCP_CALL_LST
S_DCP_CALL_LST
S_DCP_CALL_LST
S_DCP_CALL_LST
S_DCP_URL
S_DCP_URL
S_DMND_CRTN_PRG
S_DMND_CRTN_PRG
S_DMND_CRTN_PRG
S_DMND_CRTN_PRG
S_DMND_CRTN_PRG
S_DMND_CRTN_PRG
S_DMND_CRTN_PRG
S_DMND_CRTN_PRG
S_DMND_CRTN_PRG
S_DMND_CRTN_PRG
S_DMND_CRTN_PRG
S_DMND_CRTN_PRG
Opt
Varchar
Varchar
Char
Varchar
UTC
DateTime
UTC
DateTime
Varchar
Char
Varchar
Varchar
Varchar
Number
Char
Varchar
Char
Number
Number
Number
Varchar
Char
Char
Number
Data
Type
30
30
30
15
1500
100
30
22
15
22
22
22
30
22
Len
22
22
22
10
10
Prec
Scale
Def
LOV Type
LOV
Bnd

REDIRECT_URL_FLG
RESUME_FLG
STRT_ON_LNDPG_FLG
STRT_SVY_BTTN_TEXT
SUBMIT_BTTN_TEXT
TEST_URL_TEXT
TINY_URL_TEXT
TITLE_NAME
S_DMND_CRTN_PRG
S_DMND_CRTN_PRG
S_DMND_CRTN_PRG
S_DMND_CRTN_PRG
S_DMND_CRTN_PRG
S_DMND_CRTN_PRG
S_DMND_CRTN_PRG
S_DMND_CRTN_PRG
TMPL_STATUS_CD
REDIRECT_URL
S_DMND_CRTN_PRG
S_DMND_CRTN_PRG
PUBLISH_TS
MKT_SRVY_ID
S_DMND_CRTN_PRG
S_DMND_CRTN_PRG
LANDGSITE_STAT_CD
S_DMND_CRTN_PRG
OWNER_POSTN_ID
KIOSK_MODE_FLG
S_DMND_CRTN_PRG
S_DMND_CRTN_PRG
DEPLOY_TS
S_DMND_CRTN_PRG
ORIG_CREATOR_ID
CREATED_TS
S_DMND_CRTN_PRG
S_DMND_CRTN_PRG
ACT_TODO_DUE_DT
S_DMND_CRTN_PRG
NEXT_BTTN_TEXT
Column
Table
S_DMND_CRTN_PRG
Table 84.
Opt
Varchar
Varchar
Varchar
Varchar
Varchar
Varchar
Char
Char
Char
Varchar
UTC
DateTime
Varchar
Varchar
Varchar
Varchar
Varchar
Char
UTC
DateTime
UTC
DateTime
UTC
DateTime
Data
Type
30
100
250
250
50
50
250
15
15
50
15
30
Len
Prec
Scale
Def
LANDING_SITE_
STATUS_TYPE
LOV Type
LOV
Bnd
175

Column
APPROVED_QTY
AUTH_COST_AMT
CLAIMED_QTY
PROD_MSRP
PURCH_COST_AMT
ENTLMNT_NUM
LEAD_ID
AREA_CD
CHAT_TRANSCRIPT
EMAIL_ADDR_PRVD
FST_NAME_PRVD
LAST_NAME_PRVD
NEW_EMAIL_PRVD_FLG
NEW_PH_PRVD_FLG
PROBLEM_DESC_TEXT
SUB_AREA_CD
WRAPUP_END_TS
WRAPUP_FEEDBACK_CD
WRAPUP_OUTCOME_CD
WRAPUP_REASON_CD
WRAPUP_START_TS
Table 84.
Table
S_ENTL_PRDPRI
1 76
S_ENTL_PRDPRI
S_ENTL_PRDPRI
S_ENTL_PRDPRI
S_ENTL_PRDPRI
S_ENTLMNT
S_EVT_ACT
S_EVT_COMM
S_EVT_COMM
S_EVT_COMM
S_EVT_COMM
S_EVT_COMM
S_EVT_COMM
S_EVT_COMM
S_EVT_COMM
S_EVT_COMM
S_EVT_COMM
S_EVT_COMM
S_EVT_COMM
S_EVT_COMM
S_EVT_COMM
Opt
UTC
DateTime
Varchar
Varchar
Varchar
UTC
DateTime
Varchar
Varchar
Char
Char
Varchar
Varchar
Varchar
Undefined
Varchar
Varchar
Varchar
Number
Number
Number
Number
Number
Data
Type
30
30
30
30
250
50
50
100
1310
72
30
15
30
22
22
22
22
22
Len
22
22
22
22
22
Prec
Scale
Def
WRAPUP_REASON
WRAPUP_OUTCOME
WRAPUP_FEEDBACK
LOV Type
LOV
Bnd
SELF_ADJ_AMT
TOT_ADJ_BY_SUB_AMT
SUBMIT_TO_PSTN_ID
ACCNT_POSTN_ID
ACCNT_REVN_AMT
IMPRT_TSK_ID
APPROVAL_STATUS_CD
PR_CON_ID
EMAIL_STATUS_CD
LST_EMAILADR_UPD
NUM_HARD_BNCE
NUM_SOFT_BNCE
CMPT_PROD_FLG
DESIGN_REG_FLG
USAGE
CAL_REPEAT_PATTERN
SEBL_USER_GRP_CD
SEBL_USREXTRACT_DT
FUNNEL_STAGE_ID
MUTL_EXCLUSIVE_FLG
PCT_ALLOC_FLG
S_FCST
S_FCST
S_FCSTSER_POSTN
S_LEAD_IMPT
S_LEAD_IMPT
S_MKTG_SRVR_TSK
S_ORG_EXT
S_ORG_EXT
S_PRSP_CONTACT
S_PRSP_CONTACT
S_PRSP_CONTACT
S_PRSP_CONTACT
S_REVN
S_REVN
S_REVN
S_SD_PIM_ROW
S_SD_USER_MAP
S_SD_USER_MAP
S_SRC
S_SRC
S_SRC
PRE_LOAD_TSK_WF_ID
Column
Table
S_SRC
Table 84.
Opt
Varchar
Char
Char
Varchar
UTC
DateTime
Varchar
Varchar
Number
Char
Char
Number
Number
UTC
DateTime
Varchar
Varchar
Varchar
Varchar
Number
Varchar
Varchar
Number
Number
Data
Type
15
15
30
500
22
22
22
30
15
30
15
22
15
15
22
22
Len
10
10
10
22
22
22
Prec
Scale
Def
EMAIL_STATUS
APPROVAL_STATUS
LOV Type
LOV
Bnd
177

Column
PST_LNCH_TSK_WF_ID
PST_LOAD_TSK_WF_ID
RECURRING_FLG
STATUS_CD
WORKITEM_ID_VAL
DESC_TEXT
EFF_END_DT
EFF_START_DT
FILE_AUTO_UPD_FLG
FILE_DATE
FILE_DEFER_FLG
FILE_DOCK_REQ_FLG
FILE_DOCK_STAT_FLG
FILE_EXT
FILE_NAME
FILE_REV_NUM
FILE_SIZE
FILE_SRC_PATH
FILE_SRC_TYPE
INT_OBJ_NAME
NAME
Table 84.
Table
S_SRC
1 78
S_SRC
S_SRC
S_USER
S_WFA_INST_LOG
S_XMLP_REP_TMPL
S_XMLP_REP_TMPL
S_XMLP_REP_TMPL
S_XMLP_REP_TMPL
S_XMLP_REP_TMPL
S_XMLP_REP_TMPL
S_XMLP_REP_TMPL
S_XMLP_REP_TMPL
S_XMLP_REP_TMPL
S_XMLP_REP_TMPL
S_XMLP_REP_TMPL
S_XMLP_REP_TMPL
S_XMLP_REP_TMPL
S_XMLP_REP_TMPL
S_XMLP_REP_TMPL
S_XMLP_REP_TMPL
Opt
Varchar
Varchar
Varchar
Varchar
Number
Varchar
Varchar
Varchar
Char
Char
Char
UTC
DateTime
Char
UTC
DateTime
UTC
DateTime
Varchar
Varchar
Varchar
Char
Varchar
Varchar
Data
Type
100
75
30
255
22
15
200
10
250
15
30
15
15
Len
10
Prec
Scale
Def
USER_STATUS
LOV Type
LOV
Bnd
XLIFF_FL_AU_UPDFLG
XLIFF_FL_DK_REQFLG
XLIFF_FL_DK_ST_FLG
XLIFF_FL_SRC_PATH
XLIFF_FL_SRC_TYPE
XMLP_REP_INTOBJ_ID
ERROR_CD
ERROR_MSG
FILE_AUTO_UPD_FLG
S_XMLP_REP_TMPL
S_XMLP_REP_TMPL
S_XMLP_REP_TMPL
S_XMLP_REP_TMPL
S_XMLP_REP_TMPL
S_XMLP_REPOUTPT
S_XMLP_REPOUTPT
S_XMLP_REPOUTPT
XLIFF_FILE_DATE
S_XMLP_REP_TMPL
S_XMLP_REP_TMPL
XIFF_FILE_DEFR_FLG
S_XMLP_REP_TMPL
XLIFF_FILE_SIZE
SEEDED_FLG
S_XMLP_REP_TMPL
S_XMLP_REP_TMPL
SEARCH_SPEC
S_XMLP_REP_TMPL
XLIFF_FILE_REV_NUM
RPT_UPLOAD_STAT_CD
S_XMLP_REP_TMPL
S_XMLP_REP_TMPL
RPT_HAS_PARAM_FLG
S_XMLP_REP_TMPL
XLIFF_FILE_NAME
REPORT_TYPE_CD
S_XMLP_REP_TMPL
S_XMLP_REP_TMPL
OUTPUT_TYPE
S_XMLP_REP_TMPL
XLIFF_FILE_EXT
Column
Table
S_XMLP_REP_TMPL
Table 84.

N
Opt
Char
Varchar
Varchar
Varchar
Varchar
Varchar
Char
Char
Char
Number
Varchar
Varchar
Varchar
UTC
DateTime
Char
Char
Varchar
Varchar
Char
Varchar
Varchar
Data
Type
250
30
15
30
255
22
15
200
10
1000
30
30
30
Len
10
Prec
Scale
Def
XMLP_RPT_SYNC_YE
SNO
LOV Type
LOV
Bnd
179

Column
FILE_DATE
FILE_DEFER_FLG
FILE_DOCK_REQ_FLG
FILE_DOCK_STAT_FLG
FILE_EXT
FILE_NAME
FILE_REV_NUM
FILE_SIZE
FILE_SRC_PATH
FILE_SRC_TYPE
GEN_DATE
NAME
OWNER_ID
SEQ_NUM
STATUS_CD
REPORT_ID
Table 84.
Table
S_XMLP_REPOUTPT
1 80
S_XMLP_REPOUTPT
S_XMLP_REPOUTPT
S_XMLP_REPOUTPT
S_XMLP_REPOUTPT
S_XMLP_REPOUTPT
S_XMLP_REPOUTPT
S_XMLP_REPOUTPT
S_XMLP_REPOUTPT
S_XMLP_REPOUTPT
S_XMLP_REPOUTPT
S_XMLP_REPOUTPT
S_XMLP_REPOUTPT
S_XMLP_REPOUTPT
S_XMLP_REPOUTPT
S_XMLP_RPT_VIEW
Opt
Varchar
Varchar
Number
Varchar
Varchar
UTC
DateTime
Varchar
Varchar
Number
Varchar
Varchar
Varchar
Char
Char
Char
UTC
DateTime
Data
Type
15
30
22
15
100
30
255
22
15
200
10
Len
10
10
Prec
Scale
Def
LOV Type
LOV
Bnd
Schema Changes Table Index Changes in This Version
Changed Table Columns in This Version

Table 85 lists table columns that have changed in this version.
Table 85.
Table Columns That Have Changed in This Version
Table
Column
Type of
Change
Previous
Value
New
Value
S_AUDIT_ITEM
ITEM_IDEN_NUM
Default
S_INST_UPG_HIST
ADDL_LANG_INSTALED
Length
50
100
S_RT_SVC
NAME
Length
30
75
S_RT_SVC_METH
NAME
Length
30
75
S_RT_SVC_M_ARG
NAME
Length
30
75
S_TIMEZONE
UTC_OFFSET
Optional
No
Yes
S_XMLP_REP_TMPL
INT_OBJ_NAME
Optional
No
Yes
S_XMLP_RPT_VIEW
VIEW_ID
Active
No
Yes
Table Index Changes in This Version

This topic lists the following changes to table indexes that have been implemented in this version of
the schema:
New Table Indexes in This Version on page 181
Changed Table Indexes in This Version on page 183
Table Indexes That Were Deleted from This Version on page 183
New Table Indexes in This Version

Table 86 lists table indexes that are new in this version. Some column headings are abbreviated as
follows:
A indicates Active
U indicates Unique
Table 86.
Table Indexes That are New in This version
Table
Index
Columns
S_ASSET
S_ASSET_M7
(STATUS_CD,REGISTERED_DT)
S_CAMP_CON
S_CAMP_CON_M3
(CAMP_LD_WAVE_ID,BATCH_NUM,
MARK_FOR_DEL_FLG,STAT_CD)
18 1
Table 86.
Table Indexes That are New in This version
Table
Index
Columns
S_COMMUNICATION
S_COMMUNICATN_F19
(MKT_SRVY_ID)
S_COMMUNICATION
S_COMMUNICATN_F20
(LEAD_ID)
S_CONTACT
S_CONTACT_M24
(PRIV_FLG,LAST_NAME,FST_NAME)
S_DCP_URL
S_DCP_URL_F1
(LAND_SITE_ID)
S_DMND_CRTN_PRG
S_DMND_CRTNPRG_F18
(MKT_SRVY_ID)
S_DMND_CRTN_PRG
S_DMND_CRTNPRG_F19
(BU_ID)
S_DMND_CRTN_PRG
S_DMND_CRTNPRG_F20
(OWNER_POSTN_ID)
S_DMND_CRTN_PRG
S_DMND_CRTNPRG_F21
(ORIG_CREATOR_ID)
S_DMND_CRTN_PRG
S_DMND_CRTNPRG_F22
(ACT_OWNER_PER_ID)
S_EVT_ACT
S_EVT_ACT_F42
(LEAD_ID)
S_EVT_ACT
S_EVT_ACT_F43
(SRC_EVT_REG_ID)
S_EVT_FUL_REQ
S_EVT_FUL_REQ_F16
(EVTLOC_ID)
S_FCSTSER_POSTN
S_FCSTSER_POSTN_F3
(SUBMIT_TO_PSTN_ID)
S_MDF
S_MDF_F9
(OWNER_ID)
S_MDF
S_MDF_F10
(REGION_ID)
S_MKTG_SRVR_TSK
S_MKTG_SRVR_TSK_F8
(IMPRT_TSK_ID)
S_SRC
S_SRC_F40
(PST_LNCH_TSK_WF_ID)
S_SRC
S_SRC_F41
(PRE_LOAD_TSK_WF_ID)
S_SRC
S_SRC_F42
(FUNNEL_STAGE_ID)
S_SRC
S_SRC_F43
(PST_LOAD_TSK_WF_ID)
S_XMLP_REP_TMPL
S_XMLP_REP_TMPL_F1
(XMLP_REP_INTOBJ_ID)
S_XMLP_REP_TMPL
S_XMLP_REP_TMPL_P1
(ROW_ID)
S_XMLP_REP_TMPL
S_XMLP_REP_TMPL_U1
(NAME,CONFLICT_ID)
S_XMLP_REPOUTPT
S_XMLP_REPOUTPT_F1
(OWNER_ID)
S_XMLP_REPOUTPT
S_XMLP_REPOUTPT_P1
(ROW_ID)
S_XMLP_REPOUTPT
S_XMLP_REPOUTPT_U1
(NAME,GEN_DATE,OWNER_ID,
SEQ_NUM,CONFLICT_ID)
S_XMLP_RPT_VIEW
S_XMLP_RPT_VIEW_F1
(VIEW_ID)
S_XMLP_RPT_VIEW
S_XMLP_RPT_VIEW_F2
(REPORT_ID)
S_XMLP_RPT_VIEW
S_XMLP_RPT_VIEW_P1
(ROW_ID)
S_XMLP_RPT_VIEW
S_XMLP_RPT_VIEW_U1
(VIEW_ID,REPORT_ID, CONFLICT_ID)
182
Changed Table Indexes in This Version

No table indexes have changed in this version.
Table Indexes That Were Deleted from This Version

Table 87 lists a table index that has been deleted from this version.
Table 87.
Table Index
Table Name
Index
Columns
S_SD_SYNC_INFO
S_SD_SYNC_INFO_M4
(SEQ_ID)
18 3
184
Index
about
34
diagram
35
tables
34
competency management system ERD
about
36
diagram
37
tables
36
Consumer Sector
CG promotion planning ERD
29
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
Customer Data Item, about
44
account ERD
about
18
diagram
20
support for Dynamic Hierarchy
18
support for Global Account Views
18
tables
18
adjustment group ERD
about
21
diagram
22
tables
21
apparel
See textile, apparel, and footwear ERD
asset management ERD
about
23
diagram
24
tables
23
tracking asset instances
23
auction ERD
about
25
diagram
26
tables
25
auto email response generator ERD
about
27
diagram
28
tables
27
C
campaign management
See marketing campaign ERD
about
29
diagram
31
tables
29
columns
domain type definitions
163
INTEGRATION_ID columns, about
165
naming conventions
159
numeric physical type
164
type definitions
163
Communications, Media, Energy
pricing comparison ERD
109
compensation planning administration ERD
about
32
diagram
33
tables
32
compensation planning execution ERD
data (intersection) table type

about
161
obsolete, table marked as
161
data (private) table type, about
161
data (public) table type
about
161
obsolete, table marked as
161
data types
limit checking
166
data visibility ERD
about
44
diagram
46
tables
44
Database Marketing, marketing program
ERD
83
database schema version number, finding
and format
166
defect tracking
See product quality tracking ERD
18 5
Index E
design
See schema
163
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
competency management system ERD
employee KPI ERD
49
performance review ERD
102
employees
field service scheduler ERD
55
time sheet ERD
145
entitlement items, service agreement
ERD
129
ERDs
account, diagram
20
account, tables
18
adjustment group, diagram
22
adjustment group, tables
21
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
CG promotion planning, diagram
31
CG promotion planning, tables
29
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
186
34
36
27
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
11
data visibility, diagram
46
data visibility, tables
44
Dun & Bradstreet integration, diagram
48
Dun & Bradstreet integration, tables
47
employee KPI, diagram
50
employee KPI, tables
49
exclusive arc relationship, diagram
conventions
12
expense reports, diagram
52
expense reports, tables
51
field service inventory, diagram
54, 56
field service inventory, tables
53
field service scheduler, tables
55
forecasts, diagram
58
forecasts, tables
57
general diagram conventions
12
high tech marketing development fund,
diagram
60
high tech marketing development fund,
tables
59
invoicable charges, diagram
62
invoicable charges, tables
61
invoices, diagram
64
invoices, tables
63
lead management, diagram
67
lead management, tables
65
marketing budget request, diagram
69
marketing budget request, tables
68
marketing campaign, diagram
71
marketing campaign, tables
70
marketing collaboration, diagram
73
marketing collaboration, tables
72
marketing encyclopedia, diagram
75
marketing encyclopedia, tables
74
marketing event driven dialogue,
diagram
77
marketing event driven dialogue, tables
76
marketing events, diagram
80
marketing events, tables
78
marketing plans, diagram
82
marketing plans, tables
81
marketing program, diagram
85
marketing program, tables
83
marketing resource management: document,
diagram
87
marketing resource management: document,
tables
86
Index F
opportunity management, diagram

89
opportunity management, tables
88
order life cycle, diagram
91
order life cycle, tables
90
orders, diagram
93
orders, tables
92
partner collaboration, diagram
95
partner collaboration, tables
94
partner program registration, diagram
97
partner program registration, tables
96
party model, diagram
99
party model, tables
98
payments, diagram
101
payments, tables
100
performance review, diagram
104
performance review, tables
102
personal account, diagram
106
personal account, tables
105
personal financial review, diagram
108
personal financial review, tables
107
pricing comparison, diagram
110
pricing comparison, tables
109
pricing, diagram
112
pricing, tables
111
product promotion, diagram
114
product promotion, tables
113
product quality tracking, diagram
116
product quality tracking, tables
115
product recommendation, diagram
118
product recommendation, tables
117
products or services, diagram
120
products or services, tables
119
professional services, diagram
122
professional services, tables
121
recursive relationship, diagram
conventions
13
revenue, diagram
124
revenue, tables
123
revision table
14
sales hierarchy and credit assignment,
diagram
126
sales hierarchy and credit assignment,
tables
125
sales portfolio management, diagram
128
sales portfolio management, tables
127
service agreement, diagram
130
service agreement, tables
129
service calendars and work shifts,
diagram
132
service calendars and work shifts,
tables
131
service request, diagram
134
service request, tables
133
shipment, diagram
136
shipment, tables
135
Siebel Assistant, diagram
138
Siebel Assistant, tables
137
territory management, diagram
140
territory management, tables
139
territory quota rollup, diagram
142
territory quota rollup, tables
141
textile, apparel, and footwear,
diagram
144
textile, apparel, and footwear, tables
143
time sheet, diagram
146
time sheet, tables
145
trade promotions, diagram
148
trade promotions, tables
147
training curriculum course, diagram
150
training curriculum course, tables
149
training test engine, diagram
152
training test engine, tables
151
versioned object definition, diagram
154
versioned object definition, tables
153
warranty, diagram
156
warranty, tables
155
exclusive arc relationship
about
12
diagram conventions
12
expense reports ERD
about
51
diagram
52
tables
51
extension (Siebel) table type
about
161
obsolete table marked as
161
extension table type, about
161
F
field service inventory ERD
about
53
diagram
54, 56
tables
53
about
55
tables
55
financial accounts
personal account ERD
105
financial review, personal financial review
ERD
107
footwear
See textile, apparel, and footwear ERD
forecasts ERD
about
57
diagram
58
tables
57
18 7
Index G
G
generating table report
167
Global Account Views, support by account
entity
18
H
high tech marketing development fund ERD
about
59
diagram
60
tables
59
I
Include Only field
165
index column fields
165
index naming conventions
159
insurance
105
invoicable charges ERD
about
61
diagram
62
tables
61
invoices ERD
about
63
diagram
64
tables
63
165
L
lead management ERD
about
65
diagram
67
tables
65
limit checking for data types
logical model
ERD conventions
11
ERD descriptions
14
166
M
Marketing
29
47
forecasts ERD
57
high tech marketing development fund
ERD
59
lead management ERD
65
marketing budget request ERD
68
marketing campaign ERD
70
marketing collaboration ERD
72
marketing encyclopedia ERD
74
marketing event driven dialogue ERD
76
marketing events ERD
78
marketing plans ERD
81
188
marketing program ERD

83
marketing resource management: document
ERD
86
marketing budget request ERD
about
68
diagram
69
tables
68
marketing campaign ERD
about
70
diagram
71
tables
70
marketing collaboration ERD
about
72
diagram
73
tables
72
marketing development funds
See CG promotion planning ERD
about
74
diagram
75
tables
74
marketing event driven dialogue ERD
about
76
diagram
77
tables
76
marketing events ERD
about
78
diagram
80
tables
78
marketing plans ERD
about
81
diagram
82
tables
81
marketing program ERD
about
83
diagram
85
tables
83
marketing resource management: document
ERD
about
86
diagram
87
tables
86
Master Data Item, about
44
MDFs
See CG promotion planning ERD
N
naming conventions
columns
159
indexes
159
physical model listings, abbreviations
used
160
table names
157
Index O
table prefixes
158
table suffixes
158
non-Siebel application products, caution
about inserting or updating data
normalized, defined
9
O
opportunity management ERD
about
88
diagram
89
tables
88
Oracle Applications, about use of
INTEGRATION_ID columns
order life cycle ERD
about
90
diagram
91
tables
90
orders ERD
about
92
diagram
93
tables
92
P
partner collaboration ERD
about
94
diagram
95
tables
94
partner program registration ERD
about
96
diagram
97
tables
96
party model ERD
about
98
diagram
99
tables
98
party model, about
167
party, defined
98
payments ERD
about
100
diagram
101
tables
100
performance review ERD
about
102
diagram
104
tables
102
about
105
diagram
106
tables
105
personal financial review ERD
about
107
diagram
108
tables
107
165
physical model
column naming conventions
159
column type definitions
163
columns of numeric physical type
164
database schema version number, finding and
format
166
163
Include Only field
165
index naming conventions
159
165
limit checking for data types
166
party model, about
167
physical model listings, abbreviations
used
160
Siebel repository tables, about
165
Siebel system fields
164
table naming conventions
157
table report, about
167
table status definitions
162
table type definitions
161
validating Siebel Schema
166
pricing comparison ERD
about
109
diagram
110
tables
109
pricing ERD
about
111
diagram
112
tables
111
product promotion ERD
about
113
diagram
114
tables
113
product quality tracking ERD
about
115
diagram
116
tables
115
product recommendation ERD
about
117
diagram
118
tables
117
products or services ERD
about
119
diagram
120
tables
119
professional services ERD
about
121
diagram
122
tables
121
projects, professional services ERD
121
R
recursive relationship
18 9
Index S
about
13
diagram conventions
13
repository, about Siebel repository
revenue ERD
about
123
diagram
124
tables
123
165
S
Sales
47
forecasts ERD
57
lead management ERD
65
74
opportunity management ERD
88
sales hierarchy and credit assignment ERD
sales portfolio management ERD
127
territory management ERD
139
territory quota rollup ERD
141
sales hierarchy and credit assignment ERD
about
125
diagram
126
tables
125
Sales Hierarchy Module
See sales hierarchy and credit assignment
ERD
sales portfolio management ERD
about
127
diagram
128
tables
127
schema
database schema version number, finding and
format
166
defined
9
166
Service
field service inventory ERD
53
55
invoicable charges ERD
61
invoices ERD
63
products or services ERD
119
service agreement ERD
129
service calendars and work shifts ERD
131
service request ERD
133
warranty ERD
155
service activities, field service scheduler
ERD
55
service agreement ERD
about
129
diagram
130
tables
129
service calendars and work shifts ERD
about
131
190
diagram
132
tables
131
service region, field service scheduler
ERD
55
service request ERD
about
133
diagram
134
tables
133
shipment ERD
about
135
diagram
136
tables
135
Siebel Assistant ERD
about
137
diagram
138
tables
137
Siebel repository, about
165
Siebel SAP R/3 Connector, about use of
INTEGRATION_ID columns
165
Siebel system fields
164
special ERD conventions
exclusive arc relationship
12
recursive relationship
13
system fields
164
T
tables
generating report
167
naming conventions
157
prefix naming conventions
158
suffix naming conventions
158
table status definitions
162
types of
161
territory management ERD
about
139
diagram
140
tables
139
territory quota rollup ERD
about
141
diagram
142
tables
141
tests, training test engine ERD
151
textile, apparel, and footwear ERD
about
143
diagram
144
tables
143
time sheet ERD
about
145
diagram
146
tables
145
trade promotions ERD
about
147
diagram
148
Index V
tables
147
training curriculum course ERD
about
149
diagram
150
tables
149
training test engine ERD
about
151
diagram
152
tables
151
V
166
versioned object definition ERD
about
153
diagram
154
tables
153
W
warranty ERD
about
155
diagram
156
tables
155
work shifts
See service calendars and work shifts ERD
workflow process
19 1
Index W
192

DMR

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

DMR

Transféré par

Droits d'auteur :

Formats disponibles

Siebel Data Model

Copyright 2005, 2008, Oracle. All rights reserved.

Siebel Data Model Reference 1

Chapter 1: Whats New in This Release

Entity Relationship Diagrams and Descriptions

Siebel Data Model Reference Version 8.1

Siebel Data Model Reference Version 8.1

Chapter 4: Physical Model

Table Naming Conventions 157

Data Model Type Definitions

Table Type Definitions 161

Columns of Numeric Physical Type

Database Schema Version

Limit Checking for Data Types

Party Model Unifies Access to Data

Chapter 5: Schema Changes

New Tables in This Version 169

Table Column Changes in This Version

New Table Columns in This Version 172

Table Index Changes in This Version

New Table Indexes in This Version 181

Siebel Data Model Reference Version 8.1

Siebel Data Model Reference Version 8.1

Whats New in This Release

Whats New in Siebel Data Model Reference, Version 8.1

Whats New in Siebel Data Model Reference, Version 8.1

Lead Management on page 65.

Lead management is a new addition to Siebel Marketing that

Marketing Event Driven

This new feature is designed to enable timely communication

Table Changes in This Version

A listing of the table changes in this schema, including the new

Table Column Changes in This

A listing of the column changes in this schema, including the

Table Index Changes in This

A listing of the index changes in this schema, including the new

Siebel Data Model Reference Version 8.1

Whats New in This Release

Siebel Data Model Reference Version 8.1

Data Model Overview

Siebel Data Model Reference Version 8.1

Data Model Overview

Siebel Data Model Reference Version 8.1

Relationships between entities

This information is represented in entity relationship diagrams (ERDs).

Entity Relationship Diagram Conventions

Entity Relationship Diagrams and Descriptions on page 14

Entity Relationship Diagram

General Entities on page 12

Exclusive Arc Relationship on page 12

Recursive Relationship on page 13

Siebel Data Model Reference Version 8.1

Logical Model Entity Relationship Diagram Conventions

General Entity Relationship Diagram Conventions

Exclusive Arc Relationship

Siebel Data Model Reference Version 8.1

Logical Model Entity Relationship Diagram Conventions

Exclusive Arc Relationship Diagram Convention Example

Entity Relationship Example:

Recursive Relationship Diagram Convention Example

Siebel Data Model Reference Version 8.1

Logical Model Entity Relationship Diagrams and Descriptions

Entity Relationship Diagrams and

Entity Relationship Diagrams