Siebel Data Model Reference: Version 8.0, Rev. A May 2008

Siebel Data Model
Reference
Version 8.0, Rev. A
May 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 error-
free. 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. Siebel’s 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: What’s 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 17
Adjustment Group 20
Asset Management 22
Auction 24
Auto Email Response Generator 26
CG Promotion Planning 28
Compensation Planning Administration 31
Compensation Planning Execution 33
Competency Management System 35
Content Management 37
Contract Conditions 39
Contracts 41
Data Visibility 43
Dun & Bradstreet Integration 46
Employee KPI 48
Expense Reports 50
Field Service Inventory 52
Field Service Scheduler 54
Forecasts 56
High Tech Marketing Development Fund 58
High Tech Special Pricing Authorization 60
Invoicable Charges 62
Invoices 64
Marketing Budget Request 66
Marketing Campaign 68
Siebel Data Model Reference Version 8.0, Rev. A 3

Contents ■
Marketing Collaboration 70
Marketing Encyclopedia 72
Marketing Events 74
Marketing Plans 77
Marketing Program 79
Marketing Resource Management: Document 82
Opportunity Management 84
Order Life Cycle 86
Orders 88
Partner Collaboration 90
Partner Program Registration 92
Party Model 94
Payments 96
Performance Review 98
Personal Account 101
Personal Financial Review 103
Pricing Comparison 105
Pricing 107
Product Promotion 109
Product Quality Tracking 111
Product Recommendation 113
Products or Services 115
Professional Services 117
Revenue 119
Sales Hierarchy and Credit Assignment 121
Sales Portfolio Management 123
Service Agreement 125
Service Calendars and Work Shifts 127
Service Request 129
Shipment 131
Siebel Assistant 133
Territory Management 135
Territory Quota Rollup 137
Textile, Apparel, and Footwear 139
Time Sheet 141
Trade Promotions 143
Training Curriculum Course 145
Training Test Engine 147
Versioned Object Definition 149
Warranty 151
4 Siebel Data Model Reference Version 8.0, Rev. A

Contents ■
Chapter 4: Physical Model

Data Model Naming Conventions 153
Table Naming Conventions 153
Index Naming Conventions 155
Column Naming Conventions 155
Abbreviations Used in the Physical Model Listings 156
Data Model Type Definitions 156
Table Type Definitions 157
Table Status Definitions 158
Column Type Definitions 159
Domain Type Definitions 159
Columns of Numeric Physical Type 160
Siebel System Fields 160
INTEGRATION_ID Columns 161
Include Only Field 161
Siebel Repository 161
Database Schema Version 161
Limit Checking for Data Types 162
Validating the Siebel Schema 162
Party Model Unifies Access to Data 162
Chapter 5: Schema Changes

Table Changes in This Version 165
New Tables in this Version 165
Modified Tables in This Version 171
Table Column Changes in This Version 171
New Table Columns in This Version 171
New System Columns in This Version 184
Modified Table Columns in This Version 184
Table Index Changes in This Version 185
New Table Indexes in This Version 185
Modified Table Indexes in This Version 187
Table Indexes Deleted from This Version 190
Index

Contents ■

1 What’s New in This Release
What’s New in Siebel Data Model Reference, Version 8.0, Rev. A

Table 1 lists changes described in this version of the documentation to support release 8.0 of the
software.
Table 1. What’s New in Siebel Data Model Reference, Version 8.0, Rev. A
Topic Description
High Tech Special Pricing Removed this ERD as it is not available in this version of
Authorization Entity Relationship the software.
Diagram (ERD)
Marketing Program ERD, see Corrected listing to show changes for offers, treatments,
Table 33 on page 79 and campaigns in Marketing Program entities and tables.
Party model, see Table 80 on Removed row containing EIM_PARTY table as it is no longer
page 162 part of the database installation.
Table 2 lists changes described in this version of the documentation to support release 8.0 of the
software.
Table 2. What’s New in Siebel Data Model Reference, Version 8.0
Topic Description
Marketing Budget Request ERD A new entity-relationship diagram.
See “Marketing Budget Request” This ERD illustrates the Marketing Resource Management
on page 66. budget request process.
Marketing Program ERD This entity-relationship diagram has been modified.
See “Marketing Program” on A new entity Offer has been added and campaign targeting is
page 79. now performed at the offer level.
Marketing Resource A new entity-relationship diagram.

Management: Document ERD
This ERD illustrates the Marketing Resource Management
See “Marketing Resource marketing content process.
Management: Document” on
page 82.

What’s New in This Release ■
Table 2. What’s New in Siebel Data Model Reference, Version 8.0
Topic Description
Sales Portfolio Management ERD A new entity-relationship diagram.
See “Sales Portfolio The Portfolio Management Process allows portfolio managers to
Management” on page 123. manage a group of strategic accounts by:
■ Assessing the potential of their assigned accounts
■ Engaging the high-potential accounts within their portfolio
■ Directing and managing the resources at their disposal
■ Managing ongoing relationships with customers and

partners
Table changes A listing of the table changes in this schema including the new
tables, deprecated tables, and changes to the existing table
See “Table Changes in This
definitions.
Version” on page 165.
Table column changes A listing of the column changes in this schema including the new
columns, deprecated columns, and changes to the existing
See “Table Column Changes in
column definitions.
This Version” on page 171.
Table index changes A listing of the index changes in this schema including the new
indexes, deprecated indexes, and changes to the existing index
See “Table Index Changes in This
definitions.
Version” on page 185.
Territory Management ERD The relationship from Territory to Territory Hierarchy has been
changed from mandatory to optional and moved out of the
See “Territory Management” on
Territory user key. Territory is now multi-org enabled.
page 135.
Territory Quota Rollup A new entity-relationship diagram.
See “Territory Quota Rollup” on This data model supports quota assignment and quota rollup to
page 137. a territory. Users can define quotas, spread them over several
periods, and assign them to contacts, accounts, regions, and
ZIP codes.

2 Data Model Overview
Oracle’s 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 Developer’s Reference. To learn how to insert, update, and delete data in large quantities, see
Siebel Enterprise Integration Manager Administration Guide.

Data Model Overview ■

3 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

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:

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

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 3 provides a list of ERDs in alphabetic order.
Table 3. Entity Relationship Diagrams
Figure Num. Revised New

ERD Name and Page Functional Area in 8.0 in 8.0
Account Figure 4 on General

page 19
Adjustment Group Figure 5 on General

page 21
Asset Management Figure 6 on General

page 23
Auction Figure 7 on General

page 25
Auto Email Response Generator Figure 8 on General

page 27
CG Promotion Planning Figure 9 on Marketing

page 30
Compensation Planning Administration Figure 10 on ERM

page 32
Compensation Planning Execution Figure 11 on ERM

page 34
Competency Management System Figure 12 on ERM

page 36
Content Management Figure 13 on General

page 38
Contract Conditions Figure 14 on General

page 40
Contracts Figure 15 on General

page 42
Data Visibility Figure 16 on General

page 45
Dun & Bradstreet Integration Figure 17 on Sales/Marketing

page 47


Employee KPI Figure 18 on ERM

page 49
Expense Reports Figure 19 on General

page 51
Field Service Inventory Figure 20 on Service

page 53
Field Service Scheduler Figure 21 on Service

page 55
Forecasts Figure 22 on Sales/Marketing

page 57
High Tech Marketing Development Fund Figure 23 on Marketing

page 59
High Tech Special Pricing Authorization Figure 24 on Sales

page 61
Invoicable Charges Figure 25 on Service

page 63
Invoices Figure 26 on Service

page 65
Marketing Budget Request Figure 27 on Marketing Yes

page 67
Marketing Campaign Figure 28 on Marketing

page 69
Marketing Collaboration Figure 29 on Marketing

page 71
Marketing Encyclopedia Figure 30 on Sales/Marketing

page 73
Marketing Events Figure 31 on General

page 76
Marketing Plans Figure 32 on Marketing

page 78
Marketing Program Figure 33 on Marketing Yes

page 81
Marketing Resource Management: Figure 34 on Marketing Yes

Document page 83
Opportunity Management Figure 35 on Sales

page 85


Order Life Cycle Figure 36 on General

page 87
Orders Figure 37 on General

page 89
Partner Collaboration Figure 38 on General

page 91
Partner Program Registration Figure 39 on General

page 93
Party Model Figure 40 on General

page 95
Payments Figure 41 on General

page 97
Performance Review Figure 42 on ERM

page 100
Personal Account Figure 43 on Industry-Specific

page 102
Personal Financial Review Figure 44 on Industry-Specific

page 104
Pricing Comparison Figure 45 on Energy

page 106
Pricing Figure 46 on General

page 108
Product Promotion Figure 47 on General

page 110
Product Quality Tracking Figure 48 on General

page 112
Product Recommendation Figure 49 on General

page 114
Products or Services Figure 50 on Service

page 116
Professional Services Figure 51 on General

page 118
Revenue Figure 52 on General

page 120
Sales Hierarchy and Credit Assignment Figure 53 on Sales

page 122


Sales Portfolio Management Figure 54 on Sales Yes

page 124
Service Agreement Figure 55 on Service

page 126
Service Calendars and Work Shifts Figure 56 on Service

page 128
Service Request Figure 57 on Service

page 130
Shipment Figure 58 on General

page 132
Siebel Assistant Figure 59 on General

page 134
Territory Management Figure 60 on Sales Yes

page 136
Territory Quota Rollup Figure 61 on Sales Yes

page 138
Textile, Apparel, and Footwear Figure 62 on Industry-Specific

page 140
Time Sheet Figure 63 on General

page 142
Trade Promotions Figure 64 on General

page 144
Training Curriculum Course Figure 65 on General

page 146
Training Test Engine Figure 66 on General

page 148
Versioned Object Definition Figure 67 on General

page 150
Warranty Figure 68 on Service

page 152
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 4 lists the entities in this ERD and their corresponding tables.
Table 4. Account ERD Entities and Tables
Entity Tables
Account S_ORG_EXT, S_PARTY
Account Synonym S_ORG_SYN
Activity S_EVT_ACT
Address S_ADDR_ORG
Assignment Group (Territory) S_ASGN_GRP
Business Unit S_BU, S_ORG_EXT, S_PARTY
Characteristics S_CHRCTR
Dynamic Account Hierarchy S_DYN_HRCHY
Dynamic Account Hierarchy Node S_DYN_HRCHY_REL

Employee/Agent S_EMP_PER, S_CONTACT, S_PARTY
Industry S_INDUST
Market Segment S_MKT_SEG
Party S_PARTY
Payment Term S_PAYMENT_TERM
Person S_CONTACT, S_PARTY
Position S_POSTN, S_PARTY
Price List S_PRI_LST
Sales or Service Team Member S_ACCNT_POSTN

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

addressed to
a parent of
NAMED HIERARCHY
ACCOUNT DECISION participant in
ISSUES MARKET
ACTIVITY SEGMENT PRICE LIST
for of ADDRESS
for action for
for
current price applicable to
made visible through type of list for
for belong to
PARTY participate in described in

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

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

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

19
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 5. Adjustment Group ERD Entities and Tables
Entity Tables
Adjustment Group S_ADJ_GROUP
Adjustment Group Dimension S_ADJ_GROUP_DIM
Product Compatibility Matrix Rule S_PRODCOMP_MTRX
Product Eligibility Matrix Rule S_PRODELIG_MTRX
Product Promotion Pricing Matrix Rule S_PROM_PMTRX
Standard Entitlement Pricing Matrix Rule S_STDENTL_PMTRX
Standard Product Pricing Matrix Rule S_STDPROD_PMTRX
Standard Training Pricing Matrix Rule S_STDTRNG_PMTRX

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

# MTRX_RULE_NUM
contain
Adjustment Group
PRODUCT PROMOTION PRICING MATRIX RULE for

# MTRX_RULE_NUM
contain
STANDARD ENTITLEMENT PRICING MATRIX for

RULE
# MTRX_RULE_NUM contain
STANDARD PRODUCT PRICING MATRIX RULE for

# MTRX_RULE_NUM
contain
STANDARD TRAINING PRICING MATRIX RULE for

# MTRX_RULE_NUM
contain
contain
for
ADJUSTMENT GROUP
DIMENSION
# FIELD_NAME

21
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 6. Asset Management ERD Entities and Tables
Entity Tables
Activity S_EVT_ACT
Activity Part Movement S_ACTPART_MVMT
Asset Contact Relationship S_ASSET_CON
Asset Employee Relationship S_ASSET_EMP
Asset External Organization S_ASSET_ACCNT
Asset Feature S_ASSET_FEA
Asset Modification S_ASSET_TXN
Asset Relationship S_ASSET_REL
Business Address S_ADDR_ORG
Competitive Metric S_CMPT_MTRC
Competitive Product Feature S_CMPT_PROD_FEA

Contact S_CONTACT, S_PARTY
Employee S_EMP_PER, S_CONTACT, S_PARTY
External Product S_PROD_EXT
Internal Product S_PROD_INT
Opportunity S_OPTY
Opportunity Asset S_OPTY_ASSET
Personal Address S_ADDR_PER
Product Instance (Asset) S_ASSET
Service Request S_SRV_REQ

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

23
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 7. Auction ERD Entities and Tables
Entity Tables
Asset S_ASSET
Auction Alert Definition S_AUC_ALRT_DEF
Auction Item S_AUC_ITEM
Auction Item Bid S_AUC_BID
Auction Item Promotion S_AUC_ITM_PROMO
Auction Item Watch S_AUC_WATCH
Auction Lister/Bidder Rating S_AUC_RATING
Catalog S_CTLG
Catalog Category S_CTLG_CAT
Catalog Category Item S_CTLG_CAT_PROD, S_CTLGCAT_ASSET, S_CTLG_CAT_AUC
Order S_ORDER
Order Item S_ORDER_ITEM
Party S_PARTY
Person S_CONTACT
Product S_PROD_INT
Triggered Auction Alert Item S_AUC_ALRT
User S_USER, S_CONTACT, S_PARTY

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

25
Auto Email Response Generator

Figure 8 shows the Auto Email Response Generator ERD. This ERD illustrates the data model for the
automatic generation of a response to an inbound communication. Incoming messages (inbound
communications) are compared against a database of previously categorized messages to categorize
them in one or more categories. The categories are associated with predefined template
communication responses, used to generate a default response to each category of message. A
notification mechanism can be defined to alert a person whenever the usage of a category or
template exceeds a predefined limit.
Table 8. Auto Email Response Generator ERD Entities and Tables
Entity Tables
Activity S_EVT_ACT
Catalog S_CTLG
Category Usage Notification S_COMM_CTG_NTFY
Communication Template Usage Notification S_COMMTMPL_NTFY
Problem Resolution Document S_RESITEM
Template Communication Response S_DMND_CRTN_PRG

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

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

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

27
CG Promotion Planning
Figure 9 shows the CG Promotion Planning ERD. This ERD illustrates how Siebel Business Applications
support the funding of trade promotions in channel management and the Consumer Goods (CG)
industry. Marketing development funds (MDFs) are defined for an account, for a product line or
product category, and for an accounting period. An MDF can be a fixed sum of money, an accrual
fund, or a mixture of the two. The value of the accrual fund is typically determined based on an
accrual rate multiplied by either the number of units sold, or the revenue in a given period from one
or more specific products that are representative of the product line or category of the fund. Planned
expenses for the various tactics involved in the planning and execution of product promotions can
be allocated to one or more MDFs. Allocations that have not yet been approved are considered fund
requests. One or more such MDF allocations may be covered by a single payment to the partner
account.
Advanced Planning is a feature designed to address the process used by CG organizations to plan
sales volume and sales revenue at key accounts. Advanced Planning is part of a broader process
called Trade Marketing. Trade Marketing includes planning, executing, and analyzing sales.
Table 9. CG Promotion Planning ERD Entities and Tables
Entity Tables
Authorized Product S_ORG_PROD
Fund Allocation S_MDF_ALLOC
Marketing Development Fund S_MDF
Marketing Event or Activity S_SRC
MDF Accrual S_MDF_ACCRUAL

Payment S_SRC_PAYMENT
Period S_PERIOD
Price List Item S_PRI_LST_ITEM
Product Internal S_PROD_INT
Product Line S_PROD_LN
Product Structure S_PROD_REL or S_PROD_ITEM

Promotion Plan S_SRC
Promotion S_SRC
Promotion Account S_SRC

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

30

PAYMENT MARKETING EVENT OR ACTIVITY
Oracle
OTHER PAYMENT
Figure 9.
PROMOTION PLAN
FUND PROMOTION
ALLOCATION PROMOTION PAYMENT for
covered by
subject of
PROMOTION ACCOUNT
sub allocation of for
to
requested by recipient of
PERSON PROMOTION CATEGORY
sub allocated to
approved by requestor of
EMPLOYEE / AGENT
approver of made of PROMOTION PRODUCT
assigned to
CG Promotion Planning
OTHER PERSON
responsible for POSITION
made up of of part of
PROMOTION ACCOUNT PRODUCT
subject of
subject of
assigned to ACCOUNT
MARKETING
part of DEVELOPMENT defined for
responsible for OTHER MARKETING EVENT OR
FUND target of
target of ACTIVITY
designated to available to
ACCRUAL related to
FUND user of defined for of
AUTHORIZED
PRODUCT
used by PRODUCT
relation of
at STRUCTURE
subject to
subject of PRICE LIST for
of
applicable to
for

FIXED FUND PRICE LIST ITEM basis for a component of
composed of promoted via
an assembly of
based on
of subject of INTERNAL PRODUCT OR
SERVICE
of subject of
subject of
for promotion of
MIXED FUND subject of
PRODUCT LINE composed of part of
for promotion of hierarchy parent of
earned by
MDF ACCRUAL earner of
funded through earned by earner of
for subject of
earned in subject of
PERIOD hierarchy child of
defined for subject of

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 10. Compensation Planning Administration ERD Entities and Tables
Entity Tables
Business Unit S_BU
Compensation Budget Definition S_CP_BDGT
Compensation Budget Item S_CP_BDGT_ITEM
Compensation Budget Item For Employee S_CP_BDGT_EMP
Compensation Cycle Planning Period S_CP_PD_BDGTITM
Compensation Guideline Definition S_CP_GDLN
Compensation Guideline Factor LOV
Compensation Guideline Set S_CP_GDLN_SET
Compensation Guideline Table S_CP_GDLN_TBL
Compensation Planning Period S_CP_PERIOD
Compensation Region S_CP_REGN
Compensation Type LOV

