Siebel Data Model Reference For Industry Applications v8.1.1

Siebel Data Model
Reference for Industry

Applications
Version 8.1
November 2008
Copyright © 2005, 2008, Oracle. All rights reserved.
The Programs (which include both the software and documentation) contain proprietary information;
they are provided under a license agreement containing restrictions on use and disclosure and are also
protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering,
disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability
with other independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems
in the documentation, please report them to us in writing. This document is not warranted to be 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 for Industry Applications 1
Chapter 1: What’s New in This Release
Chapter 2: Data Model Overview
Chapter 3: Logical Model

Entity Relationship Diagram Conventions 13
General Entities 14
Exclusive Arc Relationship 14
Recursive Relationship 15
Entity Relationship Diagrams and Descriptions 16
Account 23
Account Targeting 26
Activity 28
Adjustment Group 30
Affiliations and Best Times 32
Agencies/Agent 34
Asset Management 36
Auction 38
Auto Email Response Generator 40
Automotive Retail 42
Benefit Case Management 44
Brick 47
CG Promotion Planning 49
Clinical Study Management 52
Communications, Media, and Energy Account 55
CME Agreement 57
CME Alert 59
CME Energy Products, Service, and Usage 61
CME Order Management 63
Commercial Banking 65
Commercial Insurance 68
Community/Chat Discussion 70
Compensation Planning Administration 72
Compensation Planning Execution 74
Competency Management System 76
Siebel Data Model Reference for Industry Applications Version 8.1 3

Contents ■
Content Management 78
Contract Conditions 80
Contracts 82
Data Visibility 84
Dealer Sales and Service Promotion 87
Document ID and Tax ID 89
Dun & Bradstreet Integration 91
Employee KPI 93
Event Tax Administration 95
Expense Reports 97
Field Service Inventory 99
Field Service Scheduler 101
Financial Account 102
Financial Account Application 105
Financial Investments 107
Financial Products 109
Financial Services Events 111
Forecasts 114
Group Insurance Policies 116
Group Pensions 118
Health Provider and Provider Group 120
High Tech Marketing Development Fund 122
High Tech Special Pricing Authorization 124
Hospitality Category 126
Institutional Sales 128
Insurance Claims 130
Insurance Policies 133
Invoicable Charges 135
Invoices 137
Life Insurance Policy 139
Loyalty 141
Managed Care 145
Marketing Campaign 147
Marketing Collaboration 149
Marketing Encyclopedia 151
Marketing Events 153
Marketing Plans 156
Medical Education Event Management 158
Objectives 160
Opportunity Management 162
Order Life Cycle 164
Orders 166
4 Siebel Data Model Reference for Industry Applications Version 8.1

Contents ■
Partner Collaboration 168

Partner Program Registration 170
Party Model 172
Payments 174
Performance Review 176
Personal Account 179
Personal Financial Review 181
Personalized Content Delivery 183
Pricing Comparison 185
Pricing 187
Product Promotion 189
Product Quality Tracking 191
Product Recommendation 193
Products or Services 195
Professional Services 197
Public Sector Case Lead Management 199
Public Sector Contact Identity 202
Public Sector Evidence Management 204
Public Sector Incident Management 206
Revenue 208
Routes and Best Call Hours 210
Sales Hierarchy and Credit Assignment 212
Sales Volume Planning 214
Sample Management 216
Service Agreement 218
Service Calendars and Work Shifts 220
Service Request 222
Shipment 224
Siebel Assistant 226
Syndicated Data 228
Teller Administration 230
Territory Alignment–Quota Assignment 232
Territory Management 234
Territory Management - Consumer Sector 236
Territory Management - Life Sciences 238
Textile, Apparel, and Footwear 240
Time Sheet 242
Trade Promotions 244
Training Curriculum Course 246
Training Test Engine 248
Universal Customer Master 250
Vehicle 252

Contents ■
Vehicle Collection 254

Vehicle Financing 256
Vehicle Sales 258
Versioned Object Definition 260
Warranty 262
Chapter 4: Physical Model

Data Model Naming Conventions 265
Table Naming Conventions 265
Index Naming Conventions 267
Column Naming Conventions 267
Abbreviations Used in the Physical Model Listings 268
Data Model Type Definitions 268
Table Type Definitions 269
Table Status Definitions 270
Column Type Definitions 271
Domain Type Definitions 271
Columns of Numeric Physical Type 272
Siebel System Fields 272
INTEGRATION_ID Columns 273
Include Only Field 273
Siebel Repository 273
Database Schema Version 274
Limit Checking for Data Types 274
Validating the Siebel Schema 274
Party Model Unifies Access to Data 275
Generating a Report about Tables 275
Chapter 5: Schema Changes

Table Changes in This Version 277
New Tables in This Version 277
Changed Tables in This Version 281
Table Column Changes in This Version 281
New Table Columns in This Version 282
Changed Table Columns in This Version 311
Table Index Changes in This Version 311
New Table Indexes in This Version 312

Contents ■
Changed Table Index in This Version 317

Table Index That Was Deleted from This Version 318
Index

Contents ■

1 What’s New in This Release
What’s New in Siebel Data Model Reference for Industry Applications,

Version 8.1
Table 1 lists changes described in this version of the documentation to support release 8.1 of the
software.
Table 1. What’s New in Siebel Data Model Reference for Industry Applications, Version 8.1
Topic Description
“Benefit Case Management” on page 44 This new feature supports benefits determination and
case-information verification.
“Loyalty” on page 141 The Loyalty Member and Loyalty Program ERDs of
previous releases have been consolidated into a single
ERD. Features that are designed to extend accrual,
redemption, promotion, enrollment, member
administration, partner administration, and other
functions have been added.
“Personalized Content Delivery” on This new feature allows sales representatives for
page 183 pharmaceutical companies to deliver a sales
communication using multimedia visualizations.
“Public Sector Case Lead Management” on The functionality of this ERD has been extended to
page 199 enable data from application forms to be uploaded into
Siebel objects.
“Sample Management” on page 216 This ERD has been modified to improve a
pharmaceutical company’s ability to monitor and use
its auditing and compliance processes.
“Table Changes in This Version” on A listing of the table changes in this schema, including
page 277 the new tables and changes to the existing table
definitions.
“Table Column Changes in This Version” on A listing of the table column changes in this schema,
page 281 including the new columns and changes to the existing
column definitions.
“Table Index Changes in This Version” on A listing of the index changes in this schema, including
page 311 the new indexes, deleted indexes, and changes to the
existing index definitions.

What’s New in This Release ■

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.
NOTE: The Siebel Bookshelf is available on Oracle Technology Network (OTN) and Oracle E-Delivery.
It might also be installed locally on your intranet or on a network location.

Data Model Overview ■

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 16
Entity Relationship Diagram

Conventions
This topic describes entity relationship diagram conventions, as follows:
■ General Entities on page 14
■ Exclusive Arc Relationship on page 14
■ Recursive Relationship on page 15

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

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

page 25
Account Targeting Figure 5 on Consumer Sector No No

page 27
Activity Figure 6 on Life Sciences No No

page 29
Adjustment Group Figure 7 on General No No

page 31
Affiliations and Best Times Figure 8 on Life Sciences No No

page 33
Agencies/Agent Figure 9 on Financial Services No No

page 35
Asset Management Figure 10 on General No No

page 37
Auction Figure 11 on General No No

page 39
Auto Email Response Generator Figure 12 on General No No

page 41
Automotive Retail Figure 13 on Automotive No No

page 43
Benefit Case Management Figure 14 on Public Sector No Yes

page 46
Brick Figure 15 on Life Sciences No No

page 48
CG Promotion Planning Figure 16 on Marketing No No

page 51
Clinical Study Management Figure 17 on Life Sciences No No

page 54


Communications, Media, and Energy Figure 18 on CME No No

Account page 56
CME Agreement Figure 19 on CME No No

page 58
CME Alert Figure 20 on CME No No

page 60
CME Energy Products, Service, and Figure 21 on CME No No

Usage page 62
CME Order Management Figure 22 on CME No No

page 64
Commercial Banking Figure 23 on Financial Services No No

page 67
Commercial Insurance Figure 24 on Financial Services No No

page 69
Community/Chat Discussion Figure 25 on Life Sciences No No

page 71
Compensation Planning Administration Figure 26 on ERM No No

page 73
Compensation Planning Execution Figure 27 on ERM No No

page 75
Competency Management System Figure 28 on ERM No No

page 77
Content Management Figure 29 on General No No

page 79
Contract Conditions Figure 30 on General No No

page 81
Contracts Figure 31 on General No No

page 83
Data Visibility Figure 32 on General No No

page 86
Dealer Sales and Service Promotion Figure 33 on Automotive No No

page 88
Document ID and Tax ID Figure 34 on Handheld No No

page 90
Dun & Bradstreet Integration Figure 35 on Sales/Marketing No No

page 92


Employee KPI Figure 36 on ERM No No

page 94
Event Tax Administration Figure 37 on Hospitality No No

page 96
Expense Reports Figure 38 on General No No

page 98
Field Service Inventory Figure 39 on Service No No

page 100
Field Service Scheduler Figure 40 on Service No No

page 102
Financial Account Figure 41 on Financial Services No No

page 104
Financial Account Application Figure 42 on Financial Services No No

page 106
Financial Investments Figure 43 on Financial Services No No

page 108
Financial Products Figure 44 on Financial Services No No

page 110
Financial Services Events Figure 45 on Financial Services No No

page 113
Forecasts Figure 46 on Sales/Marketing No No

page 115
Group Insurance Policies Figure 47 on Financial Services No No

page 117
Group Pensions Figure 48 on Financial Services No No

page 119
Health Provider and Provider Group Figure 49 on Financial Services No No

page 121
High Tech Marketing Development Fund Figure 50 on Marketing No No

page 123
High Tech Special Pricing Authorization Figure 51 on Sales No No

page 125
Hospitality Category Figure 52 on General No No

page 127
Institutional Sales Figure 53 on Financial Services No No

page 129


Insurance Claims Figure 54 on Financial Services No No

page 132
Insurance Policies Figure 55 on Financial Services No No

page 134
Invoicable Charges Figure 56 on Service No No

page 136
Invoices Figure 57 on Service No No

page 138
Life Insurance Policy Figure 58 on Financial Services No No

page 140
Loyalty Figure 59 on General Yes No

page 144
Managed Care Figure 60 on Life Sciences No No

page 146
Marketing Campaign Figure 61 on Marketing No No

page 148
Marketing Collaboration Figure 62 on Marketing No No

page 150
Marketing Encyclopedia Figure 63 on Sales/Marketing No No

page 152
Marketing Events Figure 64 on General No No

page 155
Marketing Plans Figure 65 on Marketing No No

page 157
Medical Education Event Management Figure 66 on Life Sciences No No

page 159
Objectives Figure 67 on Consumer Sector No No

page 161
Opportunity Management Figure 68 on Sales No No

page 163
Order Life Cycle Figure 69 on General No No

page 165
Orders Figure 70 on General No No

page 167
Partner Collaboration Figure 71 on General No No

page 169


Partner Program Registration Figure 72 on General No No

page 171
Party Model Figure 73 on General No No

page 173
Payments Figure 74 on General No No

page 175
Performance Review Figure 75 on ERM No No

page 178
Personal Account Figure 76 on Industry-Specific No No

page 180
Personal Financial Review Figure 77 on Industry-Specific No No

page 182
Personalized Content Delivery Figure 78 on Life Sciences No Yes

page 184
Pricing Comparison Figure 79 on Energy No No

page 186
Pricing Figure 80 on General No No

page 188
Product Promotion Figure 81 on General No No

page 190
Product Quality Tracking Figure 82 on General No No

page 192
Product Recommendation Figure 83 on General No No

page 194
Products or Services Figure 84 on Service No No

page 196
Professional Services Figure 85 on General No No

page 198
Public Sector Case Lead Management Figure 86 on Public Sector Yes No

page 201
Public Sector Contact Identity Figure 87 on Public Sector No No

page 203
Public Sector Evidence Management Figure 88 on Public Sector No No

page 205
Public Sector Incident Management Figure 89 on Public Sector No No

page 207


Revenue Figure 90 on General No No

page 209
Routes and Best Call Hours Figure 91 on Sales No No

page 211
Sales Hierarchy and Credit Assignment Figure 92 on Sales No No

page 213
Sales Volume Planning Figure 93 on Consumer Sector No No

page 215
Sample Management Figure 94 on Life Sciences Yes No

page 217
Service Agreement Figure 95 on Service No No

page 219
Service Calendars and Work Shifts Figure 96 on Service No No

page 221
Service Request Figure 97 on Service No No

page 223
Shipment Figure 98 on General No No

page 225
Siebel Assistant Figure 99 on General No No

page 227
Syndicated Data Figure 100 on Life Sciences No No

page 229
Teller Administration Figure 101 on Financial Services No No

page 231
Territory Alignment–Quota Assignment Figure 102 on Sales No No

page 233
Territory Management Figure 103 on Sales No No

page 235
Territory Management - Consumer Figure 104 on Service No No

Sector page 237
Territory Management - Life Sciences Figure 105 on Sales No No

page 239
Textile, Apparel, and Footwear Figure 106 on Consumer Sector No No

page 241
Time Sheet Figure 107 on General No No

page 243


Trade Promotions Figure 108 on General No No

page 245
Training Curriculum Course Figure 109 on General No No

page 247
Training Test Engine Figure 110 on General No No

page 249
Universal Customer Master Figure 111 on General No No

page 251
Vehicle Figure 112 on Automotive No No

page 253
Vehicle Collection Figure 113 on Automotive No No

page 255
Vehicle Financing Figure 114 on Automotive No No

page 257
Vehicle Sales Figure 115 on Automotive No No

page 259
Versioned Object Definition Figure 116 on General No No

page 261
Warranty Figure 117 on Service No No

page 263

Account
Figure 4 shows the Account ERD. The account entity is a key entity in the Siebel Data Model. The
account entity appears in many diagrams in this publication, and is often referred to as an
organization unit.
The account entity is a subtype of party composed of one or more people or contacts. An account is
any organization or subset of an organization that can be sold to or serviced. An account might
represent a company, a site, a subsidiary, a division, or any other subset of an organization. An
account might also represent a governmental agency, club, or other formal or informal group of
individuals. Each account might be accessible at one or more addresses.
The account entity supports Global Account Views and Dynamic Hierarchy. This allows a universal
view of all customer interactions. The Global Account Views present accounts in the context of a
customizable hierarchy, allowing navigation to parent and child accounts. Roll-up and roll-down
functionality gives users access to account-specific information, and aggregate information including
child accounts, activities, contacts, opportunities, and the account team.
Dynamic Hierarchy allows the Global Account Views to display a different hierarchy depending on the
business unit of the user. Each custom account hierarchy is represented completely in a relationship
table. The relationships are then denormalized into a separate table to be used for roll-up support.
Table 3 lists the entities in this ERD and their corresponding tables.
Table 3. Account ERD Entities and Tables
Entity Table
Account S_ORG_EXT, S_PARTY
Account Synonym S_ORG_SYN
Activity S_EVT_ACT
Address S_ADDR_PER
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

Table 3. Account ERD Entities and Tables
Entity Table
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 for Industry Applications Version 8.1

25
Account Targeting
Figure 5 shows the Account Targeting ERD. This ERD illustrates how Siebel Enterprise applications
(Consumer Goods) support account targeting as an extension of basic querying. Account targeting
provides the capability to save the results of account queries and apply those account lists when you
schedule routes. The results that you save are called target lists. Target lists consist of sets of
accounts that meet the conditions defined by the query. Typically, the target lists you create in
account targeting are for a specific purpose and period of time. For example, the target lists might
be used to support a promotion, a campaign, or an objective.
Table 4. Account Targeting ERD Entities and Tables
Entity Table
Criteria S_CG_QUERY_ITEM
Employee S_CONTACT, S_PARTY
Objective S_SRC
Query S_CG_QUERY
Route S_ACCNTRT

Figure 5. Account Targeting
OBJECTIVE ROUTE ACCOUNT

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

combine
combined by
returned by
return
submit QUERY
submitted by
have
belong to
CRITERIA

Activity
Figure 6 shows the Activity ERD. This ERD illustrates how activities, contact calls, account calls,
attendee calls, and meetings are managed. Every activity belongs to the employee creator and other
employees assigned to the activity. Activities can be associated with one or more contacts and one
account. Contact calls are associated with the employee creator and the contact, and can be
associated with other employees who have been assigned, product details, samples, promotional
items, and decision issues. Account calls are associated with the employee creator and an account,
and can be associated with other employees who have been assigned, product details, and multiple
attendee calls. Each attendee call is associated with the product details from the account call and
one contact, and can be associated with samples, promotional items, and decision issues. Meetings
include the employee who owns the meeting, the contacts invited to attend, the account where the
meeting is taking place, and the product to be discussed at the meeting.
Table 5. Activity ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Contact S_CONTACT
Employee S_EMP_PER, S_CONTACT, S_PARTY
Indication S_PROD_APPLCTN
Issue S_PROD_ISS
Product S_PROD_INT

Title : Activity
Author : Oracle, Confidential
PERSON Figure 6.
PRODUCT belong to EMPLOYEE

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

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

ADJUSTMENT GROUP
# ADJ_GROUP_NAME
Figure 7.
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

31
Affiliations and Best Times

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

Figure 8. Affiliations and Best Times
ADDRESS USAGE
for located at for having
PERSON POSITION POSITION

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

having
composed of ORGANIZATION
ACCOUNT AFFILIATION
for
located at for for composed of
CONTACT

Agencies/Agent
Figure 9 shows the Agencies/Agent ERD. This ERD illustrates how Siebel Financial Services supports
generation of internal organization units (such as insurance agencies) that can use external
organization units or agencies (such as insurance brokers) as well as individual agents to distribute
their products. Each external organization unit agency or agent can be associated with details (such
as licensing, appointments, commission contracts, and NASD registrations, and other selling
agreements).
Table 8. Agencies/Agent ERD Entities and Tables
Entity Table
Agency Line of Business S_AGNC_LCNSLOB
Agent Line of Business S_AGENT_LCNSLOB
Agent Detail S_AGENT_DETAIL
Agency Detail S_AGENCY_DETAIL
Contact S_CONTACT, S_PARTY
Organization Unit S_ORG_EXT, S_PARTY
Product Line S_PROD_LN

Figure 9. Agencies/Agent
AGENCY LINE OF based on for AGENT LINE OF

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

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

has works for

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

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
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
Figure 10. 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

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

part of
accessed
via
CATALOG CATEGORY ITEM CATALOG CATEGORY
owner of made up of
represented by represented by
Figure 11. 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

39
Auto Email Response Generator

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

ACTIVITY
part of made up
CATALOG CATEGORY
categorized within
INBOUND COMMUNICATION
classification for
PROBLEM
RESOLUTION
DOCUMENT categorized under
OUTBOUND RESPONSE classification for
Figure 12. 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

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

Store Budget/Forecast S_AT_ORG_FCST
Vehicle S_ASSET, S_ASSET_ATX

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

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

SALES STEP
43
Benefit Case Management

This ERD (shown in Figure 14) illustrates how Benefit Case Management supports benefits
determination and case-information verification, specifically:
■ Eligibility Determination. Provides the capability to develop benefits plans that allow
caseworkers to make eligibility changes in program rules that impact benefit disbursement while
reducing the number of overpayments. The feature provides the ability to submit individual or
household profiles to a rules engine for eligibility determination.
The ERD shows that a Benefit Plan consists of Benefit Plan Items associated to Recipient and
provided by a Provider. A Benefit Plan belongs to a Case and a Case may have a Change of
Circumstance which may or may not be associated to a Benefit Plan.
■ Supporting Tasks. Helps a caseworker verify information during the intake process, where the
caseworker uses the Public Sector application to document that the information was verified, how
verification was accomplished and who verified the information. The caseworker performing
quality assurance is presented with cases based upon random selection, queued, or high-risk
profiles. The feature is also useful when a quality assurance worker reviews selected cases by
following a template which provides a list of items that must be checked off to ensure uniformity
in the review process.
As the ERD shows, a Case Verification Template is associated to a Case and may consist of one
or more Case Verification Items. The Case Verification Template Items may be associated to a
submitter and a verifier. This feature can also help a quality-assurance worker review cases
following a checklist for adherence to standards and ensuring that each case in reviewed in the
same way.
Table 13 lists the entities in this ERD and their corresponding tables
Table 13. Benefit Case Management ERD Entities and Tables
Entity Table
Account S_PARTY, S_ORG_EXT
Activity S_EVT_ACT
Admin Verification Template S_TMPL_PLANITEM
Admin Verification Template Item S_ASSESS_ATTRIB
Benefit Plan S_CASE_BNFTPLAN
Benefit Plan Item S_BNFT_PLAN_ITM
Benefit Plan Item Payment S_BNFPLNITM_PAY
Case S_CASE
Case Verification Item S_ASSESS_ATTRIB
Case Verification Template S_TMPL_PLANITEM
Change of Circumstance S_CASE_CHGOFCCM
Contact S_PARTY, S_CONTACT
Quality Assurance Items S_ASSESS_ATTRIB

Table 13. Benefit Case Management ERD Entities and Tables
Entity Table
Quality Assurance Template S_TMPL_PLANITEM
User S_PARTY, S_CONTACT, S_USER

Title : PS Benefit Case Management
46
BENEFIT PLAN
Author : Oracle, Confidential ACTIVITY
ITEM
PAYMENT
payment for for PARTY
has has CONTACT

received by
has BENEFIT PLAN ITEM
CHANGE OF BENEFIT PLAN recipient of
CIRCUMSTANCE for for
provided by ACCOUNT
has
provider of
for belongs to
submitted by
CASE USER
Figure 14. Benefit Case Management
VERIFICATION submitter of
ITEM verified by
verifier of
submitted by
QUALITY
ASSURANCE submitter of
for ITEMS
completed by
completer of
has for
CASE has
VERIFICATION
TEMPLATE
QUALITY
ASSURANCE
for TEMPLATE
for
has has has has
CASE

Brick
Figure 15 shows the Brick ERD. This ERD illustrates how region (brick and mini brick) is used in Siebel
Life Sciences. Area can be associated with multiple positions. Area is defined at the address level for
organizations and at the contact level. Area is tracked for activities. Syndicated data is also available
at the area level.
Table 14. Brick ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Account Address S_CON_ADDR
Address S_ADDR_PER
Position S_POSTN
Region S_REGION
Syndicated Data S_SYND_DATA

48
parent of
REGION
child of
BRICK OTHER REGION
Figure 15. Brick
source of holders of subject of assigned to assigned to
for for
for
held by located at
ADDRESS
CONTACT ACCOUNT ADDRESS defined by
ACTIVITY POSITION SYNDICATED DATA
for
for
located at
ORGANIZATION
parent of
child of

CG Promotion Planning
Figure 16 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 15. CG Promotion Planning ERD Entities and Tables
Entity Table
Authorized Product S_ORG_PROD
Fund Allocation S_MDF_ALLOC
Marketing Development Fund S_MDF
Marketing Event or Activity S_SRC
MDF Accrual S_MDF_ACCRUAL

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

Promotion Plan S_SRC
Promotion S_SRC
Promotion Account S_SRC

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

PAYMENT MARKETING EVENT OR ACTIVITY
Oracle
OTHER PAYMENT
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
Figure 16. 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

51
Clinical Study Management

Figure 17 shows the Clinical Study Management ERD. This ERD illustrates how clinical trials are
managed. Each clinical trial starts with a protocol for a specific compound (product). Each protocol
is conducted by sites and managed by site personnel. A protocol can have many versions and
multiple protocols can roll up to a single program. Protocols can also roll up to regions. Subjects are
screened and enrolled at protocol sites for specific protocol versions. Protocol sites are paid, based
on the activities they complete. Visits and activities are generated for subjects based on templates
defined for the protocol. The Clinical Research Associates perform site initiation activities for protocol
sites and submit periodic trip reports. A protocol can also be associated with one or more projects.
For a complete layout of projects, refer to “Professional Services” on page 197.
Table 16. Clinical Study Management ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Address S_ADDR_PER
Affiliation S_PTCL_ST_CON_LS
Application S_CL_PGM_APP_LS
Clinical Payment S_SRC_PAYMENT
Design S_CL_DSGN_LS
Position S_POSTN
Product S_PROD_INT
Program S_CL_PGM_LS
Project S_PROJ
Project Subcontractor S_PROG_ORG
Project Subcontractor Contact S_PROJ_ORG_CON
Protocol S_CL_PTCL_LS
Protocol Site S_PTCL_SITE_LS
Subject S_CL_SUBJ_LS
Subject Status S_CL_SUBJ_ST_LS
Subject Template S_SUBJ_TMPL_LS
Template Version S_SBJTMP_VER_LS
Template Visit S_TMPL_PLANITEM

Table 16. Clinical Study Management ERD Entities and Tables
Entity Table
Trip Report S_EVT_ACT
Visit S_EVT_ACT

54
Title : Clinical Study Management
PROJECT ACCOUNT
SUBCONTRACTOR belong to
a partner for
PROJECT
having composed of CONTACT
SUBCONTACTOR
contact for CONTACT for
having study conducted by for located at
AFFILIATION ADDRESS
subcontractor for
subcontracted to ACTIVITY
affiliated to for having
source of for primary investigator
PROJECT recipient of
CLINICAL PROTOCOL SITE
composed of PAYMENT paid to
made for for
Figure 17. Clinical Study Management
TRIP
REPORT for subject of participating in
subject of source of
SUBJECT
defined STATUS
having for
made by participant at
VISIT SUBJECT
involved in for
having
generated by generator of
team composed of POSITION
TEMPLATE
VISIT team members of
applied
composed of to
for using participant of
TEMPLATE VERSION used by

conducted at
having PROTOCOL having team of

used by
DESIGN
having team members of
for
PROGRAM
consisting of
composed of REGION for
APPLICATION
for having
SUBJECT having
TEMPLATE associated with
PRODUCT

associated to
belongs to
for
consists of
associated with
Communications, Media, and Energy Account

Figure 18 shows the Communications, Media, and Energy (CME) Account ERD. This ERD illustrates
how complex hierarchies of accounts are maintained in Siebel Communications and Siebel Energy.
Profiles are the way an account is further described. Addresses are associated with contacts and
accounts. Addresses are unique in the database. Trouble tickets (service requests) and activities can
be associated at the accounts level.
Table 17. CME Account ERD Entities and Tables
Entity Table
Account S_ORG_EXT
Activity S_EVT_ACT
Address S_ADDR_PER
Billing Profile S_INV_PROF
Exemption Profile S_SUBSIDY
Financial Profile S_FINAN_PROF
Trouble Ticket S_SRV_REQ

Figure 18. Communications, Media, and Energy Account
ADDRESS
PREMISE
SERVICE ADDR
for
for
for for for
associated child of
described with
FINANCIAL by
PROFILE for
ACCOUNT
parent of
described
for by CUSTOMER
EXEMPTION ACCT
PROFILE located at
PREMISE ACCT
located at
mailed to
associated with
SERVICE ACCT
BILLING PROFILE
CONTACT
has
INVOICE described by
for BILLING ACCT associated with
for associated with
STATEMENT
tracked by tracked by
for
problems
with
TROUBLE TICKET
made
up of associated
part of with
ACTIVITY

CME Agreement
Figure 19 shows the CME Agreement ERD. This ERD illustrates how an agreement is managed in
Siebel Business applications. An agreement can be associated with many accounts. An agreement
has terms and entitlements associated with it. An agreement covers service instances and products
through the account with which it is associated.
Table 18. CME Agreement ERD Entities and Tables
Entity Table
Accounts S_ORG_EXT, S_PARTY
Agreement S_DOC_AGREE
Agreement Note S_NOTE_AGR_CUT
Agreement Terms S_AGREE_TERMS
Event Activity S_EVT_ACT
Parameter S_QUOTE_ITEM_XA
Quote S_DOC_QUOTE
Quote Item S_QUOTE_ITEM
Solution Set S_QUOTE_ITEM

58
Title : CME AGREEMENTS
Author : Oracle. Confidential
QUOTE ITEM
belongs to child of
has ACCOUNTS
Figure 19. CME Agreement
parent of
QUOTE for subject of
AGREEMENT AGREEMENT EVENT ACTIVITY

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

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

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

OTHER
CME Energy Products, Service, and Usage

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

Service Instance S_ASSET
Usage S_USAGE

62
Title : CME Energy Products, Services, and Usage
PRODUCT INVOICE ITEM

INTERNAL PRODUCT
for line item of

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

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

PRESENCE
METER
EQUIPMENT for for subject of

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

ACCOUNT of
CUSTOMER SERVICE BILLING

CME Order Management

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

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

instance of
subject of instance of
part of
subject of part of subject of
of of of
ORDER ITEM QUOTE ITEM

composed of
composed of
subject of for provision of for of

for for
Figure 22. CME Order Management
subject of
ASSET
an instance of
ordered on quoted for purchase on
made into
PRODUCT OR SERVICE
composed of composed of
ORDER QUOTE
created from
leads to
billed by serviced by serviced by billed by
associated with associated with

ACCOUNT
SERVICE ACCOUNT

associated with
associated with
OTHER
BILLING ACCOUNT ACCOUNT
Commercial Banking
Figure 23 shows the Commercial Banking ERD. This ERD illustrates how Siebel Financial Services
supports generation of a commercial loan (or facility) application by portfolio type. Each application
is associated with many organizations as borrowers or lenders. The application tracks the collateral,
policies, prices of a facility, and documents used in the application process, for example, trailing
documents and attachments. An application has to undergo several stages of approvals before it is
finally approved to become a financial account.
Table 22. Commercial Banking ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Approval S_FN_APPR
Attachment S_OPTY_ATT
Borrower S_OPTY_ORG
Collateral S_FN_OFFR_COLT
Correspondence S_EVT_FUL_REQ
Exception S_OPTY_ORG_FNXM
Facility S_REVN
Facility Detail S_OPTY_PROD_FNXM
Facility Organization S_OPTYPRD_ORG
Fee S_FN_OFFR_FEE
Financial Account S_ASSET
Note S_NOTE_OPTY
Opportunity S_OPTY
Opportunity Detail S_OPTY_DTL
Portfolio Type S_MKT_SEG
Product S_PROD_INT
Rating S_OPTY_ORG_FNXM
Revenue S_REVN
Revenue S_REVN

Table 22. Commercial Banking ERD Entities and Tables
Entity Table
Trailing Document S_OPTY_DOC
Underwriting Standard S_MKT_SEG_VAL

Title : Commercial Banking part of
Author : Oracle, Confidential OPPORTUNITY DETAIL
APPROVAL
made up
UNDERWRITING KEY CREDIT
STANDARD ISSUES
NOTE ATTACHMENT CORRESPONDENCE TRAILING APPROVAL
DOCUMENT subject to STAGE
REQUEST POLICY DECISION
EXCEPTION required by
of of of for
has
of
subject of has subject of subject to has made up of

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

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

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

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

Figure 24. Commercial Insurance

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

made
up of
associated with part of
ASSET subject of subject of subject of covers
INSURANCE POLICY

Community/Chat Discussion
Figure 25 shows the Community/Chat Discussion ERD. This ERD illustrates how topics can be created
for chat or discussion purposes for a disease state (market product). Users can register to chat for
a particular topic or they can post messages to the discussion.
Table 24. Community Chat/Discussion ERD Entities and Tables
Entity Table
Discussion Post S_MESG_BRD_LS
Product S_PROD_INT
Registration S_TOPIC_CON_LS
Topic S_TOPIC_LS

Figure 25. Community/Chat Discussion
Title : Community Chat/Discussion

CONTACT
REGISTRATION of
registered for
for
registration of
TOPIC authored by
author of
for subject of
subject of
about
involving
PRODUCT
DISCUSSION POST
posted to

Compensation Planning Administration

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

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

Title : Compensation Planning Administration
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 26. 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

73
Compensation Planning Execution

Figure 27 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 26. Compensation Planning Execution ERD Entities and Tables
Entity Table
Business Unit S_BU
Compensation Budget Definition S_CP_BDGT
Compensation Budget Item S_CP_BDGT_ITEM
Compensation Budget Item For Employee S_CP_BDGT_EMP
Compensation Cycle Planning Period S_CP_PD_BDGTITM
Compensation Guideline Definition S_CP_GDLN
Compensation Guideline Set S_CP_GDLN_SET
Compensation Guideline Table S_CP_GDLN_TBL
Compensation Plan S_CP_PLAN
Compensation Plan Comments S_NOTE_CP_PLAN
Compensation Plan For Employee S_CP_PLAN_EMP
Compensation Plan Item Detail S_CP_PLNITM_DTL

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

Oracle
"'+0

$

"$%$'$"*"'+

"$%$'$*"'+
2

1 3

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

3 3
21
"$%$+

3

"$%$

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

&!'$.'
"$%$

&!'$%

75
Competency Management System

Figure 28 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 27. Competency Management System ERD Entities and Tables
Entity Table
Career Path S_JOB_PRFL_TRNS
Competency, Competency Category, Root Competency S_CMPTNCY

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

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

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

"$ + " "$ +

"'+ &$ "$ +

14

"'+ "$ +
9$
14
2613

26
? ? @
Figure 28. Competency Management System

3
"$ +

+ >;$

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

513
$$
&%

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

3


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

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

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

Figure 29. 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

79
Contract Conditions
Figure 30 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 29. Contract Conditions ERD Entities and Tables
Entity Table
Benefit S_AGREE_BNFT
Category S_CTLG_CAT
Condition S_AGREE_COND
Condition Compliance S_AGR_COND_CMPL
Contract S_DOC_AGREE
Entitlement S_ENTLMNT
Entitlement Template S_ENTL_TMPL
Object Class S_VOD, S_VOD_VER
Product S_PROD_INT

Template Benefit S_ENTL_BNFTTMPL
Template Condition S_ENTL_CONDTMPL
Template Term S_AGR_TERM_TMPL
Term S_AGR_TERM_DESC

Title : Contract Lifecycle Management
CONTRACT CONDITION
in reference to OBJECT
PRODUCT
TERM basis for
dependent upon
based on comprise
TEMPLATE TERM
used in
# TERM_NUM
applicable to CONDITION COMPLIANCE
# COMPL_NUM in reference to
subject of
in reference to
subject of
Figure 30. 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
comprise comprise
CONTRACT
AGREEMENT OTHER
CONTRACT

81
Contracts
Figure 31 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 30. Contracts ERD Entities and Tables
Entity Table
Asset S_ASSET
Contract S_DOC_AGREE, S_DOC_QUOTE, S_ORDER
Contract Line Item S_AGREE_ITEM, S_QUOTE_ITEM, S_ORDER_ITEM
Internal Product or Service S_PROD_INT

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 31. 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 subject to PAYMENT
TERM
subject of for
responsibility of responsibility of involved by

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

83
Data Visibility
The main business entities represented (shown in Figure 32) 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 31. Data Visibility ERD Entities and Tables
Entity Table
Access Group S_PARTY
Account S_ORG_EXT
Activity S_EVT_ACT
Catalog S_CTLG
Category S_CTLG_CAT
Dynamic Account Hierarchy S_DYN_HRCHY
Dynamic Account Hierarchy Node S_DYN_HRCHY_REL
Group S_PARTY
Internal/Partner Organization Unit S_ORG_EXT
Literature Item S_LIT
Opportunity S_OPTY

Table 31. Data Visibility ERD Entities and Tables
Entity Table
Order S_ORDER
Party S_PARTY
Product S_PROD_INT
Quote S_DOC_QUOTE

Figure 32. 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

Dealer Sales and Service Promotion

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

Figure 33. Dealer Sales and Service Promotion
Title : eDealer Sales and Service Promotion

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

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

target subject of subject of
of
OTHER EVENT CAMPAIGN CALL LIST

Document ID and Tax ID

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

Figure 34. Document ID and Tax ID

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

ACCOUNT TYPES
COMPONENTS
for have
have
composed of
exists for exists for
PRICE LIST

Dun & Bradstreet Integration

This ERD (shown in Figure 35) 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 34. Dun & Bradstreet Integration ERD Entities and Tables
Entity Table
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
92
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 35. Dun & Bradstreet Integration
equivalent to equivalent to
parent of child of
domestic parent of domestic child of
global parent of global child of
CALL LIST D&B

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

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

PROSPECT RESPONSIBILITY TYPE

composed of
member in
Employee KPI
This ERD (shown in Figure 36) 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 35. Employee KPI ERD Entities and Tables
Entity Table
BUSINESS UNIT S_BU
EMPLOYEE PERFORMANCE S_EMP_PERF_MEAS

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

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

PERSON

Figure 36. 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

Event Tax Administration

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

Team Member S_USER, S_PARTY

Figure 37. Event Tax Administration
Title : Event- Tax Administration

EVENT/FUNCTION EVENT LOCATION ROOM TAX CODE/SERVICE CODE

held at
FUNCTION
location of
belongs to
for
contains TAX CODE

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

instance of
current price list of

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

parent to
parent to
for

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

Figure 38. 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 39) 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 38. Field Service Inventory ERD Entities and Tables
Entity Table
Address S_ADDR_PER
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

Title : Field Service Inventory
of
100
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 39. Field Service Inventory
PRODUCT INVENTORY at
LOCATION PERSONAL (TRUNK) OTHER INVENTORY
stores
INVENTORY LOCATION LOCATION
of for
INVENTORY responsibility of
LOCATION TYPE type of
PERSON
for type of accessed by located responsibility visible
at replenished of to
affiliated holder of for
PRODUCT from
with
INVENTORY
ADDRESS
CATEGORY
responsible responsible for

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

ORGANIZATION ORGANIZATION

NON-SERIALIZABLE SERIALIZABLE
sub-org
PRODUCT PRODUCT composed of of
Field Service Scheduler

This ERD (shown in Figure 40) 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 39. Field Service Scheduler ERD Entities and Tables
Entity Table
Address S_ADDR_PER
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
Siebel Data Model Reference for Industry Applications Version 8.1 10 1

Figure 40. 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
Financial Account
This ERD (shown in Figure 41) illustrates how Siebel Financial Services supports tracking of financial
accounts (instances of products or assets). A financial account can be owned by an organization, or
a number of contacts. The owners can track the activities, service requests, balance history, and
transactions on their accounts, as well as the balance of their external accounts using Siebel
Financial Services. The manager can track the profitability of his customers through contact and
account profitability.
Table 40. Financial Account ERD Entities and Tables
Entity Table
Account Aggregation Service S_FN_AAG_SVC
Account Analysis S_FN_SRVC_TXN
Account Profitability S_ORG_PRFTBLTY
Activity S_EVT_ACT
Address S_ADDR_PER
Asset Relationship S_ASSET_REL
Assignment Group S_ASGN_GRP
Attachment S_ASSET_ATT
Authorization S_ASSETCON_AUTH
Balance History S_FN_ACCNT_BAL
Contact Profitability S_CON_PRFTBLTY
Fee S_FN_ACCNT_FEE
Financial Account Contact S_ASSET_CON
Financial Transaction S_FN_ACCNT_TXN
Note S_NOTE_ASSET

Product S_PROD_INT
Schedule S_FN_ACCNT_SCHD

Title : Financial Account
104
AUTHORIZATION
ADDRESS ASSIGNMENT
ACTIVITY
GROUP(TERRITORY)
PERSONAL for
ADDRESS participant in
defined for for
subject of
BUSINESS
ADDRESS
FINANCIAL ACCOUNT CONTACT
subject of
for
Figure 41. Financial Account
PRODUCT
ASSET NOTE ACCOUNT for
RELATIONSHIP CONTACT
ANALYSIS BALANCE ACCOUNT
AGGREGATION PROFITABILITY
HISTORY
for of SERVICE
for for
for used by of
FINANCIAL ACCOUNT
TRANSACTION PROFITABILITY
associated associated
located
subject of with with at for of
for problems with subject associated subject of

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

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

Financial Account Application

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

Fee S_FN_OFFR_FEE
Inc. Exp. Contact S_FN_INCEXP_CON
Income/Expense S_FN_INCM_EXP
Note S_NOTE_OPTY
Product S_PROD_INT
Quote S_DOC_QUOTE
Sales Stage S_STG
Trailing Document S_OPTY_DOC

Title : Financial Account Application
106
on
ASSET LIABILITY
subject of
uses reported in for has a
for INCOME/EXPENSE associated

with
FEE COLLATERAL APPROVAL
reported in for incurred
by
for for to review
to review
for
ACTIVITY ASSESSMENT
VALUE
Figure 42. Financial Account Application
APPLICATION PRODUCT NOTE STATEMENT
OTHER ACTIVITY for

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

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

with with has
by has
CREDIT ADDRESS
generated REPORT ITEM

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

acknowledged by
has
PRODUCT
for DISCLOSURE acknowledger of

Financial Investments
This ERD (shown in Figure 43) illustrates how Siebel Financial Services supports generation of
financial investments and other relevant associations with organizations, financial accounts,
holdings, distribution, and transactions. The major entities are depicted in the lower half of the
diagram (security and external organization).
Table 42. Financial Investments ERD Entities and Tables
Entity Table
Distribution S_FNSEC_DSTRBTN
External Organization S_ORG_EXT, S_PARTY
Earning S_FNSEC_ERNG
Holding S_FN_HLDNG
Industry S_INDUST
Literature S_LIT
Security S_PROD_INT
Transaction S_FN_ACCNT_TXN

Figure 43. Financial Investments

Title : Financial Investments
DISTRIBUTION
EXTERNAL ORGANIZATION
for
LITERATURE HOLDING TRANSACTION

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

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

Figure 44. Financial Products

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

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

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

Person S_EMP_PER, S_CONTACT, S_PARTY
Position S_POSTN
Product S_PROD_INT
Region S_REGION
Room Avail Equipment S_EVTLOC_RM_EQP
Travel Participant S_EVT_TRVL_PER
Travel Plan S_EVT_TRVL_PLAN
Vendor S_SRC_ORG
Vendor Offer S_EVT_VNDR_OFR
Vendor Review S_EVT_VNDR_RVW
Vendor Service S_EVT_VNDR_SVC

Table 44. Financial Services Events ERD Entities and Tables
Entity Table
Venue S_ORG_EXT, S_PARTY
Venue Offer S_EVT_VENUE_OFR
Venue Review S_EVT_VENUE_RVW
Venue Service S_EVT_VENUE_SVC
Title : Financial Services Events
Author : Oracle, Confidential VENDOR VENDOR reviewed by
VENDOR PERSON
OFFER SERVICE REVIEW
reviewer of
offered by offered by for

provider of provider of subject of
VENDOR
from has for services

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

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

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

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

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

Project S_PROJ
Quote S_DOC_QUOTE
Revenue Item S_REVN
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 46. 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

11 5
Group Insurance Policies

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

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

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

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

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

BENEFITS

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

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

PLAN
has
for consists of uses
GROUP PENSION INSTANCE

part of
has

Health Provider and Provider Group

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

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

made by
PROVIDER SPECIALTY LANGUAGE PAYMENT

SCHEDULE
belongs to for spoken by made to
specialized beneficiary
CONTACT part of part of subject of delivers part of in speaks of
PATIENT PROVIDER

High Tech Marketing Development Fund

This ERD (shown in Figure 50) 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 49. High Tech Marketing Development Fund ERD Entities and Tables
Entity Table
Account, Partner, Other Account S_ORG_EXT
Claim Item S_SRC_PAYITM
Claim, Payment, Other Payment S_SRC_PAYMENT
Event Item S_SRC_COST
General Fund S_MDF
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 50. 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

12 3
High Tech Special Pricing Authorization

This ERD (shown in Figure 51) 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 50. High Tech Special Pricing Authorization ERD Entities and Tables
Entity Table
Account S_ORG_EXT
Address S_ADDR_PER
Claim Item S_POS_CLAIM_ITM
Design Registration S_OPTY_DSGN_REG
Entitlement S_ENTLMNT
Entitlement Product Price S_ENTL_PRDPRI
Meet Competition Quote S_DOC_QUOTE
Opportunity S_OPTY
Point of Sale Header S_POS
Point of Sale Item S_POS_ITEM
Product S_PROD_INT
Quote Line Item S_QUOTE_ITEM
Title : High Tech Special Pricing Authorization
POINT OF SALE ITEM for PRODUCT
subject of
OTHER POS
ITEM
ENTITLEMENT
PRODUCT PRICE
for
having
CLAIM ITEM for
having
ENTITLEMENT QUOTE LINE

ITEM
specially quoted for
referencing
subject of
Figure 51. 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

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

Estimate
Charge Code S_EVT_CHRG_LST

Function Business Type by Date S_BIZ_TP_DT_TNT
Function S_FUNC_TNT
Quote S_DOC_QUOTE
Opportunity S_OPTY
Tax/Service List S_PRI_LST
Figure 52. Hospitality Category
Title : Hospitality Category

CATEGORY REVENUE child of

parent of
FUNCTION BUSINESS subject of FUNCTION AVERAGE HOSPITALITY CATEGORY

TYPE BY DATE LEVEL
of
PARENT
parent of
CATEGORY
FUNCTION subject of FUNCTION REVENUE child of for
BY CATEGORY subject of
for
parent of
subject of
QUOTE REVENUE BY child of
QUOTE for CATEGORY
parent of
child of
subject of
QUOTE MACRO REVENUE for
for ESTIMATE CATEGORY
subject of
generated from
lead to for
subject of OPPORTUNITY MACRO
subject of
OPPORTUNITY REVENUE ESTIMATE
for parent of
child of
PRODUCT OR
SERVICE associated with SUB CATEGORY
for
TAX / SERVICE LIST associated with CHARGE CODE related with
defined for subject of