Compensation Valid Effectivity Date S_CP_EFF_DATE
Employee Eligibility S_APP_QUERY (PDQ)
Employee/Agent S_EMP_PER
Job Category LOV
Job Code S_JOB
Job Family S_JOB_FAMILY
Job Profile S_JOB_PRFL
Period S_PERIOD
Salary Grade S_SALARY_GRADE, S_SALPLAN_GRADE
Salary Plan S_SALARY_PLAN

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

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

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

CATEGORY
salary plan for
used in defined for component of defined in defined for for

container for used by period for
PERIOD
QUARTERLY PERIOD SALARY GRADE
COMPENSATION BUDGET DEFINITION
defined for
POSITION
ANNUAL PERIOD sub-org of
used in
budget for support
have have manage by employer of
composed of
BUSINESS UNIT
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 11. Compensation Planning Execution ERD Entities and Tables
Entity Tables
Business Unit S_BU
Compensation Budget Definition S_CP_BDGT
Compensation Budget Item S_CP_BDGT_ITEM
Compensation Budget Item For Employee S_CP_BDGT_EMP
Compensation Cycle Planning Period S_CP_PD_BDGTITM
Compensation Guideline Definition S_CP_GDLN
Compensation Guideline Set S_CP_GDLN_SET
Compensation Guideline Table S_CP_GDLN_TBL
Compensation Plan S_CP_PLAN
Compensation Plan Comments S_NOTE_CP_PLAN
Compensation Plan For Employee S_CP_PLAN_EMP
Compensation Plan Item Detail S_CP_PLNITM_DTL

Compensation Plan Item For Employee S_CP_PLAN_ITEM
Compensation Plan Total S_CP_PLNITM_TOT
Compensation Planning Period S_CP_PERIOD
Compensation Type LOV
Compensation Valid Effectivity Date S_CP_EFF_DATE
Plan Approval S_CP_APPROVAL
Proxy Access To Plan S_USER_PROXY

34

Oracle
"'+0

$

"$%$'$"*"'+

"$%$'$*"'+
2

1 3

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

3 3
21
"$%$+

3

"$%$

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

!
2
3

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

&!'$.'
"$%$

&!'$%
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 12. Competency Management System ERD Entities and Tables
Entity Tables
Career Path S_JOB_PRFL_TRNS
Competency, Competency Category, Root Competency S_CMPTNCY

Category
Educational Qualification S_PER_EDU_QUAL
Employee Competency S_EMP_CMPTNCY
Employee Competency Change S_EMP_CMPT_CHG
Employee/Agent S_EMP_PER
Honors And Awards S_PER_AWARD
Job Code S_JOB
Job Profile S_JOB_PROFILE, S_JOBPRFL_CMPT
Past Work Experience S_PER_WRK_EXP
Person S_USER, S_CONTACT

Professional Membership S_PER_PROF_MBR
Professional Qualification S_PER_PROF_CERT
Review Rating S_PERF_RATING
Review Rating Scale S_PERF_RTNG_SCL
Team Competency S_TEAM_CMPTNCY
Training Course S_PROD_INT_CRSE

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

"$ + " "$ +

"'+ &$ "$ +

14

"'+ "$ +
9$
14
2613

26
? ? @
Figure 12. Competency Management System

3
"$ +

+ >;$

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


513
$$
&%

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

3

313 6 5 6
3
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 13. Content Management ERD Entities and Tables
Entity Tables
Content Item Type S_CONTENT_TYPE
Content Object S_CONTENT_OBJ
Content Project S_CONTENT_PROJ
Content Project Item S_CONTENT_ITEM
Literature S_LIT
Product S_PROD_INT

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

an example of used by
type for used by
MASTER DATA ITEM viewed via

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

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

responsibility POSITION
of
generally the responsibility of picked via based on published via
responsible held by
for PERSON basis for
holder of generally picked via
controlled
CONTENT produced by BUSINESS
by
PROJECT OBJECT
owned by producer of
owner of

generally followed used by
by
controlled by EAI
WORKFLOW PROCESS INTEGRATION
followed by OBJECT
used by used by
picked via
PICK APPLET
used by
picked via
used by
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 14. Contract Conditions ERD Entities and Tables
Entity Tables
Agreement S_DOC_AGREE
Benefit S_AGREE_BNFT
Category S_CTLG_CAT
Condition S_AGREE_COND
Condition Compliance S_AGR_COND_CMPL
Contract S_DOC_AGREE
Entitlement S_ENTLMNT
Entitlement Template S_ENTL_TMPL
Object Class S_VOD, S_VOD_VER
Product S_PROD_INT

Template Benefit S_ENTL_BNFTTMPL
Template Condition S_ENTL_CONDTMPL
Template Term S_AGR_TERM_TMPL
Term S_AGR_TERM_DESC

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

governed by used by composed of
based on ENTITLEMENT TEMPLATE

ENTITLEMENT
# NAME used by
# NAME
CATEGORY
applicable to
subject of subject of
comprise comprise
CONTRACT
AGREEMENT OTHER
CONTRACT
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 15. Contracts ERD Entities and Tables
Entity Tables
Asset S_ASSET
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

42
Title : Contracts
part of composed of
part of composed of ASSET INTERNAL

for PRODUCT OR
an instance of SERVICE
CONTRACT LINE ITEM
subject of made into
Figure 15. Contracts
AGREEMENT LINE QUOTE LINE ITEM

ITEM
for
subject of
ORDER LINE ITEM
priced by
pricing
method for
OTHER CONTRACT LINE ITEM
priced by
PRICE LIST
pricing for
part of
composed of
priced by
CONTRACT
default pricing for
applicable to subject to
AGREEMENT ORDER QUOTE
subject to for

OTHER CONTRACT
for ACCOUNT PAYMENT
subject to
TERM
subject of for
responsibility of responsibility of involved by

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

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 16. Data Visibility ERD Entities and Tables
Entity Tables
Access Group S_PARTY
Account S_ORG_EXT
Activity S_EVT_ACT
Catalog S_CTLG
Category S_CTLG_CAT
Dynamic Account Hierarchy S_DYN_HRCHY
Dynamic Account Hierarchy Node S_DYN_HRCHY_REL
Group S_PARTY
Internal/Partner Organization Unit S_ORG_EXT
Literature Item S_LIT
Opportunity S_OPTY

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

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

+

&%"!" '% @

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

+

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

1

9+
1

&