Institutional Sales
product or security traded in the stock market. One or more positions (such as institutional
salespeople) can cover a product. A position owns and prepares a call list containing one or more
contacts, who are the objects of the calls associated with any number of products. Siebel Financial
Services also tracks security or product line interests of a contact, as well as the securities held by
an organization unit (such as a company). Siebel Financial Services creates many-to-many
relationships when storing the literature associated with employees, activities, and products. A
position can send any number of pieces of literature to a contact within one activity.
Table 52. Institutional Sales ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Industry S_INDUST
Literature S_LIT
Product S_PROD_INT
Title : Institutional Sales
POSITION INDUSTRY ACTIVITY EMPLOYEE
owns covers covers subject uses author

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

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

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

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

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

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

Oracle
132

+ '" &$

$[N

13
+"$
3 2 26
'"
$

3
13
$
2 TT '"+
14
13

14
Figure 54. Insurance Claims

2 2

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

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

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

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

13 1

6

13
14 14

14 14 14
%> ! 13

2 14 6
14 14 14
14 14
14

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

License Restriction S_DL_RSTRCT
Payment Plan S_PAY_PLAN
Policy Contact S_ASSET_CON

Title : Insurance Policies
134
DISCOUNT
HOUSEHOLD CONTACT
applied to applied to
membership in membership of
LICENSE
RESTRICTION
INSURANCE POLICY ITEM

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

subject to
characterized by subject of subject of subject of composed of subject to subject of subject of
INSURANCE POLICY ITEM INSURANCE POLICY

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

Invoicable Charges
This ERD (shown in Figure 56) 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 55. Invoicable Charges ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Address S_ADDR_PER
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 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
136
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 56. 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
Invoices
This ERD (shown in Figure 57) 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 56. Invoices ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Expense S_EXP_ITEM
Invoice S_INVOICE
Invoice Attachment S_INVOICE_ATT
Order S_ORDER
Part Movement S_ORDPART_MVMT
Part Repair S_PART_RPR
Period S_PERIOD
Product S_PROD_INT
Project S_PROJ
Shipment S_SHIPMENT

138
Title : Invoices
INVOICE ATTACHMENT PAYMENT
made for
for
source for fulfilled by
INVOICE
Figure 57. 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
Life Insurance Policy

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

Insurance Coverage S_APPL_CVRG
Pay Plan S_PAY_PLAN
Product S_PROD_INT
Withdrawal/Surrender S_PAYMT_REQ

Title : Life Insurance Policy
140
ASSESSMENT
VALUE
BENEFICIARY
for
belongs of includes a component of FINANCIAL TRANSACTION
to
COVERAGE ASSESSMENT
OPTION
made up of for
for
for ORGANIZATION
subject in context of
subject SERVICE FINANCIAL
of REQUEST
has of part of responsible for TRANSFER
part of
Figure 58. Life Insurance Policy
INSURANCE undertaken for for

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

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

guaranteed by
based on
ANNUITY
guarantees

basis of
guaranteed by
LIFE POLICY
guarantees
Loyalty
The Loyalty Member and the Loyalty Program ERDs of previous releases have been consolidated into
a single ERD in addition to the new features of 8.1.
This ERD (shown in Figure 59) illustrates how programs and promotions are created for customer
loyalty. Partner companies can have association with a loyalty hosting company to create a loyalty
program. A program is the highest level entity in Siebel Loyalty. Members, tiers, promotions, point
values, and so on are all specific to a single program. The members of the loyalty program can be
individuals, households or accounts. A loyalty member can accrue or redeem points based on their
individual transactions. In Version 8.1, Pricing rule , Pricing Range, Point Subtype, Incentive Choice,
and Partner Statement entities have been introduced to support enhancements to features such as
Post-Paid and Pre-Paid Partnership Management, Promotion Registration Service and so on.
Siebel Loyalty 8.1 extends accrual, redemption, promotion, enrollment, member administration and
other functions:
■ Accrual Processing. Allows unified partner point type for simplified billing. Accrual templates
are used for configurable transaction validations. Multiple partner debits for joint promotions
enable cost sharing among partners. User-defined controls and billing triggers are provided to
manage partner point balance. Allows joint rewards to benefit the organization for employee’s
business transactions.
■ Promotion. Supports range-based points calculation as well as issuing vouchers as an accrual

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

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

occur. Content is now generated in XML format for compatibility with third-party fulfillment
applications.
Partner Administration functionality has also been extended:

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

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

Voucher S_LOY_MEM_VCHR

Title : Loyalty
Author : Oracle ,Confidential TIER
REWARD
144
for
qualified for
available for
LOAN
TIER
qualifies for
belongs to
for LOYALTY PROGRAM MEMBER
STATEMENT for
Figure 59. Loyalty
subject of part of
made up of
owned by TIER CLASS

part of
VOUCHER
owner of
for defined
INCENTIVE LOYALTY for
CHOICE PROMOTION
gives
made up of defined for
BUCKET
done by subject of
qualified for
ACTIVITY opted in by
uses
ATTRIBUTE for
executer of
used by DEFINITION
referred by of
PACKAGE REDEMPTION
TRAVEL for
PRODUCT ACTIVITY
INFORMATION
subject of
part of
part of
owned by reference for
made of made of
MEMBERSHIP PARTNER
subject of
CARD STATEMENT
owns LOYALTY TRANSACTION defined for uses
for child of
generated for
REDEMPTION partnered
enrolled by enrolled by enrolled by in for with
ITEM for type part of
for
in in subject of
in POINT BLOCK
parent of POINT
PRICING TYPE of
OPTIONS INDIVIDUAL HOUSEHOLD ACCOUNT based on
involved in
basis for
for owned by
defined for uses
defined for for owner of
uses ACCRUAL ITEM PRICING
subject of RANGE PROGRAM PARTNER
PRODUCT
for POINT
... part of SUBTYPE
consists of
in associated involved in
made of with defined for
HOSTING PURCHASE SERVICE
PARTNER COMPANY TRANSFER PRODUCT PRICING
ACCRUAL STATUS
PARTNER TRANSACTION LIMITS ASSOCIATION RULE subject of consists of
TEMPLATE RESTRICTION
PRODUCT allocated to
uses
OFFERING defined for
for partnered
defined for
used by used by with used by
defined for host for
uses for run by subject of uses uses uses uses subject of
subject of uses uses
uses
LOYALTY PROGRAM

Managed Care
This ERD (shown in Figure 60) illustrates how plan design, formulary, and formulary product are used
in Siebel Life Sciences. An account contains plan designs, which have relationships to contacts. Each
plan design contains formularies, which are associated with markets that are essentially products.
Each formulary contains formulary products, which are children products for the market the
formulary is associated with.
Table 59. Managed Care ERD Entities and Tables
Entity Table
Formulary S_INSPLN_FRMLY
Formulary Product S_PLNFRMLY_PROD
Health Care Professional S_CONTACT, S_PARTY
Managed Care Plan S_INS_PLAN
Plan Design Contact S_INSPLAN_CON
Product, Market S_PROD_INT

Figure 60. Managed Care
Title : Managed Care

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

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

PROFESSIONAL
associated
with
Marketing Campaign
This ERD (shown in Figure 61) 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 60. Marketing Campaign ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Call List Member S_CALL_LST_CON
Campaign Call List S_CAMP_CALL_LST
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
148
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 61. 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
PERSON
PROSPECTIVE CONTACT
recipient of

OTHER PERSON
Marketing Collaboration
Collaborative marketing (shown in Figure 62) 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 61. Marketing Collaboration ERD Entities and Tables
Entity Table
Internal Partner/Organization S_ORG_EXT, S_PARTY
Opportunity S_OPTY
Order S_ORDER
Organization Unit, Other Organization Unit S_ORG_EXT, S_PARTY
Partner Organization S_BU, S_PARTY
Party, Other Party S_PARTY
Quote S_DOC_QUOTE
Response S_COMMUNICATION

Figure 62. 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

OTHER ORGANIZATION UNIT

responsible for
OTHER PARTY
Marketing Encyclopedia
This ERD (shown in Figure 63) 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 62. Marketing Encyclopedia ERD Entities and Tables
Entity Table
Company Literature S_CO_LIT
Competitive Company Feature S_CMPT_CO_FEA
Competitive Metric S_CMPT_MTRC
Competitive Product Feature S_CMPT_PROD_FEA
Issue S_ISS
Product Comparison S_PROD_CMP
Product Detail S_PROD_SPEC
Product External S_PROD_EXT
Product Literature S_PROD_LIT

Title : Marketing Encyclopedia
152
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 63. Marketing Encyclopedia
subject of characterized by
competitor of competitor of subject of reference to reference to
PRODUCT OR SERVICE LITERATURE ITEM
INTERNAL PRODUCT EXTERNAL

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

relevant to
ORGANIZATION UNIT
INTERNAL / PARTNER EXTERNAL ORGANIZATION UNIT

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

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

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

Table 63. Marketing Events ERD Entities and Tables
Entity Table
Vendor Offer S_EVT_VNDR_OFR
Vendor Review S_EVT_VNDR_RVW
Vendor Service S_EVT_VNDR_SVC
Venue S_ORG_EXT, S_PARTY
Venue Offer S_EVT_VENUE_OFR
Venue Review S_EVT_VENUE_RVW
Venue Service S_EVT_VENUE_SVC
2613 26
"52 >$! >$!
Oracle >$! %$
** %> >;
13 13

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

>$>$!
213

>$& >$& >$&
1 ** %> >;
2613 13 6 26
13 >$ %
Figure 64. 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!&

%>

15 5
Marketing Plans
This ERD (shown in Figure 65) 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 64. Marketing Plans ERD Entities and Tables
Entity Table
Marketing Event Cost S_SRC_COST
Marketing Event or Activity, Marketing Plan, Other Marketing Plan S_SRC

or Activity
Marketing Goal S_SRC_GOAL
Period S_PERIOD
Planned Marketing Development Fund Allocation S_MDF_ALLOC
Product or Service, Product Line, Other Product or Service S_PROD_INT, S_PROD_LN
Product Promotion S_PROD_INT_SRC
Title : Marketing Plans
PLANNED attributed to
MARKETING MARKETING EVENT
DEVELOPMENT has OR ACTIVITY
FUND ALLOC MARKETING
GOAL
MARKETING
PLAN
estimated for
Figure 65. 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
15 7
Medical Education Event Management

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

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

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

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

Opportunity Management
This ERD (shown in Figure 68) illustrates the significant entities related to an opportunity (or lead),
including relationships to contacts, employees (generally sales representatives), products, accounts,
and so on.
Table 67. Opportunity Management ERD Entities and Tables
Entity Table
Address S_ADDR_PER
Event S_EVT_ACT
External Organization Unit S_ORG_EXT, S_PARTY
Issue S_ISS
Opportunity S_OPTY
Opportunity Relationship S_OPTY_REL
Product S_PROD_INT
Quote S_DOC_QUOTE
Sales Stage S_STG

Source S_SRC
Title : Opportunity Management
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 68. 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

16 3
Order Life Cycle

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

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

OPPORTUNITY ORDER INVOICE
Figure 69. 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

16 5
Orders
This ERD (shown in Figure 70) 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 69. Orders ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Asset S_ASSET
Inventory Transaction S_INV_TXN
Inventory Transaction Type S_INV_TXN_TYPE
Order S_ORDER
Order Type S_ORDER_TYPE
Part Movement S_ACTPART_MVMT, S_ORDPART_MVMT
Part Movement Type S_PARTMVMT_TYPE
Party S_PARTY, S_ORG_EXT, S_POSTN, S_CONTACT

Product S_PROD_INT
Title : Orders
PART MOVEMENT
proceded by followed by
ACTIVITY PART OTHER PART
INVENTORY result of ORDER PART MOVEMENT MOVEMENT MOVEMENT
TRANSACTION
cause of
Figure 70. 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

16 7
Partner Collaboration
Partner collaboration (shown in Figure 71) 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 70. Partner Collaboration ERD Entities and Tables
Entity Table
Business Unit S_BU
Collaboration S_PARTY_GROUP
Collaboration Resource S_PARTY_PER
Collaboration Invitation S_BRDCST_MSG
Party S_PARTY
Position S_POSTN
1
Oracle,
.&%$%%$% $""".
.&%$%%$%`%$%.' .&%$%%$%`%$%.'

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

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

$[$

%9!
$[$* ''.$

''.$

1
"%%

''.$$>$
14

13

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

16 9
Partner Program Registration

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

Oracle, '$
&

$
"
14

'&"
14
' $ '' ' $

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

"<
%
"$

2 2
''% 9 !!$!
"

$
"' $
6
14
2 1 113

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

>''%
14

'
.'+'%
14

' $
>'" $;'%
14

6

3 1

1
$ d

6 6 $
"
'

+
&
"
.&%$%%&$

%$

"" '
'

+


17 1
Party Model
This ERD (shown in Figure 73) 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 72. Party Model ERD Entities and Tables
Entity Table
Business Address S_ADDR_PER
Group S_PARTY
Household S_ORG_GROUP, S_PARTY
Organization Relationship S_PARTY_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 73. 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 74) 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 73. Payments ERD Entities and Tables
Entity Table
Address S_ADDR PER
Invoice S_INVOICE
Order S_ORDER
Party S_PARTY
Prepayment Balance S_PREPAY_BAL
Figure 74. Payments

Title : Payments
INVOICE
PAYMENT
in settlement of
paid by
generated for
INBOUND PAYMENT
billed via
in settlement of ORDER
paid by
received from
debited from
PREPAYMENT
source of BALANCE
OUTBOUND PAYMENT
ADDRESS
addressed to
used in available to
paid to addressed to
for
located at entitled to
receiver of
PARTY
PERSON
source for receiver of
ORGANIZATION UNIT
OTHER ACCOUNT
ORGANIZATION

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

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

Review Component S_PERF_RVW_CMP
Review Component Language S_RVW_COMP_LANG
Review For Skill Item S_PERF_CMPTNCY
Table 74. Performance Review ERD Entities and Tables
Entity Table
Review Metric S_PERF_RVW_MTRC
Review Rating S_PERF_RATING
Review Rating Scale S_PERF_RATING_SCL
Review Template S_PERF_RVW_TMPL
Review Template Component S_PERF_RVW_COMP

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

.= > >;"
26 1 1

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

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

3 >; "$$
Figure 75. 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 76) 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 75. Personal Account ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Opportunity S_OPTY
Personal Account S_ASSET
Personal Account Contact S_ASSET_CON
Product S_PROD_INT

Figure 76. 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 77) 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 76. Personal Financial Review ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Activity Product Instance S_ACT_ASSET
Asset (Liability) S_FN_ASSET_LIAB
Asset (Liability) Contact S_FN_ASSET_LIAB_CON
Contact Relationship S_CONTACT_REL
Financial Need S_FN_NEED
Financial Recommendation S_FN_RCMD
Household/Account S_ORG_GROUP, S_PARTY

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

Title : Personal Financial Review
182
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 77. 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

Personalized Content Delivery

The Personalized Content Delivery feature allows pharmaceutical sales representatives to deliver a
sales communication to general practitioners and medical specialists using multimedia visualizations.
This ERD (shown in Figure 78) illustrates how a Message Plan is associated to Messages, Products
Presentation Details and Party Entities such as Account, Contact, Position and Business Unit.
Table 77. Personalized Content Delivery ERD Entities and Tables
Entity Table
Activity S_EVT_ACT, S_EVT_ACT_LSX
Assessment Template S_TMPL_PLANITEM
Business Unit S_PARTY, S_BU
Decision Issues S_ISS
Message S_LIT, S_LIT_LSX
Message Product Application S_LIT_PROD_APPL
Messaging Plan S_MSG_PLAN
Messaging Plan Item S_MSGPLAN_ITM
Objective S_SRC
Offer S_DMND_CRTN_PRG
Period S_PERIOD
Position S_PARTY, S_POSTN
Presentation Details S_PCD_DETAIL
Product S_PROD_INT

Title : LS Personalized Content Delivery
184
for
MESSAGING
PRODUCT
PLAN associated to
has
parent of
ASSESSMENT TEMPLATE
for
MESSAGE PRODUCT has DECISION

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

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

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

Figure 79. 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 80) 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 79. Pricing ERD Entities and Tables
Entity Table
Component Price Adjustment S_PRI_CFG_ITEM
Object Class Extended Attribute S_XA_ATTR
Pricing Factor Item S_PRIFCTR_ITM
Pricing Factor Item Attrib S_PRIFCTITM_ATR
Pricing Matrix S_PRI_MTRX
Pricing Matrix Attribute S_PRI_ATTR
Pricing Matrix Item S_PRI_MTRX_ITEM
Pricing Matrix Value S_PRI_MTRX_VAL

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

Title : Pricing
188
an adjustment for INTERNAL

COMPONENT PRICE PRODUCT OR
ADJUSTMENT the subject of SERVICE
for
Figure 80. 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 81) 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 80. Product Promotion ERD Entities and Tables
Entity Table
Conditional Charge Prorate Plan S_AGR_PR_PLAN
Product Promotion S_PROD_INT
Product Promotion Charge S_PROM_CHRG
Product Promotion Item S_PROM_ITEM
Product Promotion Item Attribute S_PROM_ITEM_XA
Product Promotion Item Attribute Value S_PROMITM_VAL
Product Promotion Pricing Matrix Rule S_PROM_PMTRX
Product Promotion Term S_PROMITM_TRMS
Product Promotion Term Description S_PROD_TRM_DESC

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

has
Figure 81. 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 82) 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 81. Product Quality Tracking ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Defect Symptom S_PRDFCT_SYMP
Product or Service S_PROD_INT, S_PROD_EXT
Product Quality Item S_PROD_DEFECT
Project S_PROJ
Project Item S_PROJITEM
Resolution Item S_RESITEM

Title : Product Quality Tracking
PROJECT made up of
192
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 82. 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 83) 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 82. Product Recommendation ERD Entities and Tables
Entity Table
Communication S_COMMUNICATION
Product Message S_PROD_MSG
Product Message Response S_PROD_MSG_RESP
Product Message Variable S_PROD_MSG_VAR
Product Recommendation S_PROD_RECMNDTN

Figure 83. 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 84) 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 83. Products or Services ERD Entities and Tables
Entity Table
Catalog S_CTLG
Class Attribute S_XA_ATTR
Class of Product or Service S_VOD, S_VOD_VER
Language S_LANG
Product Assembly Port S_PROD_ITEM
Product or Service S_PROD_INT or S_PROD_EXT
Product or Service Attribute S_PROD_INT_XA
Product Structure S_PROD_ITEM
Vendor S_ORG_EXT, S_PARTY

Title : Products or Services
196
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 84. 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 85) 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 84. Professional Services ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Address S_ADDR_PER
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
198
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 85. 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

Public Sector Case Lead Management

This ERD (shown in Figure 86) illustrates how an investigative lead is related to incident and case. It
shows how a party, such as a person, organization, or group, becomes involved in the investigative lead,
and the positions of team members assigned to work on it. This ERD also shows evidence/supporting
documentation as the trigger of the investigative lead. The physical object used, location of the
investigative lead, as well as the related activity, disease, and service request are shown. This ERD
covers the features of applications received from users and their supporting documents as well as their
visibility to various organizations.
New features in 8.1 include:
■ Submitted applications are reviewed on the Siebel side and information uploaded from the
applications into Siebel objects such as case and contacts.
■ Applications received from users/citizens for benefits, visa, immigration, and so forth are taken
into account. The supporting documents for a given application, as well as any scanned images
of the application, are stored in file systems. The visibility of an application to various
organizations is also managed.
■ Data from the application form, as filled out by the citizen or employee, is transferred to the
Siebel application so that the agency has a historical record of the data as submitted at that point
in time. Employees will then upload the application into the system. During the upload process,
relevant data from the form(s) is imported into the appropriate Siebel contact, household and
case records.
Table 85. Public Sector Case Lead Management ERD Entities and Tables
Entity Table
INVESTIGATIVE CASE LEAD S_CASE_LEAD
PARTY S_PARTY
PERSON S_CONTACT, S_USER, S_CONTACT_PSX
ORGANIZATION/GROUP S_ORG_EXT, S_ORG_GRP_PSX

POSITION S_POSTN
ADDRESS S_ADDR_PER
SERVICE REQUEST S_SRV_REQ
ACTIVITY S_EVT_ACT
CASE S_CASE, S_CASE_PSX
PHYSICAL OBJECT S_ASSET
DISEASE S_DISEASE
EVIDENCE/SUPPORTING DOCUMENT S_EVIDENCE
INCIDENT S_INCIDENT
PERSON DESCRIPTION S_SUBJECT

Table 85. Public Sector Case Lead Management ERD Entities and Tables
Entity Table
APPLICATION S_PS_APPL
APPLICATION ATTACHMENT S_PS_APPL_ATT
APPLICATION/BUSINESS UNIT VISIBILITY S_PS_APPL_BU
Title : Public Sector Case Lead Management PERSON DESCRIPTION
for for for
has
for
EVIDENCE / SUPPORTING DOCUMENT
APPLICATION supported by INCIDENT
ATTACHMENT
for supported by
related to
CASE
based on basis for serviced through
ACTIVITY serviced through

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

BUSINESS UNIT
related to
subject of matching with

PARTY has visibility to involved in approver of assigned to
PERSON
ORGANIZATION/GROUP POSITION
responsibility of
AGENCY OTHER AGENT SUSPECT
OTHER SUSPICIOUS
ORGANIZATION GROUP responsible for PERSON

20 1
Public Sector Contact Identity

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

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

Figure 87. Public Sector Contact Identity

$[$0
&

%%&$

$ + 9% *$+
2

&.' % $
+
$

20 3
Public Sector Evidence Management

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

7&" 7&
13
! 1?

!"
13 13

%>
13 7&% 2

$>%
>
2 '!
$ !$

>+
2 1
13 1

2 2 1

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

! &"$
13

13
6 6
1 1 213
13 13

14
!!%%
9+% '
.=

+ 2 2 2 2

1
2
6

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

$[$
13
%&% &%

&

20 5
Public Sector Incident Management

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

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

**$%
6

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

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

1
13
Figure 89. Public Sector Incident Management
2

14 1 6 $=&+

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

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

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

2 2 2 2
+

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

$ + 9 %&%
$

$[$
& %$

20 7
Revenue
This ERD (shown in Figure 90) 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 89. Revenue ERD Entities and Tables
Entity Table
Agreement Item S_AGREE_ITEM
Invoice S_INVOICE
Invoice Item S_INVC_ITEM
Opportunity S_OPTY

Project S_PROJ
Revenue Item S_REVN
Revenue Template S_REVN_TMPL
Revenue Template Item S_REVN_TMPL_ITM
Title : Revenue
a report to manager of
revenue plan for
PERSON
POSITION OTHER PERSON
REVENUE ITEM for held by EMPLOYEE / AGENT
Figure 90. 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

20 9
Routes and Best Call Hours

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

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

OTHER ORGANIZATION
have defined for
RETAILER
STORE

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 92) 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 91. Sales Hierarchy and Credit Assignment ERD Entities and Tables
Entity Table
Credit Allocation S_SLSCR_RL_PSTN
Credit Assignment Rule S_SLSCRDT_RULE
Credit Rule Criteria S_SLSCRDT_CRIT
Credit Rule Criteria Value S_SLSCRDT_VAL
Hierarchy Version S_SLS_HIER_VER
Hierarchy Version Territory S_SLS_HIER_TERR
Position Territory Assignment S_SLSTERR_POSTN
Sales Hierarchy S_SLS_HIER

Sales Territory S_SLS_TERR
Title : Sales Hierarchy and Credit Assignment
Author : Oracle, Confidential PARTY
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 92. 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

21 3
Sales Volume Planning

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

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

part of
Title : Sales Volume Planning EXTERNAL ORGANIZATION

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

PRODUCT
BASELINE BASELINE exist for
composed of
have CATEGORY
PRODUCT CATEGORY
SHIPMENT SHIPMENT
exist for
F-GROUP
PRODUCT CATEGORY
CONSUMPTION CONSUMPTION
PRODUCT CATEGORY
TARGET TARGET PERIOD
have
exist for

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

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

for
TRANSACTION ITEM owned by
TRANSFER ITEM own
transferred by
transfer
belonging to
belonging to items of
of of of
associated composed of
with owned by
PRODUCT INVENTORY
TRANSACTION SAMPLE TRANSACTION
ATTACHMENT transferred by own
transfer
consists of
dropped at
for belonging to
AUDIT REPORT drop of
ATTACHMENT for CALL
VALIDATION
RESULT
associated with for
consists of associated with
for
INVENTORY AUDIT STOCK PERIOD owned by
REPORT
own
inventoried in subject of
INTERNAL PRODUCT
belongs to Person list factor

21 7
Service Agreement
This ERD (shown in Figure 95) 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 94. Service Agreement ERD Entities and Tables
Entity Table
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
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 95. 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
21 9
Service Calendars and Work Shifts

This ERD (shown in Figure 96) 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 95. Service Calendars and Work Shifts ERD Entities and Tables
Entity Table
Employee S_CONTACT, S_EMP_PER, S_PARTY
Employee Exception Hours S_EXCPT_CAL_HRS
Exception Calendar S_EXCPT_CAL
Exception Calendar Hours S_EXCPT_CAL_HRS
Schedule Calendar S_SCHED_CAL
Schedule Calendar Hours S_SCHED_CAL_HRS
Service Calendar S_SCHED_CAL
Work Shift S_SCHED_CAL
Figure 96. 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 97) 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 96. Service Request ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Asset (Product Instance) S_ASSET
External Product Instance S_ORG_PRDEXT
Party S_PARTY, S_ORG_EXT, S_CONTACT,

S_USER
Product or Service S_PROD_INT, S_PROD_EXT
Service Region S_SRV_REGN
made up of part of
Title : Service Request
ACTIVITY
SERVICE REQUEST ACTIVITY OTHER ACTIVITY
for responsibility of
responsibility of
part of
made up of subject of
SERVICE REQUEST PARTY
PERSON
Figure 97. 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
22 3
Shipment
This ERD (shown in Figure 98) 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 97. Shipment ERD Entities and Tables
Entity Table
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
13
!">"$
!&
613 $$'
%9"$'$"
3 ">"$
!"!'>+"% +
3
Figure 98. Shipment

9">"$

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

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

!
1
7&
1

$>$+' $


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

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

22 7
Syndicated Data
This ERD (shown in Figure 100) illustrates how the syndicated data (sales and prescription
information) is associated with a period, plan, account, contact, postal code, territory, and area.
Table 99. Syndicated Data ERD Entities and Tables
Entity Table
Period S_PERIOD
Plan S_INS_PLAN
Postal Code S_ZIPCODE
Product S_PROD_INT
Region S_REGION
Syndicated Data S_SYND_DATA
Title : Syndicated Data
for AREA
SYNDICATED DATA
PERIOD subject of
for
in SALES
Figure 100.Syndicated Data
for POSTAL CODE
subject of
PRODUCT for
of
for ACCOUNT
subject of
PLAN PRESCRIPTION
for
for CONTACT
in
subject of
POSITION
recipient of
for TERRITORY
for
subject of

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

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

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

Figure 101.Teller Administration
with with REQUEST LINE

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

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

23 1
Territory Alignment–Quota Assignment

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

0"$
9$

2

&$0
"$
9$

07&
$ 0
9$

"$
9$

$07&
9$

$07&
9$

Figure 102.Territory Alignment–Quota Assignment

'
$"$7&

'
$"$07.<!;$

14 2 15 6
+
%'%7&
! '
$"$7&

2
23 3
Territory Management
This ERD (shown in Figure 103) 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 102. Territory Management ERD Entities and Tables
Entity Table
Account S_ORG_EXT
Account Team Member S_ACCNT_POSTN
Account/Terr Mapping S_TERR_ACCNT
Asset S_ASSET
Asset Team Member S_ASSET_POSTN
Asset/Terr Mapping S_TERR_ASSET
Business Unit S_BU
Contact S_CONTACT
Contact/Terr Mapping S_TERR_CON
Contact Team Member S_POSTN_CON
Division S_ORG_EXT
Geo/Terr Mapping S_TERR_ZIP, S_TERR_REGION
Position S_POSTN
Position Territory Assignment S_TERR_POSITION
Region S_REGION
Territory Hierarchy S_TERR_HIER
Territory Version S_TERRHIER_NODE
Zipcode (None)
3"
Oracle
+

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

0
"$
"$
"$
"$

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

&$""".

13

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

13
&$

$ 13

13
.&%$%%&$
%%

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


23 5
Territory Management - Consumer Sector

Territory Management - Consumer Sector (CS), shown in Figure 104, allows multiple representatives
to call on the same account to carry out different roles on a regular basis. The Territory Management
module within Siebel Consumer Goods supports a system for creating territories and modifying them
to meet the needs of the consumer goods industry.
Table 103. Territory Management - CS ERD Entities and Tables
Entity Table
Account S_ORG_EXT
Account Team Member S_ACCNT_POSTN
Account Team Role S_ACCNT_POSROLE
Account/Terr Mapping S_TERR_ACCNT
Activity S_EVT_ACT
Business Unit S_BU
Contact S_CONTACT
Contact Team Member S_POSTN_CON
Contact/Terr Mapping S_TERR_CON
Division S_ORG_EXT
Position S_POSTN
Position Territory Assignment S_TERR_POSITION

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

%$+%%
$"$ +
13

14
>+ +>%$ 2

+
%$
'
2 2 +"$
14
'

+ &$

&$0 $ 0

"$
"$

14 13

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

14
14 14 13

%$' &$"
"".

13
$ .&%$%%&$

1

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


23 7
Territory Management - Life Sciences

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

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

0"$

9$
13

9 '

[ !
$

0
%%0
"$
9$
13

%%

0
$ 0
"$
9$
13
$

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

$!$
&$

213

+9 9+
+'
$"$
2

13

.&%$%%&$

%$ 14 @13 1

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

23 9
Textile, Apparel, and Footwear

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

Period S_PERIOD
Period Relationship S_PERIOD_REL
Product Attribute Type S_LST_OF_VAL
Product Attribute Value S_LST_OF_VAL
Product Option Mix Preference S_PROD_OPT_MIX
Product Option Mix Proportion S_PROD_OPT_PCT
Product Option Range S_PROD_OPTION
Product Option Range Member S_PROD_OPT_VAL
Quote S_DOC_QUOTE
ORDER ITEM
primarily composed of subject of PRODUCT ATTRIBUTE VALUE
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 106.Textile, Apparel, and Footwear
of RANGE MEMBER
ordered on belonging to scope of
ORDER definer of
for
billed to for PRODUCT INTERNAL
ORGANIZATION recommended to be ordered in
EXTERNAL
STYLE/COLOR/DIMENSION
ACCOUNT
primarily
defined created from launched applicable defined for collection defined by secondarily
for in to of defined by
STORE composed
composed of
of parent to defined for
lead to PRODUCT OPTION RANGE
OTHER CATEGORY
subject of ORGANIZATION
QUOTE
defined for NON-SEASONAL
for primarily
for manufactured in in
ASSORTMENT subject of composed of SIZE RUN
PLAN
MARKETING secondarily
SEGMENT the target of targetted at LINE OF BUSINESS manufactured in in
defined for SEASONAL
debut season for a collection of
COLOR PALETTE
PERIOD subject of defined for
SEASON
subject of
delivery period for delivery period for
of made up
PERIOD RELATIONSHIP of
Title : Textile, Apparel and Footwear
to part of Author : Oracle, Confidential

WEEK OTHER PERIOD TYPES
24 1
Time Sheet
This ERD (shown in Figure 107) 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 106. Time Sheet ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Period S_PERIOD
Project S_PROJ
Time Unit S_TMSHT_ITEM
Timesheet S_TMSHT
Timesheet Approval S_TMSHT_APPR
Timesheet Line S_TMSHT_LN
Work Type S_PROJ
Title : Time Sheet
adjusted
ACTIVITY
TIME UNIT
Figure 107.Time Sheet
adjustment
TIME ADJUSTMENT WORK TIME UNIT based
basis for
owned by targeted at owned by associated with

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

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

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

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

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

Oracle
!"
13

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

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

?13
%$
?

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

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

!&
!& 8$'
14 14
!& $$'

24 5
Training Curriculum Course

This ERD (shown in Figure 109) 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 108. Training Curriculum Course ERD Entities and Tables
Entity Table
Employee Course S_EMP_CRSE
Employee Course Status S_EMP_CRSE_STAT
Title : Training Curriculum Course
TRAINING CURRICULUM CURRICULUM ACCESS GROUP
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 109.Training Curriculum Course
EMPLOYEE COURSE STATUS
of
COURSE
AVAILABLE
LANGUAGE tracked by
EMPLOYEE COURSE certified for

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

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

basis of PERSON
TRAINING COURSE
OTHER PRODUCT OR SERVICE

24 7
Training Test Engine

This ERD (shown in Figure 110) 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 109. Training Test Engine ERD Entities and Tables
Entity Table
Course/Course Offering Test S_CRSE_OFFR_TST
Event Location S_EVTLOC
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
'7&%$

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

14 7&%$ 7&%$
14 '

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

%7&%$
13

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

+ '$
&

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

14
7&%$ 0.= >

+
>$' $
6

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

24 9
Universal Customer Master

This ERD (shown in Figure 111) illustrates how Universal Customer Master works with external
systems and the Siebel application. This ERD also shows the UCM engine schematics including the
survivorship rule set and its relationship with repository-based information, UCM objects, and
operations such as deduplication, merge, and the keeping of history.
Table 110. Universal Customer Master ERD Entities and Tables
Entity Table
Attribute Group S_UCM_ATGP
Attribute Group Field Mapping S_UCM_ATGP_FLD
Attribute Group Rule S_UCM_ATGP_RULE
Attribute Group Update History S_UCM_CON_ATGP,

S_UCM_ORG_ATGP
S_UCM_OGP_ATGP
Confidence Level S_UCM_CONF_LVL
External Information System S_CIF_EXT_SYST
External Information System Mapping S_CIF_CON_MAP,

S_CIF_ORGRP_MAP,
S_CIF_ORG_MAP
External System Privilege S_CIF_SYS_DTL
Rule Set S_UCM_RULE_SET
UCM Address S_UCM_ADDR_PER
UCM Asset S_UCM_ASSET

UCM Child Object S_UCM_CON_CHILD
S_UCM_OGP_CHILD
S_UCM_ORG_CHILD
UCM Deduplication S_UCM_DEDUP
UCM Merge History S_UCM_CON_MERGE,

S_UCM_ORG_MERGE
UCM Object S_UCM_CONTACT

S_UCM_ORG_EXT
S_UCM_ORGGRP
UCM Privacy S_UCM_PRIVACY
&2 "
Oracle .&
&
.& 1 *'!"$
&'%

&&'

$*!$ '>' 1

6
.&
&
1

.&
&&!9%+

& "!!%%
Figure 111.Universal Customer Master

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

& "!!&
9%+
& "> +
1
1

3 %+.&%$%%
"$$
8$' & ".=

%+%"
>'
& "%$ & " & "

$[$ 9&%9'!
& "+
8

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

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

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

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

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

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

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

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

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

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

VEHICLE LEASE
CONTACT COLLECTION AGENCY
HOLDING
AGENT
COMPANY
OTHER OTHER ORGANIZATION

PERSON

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

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

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

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

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

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

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

25 9
Versioned Object Definition

Versioned Object Definition (shown in Figure 116) 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 115. Versioned Object Definition ERD Entities and Tables
Entity Table
Attribute Definition S_ISS_ATTR_DEF
Attribute Value S_ISS_ATTR_VAL
Joint Workspace S_ISS_JWS
Joint Workspace Item S_ISS_JWS_ITEM
Object Attribute S_ISS_OBJ_ATTR
Object Attribute Value S_ISS_OBATR_VAL
Object Definition S_ISS_OBJ_DEF
Object Definition S_VOD
Versioned Object Definition Version S_VOD_VER
Title : Versioned Object Definition
OBJECT ATTRIBUTE VALUE JOINT WORKSPACE
PRODUCT ATTRIBUTE VALUE PRODUCT TEMPLATE

ATTRIBUTE VALUE
for for for for

have
for
have
OBJECT ATTRIBUTE JOINT WORKSPACE

Figure 116.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

26 1
Warranty
This ERD (shown in Figure 117) 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 116. Warranty ERD Entities and Tables
Entity Table
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
ORDER ITEM claimed against ASSET of ASSET PRODUCT

WARRANTY an instance of
applied to COVERAGE subject of
made into
part of by
Figure 117.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
warrantor of vendor of
ORGANIZATION UNIT
role played by
subject of

26 3
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 265
■ “Data Model Type Definitions” on page 268
■ “Columns of Numeric Physical Type” on page 272
■ “Siebel System Fields” on page 272
■ “INTEGRATION_ID Columns” on page 273
■ “Include Only Field” on page 273
■ “Siebel Repository” on page 273
■ “Database Schema Version” on page 274
■ “Limit Checking for Data Types” on page 274
■ “Validating the Siebel Schema” on page 274
■ “Party Model Unifies Access to Data” on page 275
■ “Generating a Report about Tables” on page 275
Data Model Naming Conventions

This topic describes:
■ Table Naming Conventions
■ Index Naming Conventions on page 267
■ Column Naming Conventions on page 267
■ Abbreviations Used in the Physical Model Listings on page 268
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.

Physical Model ■ Data Model Naming Conventions
SUFFIX A supertype name may be followed by the entity subtype. For example, the supertype
EVT (event) has ACT (activity) as one of its subtypes. Thus, the name becomes
S_EVT_ACT.
The prefix indicates the part of the Siebel schema to which a table belongs. Table 117 provides some
of the prefixes and their descriptions.
Table 117. 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 118 provides some of the suffixes and their descriptions.
Table 118. 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 119.
Table 119. 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 120 shows the
standard suffixes for column names and their possible values.
Table 120. 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 120. 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 121.
Table 121. 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 126 on page 272.
Data Model Type Definitions

This topic contains the following type definitions:
■ Table Type Definitions on page 269
■ Table Status Definitions on page 270
■ Column Type Definitions on page 271
■ Domain Type Definitions on page 271
Table Type Definitions

Table 122 provides descriptions of the types of tables in the Siebel database.
Table 122. 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 122. 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 123.
Table Status Definitions

Table 123 provides descriptions of the types of table status in the Siebel database.
Table 123. 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 124 provides descriptions for the types of columns in the Siebel database.
Table 124. 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 126 on
page 272.
Domain Type Definitions

Table 125 provides descriptions for the domain types of certain columns in the Siebel database.
Table 125. 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 125. 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 126. Do not alter the contents of
these fields.
Table 126. 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 126. Siebel System Fields
Column Name Description
DB_LAST_UPD Date and time the record was last changed in the database.
DB_LAST_UPD_SRC Source of the instance or operation that changed the record in the
database.
LAST_UPD Date and time the record was last changed.
LAST_UPD_BY User who last changed record (foreign key to S_USER).
MODIFICATION_NUM Internally incremented number used for locking and to identify

records for incremental updates of the Siebel Business Data
Warehouse.
ROW_ID Unique row identifier.
INTEGRATION_ID Columns
Many tables contain a column called INTEGRATION_ID 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.

Physical Model ■ Database Schema Version
Database Schema Version

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

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

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

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

Physical Model ■ Generating a Report about Tables
To generate a table report

1 Log in to the Siebel application, and navigate to the Administration - Application screen, then
Tables view.
2 From the Menu menu, choose New Query.
3 In the Name column, enter the name of the table for which the report is to be generated, and
press Enter.
4 Click the Reports icon in the icon bar.
5 Select Tables Report from the drop-down list.
The Output Type dialog box appears.
6 Select the output format for the report from the drop-down list.
7 Click Submit to generate the report.
The File Download dialog box appears.
8 Choose to open, save or cancel the report.
NOTE: For more information about generating reports, see Siebel Reports Administration Guide.
5 Schema Changes
This chapter lists the table, table column and table index changes in this version of the schema:
■ “Table Changes in This Version” on page 277
■ “Table Column Changes in This Version” on page 281
■ “Table Index Changes in This Version” on page 311
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 277
■ “Changed Tables in This Version” on page 281
New Tables in This Version

Table 129 lists tables that are new in this version.
Table 129. New Tables in This Version
Table Type Active
S_ACC_VIEW_APPL Data(Private) Yes
S_ACRL_RULE_ITM Data (Public) Yes
S_ACT_PGROUP Data (Intersection) Yes

S_BNFPLNITM_PAY Data(Public) Yes
S_BNFT_PLAN_ITM Data(Public) Yes
S_BR_ACTION Data (Public) Yes
S_BR_ACTN_SET Data (Public) Yes
S_BR_EXCPTN Data (Public) Yes
S_BR_INST Data (Public) Yes
S_BULK_REQ Data (Public) Yes
S_CASE_BNFTPLAN Data(Public) Yes
S_CASE_CHGOFCCM Data(Public) Yes
S_CASE_PSX Extension Yes

Schema Changes ■ Table Changes in This Version
Table Type Active
S_CASE_TMPL Data(Intersection) Yes
S_CASE_TMPLITM Data(Intersection) Yes
S_CHAT_KB_VSTD Data (Public) Yes
S_CHAT_LANG_MAP Data (Public) Yes
S_CHAT_PARAM Data (Public) Yes
S_CHAT_ROUTE Data (Public) Yes
S_CHRCTR_IMPT Data (Public) Yes
S_COMM_IMPT Data (Public) Yes
S_COMM_PGROUP Data (Intersection) Yes
S_COMM_SVY_LOG Data (Public) Yes
S_CON_PGROUP Data (Intersection) Yes
S_CONTACT_IMPT Data (Public) Yes
S_CONTACT_PSX Extension Yes
S_CTLGCAT_MSGPL Data(Intersection) Yes
S_DCP_MSGPLAN Data(Intersection) Yes
S_EMP_AUDITSIGN Data(Intersection) Yes
S_INT_OBJ_DATA Data (Private) Yes
S_INT_OBJ_DPLOY Data (Private) Yes
S_INV_AUDIT_RPT Data(Public) Yes

S_INVADTRPT_ATT Data(Public) Yes
S_LEAD Data (Public) Yes
S_LEAD_BU Data (Intersection) Yes
S_LEAD_IMPT Data (Public) Yes
S_LEAD_OPTY Data (Intersection) Yes
S_LEAD_POSTN Data (Intersection) Yes
S_LEAD_PROD Data (Intersection) Yes
S_LEADPROD_IMPT Data (Public) Yes
S_LEADRESP_IMPT Data (Public) Yes
S_LIT_LSX Extension(Siebel) Yes
S_LIT_PROD_APPL Data(Intersection) Yes
S_LITERATUR_REL Data(Intersection) Yes
Table Type Active
S_LOY_ACRL_RULE Data (Public) Yes
S_LOY_ACTRANGE Data (Public) Yes
S_LOY_DISTANCE Data (Public) Yes
S_LOY_LOAN Data (Public) Yes
S_LOY_MEM_BLKAD Data (Public) Yes
S_LOY_MSTAT_PRF Data (Public) Yes
S_LOY_OLAPSTG Data (Public) Yes
S_LOY_PG_PR_ITM Data (Public) Yes
S_LOY_PRI_RANGE Data(Public) Yes
S_LOY_PRI_RULE Data(Public) Yes
S_LOY_PRT_TXN Data (Public) Yes
S_LOY_PTSUBTYPE Data(Public) Yes
S_LOY_PURTRN_LM Data (Public) Yes
S_LOY_RDM_ACT Data (Public) Yes
S_LOY_SOM_HIST Data (Public) Yes
S_LOY_SRC_PROMO Data (Intersection) Yes
S_LOY_SRV_PROD Data (Public) Yes
S_LOY_TRVL_INFO Data (Public) Yes
S_LOY_TXN_ITEM Data (Public) Yes

S_LOY_TXN_STG Data (Public) Yes
S_LOYPR_ICHOICE Data(Public) Yes
S_MKT_EVT_TRG Data(Public) Yes
S_MKT_IMPRT_TSK Data (Public) Yes
S_MKT_IMPT_MAP Data (Public) Yes
S_MKT_SRVY Data (Public) Yes
S_MKT_STGWAIT Data(Public) Yes
S_MKT_STGWT_REL Data(Public) Yes
S_MKTEVTRG_HST Data(Public) Yes
S_MKTEVTRG_MAP Data(Intersection) Yes
S_MKTIMP_CHRCTR Data (Intersection) Yes
S_MKTIMPMAP_ITM Data (Public) Yes

Table Type Active
S_MKTIMPTSK_ARG Data (Public) Yes
S_MKTIMPTSK_LOG Data (Public) Yes
S_MKTPRG_ACTN Data(Public) Yes
S_MKTPRGACT_LST Data(Intersection) Yes
S_MKTSVY_A_LANG Data (Intersection) Yes
S_MKTSVY_ANSW Data (Public) Yes
S_MKTSVY_Q_LANG Data (Intersection) Yes
S_MKTSVY_QUES Data (Public) Yes
S_MKTSVY_SCTN Data (Public) Yes
S_MKTSVYST_QUES Data (Public) Yes
S_MSG_PLAN Data(Public) Yes
S_MSGPL_ITM_REL Data(Intersection) Yes
S_MSGPLAN_BU Data(Intersection) Yes
S_MSGPLAN_ITM Data(Intersection) Yes
S_NOTE_LEAD Data (Public) Yes
S_NOTEOPTY_PGRP Data (Intersection) Yes
S_OPTY_ORG_ATTR Data(Public) Yes
S_OPTY_PGROUP Data (Intersection) Yes
S_ORDER_ACTNSET Data (Intersection) Yes

S_ORG_EXT_IMPT Data (Public) Yes
S_ORG_GRP_PSX Extension Yes
S_ORG_PGROUP Data (Intersection) Yes
S_ORG_RL_PROF Extension (Siebel) Yes
S_PCD_DETAIL Data(Public) Yes
S_PGM_ORG_PROD Data (Public) Yes
S_PGMORG_PNTTYP Data (Public) Yes
S_PGROUP_LANG Data (Intersection) Yes
S_PGROUP_REL Data (Public) Yes
S_PRO_CFG_ITEM Data (Intersection) Yes
S_PROGORG_STMT Data(Public) Yes
S_PROMO_PRTNR Data (Public) Yes
Schema Changes ■ Table Column Changes in This Version
Table Type Active
S_PRSPCON_IMPT Data (Public) Yes
S_PS_APPL Data (Public) Yes
S_PS_APPL_ATT Data (Public) Yes
S_PS_APPL_BU Data (Intersection) Yes
S_SMPL_TXN_ATT Data(Public) Yes
S_SRC_MSGPLAN Data(Intersection) Yes
S_STKPEREMP_EMP Data(Intersection) Yes
S_TIMEZONE_DTL Data (Private) Yes
S_VALDN_RESULT Data(Public) Yes
S_WEB_SITE Data (Public) Yes
S_WEB_SITE_LANG Data (Public) Yes
S_WEBSITE_CNTNT Data (Public) Yes
S_WEBST_TMPL_RL Data (Public) Yes
S_XMLP_REP_IOBJ Data(Public) Yes
S_XMLP_REP_TMPL Data (Public) Yes
S_XMLP_REPOUTPT Data (Public) Yes
S_XMLP_RPT_LANG Data (Intersection) Yes
S_XMLP_RPT_VIEW Data (Intersection) Yes
Changed Tables in This Version

Table 130 lists tables whose type has changed in this version.
Table 130. Table with Changed Type
Table Previous Type New Type
S_TIMEZONE Data (Public) Data (Private)
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 282

■ “Changed Table Columns in This Version” on page 311
New Table Columns in This Version

Table 131 lists table columns that are new in this version. Some column headings are abbreviated as
follows:
■ Opt indicates optional.
■ Len indicates length.
■ Prec indicates precision.
■ Def indicates default.
■ LOV Bnd indicates LOV bound.
Table 131. New Table Columns in This Version
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
S_ACCNT_POSTN NEXT_CALL_DT Y UTC 7

DateTime
S_ACCNT_POSTN NEXT_CALL_OBJECTIV Y Varchar 1500
S_ACT_PRDINT INTEGRATION_ID Y Varchar 30
S_ACT_PRDINT MAX_ALLOC_QTY Y Number 22 22 7
S_ACT_PRDINT MAX_CALL_QTY Y Number 22 22 7
S_ACT_PRDINT MAX_PRODUCT_QTY Y Number 22 22 7

S_ACT_PRDINT PROD_ALLOC_ID Y Varchar 15
S_ACT_PRDINT SUM_SAMPLE_ALLOC Y Number 22 22 7
S_ACT_PRDINT SUM_SAMPLE_PROD Y Number 22 22 7
S_ACT_PROD_APPL PROD_ALLOC_ID Y Varchar 15
S_ACT_SIGN CON_FST_NAME Y Varchar 50
S_ACT_SIGN CON_LST_NAME Y Varchar 50
S_ACT_SIGN DISCLAIMER_TEXT Y Varchar 2000
S_ACT_SIGN INV_AUDIT_RPT_ID Y Varchar 15
S_ACT_SIGN REP_COMP_NAME Y Varchar 50
S_ACT_SIGN REP_FST_NAME Y Varchar 50
S_ACT_SIGN REP_LST_NAME Y Varchar 50
S_ACT_SIGN REP_POSTN Y Varchar 50
S_ACT_SIGN REP_SUB_CONTRACTOR Y Varchar 50

S_ACT_SIGN SAMPLE_TXN_ID Y Varchar 15

S_ADDR_ORG ADDRESSEE Y Varchar 100
S_ADDR_PER ADDRESSEE Y Varchar 100

283
2 84
Data LOV
S_ADDR_PER AIA_INTEG_ID Y Varchar 150
S_ASSESS INV_AUDIT_RPT_ID Y Varchar 15
S_ASSESS LIT_ID Y Varchar 15
S_ASSET AIA_INTEG_ID Y Varchar 150
S_ASSET BILL_PROFILE_ID Y Varchar 15
S_CAMP_CON CTRL_GRP_FLG N Char 1 N
S_CAMP_CON SEGMENT_CODE_1 Y Varchar 30
S_CAMP_CON SEGMENT_CODE_2 Y Varchar 30

S_CASE APPLICANT_ID Y Varchar 15
S_CASE AUDIT_EMP_ID Y Varchar 15
S_CASE CHGOFCCM_REQ_FLG N Char 1 N
S_CASE MSTR_CASE_ID Y Varchar 15
S_CASE PS_APPL_ID Y Varchar 15
S_CIF_EXT_SYST MIDDLEWARE_FLG N Char 1 N

S_CIF_EXT_SYST MSG_TYPE_CD Y Varchar 30
S_CIF_SYS_DTL PROXY_BS Y Varchar 100
S_CIF_SYS_DTL PROXY_MTD_NAME Y Varchar 150
S_COMM_DTL BANNER_AD_STRNG Y Varchar 100
S_COMM_DTL CLIENT_IP_ADDR Y Varchar 100
S_COMM_DTL CURRENT_URL Y Varchar 200

S_COMM_DTL KEYWORD_STRNG Y Varchar 100
S_COMM_DTL MKT_SRVY_LANG_ID Y Varchar 5
S_COMM_DTL REFERRER_URL Y Varchar 200

Data LOV
S_COMM_DTL REFERRER_USERNAME Y Varchar 100
S_COMM_IMPT ACCNT_POSTN_ID Y Varchar 15
S_COMM_IMPT ACCNT_REVN_AMT Y Number 22 22 7
S_COMMUNICATION COST_AMT Y Number 22 22 7
S_COMMUNICATION COST_CURCY_CD Y Varchar 20
S_COMMUNICATION LEAD_ID Y Varchar 15
S_COMMUNICATION MKT_SRVY_ID Y Varchar 15
S_COMMUNICATION PGROUP_PUBLIC_FLG Y Char 1 N

S_COMMUNICATION RESP_VALUE_CD Y Varchar 30
S_CON_ADDR ADDRESSEE Y Varchar 100
S_CONTACT AIA_INTEG_ID Y Varchar 150
S_CONTACT APPROVAL_STATUS_CD Y Varchar 30 APPROVAL_STATUS Y
S_CONTACT EMAIL_STATUS_CD Y Varchar 30 EMAIL_STATUS
S_CONTACT LST_EMLADR_UPD_TS Y UTC 7

DateTime
S_CONTACT MSTR_CASE_ID Y Varchar 15
S_CONTACT NUM_HARD_BNCE Y Number 22 10 0
S_CONTACT NUM_SOFT_BNCE Y Number 22 10 0
S_CONTACT_LOYX HOME_AIRPORT Y Varchar 30
S_CONTACT_LSX CERT_EXPIRE_DT Y UTC 7

DateTime
S_CONTACT_LSX LAST_SMPL_AUDIT_DT Y UTC 7

DateTime
S_CONTACT_LSX MASTER_SIGN_ID Y Varchar 15

285
2 86
Data LOV
S_CT_APLT_RLST LOCK_FLG Y Char 1 N
S_CT_RULE_SET LOCK_FLG Y Char 1 N
S_CT_RULE_SET RULE_SET_TYPE_CD Y Varchar 30
S_DCP_CALL_LST ALLOCATED_CNT Y Number 22 10 0
S_DCP_CALL_LST ALLOCATED_PCT Y Number 22 22 7
S_DCP_CALL_LST CTRL_GRP_PCT Y Number 22 22 7
S_DCP_CALL_LST PCT_ALLOC_FLG N Char 1 Y
S_DCP_URL LAND_SITE_ID Y Varchar 15

S_DCP_URL RELAY_EMBED_ID_FLG N Char 1 N
S_DMND_CRTN_PRG ACT_APPT_DURTN_MIN Y Number 22 22 7
S_DMND_CRTN_PRG ACT_CAL_TYPE_CD Y Varchar 30
S_DMND_CRTN_PRG ACT_COMMENTS Y Varchar 100
S_DMND_CRTN_PRG ACT_COMMENTS_LONG Y Varchar 1500
S_DMND_CRTN_PRG ACT_DONE_FLG N Char 1 N

S_DMND_CRTN_PRG ACT_OWNER_PER_ID Y Varchar 15
S_DMND_CRTN_PRG ACT_PLAN_END_DT Y UTC 7

DateTime
S_DMND_CRTN_PRG ACT_PLAN_START_DT Y UTC 7

DateTime
S_DMND_CRTN_PRG ACT_PRIORITY_CD Y Varchar 30
S_DMND_CRTN_PRG ACT_PRIV_FLG N Char 1 N

S_DMND_CRTN_PRG ACT_STAT_CD Y Varchar 30
S_DMND_CRTN_PRG ACT_TODO_CD Y Varchar 30

Data LOV
S_DMND_CRTN_PRG ACT_TODO_DUE_DT Y UTC 7

DateTime
S_DMND_CRTN_PRG CREATED_TS Y UTC 7

DateTime
S_DMND_CRTN_PRG DEPLOY_TS Y UTC 7

DateTime
S_DMND_CRTN_PRG KIOSK_MODE_FLG N Char 1 N
S_DMND_CRTN_PRG LANDGSITE_STAT_CD Y Varchar 30 LANDING_SITE_

STATUS_TYPE
S_DMND_CRTN_PRG MKT_SRVY_ID Y Varchar 15
S_DMND_CRTN_PRG NEXT_BTTN_TEXT Y Varchar 50
S_DMND_CRTN_PRG ORIG_CREATOR_ID Y Varchar 15
S_DMND_CRTN_PRG OWNER_POSTN_ID Y Varchar 15
S_DMND_CRTN_PRG PUBLISH_TS Y UTC 7

DateTime
S_DMND_CRTN_PRG REDIRECT_URL Y Varchar 250
S_DMND_CRTN_PRG REDIRECT_URL_FLG N Char 1 N
S_DMND_CRTN_PRG RESUME_FLG Y Char 1
S_DMND_CRTN_PRG STRT_ON_LNDPG_FLG N Char 1 N
S_DMND_CRTN_PRG STRT_SVY_BTTN_TEXT Y Varchar 50
S_DMND_CRTN_PRG SUBMIT_BTTN_TEXT Y Varchar 50
S_DMND_CRTN_PRG TEST_URL_TEXT Y Varchar 250
S_DMND_CRTN_PRG TINY_URL_TEXT Y Varchar 250

S_DMND_CRTN_PRG TITLE_NAME Y Varchar 100
S_DMND_CRTN_PRG TMPL_STATUS_CD Y Varchar 30

287
2 88
Data LOV
S_DOC_QUOTE ATTR_ID Y Varchar 15
S_DOC_QUOTE BILL_PROFILE_ID Y Varchar 15
S_DOC_QUOTE_SPA APPR_SEQ_NUM Y Number 22 10 0
S_DOC_QUOTE_SPA SPA_SUB_TYPE_CD Y Varchar 30
S_EMP_PER LS_APPROVER_ID Y Varchar 15
S_EMP_PER PCD_TBAR_ALIGN_CD Y Varchar 30
S_EMP_PRDINT ALLOC_TYPE_CD N Varchar 30 Prod-

uct Al
loca-
tion
S_EMP_PRDINT END_DT Y UTC 7

DateTime
S_EMP_PRDINT MAX_ALLOC_QTY Y Number 22 22 7
S_EMP_PRDINT MAX_CALL_QTY Y Number 22 22 7
S_EMP_PRDINT MAX_ORDER_QTY Y Number 22 22 7

S_EMP_PRDINT MIN_ORDER_QTY Y Number 22 22 7
S_EMP_PRDINT START_DT Y UTC 7

DateTime
S_EMP_PRDINT STOP_SAMPLE_FLG N Char 1 N
S_EVT_ACT BNFT_PLAN_ITM_ID Y Varchar 15
S_EVT_ACT LEAD_ID Y Varchar 15
S_EVT_ACT SKIN_CD Y Varchar 30

S_EVT_ACT_FNX PGROUP_PUBLIC_FLG Y Char 1 N
S_EVT_ACT_LSX CALL_VALDN_RESULT Y Varchar 50

Data LOV
S_EVT_ACT_LSX NEXT_CALL_DT Y UTC 7

DateTime
S_EVT_ACT_LSX SUPERVISOR_ID Y Varchar 15
S_EVT_COMM AREA_CD Y Varchar 30
S_EVT_COMM CHAT_TRANSCRIPT Y Undefine 1310

d 72
S_EVT_COMM EMAIL_ADDR_PRVD Y Varchar 100
S_EVT_COMM FST_NAME_PRVD Y Varchar 50

S_EVT_COMM LAST_NAME_PRVD Y Varchar 50
S_EVT_COMM NEW_EMAIL_PRVD_FLG N Char 1 N
S_EVT_COMM NEW_PH_PRVD_FLG N Char 1 N
S_EVT_COMM PROBLEM_DESC_TEXT Y Varchar 250
S_EVT_COMM SUB_AREA_CD Y Varchar 30
S_EVT_COMM WRAPUP_END_TS Y UTC 7

DateTime
S_EVT_COMM WRAPUP_FEEDBACK_C Y Varchar 30 WRAPUP_ Y

D FEEDBACK
S_EVT_COMM WRAPUP_OUTCOME_CD Y Varchar 30 WRAPUP_ Y

OUTCOME
S_EVT_COMM WRAPUP_REASON_CD Y Varchar 30 WRAPUP_REASON Y
S_EVT_COMM WRAPUP_START_TS Y UTC 7

DateTime
S_FCST SELF_ADJ_AMT Y Number 22 22 7

S_FCST TOT_ADJ_BY_SUB_AMT Y Number 22 22 7
S_FCSTSER_POSTN SUBMIT_TO_PSTN_ID Y Varchar 15

289
2 90
Data LOV
S_FORM_MAP CATEGORY_CD Y Varchar 30 PUB_FORM_ Y

CATEGORY
S_FORM_MAP DOC_NUMBER Y Varchar 30
S_INCIDENT SIGN_EVT_ID Y Varchar 15
S_INCIDENT_CON ROW_STATUS N Varchar 10 Y
S_INV_PROF AUTO_TOP_UP_FLG Y Char 1 N
S_INV_PROF BILL_PRFL_COMMENTS Y Varchar 255
S_INV_PROF CC_SEC_CODE Y Varchar 10

S_INV_PROF CCNUM_ENCRPKEY_REF Y Varchar 30
S_INV_PROF CCV_NUMBER Y Varchar 20
S_INV_PROF CCVNUM_ENCRPKY_REF Y Varchar 30
S_INV_PROF CRDT_CRD_EXP_MO_C Y Varchar 30 TELCO_MONTH_ Y

D TYPE
S_INV_PROF CRDT_CRD_EXP_YR_CD Y Varchar 30 YEAR
S_INV_PROF PAYMENT_TYPE_CD Y Varchar 30 BILL_PAYMENT_ Y

TYPE
S_INV_PROF ROUTING_NUM Y Varchar 50
S_INV_PROF ROUTING_NUMBER Y Varchar 30
S_INV_PROF SMS_NOTIFY_FLG Y Char 1 N
S_INV_PROF THRESHOLD_UOM_CD Y Varchar 30 BILL_PREPAID_ Y

UOM
S_INV_PROF THRESHOLD_VALUE Y Number 22 22 7

S_INV_PROF TOP_UP_UOM_CD Y Varchar 30 BILL_PREPAID_ Y
UOM
S_INV_PROF TOP_UP_VALUE Y Number 22 22 7

Data LOV
S_INV_PROF TOPUP_FREQ_CD Y Varchar 30 BILL_ FREQUENCY Y
S_INVC_ADJ_ITEM ADJ_EFFECTIVE_DT Y Date 7
S_INVC_ADJ_ITEM ADJ_PERCENTAGE Y Number 3 22 7
S_INVC_ADJ_ITEM ADJ_TYPE_CD Y Varchar 30
S_INVC_ADJ_ITEM ADJUSTMENT_VALUE Y Number 22 22 7
S_INVC_ADJ_ITEM APPR_PERCENTAGE Y Number 22 22 7
S_INVC_ADJ_ITEM APPR_VALUE Y Number 22 22 7
S_INVC_ADJ_ITEM APPROV_ADJ_PERCENT Y Number 3 22 7

S_INVC_ADJ_ITEM INV_ITEM_DETAIL_ID Y Varchar 15
S_INVC_ADJ_ITEM NOTES Y Varchar 30
S_INVC_ADJ_ITEM ORIGINAL_VALUE Y Number 22 22 7
S_INVC_ADJ_ITEM REASON_CD Y Varchar 30
S_INVC_ADJ_ITEM REQ_PERCENTAGE Y Number 22 22 7
S_INVC_ADJ_ITEM REQ_VALUE Y Number 22 22 7
S_INVC_ADJ_ITEM RESOURCE_TO_ADJ_CD Y Varchar 30
S_INVC_ADJ_ITEM TAX_TREATMENT_CD Y Varchar 30
S_INVC_ADJ_ITEM TAX_VALUE Y Number 22 22 7
S_INVC_ITM_DTL DISCOUNT_AMT Y Number 22 10 0
S_INVC_ITM_DTL IS_CURRENCY_FLG Y Char 1 N
S_INVC_ITM_DTL ITEM_DT Y Date 7
S_INVC_ITM_DTL PH_EXT_NUM Y Varchar 100

S_INVC_ITM_DTL TOTAL_USG Y Number 22 10 0
S_INVOICE BILL_PROF_ID Y Varchar 15

291
2 92
Data LOV
S_INVOICE_ADJ ADJ_EFF_DT Y Date 7
S_INVOICE_ADJ ADJ_LEVEL_CD Y Varchar 30
S_INVOICE_ADJ APPR_PERCENTAGE Y Number 22 22 7
S_INVOICE_ADJ BILL_PROF_ID Y Varchar 15
S_INVOICE_ADJ REQ_PERCENTAGE Y Number 22 22 7
S_INVOICE_ADJ TAX_TREATMENT_CD Y Varchar 30
S_INVOICE_ADJ TAX_VALUE Y Number 22 22 7
S_LEAD_IMPT ACCNT_POSTN_ID Y Varchar 15

S_LEAD_IMPT ACCNT_REVN_AMT Y Number 22 22 7
S_LEADRESP_IMPT QUESTION_NAME Y Varchar 100
S_LOY_ACRL_ITM PRTNR_PT_DEBT_QTY Y Number 22 10 0
S_LOY_ACRL_ITM PT_SUB_TYPE_ID Y Varchar 15
S_LOY_ACRL_ITM RET_EFF_DT Y UTC 7

DateTime
S_LOY_ACTCRTR BUS_SERVICE_NAME Y Varchar 75
S_LOY_ACTCRTR METHOD_NAME Y Varchar 75
S_LOY_ACTCRTR PROD_ID Y Varchar 15
S_LOY_ACTCRTR PT_SUB_TYPE_ID Y Varchar 15
S_LOY_ACTCRTR REL_TYPE_CD Y Varchar 30 PARTY_RELATIONS Y

HIP_TYPE
S_LOY_ACTCRTR VOUCHER_QTY Y Number 22 10 0

S_LOY_ATTRDEFN ACCNT_ACT_CD Y Varchar 30 LOY_PT_EXP_ Y
ACC_ACTVITY_CD
S_LOY_ATTRDEFN EXP_PD_UOM_CD Y Varchar 30 LOY_PT_EXP_ UOM Y

Data LOV
S_LOY_ATTRDEFN EXP_PERIOD_LEN Y Number 22 22 7
S_LOY_ATTRDEFN EXPIRY_ALIGN_CD Y Varchar 30 LOY_PT_EXP_ Y

SNAP_TO
S_LOY_ATTRDEFN EXPIRY_BASIS_CD Y Varchar 30 LOY_PT_EXPIRY_ Y

BASIS_CD
S_LOY_ATTRDEFN EXPIRY_DAY_CD Y Varchar 30 FINS_CF_ Y

AGREEMNT_
PAYMT_DUE_DAY
S_LOY_ATTRDEFN EXPIRY_MONTH_CD Y Varchar 30 LOY_MONTH_ TYPE Y

S_LOY_ATTRDEFN METHOD_NAME Y Varchar 75
S_LOY_ATTRDEFN MIN_REACTIVATN_QTY Y Number 22 10 0
S_LOY_ATTRDEFN QUAL_POINT_FLG N Char 1 N
S_LOY_ATTRDEFN REACTIVATE_FLG N Char 1 N
S_LOY_ATTRDEFN RET_EFF_FLG N Char 1 N
S_LOY_ATTRDEFN RPT_EXP_PD_UOM_CD Y Varchar 30
S_LOY_ATTRDEFN RPT_EXP_PERIOD_LEN Y Number 22 10 0
S_LOY_BUCKET ORDER_NUM Y Number 22 10 0
S_LOY_MEM_TIER APPLD_PROMO_RL_ID Y Varchar 15
S_LOY_MEM_TIER APPLIED_PROMO_ID Y Varchar 15
S_LOY_MEM_TIER BULK_REF_ID Y Varchar 15
S_LOY_MEM_TIER FUTR_TIER_ID Y Varchar 15
S_LOY_MEM_TIER FUTR_TIER_STAMP_DT Y UTC 7

DateTime

S_LOY_MEM_TIER NEXT_ASSESS_DT Y UTC 7
DateTime
293
2 94
Data LOV
S_LOY_MEM_TIER POINT_TYPE_E_VAL Y Number 22 22 7
S_LOY_MEM_TIER POINT_TYPE_F_VAL Y Number 22 22 7
S_LOY_MEM_TIER POINT_TYPE_G_VAL Y Number 22 22 7
S_LOY_MEM_TIER POINT_TYPE_H_VAL Y Number 22 22 7
S_LOY_MEM_TIER QUAL_END_DT Y UTC 7

DateTime
S_LOY_MEM_VCHR BASIS_CD Y Varchar 30 Tier LOY_VCHR_BASIS_ Y

Rewa CD
r
S_LOY_MEM_VCHR CONSUMED_TXN_ID Y Varchar 15
S_LOY_MEM_VCHR MERGE_MEM_ID Y Varchar 15
S_LOY_MEM_VCHR ORIG_VCHR_ID Y Varchar 15
S_LOY_MEM_VCHR TXN_ITEM_ID Y Varchar 15
S_LOY_MEMBER ACCRUAL_TYPE_CD Y Varchar 30 LOY_CORP_ACCR_ Y

TYPE
S_LOY_MEMBER CORP_MEM_NUM Y Varchar 15
S_LOY_MEMBER HOME_AIRPORT Y Varchar 30
S_LOY_MEMBER LAST_ACCR_TXN_DT Y UTC 7

DateTime
S_LOY_MEMBER LAST_RDM_TXN_DT Y UTC 7

DateTime
S_LOY_MEMBER LFTM_PT_TYPE_E_VAL Y Number 22 22 7

S_LOY_MEMBER LFTM_PT_TYPE_F_VAL Y Number 22 22 7
S_LOY_MEMBER LFTM_PT_TYPE_G_VAL Y Number 22 22 7
S_LOY_MEMBER LFTM_PT_TYPE_H_VAL Y Number 22 22 7

Data LOV
S_LOY_MEMBER MEMSHIP_SCHEME_ID Y Varchar 15
S_LOY_MEMBER POINT_TYPE_E_VAL Y Number 22 22 7
S_LOY_MEMBER POINT_TYPE_F_VAL Y Number 22 22 7
S_LOY_MEMBER POINT_TYPE_G_VAL Y Number 22 22 7
S_LOY_MEMBER POINT_TYPE_H_VAL Y Number 22 22 7
S_LOY_MEMBER STMT_TYPE_CD Y Varchar 30 LOY_STMT_TYPE_

CD
S_LOY_MEMBER SURV_MEM_ID Y Varchar 15

S_LOY_PROD_PT DISTANCE_UOM_CD Y Varchar 30 LOY_UOM_CD Y
S_LOY_PROD_PT MAX_DISTANCE Y Number 22 22 7
S_LOY_PROD_PT MIN_DISTANCE Y Number 22 22 7
S_LOY_PROD_PT PR_AMT_CRCY_EXC_DT Y Date 7
S_LOY_PROD_PT PRICE_AMT Y Number 22 22 7
S_LOY_PROD_PT PRICE_AMT_CURCY_CD Y Varchar 20
S_LOY_PROD_PT PROD_PT_UID N Varchar 15
S_LOY_PROD_PT PRTNR_PRI_TYPE_CD Y Varchar 30 LOY_PRTNR_ Y

PRICE_TYPE_CD
S_LOY_PROD_PT PRTNR_PRICE_AMT Y Number 22 22 7
S_LOY_PROD_PT PYMT_TYPE_CD Y Varchar 30 Point LOY_PAYMENT_ CD Y

s
S_LOY_PROG_ORG ACRL_VALID_PD_LEN Y Number 22 22 7
S_LOY_PROG_ORG ACRL_VALID_UOM_CD Y Varchar 30 LOY_PT_EXP_ UOM Y

S_LOY_PROG_ORG ALLW_NEGATIVE_FLG N Char 1 N
S_LOY_PROG_ORG BILLING_TYPE_CD Y Varchar 30

295
2 96
Data LOV
S_LOY_PROG_ORG CREDIT_LIMIT Y Number 22 10 0
S_LOY_PROG_ORG MIN_ORDER_QTY Y Number 22 10 0
S_LOY_PROG_ORG PRECALC_ACRL_FLG N Char 1 N
S_LOY_PROG_ORG PRICING_RULE_ID Y Varchar 15
S_LOY_PROG_ORG REORDER_LIMIT Y Number 22 10 0
S_LOY_PROG_ORG RET_BEFORE_DAYS Y Number 22 10 0
S_LOY_PROG_ORG SKIP_ACRL_VAL_FLG N Char 1 N
S_LOY_PROG_ORG VALDT_DISPUTE_USR Y Varchar 30

S_LOY_PROG_ORG VALID_DISPUTE_FLG N Char 1 N
S_LOY_PROGRAM PNT_TO_PAY_FLG N Char 1 N
S_LOY_PROGRAM POINT_EXP_LEVEL_CD Y Varchar 30 Tier LOY_PT_EXP_LVL_ Y

Level CD
S_LOY_PROGRAM PUR_STRT_DAY_CD Y Varchar 30 1 FINS_CF_ Y

AGREEMNT_
PAYMT_DUE_ DAY
S_LOY_PROGRAM PUR_STRT_MTH_CD Y Varchar 30 Janu MONTH_NAME Y

ary
S_LOY_PROGRAM REVRECG_PERIOD_DUR Y Number 22 22 7
S_LOY_PROGRAM REVRECG_PRD_TYP_CD Y Varchar 30 LOY_REVRECG_ Y

PERIOD
S_LOY_PROGRAM TXFR_STRT_DAY_CD Y Varchar 30 1 FINS_CF_ Y

AGREEMNT_
PAYMT_DUE_ DAY

S_LOY_PROGRAM TXFR_STRT_MTH_CD Y Varchar 30 Janu MONTH_NAME Y
ary
S_LOY_PROMO BASE_PROMO_FLG N Char 1 N

Data LOV
S_LOY_PROMO EXPORT_FLG N Char 1 N
S_LOY_PROMO ORDER_FLG N Char 1 N
S_LOY_PROMO PKG_ACRL_FLG N Char 1 N
S_LOY_PROMOMEM ELIG_FLG N Char 1 N
S_LOY_PTR_ATMP CITY_CD Y Varchar 30
S_LOY_RDM_ITM PR_DEBT_PT Y Number 22 10 0
S_LOY_STMT MEM_TIER_ID Y Varchar 15
S_LOY_STMT PARTNER_ID Y Varchar 15

S_LOY_STMT REP_FILE_NAME Y Varchar 500
S_LOY_STMT REP_STATUS_CD Y Varchar 30 LOY_STMT_CRTN_

STATUS_CD
S_LOY_STMT STMT_TYPE_CD Y Varchar 30 LOY_STMT_TYPE_

CD
S_LOY_STMT TRX_ID Y Varchar 15
S_LOY_STMT VOUCHER_ID Y Varchar 15
S_LOY_STMT_CRTN PROG_ID Y Varchar 15
S_LOY_STMT_CRTN STMT_TYPE_CD Y Varchar 30 LOY_STMT_TYPE_

CD
S_LOY_STMT_ITM BILL_AMOUNT Y Number 22 10 0
S_LOY_STMT_ITM CURCY_CD Y Varchar 20
S_LOY_STMT_ITM NON_BILL_AMOUNT Y Number 22 10 0
S_LOY_STMT_ITM PARTNER_PRICE Y Number 22 10 0

S_LOY_STMT_ITM PT_SUB_TYPE_ID Y Varchar 15
S_LOY_STMT_LOG PARTNER_ID Y Varchar 15

297
2 98
Data LOV
S_LOY_STMT_TXN PARTNER_PRICE Y Number 22 10 0
S_LOY_TIER DWNGRD_APPRV_FLG N Char 1 N
S_LOY_TIER_CLS APPLY_FLG N Char 1 N
S_LOY_TIER_CLS APPROVER_ID Y Varchar 15
S_LOY_TIER_CLS ASSESS_DAY_CD Y Varchar 30 FINS_CF_ Y

AGREEMNT_
PAYMT_DUE_ DAY
S_LOY_TIER_CLS ASSESS_MONTH_CD Y Varchar 30 MONTH_NAME Y

S_LOY_TIER_CLS ASSESS_RECUR_CD Y Varchar 30 LOY_TA_RECUR_ Y
TYPE
S_LOY_TIER_CLS END_TIER_PD_DAY_CD Y Varchar 30 FINS_CF_ Y

AGREEMNT_
PAYMT_DUE_ DAY
S_LOY_TIER_CLS END_TIER_PD_MTH_CD Y Varchar 30 MONTH_NAME Y
S_LOY_TIER_CLS MIN_TIER_LEN Y Number 22 22 7
S_LOY_TIER_CLS MIN_TIERLEN_UOM_CD Y Varchar 30 LOY_LEAD_TIME_ Y

CD
S_LOY_TIER_CLS QUAL_PD_UOM_CD Y Varchar 30 LOY_LEAD_TIME_ Y

CD
S_LOY_TIER_CLS QUAL_PERIOD_LEN Y Number 22 22 7
S_LOY_TIER_CLS REQUAL_PD_UOM_CD Y Varchar 30 REQUAL_PD_UOM_ Y

CD
S_LOY_TIER_CLS REQUAL_PERIOD_LEN Y Number 22 22 7

S_LOY_TIER_CLS ST_QUAL_PD_DAY_CD Y Varchar 30 FINS_CF_
AGREEMNT_PAYMT
_DUE_ DAY
Data LOV
S_LOY_TIER_CLS ST_QUAL_PD_MTH_CD Y Varchar 30 MONTH_NAME
S_LOY_TIER_CLS ST_TIER_PD_DAY_CD Y Varchar 30 FINS_CF_ Y

AGREEMNT_
PAYMT_DUE_ DAY
S_LOY_TIER_CLS ST_TIER_PD_MTH_CD Y Varchar 30 MONTH_NAME Y
S_LOY_TXN ACCR_RULE_ID Y Varchar 15
S_LOY_TXN ACTIVITY_DAY Y Number 22 10 0
S_LOY_TXN ACTIVITY_HOUR Y Number 22 10 0

S_LOY_TXN AMT_VAL Y Number 22 22 7
S_LOY_TXN BID_FLG N Char 1 N
S_LOY_TXN BOOKING_DT Y UTC 7

DateTime
S_LOY_TXN BULK_REF_ID Y Varchar 15
S_LOY_TXN CANC_REASON_CD Y Varchar 30 LOY_CANC_ Y

REASON_CD
S_LOY_TXN CHILD_TXN_ID Y Varchar 15
S_LOY_TXN CORP_REF_NUM Y Varchar 15
S_LOY_TXN DEST_CITY_CD Y Varchar 30
S_LOY_TXN ENROL_PROMO_ID Y Varchar 15
S_LOY_TXN INCENTIV_CHOICE Y Varchar 30
S_LOY_TXN LOCATION_CD Y Varchar 30
S_LOY_TXN MKTG_FLT_NUM Y Varchar 30

S_LOY_TXN OPER_CARRIER_ID Y Varchar 15
S_LOY_TXN OPER_FLT_NUM Y Varchar 30

299
3 00
Data LOV
S_LOY_TXN ORDER_NUM Y Number 22 10 0
S_LOY_TXN ORDER_QTY Y Number 22 22 7
S_LOY_TXN ORIG_ACRL_REF_ID Y Varchar 15
S_LOY_TXN ORIG_AMOUNT Y Number 22 22 7
S_LOY_TXN ORIG_ORD_ITM_ID Y Varchar 15
S_LOY_TXN ORIG_POINTS Y Number 22 10 0
S_LOY_TXN ORIGIN_CITY_CD Y Varchar 30
S_LOY_TXN OVR_DUP_CHECK_FLG N Char 1 N

S_LOY_TXN OVR_PRI_FLAG N Char 1 N
S_LOY_TXN PACKAGE_CD Y Varchar 30 LOY_PACKAGE
S_LOY_TXN PERIOD_DUR_CD Y Varchar 30 LOY_MEM_PER_ Y

TYPE
S_LOY_TXN PERIOD_TYPE_CD Y Varchar 30 LOY_MEM_PER_ Y

TYPE
S_LOY_TXN PYMT_TYPE_CD Y Varchar 30 LOY_PAYMENT_ CD

S_LOY_TXN RDM_ITM_ID Y Varchar 15
S_LOY_TXN RDM_QTY Y Number 22 22 7
S_LOY_TXN RDM_QTY_UOM_CD Y Varchar 30 LOY_UOM_CD Y
S_LOY_TXN REASON_CD Y Varchar 30
S_LOY_TXN REFUND_BASIS_CD Y Varchar 30 LOY_REFUND_ Y

BASIS

S_LOY_TXN REFUND_PCT Y Number 22 22 7
S_LOY_TXN RFND_OVRD_CMNTS Y Varchar 250

Data LOV
S_LOY_TXN RFND_OVRD_RSN_CD Y Varchar 30 LOY_OVR_ Y

REASON_CD
S_LOY_TXN SOURCE_CD Y Varchar 30 LOY_TXN_

SOURCE_CD
S_LOY_TXN TAX_AMT Y Number 22 22 7
S_LOY_TXN TO_MEM_NUM Y Varchar 30
S_LOY_TXN TOTAL_LINES Y Number 22 10 0
S_LOY_TXN TRVL_DISTANCE Y Number 22 22 7

S_LOY_TXN TXN_SOURCE_CD Y Varchar 30 LOY_TXN_
SOURCE_CD
S_LOY_TXN VAL_STATUS_CD Y Varchar 30 LOY_TXN_VAL_

STATUS
S_MKTG_SRVR_TSK IMPRT_TSK_ID Y Varchar 15
S_NOTE_OPTY PGROUP_PUBLIC_FLG Y Char 1 N
S_OPTY PGROUP_PUBLIC_FLG Y Char 1 N
S_OPTY_DSGN_REG CUST_ACCNT_ID Y Varchar 15
S_OPTY_DSGN_REG DSGN_COMPLETE_DT Y UTC 7

DateTime
S_OPTY_DSGN_REG END_EQUIP_CD Y Varchar 30 HTIM_END_ Y

EQUIP_CD
S_OPTY_DSGN_REG ESTIMATE_UNITS Y Number 22 10 0
S_OPTY_DSGN_REG PROD_PROB_CD Y Varchar 30 PROJ_PRIORITY_ Y

CODE

S_OPTY_DSGN_REG PROD_PROB_REASON Y Varchar 50
S_OPTY_DSGN_REG PROG_LIFE_TIME Y Number 22 10 0

301
3 02
Data LOV
S_OPTY_DSGN_REG PROG_TYPE_CD Y Varchar 30 HTIM_PROG_ Y

TYPE_CD
S_OPTY_DSGN_REG REG_STAT_CD Y Varchar 30 HTIM_STATUS_ CD
S_OPTY_DSGN_REG TIME_UNIT_CD Y Varchar 30 Mont UNIT_VALUES Y

hs
S_OPTY_DSGN_REG USAGE Y Number 22 10 0
S_ORD_ITM_LOYX BID_FLAG N Char 1 N
S_ORD_ITM_LOYX BOOKING_DT Y UTC 7

DateTime
S_ORD_ITM_LOYX DISTANCE Y Number 22 22 7
S_ORD_ITM_LOYX END_DT Y UTC 7

DateTime
S_ORD_ITM_LOYX OVERRIDE_PRI_FLG N Char 1 N
S_ORD_ITM_LOYX OVERRIDE_REASON Y Varchar 250
S_ORD_ITM_LOYX OVERRIDE_REASON_CD Y Varchar 30 LOY_OVR_ Y

REASON_CD
S_ORD_ITM_LOYX POINTS_LOAN Y Number 22 22 7
S_ORD_ITM_LOYX POINTS_USED Y Number 22 22 7
S_ORD_ITM_LOYX START_DT Y UTC 7

DateTime
S_ORD_ITM_LOYX TRVL_DISTANCE Y Number 22 22 7
S_ORD_ITM_LOYX TXN_AMOUNT Y Number 22 22 7

S_ORD_ITM_LOYX TXN_POINTS Y Number 22 22 7
S_ORD_ITM_LOYX VOUCHER_ID Y Varchar 15
S_ORD_ITM_LOYX VOUCHER_QTY Y Number 10 10 0

Data LOV
S_ORDER BILL_PROFILE_ID Y Varchar 15
S_ORDER_ITEM AGENCY_NAME Y Varchar 100
S_ORDER_ITEM BILL_PROFILE_ID Y Varchar 15
S_ORDER_ITEM END_PHONE_NUM Y Varchar 20
S_ORDER_ITEM ORIG_ACCNT_NUM Y Varchar 50
S_ORDER_ITEM ORIG_PIN Y Varchar 50
S_ORDER_ITEM PORT_NUM Y Varchar 20
S_ORDER_ITEM RLTD_SRVC_PROD_ID Y Varchar 15

S_ORDER_ITEM RLTDSRVCAST_INT_ID Y Varchar 15
S_ORDER_ITEM RQST_PORT_DATE Y UTC 7

DateTime
S_ORDER_ITEM START_PHONE_NUM Y Varchar 20
S_ORDER_ITEM SVC_PROVIDER Y Varchar 100
S_ORDER_ITEM SVC_ZIP_CODE Y Varchar 30
S_ORDER_ITEM_OM PREV_BILL_PROF_ID Y Varchar 15
S_ORDER_ITEM_OM PREV_NET_PRI Y Number 25 10 0
S_ORDER_ITEM_OM SUB_ACTION_CD Y Varchar 30
S_ORG_EXT AIA_INTEG_ID Y Varchar 150
S_ORG_EXT APPROVAL_STATUS_CD Y Varchar 30 APPROVAL_ Y

STATUS
S_ORG_EXT PR_BILL_PRFL_ID Y Varchar 15
S_ORG_GROUP AIA_INTEG_ID Y Varchar 150

S_ORG_GROUP MNTHLY_HS_COST_AM Y Number 22 10 0
T
303
3 04
Data LOV
S_ORG_GROUP PR_DOMESTC_LANG_ID Y Varchar 5
S_PARTY ADMIN_ADJ_FLG N Char 1 N
S_PGROUP CONFIDENTIAL_FLG Y Char 1 N
S_PGROUP PR_POSTN_ID Y Varchar 15
S_PGROUP SUPPRESS_FLG Y Char 1 N
S_POSTN PGROUP_ID Y Varchar 15
S_POSTN_CON NEXT_CALL_DT Y UTC 7

DateTime
S_POSTN_CON NEXT_CALL_OBJECTIV Y Varchar 1500
S_PRD_CMPLNT_LS COMB_PROD_FLG Y Char 1 N
S_PRD_CMPLNT_LS PRD_SUB_TRACK_NUM Y Varchar 30
S_PRD_CMPLNT_LS PRE_MKT_APPL_NUM Y Varchar 30
S_PRD_CMPLNT_LS SEVEN_DAY_RPT_FLG Y Char 1 N
S_PRD_CMPLNT_LS THIRTY_DAY_RPT_FLG Y Char 1 N

S_PROD_INT BILLING_TYPE_CD Y Varchar 30
S_PROD_INT DPNDNCY_VLDTN_FLG Y Char 1 N
S_PROD_INT LOY_EXPR_BASIS_CD Y Varchar 30 LOY_EXPR_ Y

BASIS_CD
S_PROD_INT LOY_NUM_YEAR Y Number 22 22 7
S_PROD_INT LOY_PERIOD_DUR Y Number 22 22 7
S_PROD_INT LOY_PERIOD_TYPE_CD Y Varchar 30 LOY_MEM_PER_ Y

TYPE
S_PROD_INT LOY_SEQ_TYPE_CD Y Varchar 30 LOY_SEQ_TYPE_ Y

CD
Data LOV
S_PROD_INT LOY_SERIES_PREFIX Y Varchar 15
S_PROD_INT LOY_VCH_EXP_DAY_CD Y Varchar 30 FINS_CF_ Y

AGREEMNT_
PAYMT_DUE_DAY
S_PROD_INT LOY_VCH_EXP_MTH_CD Y Varchar 30 MONTH_NAME Y
S_PROD_INT LOY_VCHREXP_PRDDUR Y Number 22 22 7
S_PROD_INT LOY_VEXP_PERTYP_CD Y Varchar 30 LOY_VCHR_ Y

EXPIRY_PERIOD_
TYPE
S_PROD_INT PAYMNT_TYPE_CD Y Varchar 30 BILL_PAYMENT_ Y

TYPE
S_PROD_INT PERMITTED_TYPE Y Varchar 250
S_PROD_INT REQD_SERVICE_FLG Y Char 1 N
S_PROD_INT_LSX COM_DEV_NAME Y Varchar 50
S_PROD_INT_LSX CUTOFF_THRESHOLD Y Number 22 22 7
S_PROD_INT_LSX MAX_PRODUCT_QTY Y Number 22 22 7
S_PROD_REL SVC_CHRG_CD Y Varchar 30
S_PROM_PMTRX EFF_END_TS Y UTC 7

DateTime
S_PROM_PMTRX EFF_START_TS Y UTC 7

DateTime
S_PRSP_CONTACT EMAIL_STATUS_CD Y Varchar 30 EMAIL_STATUS Y
S_PRSP_CONTACT LST_EMAILADR_UPD Y UTC 7

DateTime

S_PRSP_CONTACT NUM_HARD_BNCE Y Number 22 10 0
S_PRSP_CONTACT NUM_SOFT_BNCE Y Number 22 10 0

305
3 06
Data LOV
S_PS_CONTACT ATTACH_CNTR Y Number 22 10 0
S_PS_CONTACT STUDENT_FLG Y Char 1 N
S_PS_CONTACT VETERAN_FLG Y Char 1 N
S_QUO_ITM_LOYX BID_FLAG N Char 1 N
S_QUO_ITM_LOYX BOOKING_DT Y UTC 7

DateTime
S_QUO_ITM_LOYX DISTANCE Y Number 22 22 7
S_QUO_ITM_LOYX END_DT Y UTC 7

DateTime
S_QUO_ITM_LOYX OVERRIDE_PRI_FLG N Char 1 N
S_QUO_ITM_LOYX OVERRIDE_REASON Y Varchar 250
S_QUO_ITM_LOYX OVERRIDE_REASON_CD Y Varchar 30 LOY_OVR_ Y

REASON_CD
S_QUO_ITM_LOYX POINTS_LOAN Y Number 22 22 7
S_QUO_ITM_LOYX POINTS_USED Y Number 22 22 7

S_QUO_ITM_LOYX START_DT Y UTC 7

DateTime
S_QUO_ITM_LOYX TRVL_DISTANCE Y Number 22 22 7
S_QUO_ITM_LOYX TXN_AMOUNT Y Number 22 22 7
S_QUO_ITM_LOYX TXN_POINTS Y Number 22 22 7
S_QUO_ITM_LOYX VOUCHER_ID Y Varchar 15
S_QUO_ITM_LOYX VOUCHER_QTY Y Number 10 10 0

S_QUOTE_ITEM AGENCY_NAME Y Varchar 100
S_QUOTE_ITEM BILL_PROFILE_ID Y Varchar 15

Data LOV
S_QUOTE_ITEM END_PHONE_NUM Y Varchar 20
S_QUOTE_ITEM ORIG_ACCNT_NUM Y Varchar 50
S_QUOTE_ITEM ORIG_PIN Y Varchar 50
S_QUOTE_ITEM PORT_NUM Y Varchar 20
S_QUOTE_ITEM RLTD_SRVC_PROD_ID Y Varchar 15
S_QUOTE_ITEM RLTDSRVCAST_INT_ID Y Varchar 15
S_QUOTE_ITEM RQST_PORT_DATE Y Time 7

Stamp
S_QUOTE_ITEM START_PHONE_NUM Y Varchar 20
S_QUOTE_ITEM SVC_PROVIDER Y Varchar 100
S_QUOTE_ITEM SVC_ZIP_CODE Y Varchar 30
S_QUOTE_ITEM_OM PREV_BILL_PROF_ID Y Varchar 15
S_QUOTE_ITEM_OM PREV_NET_PRI Y Number 25 10 0
S_QUOTE_ITEM_OM SUB_ACTION_CD Y Varchar 30
S_QUOTE_ITM_SPA AUTH_COST_AMT Y Number 22 22 7
S_QUOTE_ITM_SPA SPA_ITM_ACTION_CD Y Varchar 30 HTIM_QUOTE_

ACTION_TYPE
S_QUOTE_ITM_SPA STATUS_UPD_BY Y Varchar 15
S_REVN USAGE Y Number 22 10 0
S_SAMPLE_TXN APPROVER_ID Y Varchar 15
S_SAMPLE_TXN NUM_PACKAGE_RECD Y Number 22 10 0
S_SAMPLE_TXN NUM_PACKAGE_SENT Y Number 22 10 0

S_SAMPLE_TXN OLD_TXN_ID Y Varchar 15
307
3 08
Data LOV
S_SAMPLE_TXN PKG_ARRIVAL_DT Y UTC 7

DateTime
S_SAMPLE_TXN PKG_DLVRY_DT Y UTC 7

DateTime
S_SAMPLE_TXN ROOT_TXN_ID Y Varchar 15
S_SAMPLE_TXN SRC_TXN_ID Y Varchar 15
S_SAMPLE_TXN TRACKING_NUM Y Varchar 30
S_SD_PIM_ROW CAL_REPEAT_PATTERN Y Varchar 500

S_SD_USER_MAP SEBL_USER_GRP_CD Y Varchar 30
S_SD_USER_MAP SEBL_USREXTRACT_DT Y UTC 7

DateTime
S_SIGN_DISC_LS DISC_SUB_TYPE_CD Y Varchar 30
S_SIGN_DISC_LS DISC_TYPE_CD Y Varchar 30
S_SMPL_TXN_ITEM MAX_ORDER_QTY Y Number 22 22 7
S_SMPL_TXN_ITEM MIN_ORDER_QTY Y Number 22 22 7

S_SMPL_TXN_ITEM PROD_ALLOC_ID Y Varchar 15
S_SMPL_TXN_ITEM RECEIVED_DT Y UTC 7

DateTime
S_SMPL_TXN_ITEM STK_PERD_EMP_ID Y Varchar 15
S_SRC FUNNEL_STAGE_ID Y Varchar 15
S_SRC MUTL_EXCLUSIVE_FLG N Char 1 Y
S_SRC PCT_ALLOC_FLG N Char 1 Y

S_SRC PRE_LOAD_TSK_WF_ID Y Varchar 15
S_SRC PST_LNCH_TSK_WF_ID Y Varchar 15

Data LOV
S_SRC PST_LOAD_TSK_WF_ID Y Varchar 15
S_SRC RECURRING_FLG N Char 1 Y
S_SRC_PAYMENT APPRV_POSTN_ID Y Varchar 15
S_STATE_LIC_LS ONE_SAMPLE_FLG N Char 1 N
S_STK_PERD_EMP APPROVER_ID Y Varchar 15
S_STK_PERD_EMP AUDIT_EMP_ID Y Varchar 15
S_STOCK_EMP INV_AUDIT_RPT_ID Y Varchar 15
S_STOCK_EMP INVENTORY_COUNT Y Number 22 22 7

S_TMPL_PLANITEM CASE_TYPE_CD Y Varchar 30
S_USER DAY_OVERDUE_INVCHK Y Number 22 10 0
S_USER DAYS_COMP_TRNG Y Number 22 10 0
S_USER DAYS_INV_AUDIT Y Number 22 10 0
S_USER DAYS_OVERDUE_ACK Y Number 22 10 0
S_USER DAYS_REPORT_LOSS Y Number 22 10 0
S_USER DAYS_SMPL_WARNING Y Number 22 10 0
S_USER DAYS_TRANSFER_IN Y Number 22 10 0
S_USER DAYS_TRSFR_DISCR Y Number 22 10 0
S_USER INTEG_USER_FLG N Char 1 N
S_USER LAST_UNCOMPRESS_DT Y UTC 7

DateTime
S_USER MAX_SAMPLE_CALL Y Number 22 10 0

S_USER MIN_INVENTORY Y Number 22 10 0
S_USER STATUS_CD Y Varchar 30 USER_STATUS Y

309
3 10
Data LOV
S_WFA_INST_LOG WORKITEM_ID_VAL Y Varchar 15
S_XMLP_REP_TMPL RPT_HAS_PARAM_FLG N Char 1 N
S_XMLP_REP_TMPL RPT_UPLOAD_STAT_CD Y Varchar 30
S_XMLP_REP_TMPL XMLP_REP_INTOBJ_ID Y Varchar 15


Schema Changes ■ Table Index Changes in This Version
Changed Table Columns in This Version

Table 132 lists table columns that have changed in this version.
Table 132. Table Columns That Have Changed in This Version
Type of Previous
Table Name Column Change Value New Value
S_ASSET RATE_STATE Length 10 30
S_AUDIT_ITEM ITEM_IDEN_NUM Default 0
S_INST_UPG_HIST ADDL_LANG_INSTALED Length 50 100
S_INVC_ADJ_ITEM INTEGRATION_ID Varchar 30 450
S_INVC_ITM_DTL INTEGRATION_ID Varchar 30 450
S_INVOICE INTEGRATION_ID Varchar 30 450
S_INVOICE_ADJ INTEGRATION_ID Varchar 30 450
S_INVOICE_DTL INTEGRATION_ID Varchar 30 450
S_LOY_MEMBER VAL_SCORE Length 50 30
S_LOY_PROD_PT PARTNER_ID Opt N Y
S_LOY_STMT_CRTN TIER_ID Opt N Y
S_LOY_STMT_LOG MEMBER_ID Opt N Y
S_LOY_TIER_CLS START_QUAL_PD_CD Active Enrollment/

Anniversary Date
LOV Type LOY_START_ LOY_START_QUAL

QUAL_PER_CD _PER_CD
S_RT_SVC NAME Length 30 75
S_RT_SVC_METH NAME Length 30 75

S_RT_SVC_M_ARG NAME Length 30 75
S_SRV_REQ2_FNX WTR_COUNTRY Length 25 30
S_TIMEZONE UTC_OFFSET Opt N Y
S_XMLP_REP_TMPL INT_OBJ_NAME Opt N Y
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 312
■ “Changed Table Index in This Version” on page 317

■ “Table Index That Was Deleted from This Version” on page 318
New Table Indexes in This Version

Table 133 lists table indexes that are new in this version. Some column headings are abbreviated as
follows:
■ A indicates active.
■ U indicates unique.
Table 133. Table Indexes That Are New in This Version
Table Index A U Columns
S_ACT_PRDINT S_ACT_PRDINT_F52 Y N (PROD_ALLOC_ID)
S_ACT_PROD_APPL S_ACT_PROD_APPL_F3 Y N (PROD_ALLOC_ID)
S_ACT_SIGN S_ACT_SIGN_F4 Y N (INV_AUDIT_RPT_ID)
S_ACT_SIGN S_ACT_SIGN_F5 Y N (SAMPLE_TXN_ID)
S_ACT_SIGN S_ACT_SIGN_U1 Y Y (ACTIVITY_ID,SIGN_NUM,

INV_AUDIT_RPT_ID,SAMPLE_TXN_ID,
CONFLICT_ID)
S_ASSESS S_ASSESS_F55 Y N (INV_AUDIT_RPT_ID)
S_ASSESS S_ASSESS_F56 Y N (LIT_ID)
S_ASSET S_ASSET_M7 Y N (STATUS_CD,REGISTERED_DT)
S_ASSET S_ASSET_F74 Y N (BILL_PROFILE_ID)

S_CAMP_CON S_CAMP_CON_M3 Y N (CAMP_LD_WAVE_ID,BATCH_NUM,
MARK_FOR_DEL_FLG,STAT_CD)
S_CASE S_CASE_F4 Y N (AUDIT_EMP_ID)
S_CASE S_CASE_F5 Y N (MSTR_CASE_ID)
S_CASE S_CASE_F6 Y N (APPLICANT_ID)
S_CASE S_CASE_F7 Y N (PS_APPL_ID)
S_COMMUNICATION S_COMMUNICATN_F19 Y N (MKT_SRVY_ID)
S_COMMUNICATION S_COMMUNICATN_F20 Y N (LEAD_ID)
S_COMMUNICATION S_COMUNICATION_M51 Y N (PGROUP_PUBLIC_FLG)
S_CONTACT S_CONTACT_M24 Y N (PRIV_FLG,LAST_NAME,FST_NAME)

S_CONTACT S_CONTACT_F65 Y N (MSTR_CASE_ID)
S_CONTACT_LSX S_CONTACT_LSX_F2 Y N (MASTER_SIGN_ID)
S_DCP_URL S_DCP_URL_F1 Y N (LAND_SITE_ID)
S_DMND_CRTN_PRG S_DMND_CRTNPRG_F22 Y N (ACT_OWNER_PER_ID)
S_DMND_CRTN_PRG S_DMND_CRTNPRG_F18 Y N (MKT_SRVY_ID)
S_DMND_CRTN_PRG S_DMND_CRTNPRG_F19 Y N (BU_ID)
S_DMND_CRTN_PRG S_DMND_CRTNPRG_F20 Y N (OWNER_POSTN_ID)
S_DMND_CRTN_PRG S_DMND_CRTNPRG_F21 Y N (ORIG_CREATOR_ID)
S_DOC_QUOTE S_DOC_QUOTE_F65 Y N (ATTR_ID)
S_DOC_QUOTE S_DOC_QUOTE_F40 Y N (BILL_PROFILE_ID)
S_EMP_PER S_EMP_PER_F50 Y N (LS_APPROVER_ID)
S_EMP_PRDINT S_EMP_PRDINT_U1 Y Y (EMP_ID,RELATION_TYPE,PRDINT_ID,

START_DT,END_DT,ALLOC_TYPE_CD,
CONFLICT_ID)
S_EMP_PRDINT S_EMP_PRDINT_U2 Y Y (PRDINT_ID,RELATION_TYPE,EMP_ID,

START_DT,END_DT,ALLOC_TYPE_CD,
CONFLICT_ID)
S_EVT_ACT S_EVT_ACT_F82 Y N (BNFT_PLAN_ITM_ID)
S_EVT_ACT S_EVT_ACT_F42 Y N (LEAD_ID)
S_EVT_ACT S_EVT_ACT_F43 Y N (SRC_EVT_REG_ID)
S_EVT_ACT_FNX S_EVT_ACT_FNX_M1 Y N (PGROUP_PUBLIC_FLG)
S_EVT_ACT_LSX S_EVT_ACT_LSX_F5 Y N (SUPERVISOR_ID)
S_EVT_FUL_REQ S_EVT_FUL_REQ_F16 Y N (EVTLOC_ID)

S_FCSTSER_POSTN S_FCSTSER_POSTN_F3 Y N (SUBMIT_TO_PSTN_ID)
S_INCIDENT S_INCIDENT_F5 Y N (SIGN_EVT_ID)
S_INVC_ADJ_ITEM S_INVC_ADJ_ITEM_II Y N (INTEGRATION_ID)
S_INVC_ADJ_ITEM S_INVC_ADJ_ITEM_U1 Y Y (INVOICE_ADJ_ID,INVOICE_ITEM_ID,

INV_ITEM_DETAIL_ID,CONFLICT_ID)
S_INVOICE S_INVOICE_M51 Y N (INVC_DT,SRC_ID)
S_INVOICE S_INVOICE_M1 Y N (INVC_DT)
S_INVOICE_ADJ S_INVOICE_ADJ_II Y N (INTEGRATION_ID)
S_LOY_ACRL_ITM S_LOY_ACRL_ITM_F8 Y N (PT_SUB_TYPE_ID)
S_LOY_ACTCRTR S_LOY_ACTCRTR_F6 Y N (PT_SUB_TYPE_ID)
S_LOY_ACTCRTR S_LOY_ACTCRTR_F4 Y N (PROD_ID)
S_LOY_ACTCRTR S_LOY_ACTCRTR_F5 Y N (PROMO_RULE_ID)

S_LOY_ADN_LANG S_LOY_ADN_LANG_F1 Y N (LANG_ID)
S_LOY_ATTRDEFN S_LOY_ATTRDEFN_F4 Y N (CURCY_CD)
S_LOY_ATTRDEFN S_LOY_ATTRDEFN_F5 Y N (PROGRAM_ID)
S_LOY_ATTRIB S_LOY_ATTRIB_F2 Y N (MEMBER_ID)
S_LOY_BCKT_TXN S_LOY_BCKT_TXN_F2 Y N (PROMO_BUCKET_ID)
S_LOY_CRTR_VAL S_LOY_CRTR_VAL_F1 Y N (CRITERIA_ID)
S_LOY_MEM_BU S_LOY_MEM_BU_F1 Y N (BU_ID)
S_LOY_MEM_BU S_LOY_MEM_BU_F2 Y N (MEMBER_ID)
S_LOY_MEM_CON S_LOY_MEM_CON_F2 Y N (MEMBER_ID)
S_LOY_MEM_PSTN S_LOY_MEM_PSTN_F1 Y N (MEMBER_ID)
S_LOY_MEM_PSTN S_LOY_MEM_PSTN_F2 Y N (POSTN_ID)
S_LOY_MEM_TIER S_LOY_MEM_TIER_F10 Y N (MEMBER_ID)
S_LOY_MEM_TIER S_LOY_MEM_TIER_F6 Y N (FUTR_TIER_ID)
S_LOY_MEM_TIER S_LOY_MEM_TIER_F7 Y N (APPLIED_PROMO_ID)
S_LOY_MEM_TIER S_LOY_MEM_TIER_F8 Y N (APPLD_PROMO_RL_ID)
S_LOY_MEM_TIER S_LOY_MEM_TIER_F9 Y N (BULK_REF_ID)
S_LOY_MEM_TIER S_LOY_MEM_TIER_M2 Y N (MEM_TIER_NUM)
S_LOY_MEM_VCHR S_LOY_MEM_VCHR_F4 Y N (ORIG_VCHR_ID)
S_LOY_MEM_VCHR S_LOY_MEM_VCHR_F5 Y N (TXN_ITEM_ID)

S_LOY_MEM_VCHR S_LOY_MEM_VCHR_F6 Y N (MERGE_MEM_ID)
S_LOY_MEM_VCHR S_LOY_MEM_VCHR_F7 Y N (CONSUMED_TXN_ID)
S_LOY_MEMBER S_LOY_MEMBER_F15 Y N (MEMSHIP_SCHEME_ID)
S_LOY_MEMBER S_LOY_MEMBER_F16 Y N (BU_ID)
S_LOY_MEMBER S_LOY_MEMBER_F17 Y N (CURCY_CD)
S_LOY_MEMBER S_LOY_MEMBER_F18 Y N (LANG_ID)
S_LOY_MEMBER S_LOY_MEMBER_F19 Y N (SURV_MEM_ID)
S_LOY_MEMPTRPG S_LOY_MEMPTRPG_F3 Y N (MEMBER_ID)
S_LOY_PROD_PT S_LOY_PROD_PT_F4 Y N (CURCY_CD)
S_LOY_PROD_PT S_LOY_PROD_PT_F5 Y N (PRICE_AMT_CURCY_CD)
S_LOY_PROD_PT S_LOY_PROD_PT_F6 Y N (PROGRAM_ID)
S_LOY_PROD_PT S_LOY_PROD_PT_U1 Y Y (PROD_PT_UID,CONFLICT_ID)
S_LOY_PROG_BU S_LOY_PROG_BU_F1 Y N (BU_ID)
S_LOY_PROG_BU S_LOY_PROG_BU_F2 Y N (PROG_ID)
S_LOY_PROG_ORG S_LOY_PROG_ORG_F2 Y N (PROG_ID)
S_LOY_PROG_ORG S_LOY_PROG_ORG_F3 Y N (PRICING_RULE_ID)
S_LOY_PROGRAM S_LOY_PROGRAM_F2 Y N (BU_ID)
S_LOY_PROMO S_LOY_PROMO_F8 Y N (BU_ID)
S_LOY_PROMO_ATR S_LOY_PROMO_ATR_F2 Y N (LOY_PROMO_ID)
S_LOY_PROMO_BU S_LOY_PROMO_BU_F1 Y N (BU_ID)
S_LOY_PROMO_BU S_LOY_PROMO_BU_F2 Y N (PROMO_ID)
S_LOY_PROMO_CST S_LOY_PROMO_CST_F2 Y N (COST_CURCY_CD)
S_LOY_PROMO_CST S_LOY_PROMO_CST_F3 Y N (PROMO_ID)
S_LOY_PROMO_RL S_LOY_PROMO_RL_F1 Y N (PROMO_ID)
S_LOY_PROMO_TR S_LOY_PROMO_TR_F2 Y N (PROMOTION_ID)
S_LOY_PROMOMEM S_LOY_PROMOMEM_F2 Y N (PROMO_ID)
S_LOY_PROMOPRD S_LOY_PROMOPRD_F4 Y N (PROMO_ID)
S_LOY_PT_BLCK S_LOY_PT_BLCK_F8 Y N (CURCY_CD)
S_LOY_PT_BLCK S_LOY_PT_BLCK_F9 Y N (SALE_CURCY_CD)
S_LOY_PTR_ATMP S_LOY_PTR_ATMP_F2 Y N (PARTNER_ID)
S_LOY_PTR_ZONE S_LOY_PTR_ZONE_F1 Y N (PARTNER_ID)

S_LOY_SR_TXN S_LOY_SR_TXN_F2 Y N (SRV_REQ_ID)
S_LOY_STMT S_LOY_STMT_F6 Y N (MEM_TIER_ID)
S_LOY_STMT S_LOY_STMT_F7 Y N (PARTNER_ID)
S_LOY_STMT S_LOY_STMT_F8 Y N (TRX_ID)
S_LOY_STMT S_LOY_STMT_F9 Y N (VOUCHER_ID)
S_LOY_STMT_ATTR S_LOY_STMT_ATTR_F2 Y N (STMT_ID)
S_LOY_STMT_CRTN S_LOY_STMT_CRTN_F1 Y N (PROG_ID)
S_LOY_STMT_CRTN S_LOY_STMT_CRTN_F2 Y N (TIER_ID)
S_LOY_STMT_ITM S_LOY_STMT_ITM_F4 Y N (STMT_ID)
S_LOY_STMT_ITM S_LOY_STMT_ITM_F5 Y N (PT_SUB_TYPE_ID)
S_LOY_STMT_LOG S_LOY_STMT_LOG_F3 Y N (PARTNER_ID)
S_LOY_STMT_TXN S_LOY_STMT_TXN_F7 Y N (CURCY_CD)

S_LOY_STMT_TXN S_LOY_STMT_TXN_F8 Y N (STMT_ID)
S_LOY_STMT_VCHR S_LOY_STMT_VCHR_F2 Y N (STMT_ID)
S_LOY_TIER S_LOY_TIER_F3 Y N (TIER_CLASS_ID)
S_LOY_TIER_CLS S_LOY_TIER_CLS_F1 Y N (APPROVER_ID)
S_LOY_TIER_CLS S_LOY_TIER_CLS_F2 Y N (PROGRAM_ID)
S_LOY_TIER_MAP S_LOY_TIER_MAP_F3 Y N (PROG_TIER_ID)
S_LOY_TXN S_LOY_TXN_F19 Y N (ACCR_RULE_ID)
S_LOY_TXN S_LOY_TXN_F20 Y N (BULK_REF_ID)
S_LOY_TXN S_LOY_TXN_F21 Y N (BU_ID)
S_LOY_TXN S_LOY_TXN_F22 Y N (CURCY_CD)
S_LOY_TXN S_LOY_TXN_F23 Y N (ORIG_ACRL_REF_ID)
S_LOY_TXN S_LOY_TXN_F24 Y N (CHILD_TXN_ID)
S_LOY_TXN S_LOY_TXN_F25 Y N (ORIG_ORD_ITM_ID)
S_LOY_TXN S_LOY_TXN_F26 Y N (RDM_ITM_ID)
S_LOY_TXN S_LOY_TXN_F27 Y N (ENROL_PROMO_ID)
S_LOY_TXN S_LOY_TXN_F28 Y N (OPER_CARRIER_ID)
S_LOY_TXN_BU S_LOY_TXN_BU_F1 Y N (BU_ID)
S_LOY_TXN_BU S_LOY_TXN_BU_F2 Y N (TXN_ID)
S_LOYAL_PROF S_LOYAL_PROF_F1 Y N (ACCNT_ID)

S_MDF S_MDF_F9 Y N (OWNER_ID)
S_MDF S_MDF_F10 Y N (REGION_ID)
S_MKTG_SRVR_TSK S_MKTG_SRVR_TSK_F8 Y N (IMPRT_TSK_ID)
S_OPTY S_OPTY_M60 Y N (PGROUP_PUBLIC_FLG)
S_OPTY_DSGN_REG S_OPTY_DSGN_REG_F8 Y N (CUST_ACCNT_ID)
S_ORD_ITM_LOYX S_ORD_ITM_LOYX_F2 Y N (VOUCHER_ID)
S_ORDER S_ORDER_F44 Y N (BILL_PROFILE_ID)
S_ORDER_ITEM S_ORDER_ITEM_F47 Y N (BILL_PROFILE_ID)
S_ORG_EXT S_ORG_EXT_F22 Y N (PR_BILL_PRFL_ID)
S_POSTN S_POSTN_F5 Y N (PGROUP_ID)
S_QUO_ITM_LOYX S_QUO_ITM_LOYX_F2 Y N (VOUCHER_ID)
S_QUOTE_ITEM S_QUOTE_ITEM_F41 Y N (BILL_PROFILE_ID)
S_SAMPLE_TXN S_SAMPLE_TXN_F7 Y N (OLD_TXN_ID)
S_SAMPLE_TXN S_SAMPLE_TXN_F8 Y N (SRC_TXN_ID)
S_SAMPLE_TXN S_SAMPLE_TXN_F9 Y N (APPROVER_ID)
S_SAMPLE_TXN S_SAMPLE_TXN_F10 Y N (ROOT_TXN_ID)
S_SMPL_TXN_ITEM S_SMPL_TXN_ITEM_F6 Y N (PROD_ALLOC_ID)
S_SMPL_TXN_ITEM S_SMPL_TXN_ITEM_F7 Y N (STK_PERD_EMP_ID)
S_SRC S_SRC_F40 Y N (PST_LNCH_TSK_WF_ID)
S_SRC S_SRC_F41 Y N (PRE_LOAD_TSK_WF_ID)
S_SRC S_SRC_F42 Y N (FUNNEL_STAGE_ID)
S_SRC S_SRC_F43 Y N (PST_LOAD_TSK_WF_ID)
S_SRC_PAYMENT S_SRC_PAYMENT_F66 Y N (APPRV_POSTN_ID)
S_STK_PERD_EMP S_STK_PERD_EMP_F1 Y N (APPROVER_ID)
S_STK_PERD_EMP S_STK_PERD_EMP_F2 Y N (AUDIT_EMP_ID)
S_STOCK_EMP S_STOCK_EMP_F4 Y N (INV_AUDIT_RPT_ID)
S_STOCK_EMP S_STOCK_EMP_U1 Y Y (EMP_ID,PRDINT_ID,

STK_PERD_EMP_ID,LOT_ID,
INV_AUDIT_RPT_ID,CONFLICT_ID)
S_XMLP_REP_TMPL S_XMLP_REP_TMPL_F1 Y N (XMLP_REP_INTOBJ_ID)
Changed Table Index in This Version

Table 134 lists a table index that was changed in this version.
Table 134. Table Index That Changed Definition in This Version
Table Name Index Previous Columns New Columns
S_LOY_PROD_PT S_LOY_PROD_PT_U1 (PROGRAM_ID,TXN_TYPE_CD, (PROD_PT_UID,

PROD_ID,ATTRIB_1,ATTRIB_2, CONFLICT_ID)
ATTRIB_3,ATTRIB_4,ATTRIB_5,
ATTRIB_6,CONFLICT_ID)

Table Index That Was Deleted from This Version

Table 135 lists a table index that was deleted from this version.
Table 135. Table Index
Table Name Index A U Column
S_SD_SYNC_INFO S_SD_SYNC_INFO_M4 Y N (SEQ_ID)
Index
A diagram 41
account ERD tables 40
about 23 Automotive
diagram 25 automotive retail ERD 42
support for Dynamic Hierarchy 23 dealer sales and service promotion 87
support for Global Account Views 23 vehicle collection ERD 254
tables 23 vehicle ERD 252
account targeting ERD vehicle financing ERD 256
about 26 vehicle sales ERD 258
diagram 27 automotive retail ERD
tables 26 about 42
activity ERD diagram 43
about 28 tables 42
diagram 29
tables 28 B
adjustment group ERD banking
about 30 See commercial banking ERD
diagram 31 benefit case management ERD
tables 30 about 44
affiliations and best times ERD diagram 46
about 32 tables 44
diagram 33 best call hours
tables 32 See routes and best call hours ERD
agencies/agent ERD brick ERD
about 34 about 47
diagram 35 diagram 48
tables 34 tables 47
agreement
See CME agreement ERD C
alerts
campaign management
See CME alert ERD
See marketing campaign ERD
apparel
CG promotion planning ERD
See textile, apparel, and footwear ERD
about 49
asset management ERD
diagram 51
about 36
tables 49
diagram 37
chat
tables 36
See community/chat discussion ERD
tracking asset instances 36
clinical study management ERD
assets
about 52
See CME energy products, service, and usage
diagram 54
ERD
tables 52
auction ERD
CME account ERD
about 38
about 55
diagram 39
diagram 56
tables 38
tables 55
auto email response generator ERD
CME agreement ERD
about 40

Index ■ D
about 57 Consumer Sector

diagram 58 account targeting ERD 26
tables 57 best hours entity 210
CME alert ERD CG promotion planning ERD 49
about 59 objectives ERD 160
diagram 60 sales volume planning ERD 214
tables 59 territory management - CS ERD 236
CME energy products, service, and usage content management ERD
ERD about 78
about 61 diagram 79
diagram 62 tables 78
tables 61 content object
CME order management ERD See content management ERD
about 63 content process
diagram 64 See content management ERD
tables 63 contract conditions ERD
columns about 80
domain type definitions 271 diagram 81
INTEGRATION_ID columns, about 273 tables 80
naming conventions 267 contracts ERD
numeric physical type 272 about 82
type definitions 271 diagram 83
commercial banking ERD tables 82
about 65 credit alerts
diagram 67 See CME alert ERD
tables 65 Customer Data Item, about 84
commercial insurance ERD
about 68 D
diagram 69 data (intersection) table type
tables 68 about 269
Communications, Media, Energy obsolete, table marked as 269
CME account ERD 55 data (private) table type, about 269
CME agreement ERD data (public) table type
CME alert ERD 59 about 269
CME energy products, service, and usage obsolete, table marked as 269
ERD 61 data types
CME order management ERD 63 limit checking 274
pricing comparison ERD 185 data visibility ERD
community/chat discussion ERD about 84
about 70 diagram 86
tables 70 database schema version number, finding
compensation planning administration ERD and format 274
about 72 dealer sales and service promotion ERD
diagram 73 about 87
tables 72 diagram 88
compensation planning execution ERD tables 87
about 74 defect tracking
diagram 75 See product quality tracking ERD
tables 74 design
competency management system ERD See schema
about 76 discussion
diagram 77 See community/chat discussion ERD
tables 76
Index ■ E
document ID and tax ID ERD brick, diagram 48

about 89 brick, tables 47
diagram 90 CG promotion planning, diagram 51
tables 89 CG promotion planning, tables 49
domain type definitions 271 clinical study management, diagram 54
Dun & Bradstreet integration ERD clinical study management, tables 52
about 91 CME account, diagram 56
diagram 92 CME account, tables 55
tables 91 CME agreement, diagram 58
Dynamic Hierarchy, support by account CME agreement, tables 57
entity 23 CME alert, diagram 60
CME alert, tables 59
E CME energy products, service, and usage,
employee KPI ERD diagram 62
about 93 CME energy products, service, and usage,
tables 93 CME order management ERD, diagram 64
Employee Relationship Management CME order management ERD, tables 63
compensation planning administration commercial banking, diagram 67
ERD 72 commercial banking, tables 65
compensation planning execution ERD 74 commercial insurance, diagram 69
competency management system ERD 76 commercial insurance, tables 68
employee KPI ERD 93 community/chat discussion, diagram 71
performance review ERD 176 community/chat discussion, tables 70
employees compensation planning administration,
field service scheduler ERD 101 diagram 73
time sheet ERD 242 compensation planning administration,
entitlement items, service agreement tables 72
ERD 218 compensation planning execution,
ERDs diagram 75
account targeting, diagram 27 compensation planning execution,
account targeting, tables 26 tables 74
account, diagram 25 competency management system,
account, tables 23 diagram 77
activity, diagram 29 competency management system,
activity, tables 28 tables 76
adjustment group, diagram 31 content management, diagram 79
adjustment group, tables 30 content management, tables 78
affiliations and best times, diagram 33 contract conditions, diagram 81
affiliations and best times, tables 32 contract conditions, tables 80
agencies/agent, diagram 35 contracts, diagram 83
agencies/agent, tables 34 contracts, tables 82
asset management, diagram 37 conventions, description of 13
asset management, tables 36 data visibility, diagram 86
auction, diagram 39 data visibility, tables 84
auction, tables 38 dealer sales and service promotion,
auto email response generator, diagram 88
diagram 41 dealer sales and service promotion,
auto email response generator, tables 40 tables 87
automotive retail, diagram 43 document ID and tax ID, diagram 90
automotive retail, tables 42 document ID and tax ID, tables 89
benefit case management, diagram 46 Dun & Bradstreet integration, diagram 92
benefit case management, tables 44 Dun & Bradstreet integration, tables 91
employee KPI, diagram 94

Index ■ E
employee KPI, tables 93 loyalty, tables 142

event tax administration, diagram 96 managed care, diagram 146
event tax administration, tables 95 managed care, tables 145
exclusive arc relationship, diagram marketing campaign, diagram 148
conventions 14 marketing campaign, tables 147
expense reports, diagram 98 marketing collaboration, diagram 150
expense reports, tables 97 marketing collaboration, tables 149
field service inventory, diagram 100, marketing encyclopedia, diagram 152
102 marketing encyclopedia, tables 151
field service inventory, tables 99 marketing events, diagram 155
field service scheduler, tables 101 marketing events, tables 153
financial account application, diagram 106 marketing plans, diagram 157
financial account application, tables 105 marketing plans, tables 156
financial account, diagram 104 medical education event management,
financial account, tables 103 diagram 159
financial investments, diagram 108 medical education event management,
financial investments, tables 107 tables 158
financial products, diagram 110 objectives, diagram 161
financial products, tables 109 objectives, tables 160
financial services events, diagram 113 opportunity management, diagram 163
financial services events, tables 111 opportunity management, tables 162
forecasts, diagram 115 order life cycle, diagram 165
forecasts, tables 114 order life cycle, tables 164
general diagram conventions 14 orders, diagram 167
group insurance policies, diagram 117 orders, tables 166
group insurance policies, tables 116 partner collaboration, diagram 169
group pensions, diagram 119 partner collaboration, tables 168
group pensions, tables 118 partner program registration, diagram 171
health provider/provider group, partner program registration, tables 170
diagram 121 party model, diagram 173
health provider/provider group, tables 120 party model, tables 172
high tech marketing development fund, payments, diagram 175
diagram 123 payments, tables 174
high tech marketing development fund, performance review, diagram 178
tables 122 performance review, tables 176
high tech special pricing authorization, personal account, diagram 180
diagram 125 personal account, tables 179
high tech special pricing authorization, personal financial review, diagram 182
tables 124 personal financial review, tables 181
hospitality category, diagram 127 personalized content delivery, tables 183
hospitality category, tables 126 pricing comparison, diagram 184, 186
institutional sales, diagram 129 pricing comparison, tables 185
institutional sales, tables 128 pricing, diagram 188
insurance claims, diagram 132 pricing, tables 187
insurance claims, tables 130 product promotion, diagram 190
insurance policies, diagram 134 product promotion, tables 189
insurance policies, tables 133 product quality tracking, diagram 192
invoicable charges, diagram 136 product quality tracking, tables 191
invoicable charges, tables 135 product recommendation, diagram 194
invoices, diagram 138 product recommendation, tables 193
invoices, tables 137 products or services, diagram 196
life insurance policy, diagram 140 products or services, tables 195
life insurance policy, tables 139 professional services, diagram 198
loyalty, diagram 144 professional services, tables 197
Index ■ F
public sector case lead management, territory management, tables 234

diagram 201 textile, apparel, and footwear,
public sector case lead management, diagram 241
tables 199 textile, apparel, and footwear, tables 240
public sector contact identity, diagram 203 time sheet, diagram 243
public sector contact identity, tables 202 time sheet, tables 242
public sector evidence management, trade promotions, diagram 245
diagram 205 trade promotions, tables 244
public sector evidence management, training curriculum course, diagram 247
tables 204 training curriculum course, tables 246
public sector incident management, training test engine, diagram 249
diagram 207 training test engine, tables 248
public sector incident management, universal customer master, diagram 251
tables 206 universal customer master, tables 250
recursive relationship, diagram vehicle collection, diagram 255
conventions 15 vehicle collection, tables 254
revenue, diagram 209 vehicle financing, diagram 257
revenue, tables 208 vehicle financing, tables 256
revision table 16 vehicle sales, diagram 259
routes and best call hours, diagram 211 vehicle sales, tables 258
routes and best call hours, tables 210 vehicle, diagram 253
sales hierarchy and credit assignment, vehicle, tables 252
diagram 213 versioned object definition, diagram 261
sales hierarchy and credit assignment, versioned object definition, tables 260
tables 212 warranty, diagram 263
sales volume planning, diagram 215 warranty, tables 262
sales volume planning, tables 214 event tax administration ERD
sample management, diagram 217 about 95
sample management, tables 216 diagram 96
service agreement, diagram 219 tables 95
service agreement, tables 218 exclusive arc relationship
service calendars and work shifts, about 14
diagram 221 diagram conventions 14
service calendars and work shifts, expense reports ERD
tables 220 about 97
service request, diagram 223 diagram 98
service request, tables 222 tables 97
shipment, diagram 225 extension (Siebel) table type
shipment, tables 224 about 269
Siebel Assistant, diagram 227 obsolete table marked as 269
Siebel Assistant, tables 226 extension table type, about 269
syndicated data, diagram 229
syndicated data, tables 228 F
teller administration, diagram 231 field service inventory ERD
teller administration, tables 230 about 99
territory alignment - quota assignment diagram 100, 102
territory alignment - quota assignment, field service scheduler ERD
tables 232 about 101
territory management - CS, diagram 237 tables 101
territory management - CS, tables 236 financial account application ERD
territory management - LS, diagram 239 about 105
territory management - LS, tables 238 diagram 106
territory management, diagram 235

Index ■ G
tables 105 group insurance policies ERD

financial account ERD about 116
about 102 diagram 117
tables 103 group pensions ERD
financial accounts about 118
financial account application ERD 105 diagram 119
financial account ERD 102 tables 118
personal account ERD 179
financial investments ERD H
about 107 health provider/provider group ERD
diagram 108 about 120
financial products ERD tables 120
about 109 high tech marketing development fund ERD
financial review, personal financial review tables 122
ERD 181 high tech special pricing authorization ERD
Financial Services about 124
agencies/agent ERD 34 diagram 125
commercial banking ERD 65 tables 124
commercial insurance ERD 68 Hospitality
financial account application ERD 105 event tax administration ERD 95
financial account ERD 102 hospitality category ERD
financial investments ERD 107 about 126
financial products ERD 109 diagram 127
financial services events ERD 111 tables 126
group insurance policies ERD 116
group pensions ERD 118
health provider/provider group ERD 120 I
institutional sales ERD 128 Include Only field 273
insurance claims ERD 130 index column fields 273
insurance policies ERD 133 index naming conventions 267
life insurance policy ERD 139 institutional sales ERD
teller administration ERD 230 about 128
financial services events ERD diagram 129
about 111 tables 128
diagram 113 insurance
tables 111 commercial insurance ERD 68
footwear group insurance policies ERD 116
See textile, apparel, and footwear ERD insurance claims ERD 130
forecasts ERD insurance policies ERD 133
about 114 life insurance policy ERD 139
diagram 115 personal account ERD 179
tables 114 insurance claims ERD
fraud alerts about 130
See CME alert ERD diagram 132
tables 130
insurance policies ERD
G about 133
generating table report 275 diagram 134
Global Account Views, support by account tables 133
entity 23 INTEGRATION_ID columns, about 273
Index ■ L
invoicable charges ERD marketing campaign ERD

about 135 about 147
tables 135 tables 147
invoices ERD marketing collaboration ERD
about 137 about 149
marketing development funds
L See CG promotion planning ERD
life insurance policy ERD marketing encyclopedia ERD
about 139 about 151
Life Sciences marketing events ERD
activity ERD 28 about 153
affiliations and best times ERD 32 diagram 155
brick ERD 47 tables 153
clinical study management ERD 52 marketing plans ERD
community/chat discussion ERD 70 about 156
managed care ERD 145 diagram 157
medical education event management tables 156
ERD 158 Master Data Item, about 84
personalized content delivery ERD 183 MDFs
sample management ERD 216 See CG promotion planning ERD
syndicated data ERD 228 MedEd event management
territory management - LS ERD 238 See medical education event management
limit checking for data types 274 ERD
loans, commercial banking entity 65 medical education event management ERD
logical model about 158
ERD conventions 13 diagram 159
ERD descriptions 16 tables 158
loyalty ERD mini brick
about 141 See brick ERD
diagram 144
tables 142 N
naming conventions
M columns 267
managed care ERD indexes 267
about 145 physical model listings, abbreviations
diagram 146 used 268
tables 145 table names 265
Marketing table prefixes 266
CG promotion planning ERD 49 table suffixes 266
Dun & Bradstreet integration ERD 91 non-Siebel application products, caution
forecasts ERD 114 about inserting or updating
high tech marketing development fund data 11
ERD 122 normalized, defined 11
marketing campaign ERD 147
marketing collaboration ERD 149 O
marketing encyclopedia ERD 151 objectives ERD
marketing events ERD 153 about 160
marketing plans ERD 156 diagram 161

Index ■ P
tables 160 columns of numeric physical type 272

opportunity management ERD database schema version number, finding and
about 162 format 274
diagram 163 domain type definitions 271
tables 162 Include Only field 273
Oracle Applications, about use of index naming conventions 267
INTEGRATION_ID columns 273 INTEGRATION_ID columns, about 273
order life cycle ERD limit checking for data types 274
about 164 party model, about 275
diagram 165 physical model listings, abbreviations
tables 164 used 268
orders ERD Siebel repository tables, about 273
about 166 Siebel system fields 272
diagram 167 table naming conventions 265
tables 166 table report, about 275
table status definitions 270
P table type definitions 269
partner collaboration ERD validating Siebel Schema 274
about 168 physicians, health provider/provider group
diagram 169 ERD 120
tables 168 prescription information, syndicated data
partner program registration ERD ERD 228
about 170 pricing comparison ERD
tables 170 diagram 184, 186
party model ERD tables 185
about 172 pricing ERD
party model, about 275 tables 187
party, defined 172 product promotion ERD
payments ERD about 189
tables 174 product quality tracking ERD
performance review ERD about 191
tables 176 product recommendation ERD
personal account ERD about 193
tables 179 products or services ERD
personal financial review ERD about 195
tables 181 professional services ERD
personalized content delivery ERD about 197
physical model projects, professional services ERD 197
column naming conventions 267 protocols
column type definitions 271 See clinical study management ERD
public sector benefit case management ERD
Index ■ R
about 44 See sales hierarchy and credit assignment

diagram 46 ERD
tables 44 sales volume planning ERD
public sector case lead management ERD about 214
tables 199 sample management ERD
public sector contact identity ERD about 216
tables 202 schema
public sector evidence management ERD changes to 277
about 204 database schema version number, finding and
diagram 205 format 274
tables 204 defined 11
public sector incident management ERD validating Siebel Schema 274
about 206 Service
diagram 207 field service inventory ERD 99
tables 206 field service scheduler ERD 101
invoicable charges ERD 135
R invoices ERD 137
recursive relationship products or services ERD 195
about 15 service agreement ERD 218
diagram conventions 15 service calendars and work shifts ERD 220
repository, about Siebel repository 273 service request ERD 222
revenue ERD territory management - CS ERD 236
about 208 warranty ERD 262
diagram 209 service activities, field service scheduler
tables 208 ERD 101
routes and best call hours ERD service agreement ERD
about 210 about 218
service calendars and work shifts ERD
about 220
S diagram 221
Sales tables 220
Dun & Bradstreet integration ERD 91 service region, field service scheduler
forecasts ERD 114 ERD 101
high tech special pricing authorization service request ERD
ERD 124 about 222
marketing encyclopedia ERD 151 diagram 223
opportunity management ERD 162 tables 222
routes and best call hours ERD 210 service requests
sales hierarchy and credit assignment ERD See CME account ERD
territory alignment - quota assignment services
ERD 232 See CME energy products, service, and usage
territory management - LS ERD 238 ERD
territory management ERD 234 shipment ERD
sales hierarchy and credit assignment ERD about 224
tables 212 Siebel Assistant ERD
Sales Hierarchy Module about 226

Index ■ T

tables 226 tests, training test engine ERD 248
Siebel repository, about 273 textile, apparel, and footwear ERD
Siebel SAP R/3 Connector, about use of about 240
INTEGRATION_ID columns 273 diagram 241
Siebel system fields 272 tables 240
special ERD conventions time sheet ERD
exclusive arc relationship 14 about 242
recursive relationship 15 diagram 243
syndicated data ERD tables 242
about 228 trade promotions ERD
system fields 272 tables 244
training curriculum course ERD
T about 246
table columns diagram 247
changed 311 tables 246
new 282 training test engine ERD
table indexes about 248
changed 317 diagram 249
deleted 318 tables 248
new 312 trouble tickets
tables See CME account ERD
changed 281
generating report 275 U
naming conventions 265 universal customer master ERD
new 277 about 250
prefix naming conventions 266 diagram 251
suffix naming conventions 266 tables 250
table status definitions 270
types of 269 V
tax ID validating Siebel Schema 274
See document ID and tax ID ERD vehicle collection ERD
teller administration ERD about 254
tables 230 vehicle ERD
territory alignment - quota assignment ERD about 252
tables 232 vehicle financing ERD
territory management - CS ERD about 256
tables 236 vehicle sales ERD
territory management - LS ERD about 258
tables 238 versioned object definition ERD
territory management ERD about 260
Index ■ W
W work shifts
warranty ERD See service calendars and work shifts ERD
about 262 workflow process
diagram 263 See content management ERD
tables 262

Index ■ W

Siebel Data Model Reference For Industry Applications v8.1.1

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Siebel Data Model Reference For Industry Applications v8.1.1

Uploaded by

Copyright:

Available Formats

Siebel Data Model

Reference for Industry

Siebel Data Model Reference for Industry Applications 1

Chapter 1: What’s New in This Release

Chapter 2: Data Model Overview

Chapter 3: Logical Model

Siebel Data Model Reference for Industry Applications Version 8.1 3

4 Siebel Data Model Reference for Industry Applications Version 8.1

Partner Collaboration 168

Siebel Data Model Reference for Industry Applications Version 8.1 5

Vehicle Collection 254

Chapter 4: Physical Model

Chapter 5: Schema Changes

6 Siebel Data Model Reference for Industry Applications Version 8.1

Changed Table Index in This Version 317

Siebel Data Model Reference for Industry Applications Version 8.1 7

8 Siebel Data Model Reference for Industry Applications Version 8.1

What’s New in Siebel Data Model Reference for Industry Applications,

Siebel Data Model Reference for Industry Applications Version 8.1 9

10 Siebel Data Model Reference for Industry Applications Version 8.1

Siebel Data Model Reference for Industry Applications Version 8.1 11

12 Siebel Data Model Reference for Industry Applications Version 8.1

■ Relationships between entities

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

The information on ERDs is organized as follows:

■ Entity Relationship Diagram Conventions

■ Entity Relationship Diagrams and Descriptions on page 16

Entity Relationship Diagram

■ General Entities on page 14

■ Exclusive Arc Relationship on page 14

■ Recursive Relationship on page 15

Siebel Data Model Reference for Industry Applications Version 8.1 13

Figure 1. General Entity Relationship Diagram Conventions

Exclusive Arc Relationship

14 Siebel Data Model Reference for Industry Applications Version 8.1

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 for Industry Applications Version 8.1 15

Entity Relationship Diagrams and

Table 2 provides a list of ERDs in alphabetic order.

Table 2. Entity Relationship Diagrams

Figure Num. Revised New

Account Figure 4 on General No No

Account Targeting Figure 5 on Consumer Sector No No

Activity Figure 6 on Life Sciences No No

Adjustment Group Figure 7 on General No No

Affiliations and Best Times Figure 8 on Life Sciences No No

Agencies/Agent Figure 9 on Financial Services No No

Asset Management Figure 10 on General No No

Auction Figure 11 on General No No

Auto Email Response Generator Figure 12 on General No No

Automotive Retail Figure 13 on Automotive No No

Benefit Case Management Figure 14 on Public Sector No Yes

Brick Figure 15 on Life Sciences No No

CG Promotion Planning Figure 16 on Marketing No No

Clinical Study Management Figure 17 on Life Sciences No No

16 Siebel Data Model Reference for Industry Applications Version 8.1

Table 2. Entity Relationship Diagrams

Figure Num. Revised New

Communications, Media, and Energy Figure 18 on CME No No