$[$&$

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

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

9
&
@6

Dun & Bradstreet Integration

This ERD (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 17. Dun & Bradstreet Integration ERD Entities and Tables
Entity Tables
Call List S_CALL_LST
Call List D & B Organization S_DNB_ORG_LST
D & B Contact Responsibility S_DNB_CON_MRC
D & B Management Responsibility Type S_DNB_MRC
D & B Organization S_DNB_ORG
D & B Organization Industry Classification S_DNB_ORG_SIC
D & B Standard Industry Classification S_DNB_SIC
Industry S_INDUST
Organization Industry Classification S_ORG_INDUST
Prospect S_PRSP_CONTACT

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

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

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

domestic
for child of composed of global
parent of
for of
affiliated with bearer of
created from
PROSPECT assigned to
CALL LIST OTHER D&B CONTACT D&B MANAGEMENT

PROSPECT RESPONSIBILITY TYPE
composed of

member in
47
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 18. Employee KPI ERD Entities and Tables
Entity Tables
BUSINESS UNIT S_BU
EMPLOYEE PERFORMANCE S_EMP_PERF_MEAS

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

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

PERSON

Figure 18. Employee KPI
Title : Employee KPI

KPI VALUE PERFORMANCE

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

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

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

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

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

Expense Reports
This ERD (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 19. Expense Reports ERD Entities and Tables
Entity Tables
Activity S_EVT_ACT
Expense Item S_EXP_ITEM
Expense Item Type S_EXP_ITM_TYPE
Expense Report S_EXP_RPT
Expense Report Approval S_EXP_RPT_APPR
Opportunity S_OPTY
Party S_PARTY
Project S_PROJ

Figure 19. Expense Reports
Title : Expense Reports

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

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

Field Service Inventory

This ERD (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 20. Field Service Inventory ERD Entities and Tables
Entity Tables
Address S_ADDR_ORG
Asset S_ASSET
Inventory Location S_INVLOC
Inventory Transaction S_INV_TXN
Party S_PARTY
Product Inventory S_PROD_INV
Product Inventory Category S_PROD_INV_CAT

Product Inventory Location S_PROD_INVLOC
Product or Service S_PROD_INT

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

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

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

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

ORGANIZATION ORGANIZATION
NON-SERIALIZABLE SERIALIZABLE
sub-org
PRODUCT PRODUCT

composed of of
53
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 21. Field Service Scheduler ERD Entities and Tables
Entity Tables
Address S_ADDR_ORG
Employee Exceptional Work Hours S_EMP_EXCPT_HRS
Scheduler Cost Function S_SCH_CSTFN
Scheduler Cost Function Variable S_SCH_CSTFN_VAR
Scheduler Parameter S_SCH_PARAM
Scheduler Parameter Set S_SCH_PARAM_SET
Scheduler Rule S_SCH_RULE
Scheduler Rule Node S_SCH_RULENODE
Scheduler Rule Set S_SCH_RLST
Scheduler Time Map S_SCH_TMMAP

Scheduler Time Map Duration S_SCH_TMMAP_DUR
Service Activity S_EVT_ACT
Service Region S_SRV_REGN
Timezone S_TIMEZONE
Work Shift S_SCHED_CAL
Work Shift Exception S_EXCPT_CAL
Work Shift Exception Hour S_EXCPT_CAL_HRS
Work Shift Hour S_SCHED_CAL_HRS
Zipcode S_ZIPCODE

Figure 21. Field Service Scheduler

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

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

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

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

ZIPCODE SCHEDULER PARAMETER SET

Forecasts
This ERD (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 22. Forecasts ERD Entities and Tables
Entity Tables
Forecast S_FCST
Forecast Item Detail S_FCST_ITEM_DTL
Forecast Period S_FCSTSER_DATE
Forecast Series S_FCSTSER
Forecasted Item S_FCST_ITEM
Marketing Event S_SRC
Opportunity S_OPTY

Project S_PROJ
Quote S_DOC_QUOTE
Revenue Item S_REVN

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

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

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

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

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

57
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 23. High Tech Marketing Development Fund ERD Entities and Tables
Entity Tables
Account, Partner, Other Account S_ORG_EXT
Claim Item S_SRC_PAYITM
Claim, Payment, Other Payment S_SRC_PAYMENT
Event Item S_SRC_COST
General Fund S_MDF
Internal Product or Service S_PROD_INT
Market Segment S_MKT_SEG

MDF Snapshot S_MDF_PERIOD
MDF Transaction S_MDF_TXN
Partner Event Activity S_SRC
Partner Program S_PRTNR_PROG
Partner Program Application S_PRTNRPRG_APPL
Partner Specific Fund S_MDF
Position S_POSTN

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

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

MDF hierarchy child of
SNAPSHOT . subject of

59
High Tech Special Pricing Authorization

This ERD (shown in Figure 24) illustrates the special pricing authorization business process for Siebel
High Tech, which uses the Meet Competition Quote and Design Registration features. The quote or
design registration opportunity leads to an Agreement with Entitlements for discounts on products.
Point of sale data includes claim items, which can refer to agreed upon entitlements.
Table 24. High Tech Special Pricing Authorization ERD Entities and Tables
Entity Tables
Account S_ORG_EXT
Address S_ADDR_PER
Claim Item S_POS_CLAIM_ITM
Design Registration S_OPTY_DSGN_REG
Entitlement S_ENTLMNT
Entitlement Product Price S_ENTL_PRDPRI
Meet Competition Quote S_DOC_QUOTE
Opportunity S_OPTY
Point of Sale Header S_POS
Point of Sale Item S_POS_ITEM
Product S_PROD_INT
Quote Line Item S_QUOTE_ITEM

Title : High Tech Special Pricing Authorization
POINT OF SALE ITEM for PRODUCT
subject of
OTHER POS
ITEM
ENTITLEMENT
PRODUCT PRICE
for
having
CLAIM ITEM for
having
ENTITLEMENT QUOTE LINE

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

61
Invoicable Charges
This ERD (shown in Figure 25) illustrates how financial transactions, such as charges and credits, are
handled. Any charge or credit that could be invoiced is added to this table. This is based on defined
consolidation plan rules to consolidate charges and credits into invoice and invoice items.
Table 25. Invoicable Charges ERD Entities and Tables
Entity Tables
Activity S_EVT_ACT
Address S_ADDR_ORG
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
Project Item S_PROJITEM
Project Team Role S_PROJ_RSRC
Shipment S_SHIPMENT
Time Sheet Item S_TMSHT_ITEM

Title : Invoicable Charges part of
Author : Oracle, Confidential composed of
INVOICABLE CHARGE
for charged via SERVICE
for REQUEST
charged via
INVOICE ITEM
TIME SHEET ITEM
RECONCILIATION ENTRY
for charged via
INVOICE ITEM EXPENSE ITEM
DETAIL for
PART REPAIR
for for charged via
INVOICE ITEM for charged via
AGREEMENT
INVOICABLE
CHARGE subject of based on basis of part of
AGREEMENT
for
ENTITLEMENT made up of
invoiced into ACTIVITY
Figure 25. Invoicable Charges
charged via based on

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

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

billed to contact of
63
Invoices
This ERD (shown in Figure 26) 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 26. Invoices ERD Entities and Tables
Entity Tables
Activity S_EVT_ACT
Expense S_EXP_ITEM
Invoice S_INVOICE
Invoice Attachment S_INVOICE_ATT
Order S_ORDER
Part Movement S_ORDPART_MVMT
Part Repair S_PART_RPR
Period S_PERIOD
Product S_PROD_INT
Project S_PROJ
Shipment S_SHIPMENT

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

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

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

65
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 27. Marketing Budget Request ERD Entities and Tables
Entity Tables
Budget Request S_MKTG_BDGT_REQ
Purchase Request S_ORDER
Marketing Plan S_SRC
Marketing Fund S_MDF
Marketing Tactics S_SRC
Tactics Expense S_SRC_COST
Purchase Request Line Item S_ORDER_ITEM

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

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

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

$

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

67
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 28. Marketing Campaign ERD Entities and Tables
Entity Tables
Activity S_EVT_ACT
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
Opportunity S_OPTY
Opportunity Contact S_OPTY_CON
Order S_ORDER
Prospective Contact S_PRSP_CONTACT
Response S_COMMUNICATION
Territory S_ASGN_GRP

Title : Marketing Campaign OPPORTUNITY CONTACT
Author :Oracle, Confidential
associated with
for of
RESPONSE generated by CAMPAIGN CONTACT
targeted at ORDER originator of
generated by originator of
ACTIVITY OPPORTUNITY
generated by originator of
for primarily from
initiated by
MARKETING EVENT OR ACTIVITY of of
part of initiator of CALL LIST
introduction to targeted at MEMBER
conducted as
MARKETING CAMPAIGN
FULFILLMENT of source of
RECIPIENT FULFILLMENT in
for made up of
REQUEST part of of
Figure 28. Marketing Campaign
of
addressed to
subject of CALL LIST
part of
FULFILLMENT
REQUEST ITEM made up
of
of LITERATURE relevant to MARKETING

ITEM SEGMENT
subject of promoted via
CAMPAIGN responsibility of user of

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

69
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 29. Marketing Collaboration ERD Entities and Tables
Entity Tables
Internal Partner/Organization S_ORG_EXT, S_PARTY
Opportunity S_OPTY
Order S_ORDER
Organization Unit, Other Organization Unit S_ORG_EXT, S_PARTY
Partner Organization S_BU, S_PARTY
Party, Other Party S_PARTY
Quote S_DOC_QUOTE

Figure 29. Marketing Collaboration

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

generated from

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

MARKETING EVENT OR ACTIVITY
OTHER ORGANIZATION UNIT

responsible for
OTHER PARTY

Marketing Encyclopedia
This ERD (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 30. Marketing Encyclopedia ERD Entities and Tables
Entity Tables
Company Literature S_CO_LIT
Competitive Company Feature S_CMPT_CO_FEA
Competitive Metric S_CMPT_MTRC
Competitive Product Feature S_CMPT_PROD_FEA
Issue S_ISS
Product Comparison S_PROD_CMP
Product Detail S_PROD_SPEC
Product External S_PROD_EXT
Product Literature S_PROD_LIT

Title : Marketing Encyclopedia
COMPETITIVE PRODUCT PRODUCT COMPARISON PRODUCT COMPANY COMPETITIVE

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

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

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

relevant to
ORGANIZATION UNIT
INTERNAL / PARTNER EXTERNAL ORGANIZATION UNIT

ORGANIZATION UNIT
subject of
COMPETITIVE METRIC
classification for
classification for
COMPETITIVE PRODUCT METRIC COMPETITIVE COMPANY METRIC

73
Marketing Events
This ERD (shown in Figure 31) 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 Tables
Activity S_EVT_ACT
Contract Line Item S_ORDER_ITEM, S_QUOTE_ITEM
Equipment Requirement S_SRC_REQ_EQUIP
Event S_SRC_EVT, S_SRC
Event Cost S_SRC_COST
Event Location S_EVTLOC
Event Registration S_SRC_EVT_REG
Event Session S_SRC_EVT, S_SRC
Event Vendor S_SRC_ORG
Event Venue S_SRC_VENUE

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

Table 31. Marketing Events ERD Entities and Tables
Entity Tables
Vendor Offer S_EVT_VNDR_OFR
Vendor Review S_EVT_VNDR_RVW
Vendor Service S_EVT_VNDR_SVC
Venue S_ORG_EXT, S_PARTY
Venue Offer S_EVT_VENUE_OFR
Venue Review S_EVT_VENUE_RVW
Venue Service S_EVT_VENUE_SVC

76
2613 26
"52 >$! >$!
Oracle >$! %$
** %> >;
13 13

>''$ >'
2 2 14 2 $ 1
2

>$>$!
213

>$& >$& >$&
1 ** %> >;
2613 13 6 26
13 >$ %
Figure 31. Marketing Events
14 2 14

13
>$>$& >+ 7&"$
7&"$

?13
14 2
14 13
"<$
>$ >+ 2 2

3 9"<$
>$%%%$ >$ $
>$ >+ >$ >$

%$
14 14

$[$ 14 $!
&$ "7&"$
13 2
>'.'+ ;'%
21
$ ''!
1 2
%$ $

?6
%$ '& !
"
' $" 13

7&
$ '$"

9
$
13 14
>$' $ !& %>
>$& 9' >$!& 9!&

%>
Marketing Plans
This ERD (shown in Figure 32) illustrates how marketing plans are used in conjunction with the
financial modeler for the purposes of financial planning. Marketing plans are multilevel groupings of
plan elements (campaigns) or sub-plans. Financial goals and costs can be forecasted for each level
of the plan, tracked against actual achievement after campaign execution, and rolled up to the top-
level plan. Funds can also be allocated for different plans in different periods and used as inputs for
accounting purposes or in financial calculations.
Table 32. Marketing Plans ERD Entities and Tables
Entity Tables
Marketing Event Cost S_SRC_COST
Marketing Event or Activity, Marketing Plan, Other Marketing Plan S_SRC

or Activity
Marketing Goal S_SRC_GOAL
Period S_PERIOD
Planned Marketing Development Fund Allocation S_MDF_ALLOC
Product or Service, Product Line, Other Product or Service S_PROD_INT, S_PROD_LN
Product Promotion S_PROD_INT_SRC

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

EVENT COST
incur
part of basis of
made up of based on created from
PRODUCT
PROMOTION source of
INVOICE
promotion item for created for
defined for
PRODUCT OR SERVICE
has belong to
valid in launched in
defined for
reserved from defined for launch of
source of compose of
defined for the budget of

PERIOD
MARKETING valid in owner for valid in
DEVELOPMENT defined for

FUND type of
FOR
for BUDGET
REQUEST SUBJECT OF
uses
OTHER
CALL LIST CAMPAIGN
source of created for MARKETING
CALL LIST EVENT OR
created from requirer of ACTIVITY
used for
user of
Marketing Program
This ERD (shown in Figure 33) 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 Tables
Assignment Rule Group S_ASGN_RULE_GRP

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 Status S_ SRCDCP_CONSTA
Deal S_DEAL
Filter S_DD_FILTER
Filter Clause S_DD_FILTER_DTL
Load Wave S_CAMP_LD_WAVE

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

"
$ $ +
%$
14
'''%

9
13 & 9%! %$
'%

"
%
"$ % >
%
"$ $
14

' '!%&
14 %$

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

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

"
$'! 14
14
1 "<$

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

;> 14

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

*"

"

!& %>

1 .&%$%%&$ "5
Oracle

6
81
Marketing Resource Management: Document

This ERD (shown in Figure 34) 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 Tables
Marketing Material S_CB_ASSET
Material Inventory by Location S_MKTG_DOC_INVT
Region S_REGION
Material Fulfillment Request S_EVT_FUL_REQ
Material Fulfillment Item S_FUL_REQ_ITEM
Mat Fulfill Request Attachment S_NOTE_FUL_REQ
Vendor Bidding S_FUL_REQ_BID
Vendor Bidding Item S_FR_BID_LITM
External Organization S_ORG_EXT
Offer Media Package S_DMND_CRTN_PRG
Offer Document S_OFFR_CBAST
Lead Source S_SRC

Lead Source Document S_SRC_CBAST
Project S_PROJ
Project Document S_PROJ_CBAST

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

"'$>$+.+' $

1 33 "*&'*'' 14

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

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

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

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

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

83
Opportunity Management
This ERD (shown in Figure 35) 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 Tables
Address S_ADDR_ORG
Event S_EVT_ACT
External Organization Unit S_ORG_EXT, S_PARTY
Issue S_ISS
Opportunity S_OPTY
Opportunity Relationship S_OPTY_REL
Product S_PROD_INT
Quote S_DOC_QUOTE
Sales Stage S_STG

Source S_SRC
Territory S_ASGN_GRP

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

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

85
Order Life Cycle

This ERD (shown in Figure 36) 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 Tables
Invoice S_INVOICE
Opportunity S_OPTY
Opportunity Product S_REVN
Order S_ORDER
Order Part Movement S_ORDPART_MVMT
Quote S_DOC_QUOTE
Quote Item S_QUOTE_ITEM

Shipment S_SHIPMENT

Title : Order Life Cycle
ACCOUNT
target of receiver of target of billed via
of taken for for
lead to prepared for

OPPORTUNITY ORDER INVOICE
Figure 36. Order Life Cycle
for
QUOTE reason for
lead to lead to generated for part of made up of
for created from SHIPMENT
consideration of purchase of composed of composed of billed via for
vehicle for fulfillment of

composed of subject of
part of part of
for for
for part of
ORDER PART MOVEMENT
OPPORTUNITY on
composed of QUOTE ITEM ORDER ITEM INVOICE ITEM
PRODUCT billed via
composed of for from
OTHER PART SHIP
for MOVEMENT MVMT
part of billed via
lead to
composed of RECEIPT
for MVMT
for
fulfilled by
of of ALLOCATION
a step toward the
of fulfillment of
of preceded by followed by
considered for purchase on
quoted for purchase on ordered on billed via delivered by
PRODUCT OR SERVICE

87
Orders
This ERD (shown in Figure 37) 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 Tables
Activity S_EVT_ACT
Asset S_ASSET
Inventory Transaction S_INV_TXN
Inventory Transaction Type S_INV_TXN_TYPE
Order S_ORDER
Order Type S_ORDER_TYPE
Part Movement S_ACTPART_MVMT, S_ORDPART_MVMT
Part Movement Type S_PARTMVMT_TYPE
Party S_PARTY, S_ORG_EXT, S_POSTN, S_CONTACT

Product S_PROD_INT

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

89
Partner Collaboration
Partner collaboration (shown in Figure 38) 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 Tables
Business Unit S_BU
Collaboration S_PARTY_GROUP
Collaboration Resource S_PARTY_PER
Collaboration Invitation S_BRDCST_MSG
Party S_PARTY
Position S_POSTN

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

%$
$[$
1 313 313
.&%$%%$% $
+
Figure 38. Partner Collaboration
3
$[$&$
''.$%9!%&
%$ 3

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

$[$

%9!
$[$* ''.$

''.$

1
"%%

''.$$>$
14

13

9
$[O$
&$
9"%%
9+

91
Partner Program Registration

Partner Program Registration (shown in Figure 39) 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 Tables
Application Approval Team S_PRG_APPL_PSTN
Application Attachment S_PRG_APPL_ATT
Application Question Answer S_PRG_APPL_QA
Approval List S_PRTNRPRG_PRTN
Eligibility List S_PRTNRPRG_PRTN
Partner S_ORG_EXT
Partner Program S_PRTNR_PROG
Partner Program Application S_PRTNRPRG_APPL
Partner Program Group S_PRTNRPRG_GRP
Partner Program Membership S_PRTNRPRG_MBR
Program Team S_PRTNRPRG_PSTN
Renew List S_PRTNRPRG_PRTN

Oracle, '$
&

$
"
14

'&"
14
' $ '' ' $

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

"<
%
"$

2 2
''% 9 !!$!
"

$
"' $
6
14
2 1 113

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

>''%
14

'
.'+'%
14

' $
>'" $;'%
14

6

3 1

1
$ d

6 6 $
"
'

+
&
"
.&%$%%&$

%$

"" '
'

+


93
Party Model
This ERD (shown in Figure 40) 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 Tables
Business Address S_ADDR_ORG
Group S_PARTY
Household S_ORG_GROUP, S_PARTY
Organization Relationship S_ORG_REL
Party S_PARTY
Party Relationship S_PARTY_REL
Person Relationship S_PARTY_REL or S_CONTACT_REL

User List S_PARTY
User Login S_USER

Figure 40. Party Model
3"

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

9'$%9

6

+

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

$ %$ 9
&

1

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

9
$[$&$

&%'
$

Payments
This ERD (shown in Figure 41) 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 Tables
Address S_ADDR_ORG
Invoice S_INVOICE
Order S_ORDER
Party S_PARTY
Prepayment Balance S_PREPAY_BAL

Figure 41. 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
PREPAYMENT
source of BALANCE
OUTBOUND PAYMENT
ADDRESS
addressed to
used in available to
paid to addressed to
for
located at entitled to
receiver of
PARTY
PERSON
source for receiver of
ORGANIZATION UNIT
OTHER ACCOUNT
ORGANIZATION

Performance Review
This ERD (shown in Figure 42) 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 Tables
360 Evaluation S_PERF_360_EVAL
Competency S_CMPTNCY
Employee Criteria (PDQ) S_APP_VER, S_RVW_360_CS
Evaluation Script S_CS_PATH, S_CS_PATH_SCPT

Evaluation Script Answer S_CS_RUN, S_CS_RUN_ANSWR
Job Family S_JOB_FAMILY
Party S_PARTY
Performance Measurement Item S_PERF_MEAS_ITM
Performance Review S_EMP_PERF_MEAS
Period S_PERIOD

Review Component S_PERF_RVW_CMP
Review Component Language S_RVW_COMP_LANG
Review For Skill Item S_PERF_CMPTNCY

Table 42. Performance Review ERD Entities and Tables
Entity Tables
Review Metric S_PERF_RVW_MTRC
Review Rating S_PERF_RATING
Review Rating Scale S_PERF_RATING_SCL
Review Template S_PERF_RVW_TMPL
Review Template Component S_PERF_RVW_COMP

26
100
Oracle
*"$ "%&"$"
>;*%<''" *"$ *"$

.= > >;"
26 1 1

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

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

3 >; "$$
Figure 42. Performance Review

213
?

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

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

"'+*"$

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

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

"'+ &%"

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

2
+
%$
14 9%$
2 14

$[$&$
$$'0$
"'+0
$ %$
$[$
13
313
.&%$%%&$ 9
$[$
3
Personal Account
This ERD (shown in Figure 43) 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 Tables
Activity S_EVT_ACT
Opportunity S_OPTY
Personal Account S_ASSET
Personal Account Contact S_ASSET_CON
Product S_PROD_INT
Siebel Data Model Reference Version 8.0, Rev. A 10 1

Figure 43. Personal Account

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

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

Personal Financial Review

This ERD (shown in Figure 44) 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 Tables
Activity S_EVT_ACT
Activity Product Instance S_ACT_ASSET
Asset (Liability) S_FN_ASSET_LIAB
Asset (Liability) Contact S_FN_ASSET_LIAB_CON
Contact Relationship S_CONTACT_REL
Financial Need S_FN_NEED
Financial Recommendation S_FN_RCMD
Household/Account S_ORG_GROUP, S_PARTY

Income (Expense) S_FN_INCM_EXP
Income (Expense) Contact S_FN_INCM_EXP_CON
Need Contact S_FN_NEED_CON
Opportunity S_OPTY
Product S_PROD_INT
Product Instance S_ASSET
Product Instance Contact S_ASSET_CON
Received Product Instance S_FN_RCMD_ASSET
Recommendation Contact S_FN_RCMD_CON

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

to review part of

to review
of ACTIVITY
to understand made up of in
FINANCIAL
for REVIEW ACTIVITY CONTACT
for source of for PROCESS
regarding involves
subject of recommended during
FINANCIAL RECOMMENDATION source of in
for
RECOMMENDATION CONTACT
of
with
Pricing Comparison
This ERD (shown in Figure 45) 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 Tables
Object Class Extended Attribute S_XA_ATTR
Opportunity S_OPPTY
Pricing Matrix S_PRI_MTRX
Pricing Matrix Item S_PRI_MTRX_ITEM
Product Extended Attribute S_PROD_INT_XA
Product or Service Structure S_PROD_ITEM

Quote S_DOC_QUOTE
Quote Item Extended Attribute S_QUOTE_ITEM_XA
Tier Price Value S_VDISCNT_ITEM
Tier Pricing S_VOL_DISCNT

Figure 45. Pricing Comparison

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

ITEM for
COMPETITOR
subject
COMPARISON of
priced via
for priced via

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

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

for by
PRICING MATRIX for
have types
of

Pricing
This ERD (shown in Figure 46) 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 Tables
Component Price Adjustment S_PRI_CFG_ITEM
Object Class Extended Attribute S_XA_ATTR
Pricing Factor Item S_PRIFCTR_ITM
Pricing Factor Item Attrib S_PRIFCTITM_ATR
Pricing Matrix S_PRI_MTRX
Pricing Matrix Attribute S_PRI_ATTR
Pricing Matrix Item S_PRI_MTRX_ITEM
Pricing Matrix Value S_PRI_MTRX_VAL

Pricing Model S_PRIMDL
Pricing Model Factor S_PRIMDL_FCTR
Product Extended Attribute S_PROD_INT_XA
Product or Service Structure S_PROD_ITEM

Title : Pricing
108
an adjustment for INTERNAL

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

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

part of classification for
for
used by
based on for OBJECT CLASS

made up of
used by parent class of
made up of basis of
PRICING MATRIX
PRICING MODEL
OBJECT CLASS
EXTENDED
for
ATTRIBUTE
described by
of object class
have types
Product Promotion
Product Promotion (shown in Figure 47) 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 Tables
Conditional Charge Prorate Plan S_AGR_PR_PLAN
Product Promotion S_PROD_INT
Product Promotion Charge S_PROM_CHRG
Product Promotion Item S_PROM_ITEM
Product Promotion Item Attribute S_PROM_ITEM_XA
Product Promotion Item Attribute Value S_PROMITM_VAL
Product Promotion Pricing Matrix Rule S_PROM_PMTRX
Product Promotion Term S_PROMITM_TRMS
Product Promotion Term Description S_PROD_TRM_DESC

Title : PRODUCT PROMOTION
110
PRODUCT PROMOTION ITEM ATTRIBUTE PRODUCT PROMOTION PRICING MATRIX RULE for ADJUSTMENT GROUP
VALUE
contain
define for define for

has
Figure 47. Product Promotion
PRODUCT PROMOTION ITEM ATTRIBUTE PRODUCT PROMOTION CHARGE CONDITIONAL CHARGE

associate to
PRORATA PLAN
associate by
define for define for
root of child of parent of child of

has
PRODUCT PROMOTION ITEM PRODUCT PROMOTION TERM PRODUCT PROMOTION TERM

DESCRIPTION
made up define for define for

PRODUCT
contain has has has has
PRODUCT PROMOTION
Product Quality Tracking

This ERD (shown in Figure 48) 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 Tables
Activity S_EVT_ACT
Defect Symptom S_PRDFCT_SYMP
Product or Service S_PROD_INT, S_PROD_EXT
Product Quality Item S_PROD_DEFECT
Project S_PROJ
Project Item S_PROJITEM
Resolution Item S_RESITEM

Title : Product Quality Tracking
PROJECT made up of
112
OTHER
PROJECTS
DEFECT PROJECT ITEM ACTIVITY OTHER ACTIVITY

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

ENHANCEMENT owned by
duplicate REQUEST
of owner of INTERNAL /
primarily by PARTNER
ORGANIZATION
primary of UNIT
OTHER PRODUCT QUALITY ITEM
OTHER
reported for planned to in environment of reported by owned by ORGANIZATION
be fixed in UNIT
actually fixed in reporter of owner of reporter of
owner of
PERSON
OTHER PERSON EMPLOYEE / AGENT

part of
PRODUCT OR SERVICE
target EXTERNAL PRODUCT
afflicted fix for
with a component of an assembly of
actual fix for
INTERNAL PRODUCT OR SERVICE
INTERNAL PRODUCT VERSION INTERNAL PRODUCT OTHER INTERNAL PRODUCT

OR SERVICE
version of
produced in
Product Recommendation
Product Recommendation (shown in Figure 49) 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 Tables
Communication S_COMMUNICATION
Product Message S_PROD_MSG
Product Message Response S_PROD_MSG_RESP
Product Message Variable S_PROD_MSG_VAR
Product Recommendation S_PROD_RECMNDTN

Figure 49. Product Recommendation

Title : Product Recommendation
PRODUCT recommendation for PRODUCT OR SERVICE

RECOMMENDATION
recommended via
for
subject of
displayed via
PRODUCT MESSAGE
template for
PRODUCT MESSAGE
VARIABLE defined for
utilize
have
for
COMMUNICATION PRODUCT MESSAGE
have RESPONSE
actual response for

Products or Services
This ERD (shown in Figure 50) 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 Tables
Catalog S_CTLG
Class Attribute S_XA_ATTR
Class of Product or Service S_VOD, S_VOD_VER
Language S_LANG
Product Assembly Port S_PROD_ITEM
Product or Service S_PROD_INT or S_PROD_EXT
Product or Service Attribute S_PROD_INT_XA
Product Structure S_PROD_ITEM
Vendor S_ORG_EXT, S_PARTY

Title : Products or Services
116
LANGUAGE
part of
translation for translation for translation for translation for translation
for
PRODUCT
LINE a collection of
translated into PRODUCT OR SERVICE
ATTRIBUTE
composed of PRODUCT ASSEMBLY
PORT
Figure 50. Products or Services
translated into child of of based on

constrained defined for
CATALOG CATEGORY by
parent to valid for PRICE LIST ITEM
for part of PRODUCT of for translated

STRUCTURE into
basis for
translated into composed of
made up of
for of CLASS ATTRIBUTE
PRICE
CATALOG LIST
of
PRODUCT OR SERVICE
an a
assembly component described subject subject
part of categorized in of of via

of of translated
subject of into
INTERNAL PRODUCT OR SERVICE

a classification for CLASS OF PRODUCT OR
SERVICE
classified in
a report to
produced by VENDOR
EXTERNAL PRODUCT OR SERVICE producer of a parent to
Professional Services
This ERD (shown in Figure 51) 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 Tables
Activity S_EVT_ACT
Address S_ADDR_ORG
Billing Rate List S_PRI_LST
Internal/Partner Organization S_ORG_EXT, S_PARTY
Invoice S_INVOICE
Lead Source S_SRC
Opportunity S_OPTY
Potential Project Resource S_PROJ_PTL_RSRC
Project S_PROJ
Project Contact S_PROJ_CON
Project Issue S_PROJ_ISS
Skill S_PROJRSRC_SKL

Title : Professional Services
118
SKILL
BILLING RATE for SERVICE
LIST BILLING
required by for the resolution of required by billed via POSITION
TYPE
PROJECT ISSUE
ACTIVITY
subject of
for assigned to
assigned to requirer of
billed as
PROJECT TEAM ROLE
Figure 51. Professional Services
billing type for

defined by
defined for subject of filled by
billing type for
assigned to fill
for
of PERSON
POTENTIAL PROJECT
RESOURCE
defined as
OPPORTUNITY OTHER
for PERSON
billed as
of
LEAD PROJECT CONTACT
SOURCE involved in occupant of
source of subject of POSITION
for billed for EMPLOYEE / held by
source of INVOICE AGENT
billed in
subject of billed for sent to
subject of to track work on because of employed by
the outcome of targeted at
requirer of requirer of

subject of billed by
for
composed of
located at
PROFESSIONAL SERVICE PROJECT for

ADDRESS
for ORGANIZATION UNIT
located at
for
INTERNAL/PARTNER OTHER
subcontracted to the client of ORGANIZATION ORGANIZATION
UNIT
responsibility of a partner for
responsible for
accessible to
accessor of
Revenue
This ERD (shown in Figure 52) 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 52. Revenue ERD Entities and Tables
Entity Tables
Agreement Item S_AGREE_ITEM
Invoice S_INVOICE
Invoice Item S_INVC_ITEM
Opportunity S_OPTY

Project S_PROJ
Revenue Item S_REVN
Revenue Template S_REVN_TMPL
Revenue Template Item S_REVN_TMPL_ITM

Title : Revenue
120
a report to manager of
revenue plan for
PERSON
POSITION OTHER PERSON
REVENUE ITEM for held by EMPLOYEE / AGENT
Figure 52. Revenue
owner of occupant of
for
detailed item of attributed to
for PROJECT
attributed to
ORGANIZATION UNIT
for
SERVICE REQUEST
attributed to
for
MARKETING EVENT OR
attributed to ACTIVITY
for INTERNAL /
PARTNER
for attributed to ORGANIZATION
INVOICE UNIT
attributed to
for belongs to
INVOICE ITEM
attributed to subject of
for part of
CONTRACT ITEM AGREEMENT
for attributed to made up of

subject of
for
OPPORTUNITY
attributed to
OTHER
for ORGANIZATION
UNIT
subject of PRODUCT OR SERVICE
for PRODUCT LINE composed of
subject of part of
based on
REVENUE TEMPLATE
template for
based on REVENUE TEMPLATE details of
ITEM
template item for consist of
Sales Hierarchy and Credit Assignment

The Sales Hierarchy Module allows organizations to build sales hierarchies on top of sales territories
and to assign sales credits to territories and positions accordingly. A sales hierarchy (shown in
Figure 53) 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 53. Sales Hierarchy and Credit Assignment ERD Entities and Tables
Entity Tables
Credit Allocation S_SLSCR_RL_PSTN
Credit Assignment Rule S_SLSCRDT_RULE
Credit Rule Criteria S_SLSCRDT_CRIT
Credit Rule Criteria Value S_SLSCRDT_VAL
Hierarchy Version S_SLS_HIER_VER
Hierarchy Version Territory S_SLS_HIER_TERR
Position Territory Assignment S_SLSTERR_POSTN
Sales Hierarchy S_SLS_HIER

Sales Territory S_SLS_TERR

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

TERRITORY part of VERSION approved by

subordinate to composed of approve
parent of version of
OTHER PARTY
validated by consists of versioned by
SALES HIERARCHY
Sales Portfolio Management

This ERD (shown in Figure 54) 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 54. Sales Portfolio Management ERD Entities and Tables
Entity Tables
Sales Portfolio S_SLS_PORTFOLIO
Portfolio Category S_PRTFL_CTGRY
Portfolio Account S_PRTFL_ACCNT
Product Offering S_ENT_SOLN
Portfolio Partner S_PRTFL_PRTNR
Portfolio Attachment S_PRTFL_ATT
Portfolio Product Offering S_PRTFL_ENTSOLN
Account Prod Offering S_PRTFL_ACCSOLN
Portfolio Sub_Account S_PRTFL_SUBACC
Portfolio Account Attachment S_PRTFL_ACC_ATT
Portfolio Business Driver S_PRTFL_BU_DRVR
Portfolio Business Initiative S_PRTFL_BU_INTV

Campaign S_SRC
Portfolio Account Campaign S_PRTFL_CAMP
Portfolio Partner Competitor S_PRTFL_CMPTR
Organization Unit S_ORG_EXT

% "
124
Oracle *'.&%$%% *'.&%$%%
$> !>
14

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

&$
9"$
"
$
14 14

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

$[$&$
**$

2 &$
6
13
@

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

1
$
2
$[$

14 14 *'
$
!&
%'%*'
**$
9
&$
Service Agreement
This ERD (shown in Figure 55) 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 55. Service Agreement ERD Entities and Tables
Entity Tables
Agreement Entitlement S_ENTLMNT
Agreement Item S_AGREE_ITEM
Asset S_ASSET
Entitled Product or Asset S_ENTLMNT_ITEM
Entitled Service S_ENTL_ACT_TYPE
Expense Type S_EXP_ITEM_TYPE
Material S_PROD_INT
Order S_ORDER
Preventive Maintenance S_PM_PLNITM

Price Adjustment S_ENTL_PRDPRI
Product S_PROD_INT
Service Calendar S_SCHED_CAL
Service Metric S_SVC_METRIC
Work Type S_PROJ

Title : Agreement Entitlement
126
for PRODUCT
PRICE ADJUSTMENT
subject of
based on
ENTITLED PRODUCT OR ASSET for
billable for subject of

EXPENSE ENTITLED based on for
AGREEMENT
TYPE billable as SERVICE
of ACTION ITEM RENEWAL
Figure 55. Service Agreement
TYPE TERM
WORK billable for subject of
for
TYPE
billable as
ASSET an
billable for instance
MATERIAL of
billable as AGREEMENT for
ITEM
defined for basis made
for subject of
suject of into
basis for
SERVICE based on
REQUEST AGREEMENT ENTITLEMENT based on
basis for for
basis for
subject of
part of
based on
ORDER made up of
basis for

part of AGREEMENT
made up of
SERVICE entitled by
METRIC with
basis for
subject of
CONTACT
for employed at ACCOUNT
covered by employer of
PREVENTIVE entitled by for
MAINTENANCE
basis for covered by
constrained by
SERVICE
used by CALENDER
Service Calendars and Work Shifts

This ERD (shown in Figure 56) 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 56. Service Calendars and Work Shifts ERD Entities and Tables
Entity Tables
Employee S_CONTACT, S_EMP_PER, S_PARTY
Employee Exception Hours S_EXCPT_CAL_HRS
Exception Calendar S_EXCPT_CAL
Exception Calendar Hours S_EXCPT_CAL_HRS
Schedule Calendar S_SCHED_CAL
Schedule Calendar Hours S_SCHED_CAL_HRS
Service Calendar S_SCHED_CAL
Work Shift S_SCHED_CAL

Figure 56. Service Calendars and Work Shifts

Title : Service Calendars and Work Shifts
SCHEDULE EXCEPTION
CALENDAR CALENDAR
HOURS HOURS
EMPLOYEE
EXCEPTION
HOURS
worked by for for
of
of
contributor of EXCEPTION
SCHEDULE CALENDAR
CALENDAR
PERSON SERVICE CALENDAR for of
EMPLOYEE /
OTHER PERSON AGENT
assigned to
WORK SHIFT
worked by
manager of a report to

Service Request
This ERD (shown in Figure 57) 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 57. Service Request ERD Entities and Tables
Entity Tables
Activity S_EVT_ACT
Asset (Product Instance) S_ASSET
External Product Instance S_ORG_PRDEXT
Party S_PARTY, S_ORG_EXT, S_CONTACT, S_USER
Product or Service S_PROD_INT, S_PROD_EXT
Service Region S_SRV_REGN

made up of part of
Title : Service Request
130
ACTIVITY
SERVICE REQUEST ACTIVITY OTHER ACTIVITY
for responsibility of
responsibility of
part of
made up of subject of
SERVICE REQUEST PARTY
PERSON
Figure 57. Service Request
responsible for
responsibility of responsible for

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

in in ORGANIZATION UNIT
environment environment for problems for problems
of of with with

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

PRODUCT
PRESENCE of EXTERNAL INTERNAL PRODUCT OR SERVICE
PRODUCT OR
subject of SERVICE
at
subject of
Shipment
This ERD (shown in Figure 58) 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 58. Shipment ERD Entities and Tables
Entity Tables
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
Quote S_DOC_QUOTE, S_DOC_ORDER
Quote Item Delivery Promise S_QTE_ITM_DLVRQ
Quote Item Delivery Request S_QTE_ITM_DLVRQ
Quote Line Item S_QUOTE_ITEM
Shipment S_SHIPMENT

%
Oracle
132
13
!">"$
!&
613 $$'
%9"$'$"
3 ">"$
!"!'>+"% +
3
Figure 58. Shipment

9">"$

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

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

!
1
7&
1


$>$+' $

Siebel Assistant
This ERD (shown in Figure 59) 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 59. Siebel Assistant ERD Entities and Tables
Entity Tables
Activity S_EVT_ACT
Activity Plan S_EVT_ACT
Activity Plan Template S_TMPL_PLANITEM
Assessment Template S_TMPL_PLANITEM
Assessment S_ASSESS
Assessment Attribute S_ASSESS_ATTRIB
Assessment Attribute Valid Value S_ASSESS_ATTVAL
Assessment Value S_ASSESS_VAL

Opportunity S_OPTY
Opportunity Stage S_OPTY_STG
Sales Methodology S_SALES_METHOD
Sales Stage S_STG
Stage Plan Item S_STG_PLANITEM
Stage Recommendation S_STG_RECOMMEND
Template Activity S_EVT_ACT

Title : Siebel Assistant
134
part of made up of
ASSESSMENT VALUE ASSESSMENT ATTRIBUTE ACTIVITY STAGE PLAN ITEM STAGE

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

TEMPLATE
for of at
created during for
SALES STAGE
for
of of of
subject of
planned by

PERSON
EMPLOYEE /
AGENT OPPORTUNITY STAGE of
for
OTHER of
PERSON
subject of for
currently at
subject of OPPORTUNITY
for for
ACCOUNT composed of
governed by
SALES
governor of METHODOLOGY
Territory Management
This ERD (shown in Figure 60) 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 60. Territory Management ERD Entities and Tables
Entity Tables
Account S_ORG_EXT
Account Team Member S_ACCNT_POSTN
Account/Terr Mapping S_TERR_ACCNT
Asset S_ASSET
Asset Team Member S_ASSET_POSTN
Asset/Terr Mapping S_TERR_ASSET
Business Unit S_BU
Contact S_CONTACT
Contact/Terr Mapping S_TERR_CON
Contact Team Member S_POSTN_CON
Division S_ORG_EXT
Geo/Terr Mapping S_TERR_ZIP, S_TERR_REGION
Position S_POSTN
Position Territory Assignment S_TERR_POSITION
Region S_REGION
Territory S_TERRITORY
Territory Hierarchy S_TERR_HIER
Territory Version S_TERRHIER_NODE
Zipcode (None)

3"
136
Oracle
+

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

0
"$
"$
"$
"$

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

&$""".

13

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

13
&$


$ 13


13
.&%$%%&$
%%

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

Territory Quota Rollup

This ERD (shown in Figure 61) 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 61. Territory Quota Rollup ERD Entities and Tables
Entity Tables
Sales Quota S_SLS_QUOTA
Territory S_TERRITORY
Territory Quota S_TERR_QUOTA
Account/Quota S_QUOTA_ACCNT
Contact/Quota S_QUOTA_CON
Geo/Quota S_QUOTA_REGN, S_QUOTA_ZIP
Quota Assignment Breakdown S_QTA_ACC_PD, S_QTA_CON_PD,

S_QTA_REGN_PD, S_QTA_ZIP_PD
Contact /Terr Mapping S_TERR_CON
Account / Terr Mapping S_TERR_ACCNT
Geo/Terr Mapping S_TERR_REGION, S_TERR_ZIP
Terr/Qta/Geo S_TERR_QTA_REGN, S_TERR_QTA_ZIP
Terr/Qta/Con S_TERR_QTA_CON
Terr/Qta/Accnt S_TERR_QTA_ACCT
Accnt Quota Credit S_TRQT_ACC_CRDT
Contact Quota Credit S_TRQT_CON_CRDT
Geo Quota Credit S_TRQT_REGNCRDT, S_TRQT_ZIP_CRDT
Period Quota S_QTA_PD_BRKDN
Terr Quota Breakdown S_TRQT_PD_BRKDN

+7& +
138

$7& $ 7&
7&
! ! !

+7&"$
070 $ 070 $ 070

213

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

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

1 2

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

6
2

2

9 '
&$ $
1
7&%%
$"$ [ !

$
! .<!;$
7&
15 6

14

14 7&%%

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

07& 37
Oracle

Textile, Apparel, and Footwear

This ERD (shown in Figure 62) 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 62. Textile, Apparel, and Footwear ERD Entities and Tables
Entity Tables
Marketing Segment S_MKT_SEG
Order S_ORDER
Organization External S_ORG_EXT

Period S_PERIOD
Period Relationship S_PERIOD_REL
Product Attribute Type S_LST_OF_VAL
Product Attribute Value S_LST_OF_VAL
Product Option Mix Preference S_PROD_OPT_MIX
Product Option Mix Proportion S_PROD_OPT_PCT
Product Option Range S_PROD_OPTION
Product Option Range Member S_PROD_OPT_VAL
Quote S_DOC_QUOTE

ORDER ITEM
primarily composed of subject of PRODUCT ATTRIBUTE VALUE
140
relevant to
ORDERED secondarily composed of subject of
ASSORTMENT SHOE SIZE COLOR
PLAN ITEM
primarily of subject of COLOR
PROPORTION
FAMILY
PRODUCT OPTION OTHER ATTRIBUTE VALUE includer
MIX PROPORTION of
of QUOTE ITEM secondarily of subject of
subject subject of
split into of a value
ASSORTMENT PLAN ITEM applicable to
of
for of SCHEDULED DELIVERY
ORDERED
ASSORTMENT
PLAN ITEM of subject of the domain
defined for
for primary defined by collection of
scheduled PRODUCT OPTION MIX PREFERENCE
by (SPREAD) PRODUCT
primarily specified secondary defined by collection of ATTRIBUTE
for of on TYPE
ASSORTMENT specify ACCOUNT RECOMMENDED
PLAN ITEM secondarily specified SPECIFIC MIX
specify on MIX
for primarilly secondarily
specific to the specific to of of primary secondary
default items within domain domain for
composed mix for for
for PRODUCT OPTION
Figure 62. Textile, Apparel, and Footwear
of RANGE MEMBER
ordered on belonging to scope of
ORDER definer of
for
billed to for PRODUCT INTERNAL
ORGANIZATION recommended to be ordered in
EXTERNAL
STYLE/COLOR/DIMENSION
ACCOUNT
primarily
defined created from launched applicable defined for collection defined by secondarily
for in to of defined by
STORE composed
composed of
of parent to defined for
lead to PRODUCT OPTION RANGE
OTHER CATEGORY
subject of ORGANIZATION
QUOTE
defined for

NON-SEASONAL
for primarily
for manufactured in in
ASSORTMENT subject of SIZE RUN
composed of
PLAN
MARKETING secondarily
SEGMENT the target of targetted at LINE OF BUSINESS manufactured in in
defined for SEASONAL
debut season for a collection of
COLOR PALETTE
PERIOD subject of defined for
SEASON
subject of
delivery period for delivery period for
of made up
PERIOD RELATIONSHIP of
Title : Textile, Apparel and Footwear
to part of Author : Oracle, Confidential
WEEK OTHER PERIOD TYPES
Time Sheet
This ERD (shown in Figure 63) 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 63. Time Sheet ERD Entities and Tables
Entity Tables
Activity S_EVT_ACT
Period S_PERIOD
Project S_PROJ
Time Unit S_TMSHT_ITEM
Timesheet S_TMSHT
Timesheet Approval S_TMSHT_APPR
Timesheet Line S_TMSHT_LN
Work Type S_PROJ

Title : Time Sheet
142
adjusted
ACTIVITY
TIME UNIT
Figure 63. Time Sheet
adjustment
TIME ADJUSTMENT WORK TIME UNIT based
basis for
owned by targeted at owned by associated with

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

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

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

WORK TYPE INTERNAL OTHER
ORGANIZATION UNIT ORGANIZATION
made up of
UNIT
submitted for
TIME SHEET referenced by
composed of

PERIOD
reported for
affiliated with
reporter of
for
owner of
PERSON
reported by
EMPLOYEE/AGENT
reporter of
approved
contact for
approver
OTHER PERSON
Trade Promotions
This ERD (shown in Figure 64) 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 64. Trade Promotions ERD Entities and Tables
Entity Tables
Contract S_D0C_AGREE, S_DOC_QUOTE, S_ORDER
Contract Item S_AGREE_ITEM, S_QUOTE_ITEM, S_ORDER_ITEM
Internal Product Presence S_ORG_PROD
Marketing Event or Activity S_SRC, S_SRC_CHNL
Note S_NOTE_SRC
Order S_ORDER
Other Contract S_DOC_AGREE, S_DOC_QUOTE
Product S_PROD_INT, S_PROD_EXT

Oracle
144
!"
13

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

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

?13
%$
?

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

$
14
213
"$

9"<$

>$ >+ 14
$

!&
!& 8$'
14 14
!& $$'
Training Curriculum Course

This ERD (shown in Figure 65) 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 65. Training Curriculum Course ERD Entities and Tables
Entity Tables
Employee Course S_EMP_CRSE
Employee Course Status S_EMP_CRSE_STAT

Title : Training Curriculum Course
CURRICULUM CURRICULUM ACCESS GROUP
146
TRAINING
CURRICULUM STEP TARGET AUDIENCE CATEGORY
part of
TRAINING
CURRICULUM composed of
STEP COURSE part of target of for granted access to
composed of targeted at belongs to accessed by
TRAINING CURRICULUM
part of
composed of
of
categorized into provide training for subject of subject of
Figure 65. Training Curriculum Course
EMPLOYEE COURSE STATUS
of
COURSE
AVAILABLE
LANGUAGE tracked by
EMPLOYEE COURSE certified for

available for path satisfied by for
needed by for
CATALOG CATEGORY JOB PROFILE LITERATURE CURRICULUM
PERSON
MARKETING EVENT OR ACTIVITY
for satisfied by for

OTHER MARKETING EVENT OR

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

basis of PERSON
TRAINING COURSE
OTHER PRODUCT OR SERVICE

Training Test Engine

This ERD (shown in Figure 66) 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 66. Training Test Engine ERD Entities and Tables
Entity Tables
Course/Course Offering Test S_CRSE_OFFR_TST
Individual’s Test S_CRSE_TSTRUN
Individual’s Test Answer S_CRSE_TSTRUN_A
Individual’s Test Category S_TSTRUN_CATSTS
Individual’s Test Question S_CRSE_TSTRUN_Q
Pool Question S_POOL_QUES
Question/Possible Answer S_CRSE_TST_ANSR
Question/Question Pool, Question Pool, Question S_TST_QUES

Question Category LOV
Test Available Language S_CRSE_TST_LANG
Test Question S_CRSE_TST_QUES
Topic/Objective S_CRSE_TOPIC
Training Course S_PROD_INT_CRSE, S_PROD_INT
Training Course Offering S_SRC_EVT, S_SRC
Training Test S_CRSE_TST

Oracle
148
'7&%$

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

14 7&%$ 7&%$
14 '

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

%7&%$
13

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

+ '$
&

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

14
7&%$ 0.= >

+
>$' $

6

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

Versioned Object Definition (shown in Figure 67) 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 67. Versioned Object Definition ERD Entities and Tables
Entity Tables
Attribute Definition S_ISS_ATTR_DEF
Attribute Value S_ISS_ATTR_VAL
Joint Workspace S_ISS_JWS
Joint Workspace Item S_ISS_JWS_ITEM
Object Attribute S_ISS_OBJ_ATTR
Object Attribute Value S_ISS_OBATR_VAL
Object Definition S_ISS_OBJ_DEF
Object Definition S_VOD
Versioned Object Definition Version S_VOD_VER

Title : Versioned Object Definition
150
OBJECT ATTRIBUTE VALUE JOINT WORKSPACE
PRODUCT ATTRIBUTE VALUE PRODUCT TEMPLATE

ATTRIBUTE VALUE
for for for for

have
for
have
OBJECT ATTRIBUTE JOINT WORKSPACE

Figure 67. Versioned Object Definition
have ITEM
PRODUCT PRODUCT TEMPLATE

ATTRIBUTE ATTRIBUTE
locally locally for

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

have

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

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

OBJECT DEFINITION
DEFINITION VERSION
PRODUCT DEFINITION PRODUCT TEMPLATE
DEFINITION
Warranty
This ERD (shown in Figure 68) 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 68. Warranty ERD Entities and Tables
Entity Tables
Asset S_ASSET
Asset Warranty Coverage S_ASSET_WRNTY
Order S_ORDER
Product S_PROD_INT
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

Title : Warranty
152
ORDER ITEM claimed against ASSET of ASSET PRODUCT
WARRANTY an instance of
applied to COVERAGE subject of
made into
part of by
Figure 68. Warranty
PRODUCT of
WARRANTY
COVERAGE subject of
part of vended by
by
composed of
ORDER
SERVICE ORDER composed of

PRODUCT LINE
WARRANTY subject of
COVERAGE PRODUCT
OTHER ORDER of LINE
by
made up of made up of made up of made up of
WARRANTY COVERAGE
of
WARRANTY SERVICE a part of
PROVIDER provided by
provided by

vendor of
warrantor of
ORGANIZATION UNIT
role played by
subject of
4 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 153
■ “Data Model Type Definitions” on page 156
■ “Siebel System Fields” on page 160
■ “INTEGRATION_ID Columns” on page 161
■ “Include Only Field” on page 161
■ “Siebel Repository” on page 161
■ “Database Schema Version” on page 161
■ “Limit Checking for Data Types” on page 162
■ “Party Model Unifies Access to Data” on page 162
Data Model Naming Conventions

This topic describes:
■ Table Naming Conventions
■ Index Naming Conventions on page 155
■ Column Naming Conventions on page 155
■ Abbreviations Used in the Physical Model Listings on page 156
Table Naming Conventions

Tables in the Siebel database use a three-part naming convention. The syntax is:
PREFIX_NAME_SUFFIX.
PREFIX Table names in Siebel Business Applications have a one- to three-letter prefix (EIM_,
S_, W_, and so on) to distinguish them from other tables in your application.
NAME A unique table name that is generally an abbreviation of the entity supertype name.
SUFFIX A supertype name may be followed by the entity subtype. For example, the supertype
EVT (event) has ACT (activity) as one of its subtypes. Thus, the name becomes
S_EVT_ACT.

Physical Model ■ Data Model Naming Conventions
The prefix indicates the part of the Siebel schema to which a table belongs. Table 69 provides some
of the prefixes and their descriptions.
Table 69. 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 70 provides some of the suffixes and their descriptions.
Table 70. 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.

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 71.
Table 71. Standard Index Suffixes
Unique or
Suffix Value 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 Not unique
foreign key and system foreign key columns not ordinarily
indexed (for example, primary address, primary contact, creator,
and so on).
_M# Miscellaneous index. Any index that does not fit into one of the Not unique
above categories.
CAUTION: Before modifying or deleting indexes, create a service request (SR) on 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 72 shows the standard
suffixes for column names and their possible values.
Table 72. 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.

Physical Model ■ Data Model Type Definitions
Table 72. 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 73.
Table 73. 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 78 on page 160.
Data Model Type Definitions

This topic contains the following type definitions:
■ Table Type Definitions on page 157
■ Table Status Definitions on page 158
■ Column Type Definitions on page 159
■ Domain Type Definitions on page 159

Table Type Definitions

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

(Intersection) intersection table implements a many-to-many relationship between two data
tables. The name of an intersection table is usually composed by
concatenating the two table names, abbreviated if needed. For example
S_OPTY_POSTN is the intersection table between tables S_OPTY and
S_POSTN. Intersection tables cannot be extended using extension tables, but
can be extended using extension columns, subject to database restrictions.
Data (Private) Data (Private) tables contain application administration or system data.
Private tables cannot be extended using extension tables or extension
columns.
Data (Public) Data (Public) tables contain application or end-user data. Public data tables
can be extended using extension tables and, subject to database restrictions,
extension columns.
Database View Database View objects appear as tables with regular columns. These tables
represent database views. Objects of this table type are not created by the
ddlimp Siebel database utility. Underlying views are created by SQL scripts
during install and upgrade.
Dictionary S_APP_VER is the only table in this category. This table has only one row and
contains information about the application such as major and minor version,
application name, unicode flag, and so on. This table contains information
about the data dictionary.
Extension Extension tables implement a one-to-one relationship with a data table to

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

Table 74. 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 75.
Table Status Definitions

Table 75 provides descriptions of the types of table status in the Siebel database.
Table 75. 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.

Column Type Definitions

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

Table 77 provides descriptions for the domain types of certain columns in the Siebel database.
Table 77. 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 The List of Values type against which this column is validated.
Bounded In the LOVB case, end users must specify a value from the list,
whereas in the LOV case, the user can enter a value not
contained in the list.

Physical Model ■ Columns of Numeric Physical Type
Table 77. Domain Types
Domain
Type Meaning Domain Contains
MLOV Multilingual List of The List of Values type against which this column is validated,
Values in multiple languages. End users must specify a value from the
list, but see the values in their preferred language.
MLS Multiple Language The name of the table in which the translation in an alternate
Support language can be found.
DNRM Denormalized The path to the original column, used by the Object Manager to
synchronize the values, in the form of [foreign key
column].[original column]. For example, the ACCNT_NAME
column of table S_ACCNT_POSTN is denormalized; its domain
is [OU_EXT_ID].[NAME]. In other words, the contents of
column NAME of the table referenced by OU_EXT_ID
(S_ORG_EXT) are replicated into column ACCNT_NAME of table
S_ACCNT_POSTN. Denormalization is used to improve query
performance.
(blank) There is no domain specified for this column.
Columns of Numeric Physical Type

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

Every Siebel table contains the system fields described in Table 78. Do not alter the contents of these
fields.
Table 78. Siebel System Fields
Column Name Description
CONFLICT_ID Unique value used to resolve Siebel remote routing conflicts if

necessary; otherwise, value is zero.
CREATED Date the record was entered.
CREATED_BY User who entered the record (foreign key to S_USER).
DCKING_NUM No longer used.

Physical Model ■ INTEGRATION_ID Columns
Table 78. Siebel System Fields
Column Name Description
LAST_UPD Date and time the record was last changed.
LAST_UPD_BY User who last changed record (foreign key to S_USER).
MODIFICATION_NUM Internally incremented number used for locking and to identify

records for incremental updates of the Siebel Business Data
Warehouse.
ROW_ID Unique row identifier.
INTEGRATION_ID Columns
Many tables contain a column called INTEGRATION_ID for back office integration. Normally,
customers use this column to store the unique reference identifiers for corresponding records in the
back office application. These columns are currently used by the Siebel 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.
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 X.X.X.X where each instance of X
represents an integer with one, two, or more digits.

Physical Model ■ Limit Checking for Data Types
Limit Checking for Data Types

The Object Manager imposes limit checking on data of specific types to make sure that every input,
regardless of its source, is within specified limits (shown in Table 79). Sources of inputs include
Oracle’s 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 79. Input Limits on Data Types
Data Type Limit Checking
Dates Dates must be in the range of January 1, 1753 to December 31, 4712.
Long Maximum size of 16K
Text Maximum size of 16K
CLOB Maximum size of 128K
Validating the Siebel Schema

To make sure that there are no inconsistencies between the Siebel Database Server and the physical
database schema, use the Siebel Server utility dbchck.exe (Windows) or dbchck (UNIX). You can use
the dbchck utility to validate data relationships, including foreign keys and the list of values. You can
also use the DICTUTL utility to verify that all doc objects and rule definitions are correct. For more
information about how to use these utilities, see Siebel Enterprise Integration Manager
Administration Guide.
Party Model Unifies Access to Data

The party model is a means of unifying all access to data about relationships. This covers
relationships between your company and people (contacts, employees, partner employees, users)
and other businesses (accounts, divisions, organizations, partners). The base table for all such
access is S_PARTY. Related tables are implicitly joined as extension tables. Table 80 lists the
extension tables and their corresponding EIM interface tables.
Table 80. 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

Physical Model ■ Party Model Unifies Access to Data
Table 80. S_PARTY Extension Tables and Corresponding EIM Interface Tables
Data Type Extension Table to S_PARTY EIM Interface Table
Organizations S_ORG_BU EIM_ORG_BU
Positions S_POSTN EIM_POSITION
Users S_USER EIM_USER
Because the extension tables are implicitly joined to S_PARTY, you do not need to configure anything
to access them through S_PARTY. Some data types have a many-to-many relationship. For example,
any contact can be associated with multiple accounts or partners. To model these relationships there
are preconfigured intersection tables: S_PARTY_PER and S_PARTY_REL. Use S_PARTY_REL to
implement relationships between parties in the S_PARTY table. In this case, records in S_PARTY are
both parent (PARTY_ID) and child (PERSON_ID).
Use S_PARTY_PER to implement relationships between members:
■ Access groups and members
■ Accounts and contacts
■ Employees and positions
■ User lists and users

Physical Model ■ Party Model Unifies Access to Data

5 Schema Changes
This chapter lists the table, table column and table index changes in this schema:
■ “Table Changes in This Version” on page 165
■ “Table Column Changes in This Version” on page 171
■ “Table Index Changes in This Version” on page 185
Table Changes in This Version

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

Table 81 lists tables that are new in this version.
Table 81. New Tables in This Version
Table Type Active
S_AGREE_BNFT Data (Public) Yes

S_AGREE_COND Data (Public) Yes
S_AGR_COND_CMPL Data (Public) Yes
S_ALGN_IND_TMP Data (Private) Yes
S_ALGN_POSTN Data (Intersection) Yes
S_ALGN_POS_OPTY Data (Intersection) Yes
S_ALGN_PROD_TMP Data (Private) Yes
S_ALGN_QTA_ACCT Data (Intersection) Yes
S_ALGN_QTA_AFFL Data (Intersection) Yes
S_ALGN_QTA_CON Data (Intersection) Yes

S_ALGN_QTA_REGN Data (Intersection) Yes
S_ALGN_QTA_TERR Data (Intersection) Yes

Schema Changes ■ Table Changes in This Version
Table Type Active
S_ALGN_QTA_ZIP Data (Intersection) Yes
S_ALGN_QT_BRKDN Data (Intersection) Yes
S_ALGN_TERR_POS Data (Intersection) Yes
S_APP_VER_ATT Data (Private) Yes
S_AUDIT_JOIN Data (Private) Yes
S_AUDIT_LINK Data (Private) Yes
S_AUDIT_READ Data (Private) Yes
S_AUDIT_VERSION Data (Private) Yes
S_BDGTREQ_ORDER Data (Intersection) Yes
S_BR_CONCEPT Data (Private) Yes
S_BR_GBL_BINARY Data (Private) Yes
S_BR_GBL_PARM Data (Private) Yes
S_BR_KNWLDGBASE Data (Private) Yes
S_BR_MDL_BC_FLD Data (Private) Yes
S_BR_MDL_BC_REL Data (Private) Yes
S_BR_MODULE Data (Private) Yes
S_BR_MODULE_BIN Data (Private) Yes
S_BR_MOD_BC_REL Data (Private) Yes
S_DCP_CALL_LST Data (Intersection) Yes

S_DOCK_DL_MGR Data (Private) Yes
S_DOCK_TXN_SKIP Data (Private) Yes
S_DQ_BC_FLD_MAP Data (Private) Yes
S_DQ_BUSCOMP Data (Private) Yes
S_DQ_CON_KEY Data (Public) Yes
S_DQ_ORG_KEY Data (Public) Yes
S_DQ_PRSP_KEY Data (Public) Yes
S_DQ_RULE Data (Private) Yes
S_DQ_RULE_PARAM Data (Public) Yes
S_DQ_SYST Data (Private) Yes
S_DQ_SYST_PARM Data (Private) Yes
S_EMT_DPLYPKG Data (Public) Yes

Table Type Active
S_EMT_DPLYUNIT Data (Public) Yes
S_ENTL_BNFTTMPL Data (Public) Yes
S_ENTL_CONDTMPL Data (Public) Yes
S_ENT_SOLN Data (Public) Yes
S_FCSTSER_AGFLD Data (Public) Yes
S_FR_BID_LITM Data (Public) Yes
S_FUL_REQ_BID Data (Intersection) Yes
S_INST_UPG_HIST Data (Private) Yes
S_MKTGOFFR_BU Data (Intersection) Yes
S_MKTGOFFR_PROD Data (Intersection) Yes
S_MKTG_DOC_INVT Data (Intersection) Yes
S_MKTG_OFFR Data (Public) Yes
S_NODE_PREF Data (Private) Yes
S_NOTE_FUL_REQ Data (Public) Yes
S_NOTE_MDF Data (Public) Yes
S_OFFR_CBAST Data (Intersection) Yes
S_PROD_ACCNT Data (Public) Yes
S_PROD_CON Data (Intersection) Yes
S_PROJ_CBAST Data (Intersection) Yes

S_PRTFL_ACCNT Data (Intersection) Yes
S_PRTFL_ACCSOLN Data (Intersection) Yes
S_PRTFL_ACC_ATT Data (Public) Yes
S_PRTFL_ATT Data (Public) Yes
S_PRTFL_BU_DRVR Data (Public) Yes
S_PRTFL_BU_INTV Data (Public) Yes
S_PRTFL_CAMP Data (Intersection) Yes
S_PRTFL_CMPTR Data (Intersection) Yes
S_PRTFL_CTGRY Data (Public) Yes
S_PRTFL_ENTSOLN Data (Intersection) Yes
S_PRTFL_POSTN Data (Intersection) Yes
S_PRTFL_PRTNR Data (Intersection) Yes

Table Type Active
S_PRTFL_SUBACC Data (Intersection) Yes
S_QTA_ACC_PD Data (Intersection) Yes
S_QTA_CON_PD Data (Intersection) Yes
S_QTA_PARTYAFFL Data (Public) Yes
S_QTA_PD_BRKDN Data (Intersection) Yes
S_QTA_REGN_PD Data (Intersection) Yes
S_QTA_ZIP_PD Data (Intersection) Yes
S_QUOTA_ACCNT Data (Intersection) Yes
S_QUOTA_CON Data (Intersection) Yes
S_QUOTA_REGN Data (Intersection) Yes
S_QUOTA_ZIP Data (Intersection) Yes
S_RTS_BIG_ATT Data (Public) Yes
S_RTS_CFG Data (Public) Yes
S_RTS_LOG Data (Public) Yes
S_RTS_MSG_HSTRY Data (Public) Yes
S_RTS_STATE Data (Public) Yes
S_RTS_SUBSCRN Data (Public) Yes
S_RTS_TIMEOUT Data (Public) Yes
S_RTS_TMOUT_VAL Data (Public) Yes

S_RTS_WQ Data (Public) Yes
S_RTS_WQ_USER Data (Public) Yes
S_SD_ATTENDEE Data (Private) Yes
S_SLS_PORTFOLIO Data (Public) Yes
S_SLS_QUOTA Data (Public) Yes
S_SRCH_CHG_TXN Data (Private) Yes
S_SRCH_CTGRY Data (Private) Yes
S_SRCH_CTG_FLD Data (Private) Yes
S_SRCH_CTG_REL Data (Private) Yes
S_SRCH_OPERATOR Data (Private) Yes
S_SRCH_SAVED Data (Private) Yes
S_SRCH_USR_PREF Data (Private) Yes

Table Type Active
S_SRC_BDGT_REQ Data (Intersection) Yes
S_SRC_CBAST Data (Intersection) Yes
S_SRC_OFFR Data (Intersection) Yes
S_SRC_ORDER Data (Intersection) Yes
S_SRM_TASK_HIST Data (Public) Yes
S_TASK_DEFN_REL Data (Public) Yes
S_TEAMSPACEARCH Data (Public) Yes
S_TERRALGN_BU Data (Intersection) Yes
S_TERRALGN_IND Data (Intersection) Yes
S_TERRALGN_PROD Data (Intersection) Yes
S_TERRALGN_QTA Data (Intersection) Yes
S_TERRITORY_BU Data (Intersection) Yes
S_TERR_IND Data (Intersection) Yes
S_TERR_PROD Data (Intersection) Yes
S_TERR_QTA_ACCT Data (Intersection) Yes
S_TERR_QTA_AFFL Data (Intersection) Yes
S_TERR_QTA_CON Data (Intersection) Yes
S_TERR_QTA_REGN Data (Intersection) Yes
S_TERR_QTA_ZIP Data (Intersection) Yes

S_TERR_QUOTA Data (Intersection) Yes
S_TQ_AFFL_CRDT Data (Intersection) Yes
S_TRQT_ACCT_PD Data (Intersection) Yes
S_TRQT_ACC_CRDT Data (Intersection) Yes
S_TRQT_AFFL_PD Data (Intersection) Yes
S_TRQT_CON_CRDT Data (Intersection) Yes
S_TRQT_CON_PD Data (Intersection) Yes
S_TRQT_PD_BRKDN Data (Intersection) Yes
S_TRQT_REGNCRDT Data (Intersection) Yes
S_TRQT_REGN_PD Data (Intersection) Yes
S_TRQT_ZIP_CRDT Data (Intersection) Yes
S_TRQT_ZIP_PD Data (Intersection) Yes

Table Type Active
S_TU_INST Data (Public) Yes
S_TU_LOG Data (Private) Yes
S_TU_LOG_MAP Data (Private) Yes
S_TU_LOG_X_01 Extension Yes
S_UIC_APLT_GRP Data (Public) Yes
S_UIC_APLT_LANG Data (Public) Yes
S_UIC_APPLET Data (Public) Yes
S_UIC_ATAB_GRP Data (Public) Yes
S_UIC_ATAB_ITEM Data (Public) Yes
S_UIC_VIEW Data (Public) Yes

S_UIF_WEB_FILE Data (Private) Yes
S_USR_PREF_UOM Data (Public) Yes
S_WEBCHNL_SES Data (Public) Yes
S_WEBCHNL_SNSVC Data (Public) Yes
S_WEBCHNL_USR Data (Public) Yes
S_WFA_ANLY_INFO Data (Public) Yes
S_WFA_ANLY_PROP Data (Public) Yes
S_WFA_ANLY_TS Data (Public) Yes
S_WFA_INST_PRM Data (Public) Yes
S_WFA_INTL Data (Private) Yes

Schema Changes ■ Table Column Changes in This Version
Modified Tables in This Version

Table 82 lists tables whose type has changed in this version.
Table 82. Tables with Changed Type
Table Previous Type New Type
S_AUDIT_CHILDBC Data (Public) Data (Private)
T_MASTER_DTL2_X Extension (Siebel) Extension
Table Column Changes in This Version

This topic lists the following changes to columns that have been implemented in this version of the
schema:
■ “New Table Columns in This Version” on page 171
■ “New System Columns in This Version” on page 184
■ “Modified Table Columns in This Version” on page 184
New Table Columns in This Version

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

1 72
Table 83. New Table Columns in This Version
Data LOV
Table Name Column Opt Type Len Prec Scale Default LOV Type Bnd
S_AC_RSRC_RESP PERM_FLAG_VAL N Number 22 10 0 0
S_ADDR_ORG ALIGNMENT_FLG N Char 1 N
S_ADDR_PER ALIGNMENT_FLG N Char 1 N
S_ADJ_GROUP INTEGRATION_ID Y Varchar 30
S_ALGN_ACCT_TMP AFFL_OBJECT_CD Y Varchar 30
S_ALGN_CON_TMP AFFL_OBJECT_CD Y Varchar 30
S_ALGN_REGN_TMP AFFL_OBJECT_CD Y Varchar 30
S_ALGN_REGN_TMP ASGN_OBJECT_CD Y Varchar 30
S_ALGN_ZIP_TMP AFFL_OBJECT_CD Y Varchar 30
S_ALGN_ZIP_TMP ASGN_OBJECT_CD Y Varchar 30
S_ALGN_ZIP_TMP GEO_TYPE_CD Y Varchar 30
S_APP_QUERY OWNER_ID Y Varchar 15
S_APP_VER AUDIT_ADMIN_VER Y Varchar 30
S_AUDIT_BUSCOMP BASE_TBL_NAME N Varchar 30 x
S_AUDIT_BUSCOMP DESC_TEXT Y Varchar 250
S_AUDIT_BUSCOMP EXPORT_FLG N Char 1 N
S_AUDIT_BUSCOMP SYS_AUDIT_FLG N Char 1 N
S_AUDIT_FIELD COL_NAME Y Varchar 30
S_AUDIT_FIELD JOIN_NAME Y Varchar 75
S_AUDIT_FIELD READ_FLG N Char 1 N
S_AUDIT_FIELD READ_FV_FLG N Char 1 N
S_AUDIT_FIELD SPECIAL_JOINED_FLG N Char 1 N
S_AUDIT_FIELD TBL_NAME Y Varchar 30
S_AUDIT_ITEM AUDIT_LOG Y CLOB 137625

6
S_AUDIT_ITEM AUDIT_SOURCE_CD Y Varchar 50

Data LOV
S_AUDIT_ITEM BC_BASE_TBL Y Varchar 30
S_AUDIT_ITEM CHILD_BC_BASE_TBL Y Varchar 30
S_AUDIT_ITEM CHILD_RECORD_ID Y Varchar 15
S_AUDIT_ITEM GROUP_NUM Y Varchar 15
S_AUDIT_ITEM ITEM_IDEN_NUM Y Number 22 15 0
S_AUDIT_ITEM LINK_NAME Y Varchar 175
S_AUDIT_ITEM NODE_NAME Y Varchar 50
S_AUDIT_ITEM SRC_DEST_ID Y Varchar 15


S_AUDIT_ITEM SYNC_DT Y UTC 7
DateTime
S_AUDIT_ITEM TBL_NAME Y Varchar 30
S_AUDIT_ITEM TBL_RECORD_ID Y Varchar 15
S_CAMP_CALL_LST FLOWCHART_CNCTR Y Varchar 1999
S_CAMP_CON DCP_ID Y Varchar 15
S_CB_ASSET MKTG_ASSET_FLG N Char 1 N
S_CM_CNCTR SRCH_ENGINE_ID Y Varchar 15
S_COMMUNICATION DCP_ID Y Varchar 15
S_CONTACT PRESENCE_URI Y Varchar 100
S_CON_ADDR ALIGNMENT_FLG Y Char 1 N
S_CON_SYNC_SCHD CALL_LST_ID Y Varchar 15
S_CS_PATH DEPLOY_READY_FLG N Char 1 N
S_DMND_CRTN_PRG DPLY_INSTRT_TEXT Y Varchar 250
S_DMND_CRTN_PRG LAST_SYNC_DT Y UTC 7

DateTime
S_DMND_CRTN_PRG MKTG_OFFR_ID Y Varchar 15
S_DMND_CRTN_PRG NEED_TO_SYNC_FLG N Char 1 N

173
S_DMND_CRTN_PRG OFFR_GROUP_CD Y Varchar 30 RTD_OFFER_GROUP Yes


1 74
Data LOV
S_DMND_CRTN_PRG PR_CAMPAIGN_ID Y Varchar 15
S_DMND_CRTN_PRG RTD_STATUS_CD Y Varchar 30 RTD_OFFER_STATUS Yes
S_DMND_CRTN_PRG VERSION_NUM Y Number 22 10 0 1
S_DOCK_TXN_LOG LOG_DATA_CLOB Y CLOB 131072

0
S_DOCK_TXN_LOG LOG_DATA_CLOB_LEN Y Number 22 10 0
S_DYN_HRCHY HIER_LAST_UPD Y UTC 7

DateTime
S_EMT_DSET_ITEM DEPLOY_MODE_CD N Varchar 30 Upsert EMT_OPERATION Yes
S_EMT_DSET_ITEM PDQ_ID Y Varchar 15
S_EMT_OBJECT EXPORT_BS_NAME Y Varchar 75
S_EMT_OBJECT EXPORT_MTHD_NAME Y Varchar 75
S_EMT_OBJECT IMPORT_BS_NAME Y Varchar 75
S_EMT_OBJECT IMPORT_MTHD_NAME Y Varchar 75
S_EMT_OBJECT PRVW_SP_BS_NAME Y Varchar 75
S_EMT_OBJECT PRVW_SP_MTHD_NAME Y Varchar 75
S_EMT_OBJECT XPT_VLD_BS_NAME Y Varchar 75
S_EMT_OBJECT XPT_VLD_MTHD_NAME Y Varchar 75
S_EMT_SESSN_ITM DEPLOY_MODE_CD N Varchar 30 Upsert EMT_OPERATION Yes
S_EMT_SESSN_ITM PDQ_ID Y Varchar 15
S_ENTL_PRDPRI AGREE_BNFT_ID Y Varchar 15
S_ENTL_PRDPRI CTLG_CAT_ID Y Varchar 15
S_ENTL_PRDPRI XA_CLASS_ID Y Varchar 15
S_ENTMPL_PRDPRI BNFT_TMPL_ID Y Varchar 15
S_ENTMPL_PRDPRI CTLG_CAT_ID Y Varchar 15
S_ENTMPL_PRDPRI XA_CLASS_ID Y Varchar 15
S_EVT_FUL_REQ COMMENTS Y Varchar 30

Data LOV
S_EVT_FUL_REQ EVTLOC_ID Y Varchar 15
S_EVT_FUL_REQ MKTG_ASSET_STAT_CD Y Varchar 30
S_EVT_MKTG CALL_REASON_CD Y Varchar 30 TODO_TYPE Yes
S_EVT_MKTG EVT_FUL_REQ_ID Y Varchar 15
S_EVT_MKTG PORTFOLIO_ID Y Varchar 15
S_EVT_MKTG PRTFL_ACCNT_ID Y Varchar 15
S_EVT_MKTG PRTFL_CTGRY_ID Y Varchar 15
S_EVT_MKTG STRTGY_CMPNT_CD Y Varchar 30 PMP_STATEGY_COMP Yes


S_FCST MGR_UPD_FLG N Char 1 N
S_FCSTSER QTY_AGFLD_ID Y Varchar 15
S_FCSTSER_POSTN AGGR_LVL_NUM Y Number 22 10 0
S_FCSTSER_POSTN FCSTSER_AGFLD_ID Y Varchar 15
S_FCST_ITEM_DTL ADJ_AMT Y Number 22 22 7
S_FCST_ITEM_DTL AGGR_DIM_NAME_1 Y Varchar 50
S_FCST_ITEM_DTL AGGR_FIELD_CD Y Varchar 30
S_FCST_ITEM_DTL CONV_QTY Y Number 22 22 7
S_FCST_ITEM_DTL CONV_UOM_CD Y Varchar 30
S_FCST_ITEM_DTL EXPECT_AMT Y Number 22 22 7
S_FCST_ITEM_DTL PAR_FCST_ITMDTL_ID Y Varchar 15
S_FCST_ITEM_DTL PERIOD_NAME Y Varchar 50

175
S_FCST_ITEM_DTL SEQ_NUM N Number 22 10 0 1


1 76
Data LOV
S_FCST_ITEM_DTL UOM_CONV_FCTR Y Number 22 22 7
S_FUL_REQ_ITEM CB_ASSET_ID Y Varchar 15
S_FUL_REQ_ITEM COLOR_SPEC Y Varchar 50
S_FUL_REQ_ITEM NUM_SAMPLES Y Number 22 10 0
S_FUL_REQ_ITEM PAPER_TYPE Y Varchar 50
S_FUL_REQ_ITEM RQMNT_DESC_TEXT Y Varchar 250
S_HH_SYNC_SESSN BATCH_SESSION_FLG N Char 1 N
S_HH_SYNC_SESSN DBXTRACT_CMPLT_TS Y UTC 7

DateTime
S_HH_SYNC_SESSN DBXTRACT_SCHLD_TS Y UTC 7

DateTime
S_HH_SYNC_SESSN DBXTRACT_STAT_CD Y Varchar 30 BATCHSYNC_EXTRACT_STATUS Yes
S_HH_SYNC_SESSN TXN_PROC_CMPLT_TS Y UTC 7

DateTime
S_HH_SYNC_SESSN TXN_PROC_STAT_CD Y Varchar 30 BATCHSYNC_TXN_STATUS Yes
S_HH_SYNC_SESSN TXN_RECEIVED_TS Y UTC 7

DateTime
S_HH_SYNC_SUM BATCH_SESSION_FLG N Char 1 N
S_HH_SYNC_SUM BO_FILTER_STRING_1 Y Varchar 1999
S_HH_SYNC_SUM DBXTRACT_CMPLT_TS Y UTC 7

DateTime
S_HH_SYNC_SUM DBXTRACT_SCHLD_TS Y UTC 7

DateTime
S_HH_SYNC_SUM DBXTRACT_STAT_CD Y Varchar 30 BATCHSYNC_EXTRACT_STATUS Yes
S_HH_SYNC_SUM TARGET_CLIENT_TYPE Y Varchar 30
S_HH_SYNC_SUM TXN_PROC_CMPLT_TS Y UTC 7

DateTime
S_HH_SYNC_SUM TXN_PROC_STAT_CD Y Varchar 30 BATCHSYNC_TXN_STATUS Yes

Data LOV
S_HH_SYNC_SUM TXN_RECEIVED_TS Y UTC 7
DateTime
S_INVOICE AGREE_BNFT_ID Y Varchar 15
S_MDF APPR_STATUS_CD Y Varchar 30 MKTG_PLAN_APPR_TYPE Yes
S_MDF INIT_FUND_AMT Y Number 22 22 7
S_MDF OWNER_ID Y Varchar 15
S_MDF REGION_ID Y Varchar 15
S_MKTG_BDGT_REQ MKTG_FUND_ID Y Varchar 15


S_NODE NODE_AUDIT_VER_NUM Y Varchar 30
S_NODE REAL_TM_SYNC_FLG N Char 1 N
S_OPTY_POSTN ASGN_RULE_GRP_ID Y Varchar 15
S_OPTY_POSTN ASGN_TERR_ID Y Varchar 15
S_OPTY_SRC DCP_ID Y Varchar 15
S_ORDER AGREE_BNFT_ID Y Varchar 15
S_ORDER DCP_ID Y Varchar 15
S_ORDER INIT_APRV_AMT Y Number 22 22 7
S_ORDER PURCH_ORD_EXP_TS Y TimeStamp 7
S_ORDER TOTAL_AMT Y Number 22 22 7
S_PRTNRPRG_APPL AGREE_ITEM_ID Y Varchar 15
S_PRTNRPRG_APPL AGR_IT_DT_USED_FLG N Char 1 N
S_PRTNRPRG_APPL PRTNRPRG_MBR_ID Y Varchar 15
S_PRTNRPRG_MBR AGREE_ITEM_ID Y Varchar 15
S_PRTNRPRG_MBR MEMBERSHIP_NUM N Varchar 30 x
S_PRTNR_PROG PROD_INT_ID Y Varchar 15
S_REVN ENT_SOLN_ID Y Varchar 15
S_REVN EXPECT_AMT Y Number 22 22 7

177
S_REVN REVN_TYPE_CD Y Varchar 30 PMP_REVENUE_TYPE Yes


1 78
Data LOV
S_RT_SVC STATE_MGMT_TYPE_CD Y Varchar 30 STATEFUL REPOSITORY_SVC_STATEMGM Yes

T_CD
S_SD_PIM_ROW OWNER_APPT_ID Y Varchar 15
S_SMQ_ADDR SECTKN_ENCRPKY_REF Y Number 22 10 0
S_SMQ_HISTORY MSG_ID_IDEN Y Varchar 50
S_SMQ_HISTORY SOURCE_OBJ_TYPE Y Varchar 100
S_SMQ_HISTORY SOURCE_OID Y Varchar 50
S_SMQ_HISTORY TYPE_CD Y Varchar 30 SMQ_MSG_TYPE Yes
S_SRC BDGT_ALLOC_PCT Y Number 22 22 7
S_SRC FLOWCHART_CNCTR Y Varchar 1999
S_SRC MEDIA_SUBTYPE_CD Y Varchar 30 OFFER_MEDIA
S_SRC PR_MKTG_OFFR_ID Y Varchar 15
S_SRC SPONSOR_EMP_ID Y Varchar 15
S_SRC_COST BDGT_REQ_ID Y Varchar 15
S_SRC_COST EVT_FUL_REQ_ID Y Varchar 15
S_SRC_COST PURCH_ORDER_ID Y Varchar 15
S_SRC_EVT_REG AWARE_CHNL_CD Y Varchar 30 ATTENDEE_AWARENESS Yes
S_SRC_EVT_REG MEAL_PREF_CD Y Varchar 30 ATTENDEE_MEAL_PREF Yes
S_SRC_EVT_REG NUM_GUESTS Y Number 22 10 0
S_SRC_PAYMENT AGREE_BNFT_ID Y Varchar 15
S_SRC_REL FLOWCHART_CNCTR Y Varchar 1999
S_SRM_REQUEST SRVR_FLOW_ID_VAL Y Varchar 40
S_SRV_REQ ENTLMNT_MTRC_ID Y Varchar 15
S_SRV_REQ RECOMMENDATION_CD Y Varchar 30 SR_RECOMMENDATION_TYPE Yes
S_STDENTL_PMTRX DYN_PMTRX_ID Y Varchar 15
S_STDENTL_PMTRX VOL_DISCNT_ID Y Varchar 15
S_STDTRNG_PMTRX DIST_CHANNEL_CD Y Varchar 30 SAP_DISTRIBUTION_CHANNEL Yes

Data LOV
S_STDTRNG_PMTRX DIVN_CD Y Varchar 30 SAP_DIVN_CD Yes
S_STDTRNG_PMTRX DYN_PMTRX_ID Y Varchar 15
S_STDTRNG_PMTRX SALES_ORG_CD Y Varchar 30 SAP_SALES_ORG Yes
S_STDTRNG_PMTRX VOL_DISCNT_ID Y Varchar 15
S_TASK_DEFN HELP_URL_TEXT Y Varchar 250
S_TASK_DEFN REL_TU_TASK_NAME Y Varchar 100
S_TERRALGN BU_ID N Varchar 15 0-R9NH
S_TERRALGN COMBINE_ALGN_ID Y Varchar 15


S_TERRALGN EXPIRATION_DT Y UTC 7
DateTime
S_TERRALGN LOCKED_BY_USER_ID Y Varchar 15
S_TERRALGN LOCKED_DT Y UTC 7

DateTime
S_TERRALGN LOCKED_FLG N Char 1 N
S_TERRALGN PR_POSTN_ID Y Varchar 15
S_TERRALGN ROLL_UP_AMT Y Number 22 22 7
S_TERRALGN_ACCT ACTIVATION_DT Y UTC 7

DateTime
S_TERRALGN_ACCT AFFL_OBJECT_CD Y Varchar 30 TM_AFFL_OBJECT_TYPE Yes
S_TERRALGN_ACCT APPR_PER_ID Y Varchar 15
S_TERRALGN_ACCT APPR_STATUS_CD Y Varchar 30 ALGN_APPR_STATUS_CD Yes
S_TERRALGN_ACCT EXPIRATION_DT Y UTC 7

DateTime
S_TERRALGN_ACCT FROM_TERR_ID Y Varchar 15
S_TERRALGN_ACCT REP_ACTION_CD Y Varchar 30 APPTM_REP_ACTION_TYPE Yes
S_TERRALGN_ACCT REQ_PER_ID Y Varchar 15
S_TERRALGN_AST ACTIVATION_DT Y UTC 7

DateTime
179
S_TERRALGN_AST APPR_PER_ID Y Varchar 15


1 80
Data LOV
S_TERRALGN_AST APPR_STATUS_CD Y Varchar 30 ALGN_APPR_STATUS_CD Yes
S_TERRALGN_AST EXPIRATION_DT Y UTC 7

DateTime
S_TERRALGN_AST REP_ACTION_CD Y Varchar 30 APPTM_REP_ACTION_TYPE Yes
S_TERRALGN_AST REQ_PER_ID Y Varchar 15
S_TERRALGN_CON ACTIVATION_DT Y UTC 7

DateTime
S_TERRALGN_CON AFFL_OBJECT_CD Y Varchar 30 TM_AFFL_OBJECT_TYPE Yes
S_TERRALGN_CON APPR_PER_ID Y Varchar 15
S_TERRALGN_CON APPR_STATUS_CD Y Varchar 30 ALGN_APPR_STATUS_CD Yes
S_TERRALGN_CON EXPIRATION_DT Y UTC 7

DateTime
S_TERRALGN_CON FROM_TERR_ID Y Varchar 15
S_TERRALGN_CON REP_ACTION_CD Y Varchar 30 APPTM_REP_ACTION_TYPE Yes
S_TERRALGN_CON REQ_PER_ID Y Varchar 15
S_TERRALGN_COND DIVISION_ID Y Varchar 15
S_TERRALGN_PSTN ACTIVATION_DT Y UTC 7

DateTime
S_TERRALGN_PSTN EXPIRATION_DT Y UTC 7

DateTime
S_TERRALGN_REGN ACTIVATION_DT Y UTC 7

DateTime
S_TERRALGN_REGN AFFL_OBJECT_CD Y Varchar 30 TM_AFFL_OBJECT_TYPE Yes
S_TERRALGN_REGN APPR_PER_ID Y Varchar 15
S_TERRALGN_REGN APPR_STATUS_CD Y Varchar 30 ALGN_APPR_STATUS_CD Yes
S_TERRALGN_REGN ASGN_OBJECT_CD Y Varchar 30 TM_ASSIGN_OBJECT_TYPE Yes
S_TERRALGN_REGN EXPIRATION_DT Y UTC 7

DateTime
S_TERRALGN_REGN FROM_TERR_ID Y Varchar 15
S_TERRALGN_REGN REP_ACTION_CD Y Varchar 30 APPTM_REP_ACTION_TYPE Yes

Data LOV
S_TERRALGN_REGN REQ_PER_ID Y Varchar 15
S_TERRALGN_ZIP ACTIVATION_DT Y UTC 7

DateTime
S_TERRALGN_ZIP AFFL_OBJECT_CD Y Varchar 30 TM_AFFL_OBJECT_TYPE Yes
S_TERRALGN_ZIP APPR_PER_ID Y Varchar 15
S_TERRALGN_ZIP APPR_STATUS_CD Y Varchar 30 ALGN_APPR_STATUS_CD Yes
S_TERRALGN_ZIP ASGN_OBJECT_CD Y Varchar 30 TM_ASSIGN_OBJECT_TYPE Yes
S_TERRALGN_ZIP EXPIRATION_DT Y UTC 7

DateTime

S_TERRALGN_ZIP FROM_TERR_ID Y Varchar 15
S_TERRALGN_ZIP GEO_TYPE_CD Y Varchar 30 TM_GEO_TYPE Yes
S_TERRALGN_ZIP REP_ACTION_CD Y Varchar 30 APPTM_REP_ACTION_TYPE Yes
S_TERRALGN_ZIP REQ_PER_ID Y Varchar 15
S_TERRITORY BU_ID N Varchar 15 0-R9NH
S_TERRITORY ROLL_UP_AMT Y Number 22 22 7
S_TERR_ACCNT AFFL_OBJECT_CD Y Varchar 30 TM_AFFL_OBJECT_TYPE Yes
S_TERR_ACCNT CREATED_BY_ALGN_ID Y Varchar 15
S_TERR_ACCNT EXPIRED_BY_ALGN_ID Y Varchar 15
S_TERR_ACCNT FROM_TERR_ID Y Varchar 15
S_TERR_ASSET CREATED_BY_ALGN_ID Y Varchar 15
S_TERR_ASSET EXPIRED_BY_ALGN_ID Y Varchar 15
S_TERR_CON AFFL_OBJECT_CD Y Varchar 30 TM_AFFL_OBJECT_TYPE Yes
S_TERR_CON CREATED_BY_ALGN_ID Y Varchar 15
S_TERR_CON EXPIRED_BY_ALGN_ID Y Varchar 15
S_TERR_CON FROM_TERR_ID Y Varchar 15
S_TERR_HIER ORIG_HIER_ID Y Varchar 15

181
S_TERR_POSITION CREATED_BY_ALGN_ID Y Varchar 15


1 82
Data LOV
S_TERR_POSITION EXPIRED_BY_ALGN_ID Y Varchar 15
S_TERR_REGION AFFL_OBJECT_CD Y Varchar 30 TM_AFFL_OBJECT_TYPE Yes
S_TERR_REGION ASGN_OBJECT_CD Y Varchar 30 TM_ASSIGN_OBJECT_TYPE Yes
S_TERR_REGION CREATED_BY_ALGN_ID Y Varchar 15
S_TERR_REGION EXPIRED_BY_ALGN_ID Y Varchar 15
S_TERR_REGION FROM_TERR_ID Y Varchar 15
S_TERR_ZIP AFFL_OBJECT_CD Y Varchar 30 TM_AFFL_OBJECT_TYPE Yes
S_TERR_ZIP ASGN_OBJECT_CD Y Varchar 30 TM_ASSIGN_OBJECT_TYPE Yes
S_TERR_ZIP CREATED_BY_ALGN_ID Y Varchar 15
S_TERR_ZIP EXPIRED_BY_ALGN_ID Y Varchar 15
S_TERR_ZIP FROM_TERR_ID Y Varchar 15
S_TERR_ZIP GEO_TYPE_CD Y Varchar 30 TM_GEO_TYPE Yes
S_UNVBX_ITEM CONTEXT Y Varchar 250
S_UNVBX_ITMTASK REMOTE_EXEC_CD Y Varchar 200
S_UNVBX_ITMTASK TERR_ID Y Varchar 15
S_UNVBX_ITMTYPE TRNSFR_APPLET_NAME Y Varchar 75
S_UOM_CONV_FCTR CONV_TYPE_CD Y Varchar 30
S_WFA_DATA STRING_DATA_VAL Y Varchar 1999
S_WFA_DPLOY_DEF ANALY_LVL_CD Y Varchar 30 NONE WF_ANLY_LVL_CD Yes
S_WFA_DPLOY_DEF DEL_EVT_HANDLE_FLG N Char 1 N
S_WFA_DPLOY_DEF DESCRIPTION Y Varchar 250
S_WFA_DPLOY_DEF DISPNAME_OVERRIDE Y Varchar 250
S_WFA_DPLOY_DEF DISPNAME_REF Y Varchar 75
S_WFA_DPLOY_DEF REPOSITORY_VERSION Y Number 22 10 0
S_WFA_DPLOY_DEF SUB_TASK_FLG N Char 1 N
S_WFA_DPLOY_DEF TYPE_CD N Varchar 30 PROCESS WF_TYPE_CD Yes

Data LOV
S_WFA_INSTANCE ANALY_DEF_FLG N Char 1 N
S_WFA_INSTANCE ANALY_LVL_CD N Varchar 30 NONE WF_ANLY_LVL_CD Yes
S_WFA_INSTANCE DISPNAME_OVERRIDE Y Varchar 100
S_WFA_INSTANCE INTERNAL_STAT_VAL Y Number 22 10 0
S_WFA_INSTANCE LAST_SVPT_VAL Y Varchar 15
S_WFA_INSTANCE ROOT_DEF_ID_VAL Y Varchar 15
S_WFA_INST_PROP LONG_VAL Y Text 0
S_WS_PORT ATT_PROTOCOL_CD Y Varchar 30 WS_ATT_PROTOCOL_CD Yes


T_DETAIL ENCRPTD_COL Y Varchar 50
T_DETAIL ENCRPTD_HASH_VAL Y Varchar 30
T_DETAIL ENCRPTN_KEY_INDEX Y Varchar 10
T_DETAIL NAME_CI Y Varchar 75
T_MASTER_POSTN MASTER_NAME_CI Y Varchar 75
T_MASTER_X ATTRIB_08 Y CLOB 131072
V_SA_SBLSRVR GROUP_NAME Y Varchar 45

183
New System Columns in This Version

Two new system columns, shown in Table 84, have been added to almost all of the Siebel tables.
These columns may not be present in some tables that are used by Siebel server applications as
temporary tables or log tables. These columns are maintained by the ObjectManager and Oracle’s
Siebel server applications.
Table 84. New System Columns in This Version
Column Name Description Data Type
DB_LAST_UPD Last Updated - This Database UTC Datetime
DB_LAST_UPD_SRC Source of Last Update - This Database varchar (50)
Modified Table Columns in This Version

Table 85 lists table columns that have changed in this version.
Table 85. Modified Table Columns in This Version
Type of Previous
Table Column Change Value New Value
S_AUDIT_ITEM FIELD_NAME Optional No Yes
S_CON_PRDINT_M CON_CD LOV Type CONTACT_ None

TYPE
S_DISCNT DISCNT_CD LOV Type DISCOUNT None

_TYPE
S_EMT_DSET_ITEM POST_PROC_WF_NAME Optional No Yes

S_ESCL_REQ REQ_ID Prec 9 15
S_LST_OF_VAL ACTIVE_FLG Optional Yes No
S_LST_OF_VAL MULTI_LINGUAL_FLG Optional Yes No
S_MDF_TXN TYPE_CD LOV Bnd Yes No
S_MERGE_LOG_ATTR NEW_STD_VALUE Length 128 500
S_MERGE_LOG_ATTR OLD_CUST_VALUE Length 128 500
S_MERGE_LOG_ATTR OLD_STD_VALUE Length 128 500
S_ORDER CCNUM_ENCRPKEY_REF Length 30 150
S_PRI_LST_ITEM PRI_CD LOV Type Price Type None

S_PTY_PAY_PRFL CCNUM_ENCRPKEY_REF Length 30 150
S_PTY_PAY_PRFL CCVNUM_ENCRPKY_REF Length 30 60
S_SMQ_ADDR SECURITY_TOKEN Length 100 210

Schema Changes ■ Table Index Changes in This Version
Table 85. Modified Table Columns in This Version
Type of Previous
Table Column Change Value New Value
S_SRC LOAD_BEHAVIOR_CD LOV Type None CAMPAIGN_LOAD_

BEHAVIOR
S_SRC_PAYMENT CCNUM_ENCRPKEY_REF Length 30 150
S_SSO_SYS_USER PWD_ENCRPKEY_REF Length 30 150
S_TERRASGN_INFO ASGN_OBJECT_CD LOV Type None TM_ASSIGN_OBJECT_

TYPE
S_TERRASGN_INFO SEARCH_SPEC Length 250 1999
S_TERRITORY TERR_HIER_ID Optional No Yes
S_VOD LOCKED_BY Length 15 50
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 185
■ “Modified Table Indexes in This Version” on page 187
■ “Table Indexes Deleted from This Version” on page 190
New Table Indexes in This Version

Table 86 lists table indexes that are new in this version.
Table 86. New Table Indexes in This Version
Table Name Index A U Columns
S_AUDIT_ITEM S_AUDIT_ITEM_M4 Y N (OPERATION_DT)
S_BRDCST_MSG S_BRDCST_MSG_M5 Y N (UNIVERSAL_MSG_FLG)
S_CAMP_CON S_CAMP_CON_F19 Y N (DCP_ID)
S_CM_CNCTR S_CM_CNCTR_F1 Y N (SRCH_ENGINE_ID)
S_COMMUNICATION S_COMMUNICATN_F18 Y N (DCP_ID)
S_CON_SYNC_SCHD S_CON_SYNC_SCHD_F3 Y N (CALL_LST_ID)
S_DMND_CRTN_PRG S_DMND_CRTNPRG_F17 Y N (MKTG_OFFR_ID)
S_EMT_DSET_ITEM S_EMT_DSET_ITEM_F3 Y N (PDQ_ID)
S_EMT_SESSN_ITM S_EMT_SESSN_ITM_F3 Y N (PDQ_ID)

S_ENTL_PRDPRI S_ENTL_PRDPRI_F50 Y N (AGREE_BNFT_ID)
S_ENTL_PRDPRI S_ENTL_PRDPRI_F51 Y N (CTLG_CAT_ID)
S_ENTL_PRDPRI S_ENTL_PRDPRI_F52 Y N (XA_CLASS_ID)
S_ENTMPL_PRDPRI S_ENTMPLPRDPRI_F50 Y N (BNFT_TMPL_ID)
S_ENTMPL_PRDPRI S_ENTMPLPRDPRI_F51 Y N (CTLG_CAT_ID)
S_ENTMPL_PRDPRI S_ENTMPLPRDPRI_F52 Y N (XA_CLASS_ID)
S_EVT_MKTG S_EVT_MKTG_F4 Y N (EVT_FUL_REQ_ID)
S_EVT_MKTG S_EVT_MKTG_F5 Y N (PORTFOLIO_ID)
S_EVT_MKTG S_EVT_MKTG_F6 Y N (PRTFL_ACCNT_ID)
S_EVT_MKTG S_EVT_MKTG_F7 Y N (PRTFL_CTGRY_ID)
S_FCSTSER S_FCSTSER_F2 Y N (QTY_AGFLD_ID)
S_FCSTSER_POSTN S_FCSTSER_POSTN_F2 Y N (FCSTSER_AGFLD_ID)
S_INVOICE S_INVOICE_F52 Y N (AGREE_BNFT_ID)
S_NODE S_NODE_F4 Y N (ROUTE_ID)
S_OPTY_POSTN S_OPTY_POSTN_F2 N N (ASGN_TERR_ID)
S_OPTY_SRC S_OPTY_SRC_F4 Y N (DCP_ID)
S_ORDER S_ORDER_F43 Y N (DCP_ID)
S_ORDER S_ORDER_F57 Y N (AGREE_BNFT_ID)
S_PRTNRPRG_APPL S_PRTNRPRG_APPL_F5 Y N (AGREE_ITEM_ID)

S_PRTNRPRG_APPL S_PRTNRPRG_APPL_F6 Y N (PRTNRPRG_MBR_ID)
S_PRTNRPRG_MBR S_PRTNRPRG_MBR_F1 Y N (AGREE_ITEM_ID)
S_PRTNRPRG_MBR S_PRTNRPRG_MBR_U2 Y Y (MEMBERSHIP_NUM,CONFLICT_ID)
S_PRTNR_PROG S_PRTNR_PROG_F7 Y N (PROD_INT_ID)
S_REVN S_REVN_F19 Y N (ENT_SOLN_ID)
S_SMQ_HISTORY S_SMQ_HISTORY_M1 Y N (TRANSPORT_IDEN)
S_SMQ_HISTORY S_SMQ_HISTORY_M2 Y N (OID_IDEN)
S_SORT_CHAR S_SORT_CHAR_U1 Y Y (CHAR_VAL)
S_SRC_PAYMENT S_SRC_PAYMENT_F65 Y N (AGREE_BNFT_ID)
S_TERR_ASSET S_TERR_ASSET_F2 Y N (CREATED_BY_ALGN_ID)
S_TERR_ASSET S_TERR_ASSET_F3 Y N (EXPIRED_BY_ALGN_ID)
S_TERR_CON S_TERR_CON_F2 Y N (CREATED_BY_ALGN_ID)

S_TERR_CON S_TERR_CON_F3 Y N (EXPIRED_BY_ALGN_ID)
S_TERR_CON S_TERR_CON_F4 Y N (FROM_TERR_ID)
S_TERR_POSITION S_TERR_POSITION_F3 Y N (CREATED_BY_ALGN_ID)
S_TERR_POSITION S_TERR_POSITION_F4 Y N (EXPIRED_BY_ALGN_ID)
S_TERR_REGION S_TERR_REGION_F2 Y N (CREATED_BY_ALGN_ID)
S_TERR_REGION S_TERR_REGION_F3 Y N (EXPIRED_BY_ALGN_ID)
S_TERR_REGION S_TERR_REGION_F4 Y N (FROM_TERR_ID)
S_TERR_ZIP S_TERR_ZIP_F1 Y N (CREATED_BY_ALGN_ID)
S_TERR_ZIP S_TERR_ZIP_F2 Y N (EXPIRED_BY_ALGN_ID)
S_TERR_ZIP S_TERR_ZIP_F3 Y N (FROM_TERR_ID)
S_TMSHT_ITEM S_TMSHT_ITEM_V1 Y N (CREATED_BY)
S_UNVBX_ITEM S_UNVBX_ITEM_M2 Y N (REQUESTOR_ID,RQSTD_TS)
S_UNVBX_ITMTASK S_UNVBX_ITMTASK_F2 Y N (TERR_ID)
S_UNVBX_ITMTASK S_UNVBX_ITMTASK_M1 Y N (APPROVER_ID,ACTIVE_FLG,START_TS)
T_DETAIL T_DETAIL_U1_C1 Y N (RUN_NUM,NAME_CI,CONFLICT_ID)
T_MASTER_POSTN T_MASTER_POSTN_C1 Y N (MASTER_NAME_CI)
Modified Table Indexes in This Version

Table 87 lists table indexes that are now active in this version.
Table 87. Table Indexes That Are Now Active in This Version
S_ADDR_ORG S_ADDR_ORG_M7 Y N (DB_LAST_UPD,ROW_ID)
S_ADDR_PER S_ADDR_PER_M6 Y N (DB_LAST_UPD,ROW_ID)

Table 88 lists table indexes that have changed definition in this version.
Table 88. Table Indexes That Have Changed Definition in This Version
Table Name Index Previous Columns New Columns
S_APP_QUERY S_APP_QUERY_U1 NAME NAME

DESC_TEXT DESC_TEXT
CREATED_BY OWNER_ID
LANG_ID LANG_ID
CONFLICT_ID CONFLICT_ID
PRIV_FLG PRIV_FLG
S_APP_QUERY S_APP_QUERY_V1 CREATED_BY OWNER_ID
S_FCST_ITEM_DTL S_FCST_ITEM_DTL_U1 FCST_ITEM_ID FCST_ITEM_ID

DETAIL_DT DETAIL_DT
ORIG_FCST_ID ORIG_FCST_ID
CONFLICT_ID SEQ_NUM
CONFLICT_ID
S_POSTN S_POSTN_M4 DB_LAST_UPD DB_LAST_UPD

PAR_ROW_ID ROW_ID
PAR_ROW_ID
S_QUOTE_POSTN S_QUOTE_POSTN_M1 POSTN_ID POSTN_ID

QUOTE_NUM QUOTE_NUM
REV_NUM REV_NUM
QUOTE_ID
S_REVN S_REVN_M3 EFFECTIVE_DT PROD_ID

PROD_ID EFFECTIVE_DT
S_SRM_REQUEST S_SRM_REQUEST_M6 STATUS SRVR_FLOW_ID_VAL

TGT_DELETE_TS ROW_ID
STATUS
TGT_DELETE_TS
S_TERRALGN S_TERRALGN_U1 TERR_HIER_ID TERR_HIER_ID

NAME BU_ID
CONFLICT_ID NAME
CONFLICT_ID
S_TERRALGN_ACCT S_TERRALGN_ACCT_U1 TERR_ALGN_ID TERR_ALGN_ID

TERR_ID TERR_ID
ACCNT_ID ACCNT_ID
CONFLICT_ID AFFL_OBJECT_CD
CONFLICT_ID

S_TERRALGN_CON S_TERRALGN_CON_U1 TERR_ALGN_ID TERR_ALGN_ID

TERR_ID TERR_ID
CON_ID CON_ID
CONFLICT_ID
S_TERRALGN_REGN S_TERRALGN_REGN_U1 TERR_ALGN_ID TERR_ALGN_ID

TERR_ID TERR_ID
REGION_ID REGION_ID
CONFLICT_ID ASGN_OBJECT_CD
AFFL_OBJECT_CD
CONFLICT_ID
S_TERRALGN_ZIP S_TERRALGN_ZIP_U1 TERR_ALGN_ID TERR_ALGN_ID

TERR_ID TERR_ID
ZIPCODE ZIPCODE
AFFL_OBJECT_CD
GEO_TYPE_CD
CONFLICT_ID
S_TERRITORY S_TERRITORY_U1 TERR_HIER_ID NAME

NAME BU_ID
S_TERR_ACCNT S_TERR_ACCNT_U1 TERR_ID TERR_ID

ACCNT_ID ACCNT_ID
EFF_START_DT EFF_START_DT
CONFLICT_ID
S_TERR_CON S_TERR_CON_U1 TERR_ID TERR_ID

CON_ID CON_ID
CONFLICT_ID
S_TERR_REGION S_TERR_REGION_U1 TERR_ID TERR_ID

REGION_ID REGION_ID
AFFL_OBJECT_CD
CONFLICT_ID

S_TERR_ZIP S_TERR_ZIP_U1 TERR_ID TERR_ID

ZIPCODE ZIPCODE
AFFL_OBJECT_CD
GEO_TYPE_CD
CONFLICT_ID
S_UNVBX_ITEM S_UNVBX_ITEM_F1 REQUESTOR_ID OBJECT_VAL
S_WFA_DPLOY_DEF S_WFA_DPLOY_DEF_U1 NAME TYPE_CD

VERSION NAME VERSION
Table Indexes Deleted from This Version

Table 89 lists table indexes that have been deleted from this version.
Table 89. Deleted Table Indexes
S_UNVBX_ITEM_F1 S_UNVBX_ITEM_F1 Y N REQUESTOR_ID
S_VOD S_VOD_F1 Y N LOCKED_BY

Index
A compensation planning administration ERD

account ERD about 31
about 17 diagram 32
diagram 19 tables 31
support for Dynamic Hierarchy 18 compensation planning execution ERD
support for Global Account Views 18 about 33
tables 18 diagram 34
adjustment group ERD tables 33
about 20 competency management system ERD
diagram 21 about 35
apparel tables 35
See textile, apparel, and footwear ERD Consumer Goods
asset management ERD CG promotion planning ERD 28
about 22 content management ERD
diagram 23 about 37
tracking asset instances 22 tables 37
auction ERD content object
about 24 See content management ERD
diagram 25 content process
tables 24 See content management ERD
auto email response generator ERD contract conditions ERD
about 26 about 39
diagram 27 diagram 40
tables 26 tables 39
contracts ERD
about 41
B diagram 42
banking tables 41
See commercial banking ERD Customer Data Item, about 43
C D
campaign management data (intersection) table type
See marketing campaign ERD about 157
CG promotion planning ERD obsolete, table marked as 157
about 28 data (private) table type, about 157
diagram 30 data (public) table type
tables 28 about 157
columns obsolete, table marked as 157
domain type definitions 159 data types
INTEGRATION_ID columns, about 161 limit checking 162
naming conventions 155 data visibility ERD
numeric physical type 160 about 43
type definitions 159 diagram 45
commercial banking ERD tables 43
about 31 Database Marketing, marketing program

Index ■ E
ERD 79 contract conditions, diagram 40

database schema version number, finding contract conditions, tables 39
and format 161 contracts, diagram 42
defect tracking contracts, tables 41
See product quality tracking ERD data visibility, diagram 45
design data visibility, tables 43
See schema Dun & Bradstreet integration, diagram 47
domain type definitions 159 Dun & Bradstreet integration, tables 46
Dun & Bradstreet integration ERD employee KPI, diagram 49
about 46 employee KPI, tables 48
diagram 47 exclusive arc relationship, diagram
tables 46 conventions 12
Dynamic Hierarchy, support by account expense reports, diagram 51
entity 18 expense reports, tables 50
field service inventory, diagram 53
E field service inventory, tables 52
employee KPI ERD field service scheduler, diagram 55
about 48 field service scheduler, tables 54
diagram 49 forecasts, diagram 57
tables 48 forecasts, tables 56
employees general diagram conventions 12
field service scheduler ERD 54 high tech marketing development fund,
time sheet ERD 141 diagram 59
entitlement items, service agreement high tech marketing development fund,
ERD 125 tables 58
ERDs high tech special pricing authorization,
account, diagram 19 diagram 61
account, tables 18 high tech special pricing authorization,
adjustment group, diagram 21 tables 60
adjustment group, tables 20 invoicable charges, diagram 63
asset management, diagram 23 invoicable charges, tables 62
asset management, tables 22 invoices, diagram 65
auction, diagram 25 invoices, tables 64
auction, tables 24 marketing campaign, diagram 67, 69
auto email response generator, marketing campaign, tables 68
diagram 27 marketing collaboration, diagram 71
auto email response generator, tables 26 marketing collaboration, tables 70
CG promotion planning, diagram 30 marketing encyclopedia, diagram 73
CG promotion planning, tables 28 marketing encyclopedia, tables 72
compensation planning administration, marketing events, diagram 76
diagram 32 marketing events, tables 74
compensation planning administration, marketing plans, diagram 78
tables 31 marketing plans, tables 77
compensation planning execution, marketing program, diagram 81
diagram 34 marketing program, tables 79
compensation planning execution, marketing resource management: document,
competency management system, marketing resource management: document,
competency management system, opportunity management, diagram 85
tables 35 opportunity management, tables 84
content management, diagram 38 order life cycle, diagram 87
content management, tables 37 order life cycle, tables 86
orders, diagram 89

Index ■ F
orders, tables 88 territory management, diagram 136

partner collaboration, diagram 91 territory management, tables 135
partner collaboration, tables 90 textile, apparel, and footwear,
partner program registration, diagram 93 diagram 140
partner program registration, tables 92 textile, apparel, and footwear, tables 139
party model, diagram 95 time sheet, diagram 142
party model, tables 94 time sheet, tables 141
payments, diagram 97 trade promotions, diagram 144
payments, tables 96 trade promotions, tables 143
performance review, diagram 100 training curriculum course, diagram 146
performance review, tables 98 training curriculum course, tables 145
personal account, diagram 102 training test engine, diagram 148
personal account, tables 101 training test engine, tables 147
personal financial review, diagram 104 versioned object definition, diagram 150
personal financial review, tables 103 versioned object definition, tables 149
pricing comparison, diagram 106 warranty, diagram 152
pricing comparison, tables 105 warranty, tables 151
pricing, diagram 108 exclusive arc relationship
pricing, tables 107 about 12
product promotion, diagram 110 diagram conventions 12
product promotion, tables 109 expense reports ERD
product quality tracking, diagram 112 about 50
product quality tracking, tables 111 diagram 51
product recommendation, diagram 114 tables 50
product recommendation, tables 113 extension (Siebel) table type
products or services, diagram 116 about 157
products or services, tables 115 obsolete table marked as 157
professional services, diagram 118 extension table type, about 157
professional services, tables 117
recursive relationship, diagram F
conventions 13 field service inventory ERD
revenue, diagram 120 about 52
revenue, tables 119 diagram 53
revision table 14 tables 52
sales hierarchy and credit assignment, field service scheduler ERD
diagram 122 about 54
sales hierarchy and credit assignment, diagram 55
tables 121 tables 54
sales portfolio management, diagram 124 financial accounts
sales portfolio management, tables 123, personal account ERD 101
137 financial review, personal financial review
service agreement, diagram 126 ERD 103
service agreement, tables 125 Financial Services
service calendars and work shifts, commercial banking ERD 31
diagram 128 footwear
service calendars and work shifts, See textile, apparel, and footwear ERD
tables 127 forecasts ERD
service request, diagram 130 about 56
service request, tables 129 diagram 57
shipment, diagram 132 tables 56
shipment, tables 131
Siebel Assistant, diagram 134
Siebel Assistant, tables 133 G
territory management - LS, diagram 138 Global Account Views, support by account

Index ■ H
entity 18 diagram 78
tables 77
H marketing program ERD
high tech marketing development fund ERD about 79
about 58 diagram 81
tables 58 marketing resource management: document
high tech special pricing authorization ERD ERD
about 60 about 82
diagram 61 diagram 83
tables 60 tables 82
Master Data Item, about 43
MDFs
I See CG promotion planning ERD
Include Only field 161
index column fields 161
index naming conventions 155
N
insurance naming conventions
personal account ERD 101 columns 155
INTEGRATION_ID columns, about 161 indexes 155
invoicable charges ERD physical model listings, abbreviations
about 62 used 156
diagram 63 table names 153
tables 62 table prefixes 154
invoices ERD table suffixes 154
about 64 non-Siebel application products, caution
diagram 65 about inserting or updating data 9
tables 64 normalized, defined 9
L O
limit checking for data types 162 opportunity management ERD
about 84
diagram 85
M tables 84
marketing campaign ERD Oracle Applications, about use of
about 68 INTEGRATION_ID columns 161
diagram 67, 69 order life cycle ERD
tables 68 about 86
marketing collaboration ERD diagram 87
about 70 tables 86
diagram 71 orders ERD
tables 70 about 88
marketing development funds diagram 89
See CG promotion planning ERD tables 88
marketing encyclopedia ERD
about 72
diagram 73
P
tables 72 partner collaboration ERD
marketing events ERD about 90
about 74 diagram 91
tables 74 partner program registration ERD
marketing plans ERD about 92
about 77 diagram 93
tables 92

Index ■ R
party model ERD about 111

about 94 diagram 112
tables 94 product recommendation ERD
party, defined 94 about 113
payments ERD diagram 114
about 96 tables 113
diagram 97 products or services ERD
tables 96 about 115
performance review ERD diagram 116
about 98 tables 115
diagram 100 professional services ERD
tables 98 about 117
personal account ERD diagram 118
about 101 tables 117
diagram 102 projects, professional services ERD 117
tables 101
personal financial review ERD R
about 103 recursive relationship
tables 103 diagram conventions 13
physical model repository, about Siebel repository 161
column naming conventions 155 revenue ERD
column type definitions 159 diagram 120
columns of numeric physical type 160 tables 119
database schema version number, finding and
format 161
domain type definitions 159 S
Include Only field 161 sales hierarchy and credit assignment ERD
index naming conventions 155 about 121
INTEGRATION_ID columns, about 161 diagram 122
limit checking for data types 162 tables 121
party model, aboutparty model, about 162 Sales Hierarchy Module
physical model listings, abbreviations See sales hierarchy and credit assignment
used 156 ERD
Siebel repository tables, about 161 sales portfolio management ERD
Siebel system fields 160 about 123
table naming conventions 153 diagram 124
table status definitions 158 tables 123, 137
table type definitions 157 schema
validating Siebel Schema 162 database schema version number, finding and
pricing comparison ERD format 161
about 105 defined 9
diagram 106 validating Siebel Schema 162
tables 105 service activities, field service scheduler
pricing ERD ERD 54
about 107 service agreement ERD
product promotion ERD tables 125
about 109 service calendars and work shifts ERD
product quality tracking ERD tables 127

Index ■ T
service region, field service scheduler tests, training test engine ERD 147
ERD 54 textile, apparel, and footwear ERD
service request ERD about 139
tables 129 time sheet ERD
shipment ERD about 141
tables 131 trade promotions ERD
Siebel Assistant ERD about 143
tables 133 training curriculum course ERD
Siebel Financial Services about 145
commercial banking ERD 31 diagram 146
Siebel repository, about 161 tables 145
Siebel SAP R/3 Connector, about use of training test engine ERD
INTEGRATION_ID columns 161 about 147
Siebel system fields 160 diagram 148
special ERD conventions tables 147
exclusive arc relationship 12
recursive relationship 13 V
system fields 160 validating Siebel Schema 162
versioned object definition ERD
T about 149
tables diagram 150
naming conventions 153 tables 149
prefix naming conventions 154
suffix naming conventions 154 W
table status definitions 158 warranty ERD
types of 157 about 151
territory management - LS ERD diagram 152
territory management ERD work shifts
about 135 See service calendars and work shifts ERD
diagram 136 workflow process
tables 135 See content management ERD
territory quota rollup ERD
about 137

Siebel Data Model Reference: Version 8.0, Rev. A May 2008

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Siebel Data Model Reference: Version 8.0, Rev. A May 2008

Transféré par

Droits d'auteur :

Formats disponibles

Siebel Data Model

Siebel Data Model Reference 1

Chapter 1: What’s New in This Release

Chapter 2: Data Model Overview

Chapter 3: Logical Model

Siebel Data Model Reference Version 8.0, Rev. A 3

4 Siebel Data Model Reference Version 8.0, Rev. A

Chapter 4: Physical Model

Chapter 5: Schema Changes

Siebel Data Model Reference Version 8.0, Rev. A 5

6 Siebel Data Model Reference Version 8.0, Rev. A

What’s New in Siebel Data Model Reference, Version 8.0, Rev. A

Table 2. What’s New in Siebel Data Model Reference, Version 8.0

Marketing Budget Request ERD A new entity-relationship diagram.

Marketing Program ERD This entity-relationship diagram has been modified.

Marketing Resource A new entity-relationship diagram.

Siebel Data Model Reference Version 8.0, Rev. A 7

Table 2. What’s New in Siebel Data Model Reference, Version 8.0

Sales Portfolio Management ERD A new entity-relationship diagram.

■ Assessing the potential of their assigned accounts

■ Engaging the high-potential accounts within their portfolio

■ Directing and managing the resources at their disposal

■ Managing ongoing relationships with customers and

Territory Quota Rollup A new entity-relationship diagram.

8 Siebel Data Model Reference Version 8.0, Rev. A

Siebel Data Model Reference Version 8.0, Rev. A 9

10 Siebel Data Model Reference Version 8.0, Rev. A

Relationships between entities

The information on ERDs is organized as follows:

■ 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.0, Rev. A 11

Figure 1. General Entity Relationship Diagram Conventions

Exclusive Arc Relationship

12 Siebel Data Model Reference Version 8.0, Rev. A

Figure 2. Exclusive Arc Relationship Diagram Convention Example

Entity Relationship Example:

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

Figure 3. Recursive Relationship Diagram Convention Example

Siebel Data Model Reference Version 8.0, Rev. A 13

Entity Relationship Diagrams and

Table 3 provides a list of ERDs in alphabetic order.

Table 3. Entity Relationship Diagrams

Figure Num. Revised New

Account Figure 4 on General

Adjustment Group Figure 5 on General

Asset Management Figure 6 on General

Auction Figure 7 on General

Auto Email Response Generator Figure 8 on General

CG Promotion Planning Figure 9 on Marketing

Compensation Planning Administration Figure 10 on ERM

Compensation Planning Execution Figure 11 on ERM

Competency Management System Figure 12 on ERM

Content Management Figure 13 on General

Contract Conditions Figure 14 on General

Contracts Figure 15 on General

Data Visibility Figure 16 on General

Dun & Bradstreet Integration Figure 17 on Sales/Marketing