Beruflich Dokumente
Kultur Dokumente
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
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
Index
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.
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.
The Siebel logical model represents the following in Siebel Business Applications:
■ Entities
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.
General Entities
Figure 1 shows the diagram conventions for general entities used in this publication.
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.
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
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.
Entity Table
Activity S_EVT_ACT
Address S_ADDR_PER
Characteristics S_CHRCTR
Dynamic Account Hierarchy S_DYN_HRCHY
Industry S_INDUST
Party S_PARTY
Entity Table
Figure 4.
classification for user characteristics for
ACCOUNT SYNONYM
CORRESPONDENCE ASSIGNMENT
GROUP responsible for holders
a report to of
(TERRITORY)
Account
ACCOUNT responsibility of
25
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Criteria S_CG_QUERY_ITEM
Objective S_SRC
Query S_CG_QUERY
Route S_ACCNTRT
applied to
applied to
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Activity S_EVT_ACT
Contact S_CONTACT
Indication S_PROD_APPLCTN
Issue S_PROD_ISS
Product S_PROD_INT
PERSON Figure 6.
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
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Figure 7.
PRODUCT COMPATABILITY MATRIX RULE for
# MTRX_RULE_NUM
contain
contain
for
ADJUSTMENT GROUP
DIMENSION
# FIELD_NAME
31
Logical Model ■ Entity Relationship Diagrams and Descriptions
Table 7 lists the entities in this ERD and their corresponding tables.
Entity Table
Address S_ADDR_PER
Type S_PARTY_PER_DTL
ADDRESS USAGE
for for
ADDRESS
BEST TIMES
(ACCOUNT)
TYPE BEST TIMES
(ACCOUNT
AFFILIATION)
belong to
of
belong to
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Figure 9. Agencies/Agent
for for
subject of subject of
for
CONTACT
EXTERNAL has
ORGANIZATION UNIT
AGENT
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Activity S_EVT_ACT
Opportunity S_OPTY
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
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Asset S_ASSET
Catalog S_CTLG
Order S_ORDER
Order Item S_ORDER_ITEM
Party S_PARTY
Person S_CONTACT
Product S_PROD_INT
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
39
Logical Model ■ Entity Relationship Diagrams and Descriptions
Table 11 lists the entities in this ERD and their corresponding tables.
Table 11. Auto Email Response Generator ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Catalog S_CTLG
CATALOG CATEGORY
categorized within
INBOUND COMMUNICATION
classification for
PROBLEM
RESOLUTION
DOCUMENT categorized under
OUTBOUND RESPONSE classification for
Figure 12. Auto Email Response Generator
PERSON
made up of
CATALOG
41
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Activity S_EVT_ACT
Asset S_ASSET
Period S_PERIOD
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
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
43
Logical Model ■ Entity Relationship Diagrams and Descriptions
■ 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
Entity Table
Activity S_EVT_ACT
Admin Verification Template S_TMPL_PLANITEM
Admin Verification Template Item S_ASSESS_ATTRIB
Case S_CASE
Entity Table
46
BENEFIT PLAN
Author : Oracle, Confidential ACTIVITY
ITEM
PAYMENT
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
Logical Model ■ Entity Relationship Diagrams and Descriptions
for TEMPLATE
for
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Activity S_EVT_ACT
Address S_ADDR_PER
Position S_POSTN
Region S_REGION
REGION
child of
BRICK OTHER REGION
Figure 15. Brick
for for
for
held by located at
ADDRESS
CONTACT ACCOUNT ADDRESS defined by
ACTIVITY POSITION SYNDICATED DATA
for
for
located at
ORGANIZATION
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Period S_PERIOD
Promotion S_SRC
Entity Table
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
51
Logical Model ■ Entity Relationship Diagrams and Descriptions
Table 16 lists the entities in this ERD and their corresponding tables.
Entity Table
Activity S_EVT_ACT
Address S_ADDR_PER
Affiliation S_PTCL_ST_CON_LS
Application S_CL_PGM_APP_LS
Design S_CL_DSGN_LS
Position S_POSTN
Product S_PROD_INT
Program S_CL_PGM_LS
Project S_PROJ
Protocol S_CL_PTCL_LS
Subject S_CL_SUBJ_LS
Entity Table
Visit S_EVT_ACT
PROJECT ACCOUNT
SUBCONTRACTOR belong to
a partner for
PROJECT
having composed of CONTACT
SUBCONTACTOR
contact for CONTACT for
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
conducted at
Table 17 lists the entities in this ERD and their corresponding tables.
Entity Table
Account S_ORG_EXT
Activity S_EVT_ACT
Address S_ADDR_PER
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Agreement S_DOC_AGREE
Parameter S_QUOTE_ITEM_XA
Quote S_DOC_QUOTE
QUOTE ITEM
belongs to child of
has ACCOUNTS
Figure 19. CME Agreement
parent of
QUOTE for subject of
associated associated
consists of with
with
bound by has a
tracked associated
governs part of for by with
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Activity S_EVT_ACT
Alerts S_ALERT_CUT
Asset S_ASSET
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
Logical Model ■ Entity Relationship Diagrams and Descriptions
part of
ASSET
ACTIVITY
EQUIPMENT
METER
for
attached to
Table 20 lists the entities in this ERD and their corresponding tables.
Table 20. CME Energy Products, Service, and Usage ERD Entities and Tables
Entity Table
Address S_ADDR_PER
Asset S_ASSET
Invoice S_INVOICE
Payment S_SRC_PAYMENT
Period S_PERIOD
Usage S_USAGE
USAGE INVOICE
subject of is made into ADJUSTMENT
OTHER
at of associated recorded
with in recorded
made up of in
for
SERVICE INSTANCE PERIOD
PAYMENT
Logical Model ■ Entity Relationship Diagrams and Descriptions
made by
service
Table 21 lists the entities in this ERD and their corresponding tables.
Entity Table
Asset S_ASSET
Order S_ORDER
Quote S_DOC_QUOTE
64
Author : Oracle, Confidential
subject of instance of
part of
subject of part of subject of
of of of
subject of subject of
subject of
ASSET
an instance of
ordered on quoted for purchase on
made into
PRODUCT OR SERVICE
composed of composed of
Logical Model ■ Entity Relationship Diagrams and Descriptions
ORDER QUOTE
created from
leads to
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 lists the entities in this ERD and their corresponding 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
Fee S_FN_OFFR_FEE
Financial Account S_ASSET
Note S_NOTE_OPTY
Opportunity S_OPTY
Product S_PROD_INT
Rating S_OPTY_ORG_FNXM
Revenue S_REVN
Revenue S_REVN
Entity Table
of
APPROVAL
subject of includes generates belongs to LEVEL
part of
a report to
ORGANIZATION FINANCIAL ACCOUNT
owner of
owned by
67
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Asset S_ASSET
Contact S_CONTACT,S_PARTY
associated
with belongs to part of
for
covers for
of insured as
GROUP CLASS
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Product S_PROD_INT
Registration S_TOPIC_CON_LS
Topic S_TOPIC_LS
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
Table 25 lists the entities in this ERD and their corresponding tables.
Entity Table
Employee/Agent S_EMP_PER
Period S_PERIOD
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
BUSINESS UNIT
73
Logical Model ■ Entity Relationship Diagrams and Descriptions
Table 26 lists the entities in this ERD and their corresponding tables.
Entity Table
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
Logical Model ■ Entity Relationship Diagrams and Descriptions
Table 27 lists the entities in this ERD and their corresponding tables.
Entity Table
Employee/Agent S_EMP_PER
9$%$!;!%
"$ + " "$ +
"'+ &$ "$ +
14
"'+ "$ +
9$
14
2613
26
? ?
@
Figure 28. Competency Management System
3
"$ +
+ >;$
% ' 9
%$
513
$$
&%
2
9
2
?
13
13
=.*'
=. !
3
77
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Literature S_LIT
Product S_PROD_INT
CONTENT
PROJECT picked via
ITEM
used by
for managing
changes to LITERATURE CONTENT OBJECT
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
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Agreement S_DOC_AGREE
Benefit S_AGREE_BNFT
Category S_CTLG_CAT
Condition S_AGREE_COND
Contract S_DOC_AGREE
Entitlement S_ENTLMNT
Product S_PROD_INT
Term S_AGR_TERM_DESC
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
applicable to
subject of subject of
comprise comprise
CONTRACT
AGREEMENT OTHER
CONTRACT
81
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Asset S_ASSET
part of composed of
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
83
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Account S_ORG_EXT
Activity S_EVT_ACT
Agreement S_DOC_AGREE
Catalog S_CTLG
Category S_CTLG_CAT
Group S_PARTY
Internal/Partner Organization Unit S_ORG_EXT
Opportunity S_OPTY
Entity Table
Order S_ORDER
Party S_PARTY
Product S_PROD_INT
Quote S_DOC_QUOTE
!>13
Oracle
"%!"
+
&%"!" '%
@
&$+ 7& !
"$ '&"
1
!&
%> >+ 9 &%"
7&% !"
9"%
!" '
613
13
13
+
%$
"'+0
$ 9%$ %%
&
&
$[$&$
9
$[$&$
%$
$$'0$
$[$&$
9
6
6
6
$$'0$
$[$&$
.&%$%%&$
Table 32 lists the entities in this ERD and their corresponding tables.
Table 32. Dealer Sales and Service Promotion ERD Entities and Tables
Entity Table
Campaign S_SRC
CAMPAIGN CONTACT
belong to
for
CAMPIAGN CONTACT VEHICLE VEHICLE
subject of
subject of
in context of belong to
subject of
PERSON
Table 33 lists the entities in this ERD and their corresponding tables.
Entity Table
Invoice S_INVOICE
Order S_ORDER
ORDER EMPLOYEE
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
have
composed of
exists for exists for
PRICE LIST
Table 34 lists the entities in this ERD and their corresponding tables.
Table 34. Dun & Bradstreet Integration ERD Entities and Tables
Entity Table
Industry S_INDUST
Prospect S_PRSP_CONTACT
92
Author : Oracle, Confidential
D&B 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
equivalent to equivalent to
parent of child of
domestic
for child of composed of global
parent of
for of
created from
PROSPECT assigned to
member in
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Table 36 lists the entities in this ERD and their corresponding tables.
Entity Table
Asset S_ASSET
Category S_CTLG_CAT
Event/Function S_SRC
Position S_POSTN
Product S_PROD_INT
responsible for
TEAM has
MEMBER responsibility of
for
holders of
held by
POSITION
applies to
ASSET belongs to
owns composed of
for
CHARGE composed of
CODE
for
subject of
child of
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Activity S_EVT_ACT
Opportunity S_OPTY
Party S_PARTY
Project S_PROJ
incurred for
EXPENSE ITEM
PROJECT
subject of
incurred for
OPPORTUNITY
subject of
for
ACTIVITY
source of
incurred during
for
source of
subject of
classification for
made up of
part of PARTY
charged to
charged with
Table 38 lists the entities in this ERD and their corresponding tables.
Entity Table
Address S_ADDR_PER
Asset S_ASSET
Party S_PARTY
100
Author : Oracle, Confidential INVENTORY TRANSACTION INVENTORY
for TRANSACTION TYPE
PRODUCT 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
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
Table 39 lists the entities in this ERD and their corresponding tables.
Entity Table
Address S_ADDR_PER
Timezone S_TIMEZONE
Zipcode S_ZIPCODE
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
SCHEDULER TIME
in MAP DURATION
starting ending at
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.
102 Siebel Data Model Reference for Industry Applications Version 8.1
Logical Model ■ Entity Relationship Diagrams and Descriptions
Table 40 lists the entities in this ERD and their corresponding tables.
Entity Table
Activity S_EVT_ACT
Address S_ADDR_PER
Attachment S_ASSET_ATT
Authorization S_ASSETCON_AUTH
Fee S_FN_ACCNT_FEE
Note S_NOTE_ASSET
Schedule S_FN_ACCNT_SCHD
104
Author : Oracle, Confidential
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
owner of
for
SCHEDULE subject of
subject of
of UNIT UNIT
subject of
EXTERNAL ACCOUNT
Table 41 lists the entities in this ERD and their corresponding tables.
Entity Table
Activity S_EVT_ACT
Application S_OPTY
Assessment S_ASSESS
Collateral S_FN_OFFR_COLT
Income/Expense S_FN_INCM_EXP
Note S_NOTE_OPTY
Product S_PROD_INT
Quote S_DOC_QUOTE
106
Author : Oracle, Confidential
on
ASSET LIABILITY
subject of
uses reported in for has a
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Contact S_CONTACT,S_PARTY
Distribution S_FNSEC_DSTRBTN
Earning S_FNSEC_ERNG
Holding S_FN_HLDNG
Industry S_INDUST
Literature S_LIT
Security S_PROD_INT
Transaction S_FN_ACCNT_TXN
DISTRIBUTION
EXTERNAL ORGANIZATION
for
for for
for for
PUBLIC COMPANY
subject of made against
INDUSTRY EARNING
FINANCIAL ACCOUNT for subject of
DIVIDEND
part of
CONTACT
for
for
SECURITY
invested by investor of
STOCK FUND
INTERNAL EXTERNAL
BOND
108 Siebel Data Model Reference for Industry Applications Version 8.1
Logical Model ■ Entity Relationship Diagrams and Descriptions
Financial Products
This ERD (shown in Figure 44) illustrates how Siebel Financial Services supports generation of
financial products and other relevant associations. Internal products, rates, fees, and product line
information is also depicted. The major entities are depicted in the lower half of the diagram (Product
Internal).
Table 43 lists the entities in this ERD and their corresponding 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
BENEFIT CONDITION
for
of of of
composed of
PRODUCT INTERNAL
made up of
part of
110 Siebel Data Model Reference for Industry Applications Version 8.1
Logical Model ■ Entity Relationship Diagrams and Descriptions
Table 44 lists the entities in this ERD and their corresponding tables.
Entity Table
Activity S_EVT_ACT
Industry S_INDUST
Position S_POSTN
Product S_PROD_INT
Region S_REGION
Vendor S_SRC_ORG
Entity Table
112 Siebel Data Model Reference for Industry Applications Version 8.1
Title : Financial Services Events
Author : Oracle, Confidential VENDOR VENDOR reviewed by
VENDOR PERSON
OFFER SERVICE REVIEW
reviewer of
VENDOR
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
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
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Agreement S_DOC_AGREE
Forecast S_FCST
Opportunity S_OPTY
Project S_PROJ
Quote S_DOC_QUOTE
114 Siebel Data Model Reference for Industry Applications Version 8.1
Title : Forecasts
Author : Oracle, Confidential
REVENUE ITEM generated for FORECAST ITEM DETAIL
forecasted via
manager's forecast of
for subordinator's forecast of
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
attributed to governed by
attributed to attributed to attributed to
11 5
Logical Model ■ Entity Relationship Diagrams and Descriptions
Table 46 lists the entities in this ERD and their corresponding tables.
Entity Table
Census S_ORG_CENSUS
Contact S_CONTACT,S_PARTY
116 Siebel Data Model Reference for Industry Applications Version 8.1
Title : Group Insurance Policy
Author : Oracle, Confidential
COVERAGE ROLE
PRODUCT
ENROLLMENT applied to
for part of
made up subject to
for
of belongs
to
PRODUCT FOR PRODUCT CLASS
MEMBERS has
subject of subject of
based on
for available for for based on
CONTACT INSTANCE ATTRIBUTE
Figure 47. Group Insurance Policies
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
11 7
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Allocation S_APPLD_CVRG
Beneficiary S_FN_CVRG_ROLE
118 Siebel Data Model Reference for Industry Applications Version 8.1
Logical Model ■ Entity Relationship Diagrams and Descriptions
PRODUCT
FUNDING
for ALLOCATION VEHICLE
BENEFICIARY of
has by
having for
of set up part of
has
part of
used for has
belong to
for has
CONTACT
has
Table 48 lists the entities in this ERD and their corresponding tables.
Table 48. Health Provider and Provider Group ERD Entities and Tables
Entity Table
Contact S_CONTACT,S_PARTY
Encounter S_FN_HLTH_ENCTR
Language S_CONTACT_FNXM
Payment S_SRC_PAYMENT
Specialty S_CONTACT_FNXM
120 Siebel Data Model Reference for Industry Applications Version 8.1
Logical Model ■ Entity Relationship Diagrams and Descriptions
ORGANIZATION
PROVIDER GROUP
belongs to
in provided by
PROVIDER GROUP
serve SCHEDULE
ENCOUNTER HEALTH
serve at PRODUCT
specialized beneficiary
CONTACT part of part of subject of delivers part of in speaks of
PATIENT PROVIDER
Table 49 lists the entities in this ERD and their corresponding tables.
Table 49. High Tech Marketing Development Fund ERD Entities and Tables
Entity Table
Position S_POSTN
122 Siebel Data Model Reference for Industry Applications Version 8.1
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
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
12 3
Logical Model ■ Entity Relationship Diagrams and Descriptions
Table 50 lists the entities in this ERD and their corresponding tables.
Table 50. High Tech Special Pricing Authorization ERD Entities and Tables
Entity Table
Account S_ORG_EXT
Address S_ADDR_PER
Agreement S_DOC_AGREE
Entitlement S_ENTLMNT
Opportunity S_OPTY
Product S_PROD_INT
124 Siebel Data Model Reference for Industry Applications Version 8.1
Title : High Tech Special Pricing Authorization
Author : Oracle, Confidential
subject of
OTHER POS
ITEM
ENTITLEMENT
PRODUCT PRICE
for
having
having
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
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Category S_CTLG_CAT
Subcategory S_CTLG_CAT
Function S_FUNC_TNT
Quote S_DOC_QUOTE
Opportunity S_OPTY
126 Siebel Data Model Reference for Industry Applications Version 8.1
Logical Model ■ Entity Relationship Diagrams and Descriptions
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
Institutional Sales
This ERD (shown in Figure 53) illustrates how Siebel Financial Services supports generation of a
product or security traded in the stock market. One or more positions (such as institutional
salespeople) can cover a product. A position owns and prepares a call list containing one or more
contacts, who are the objects of the calls associated with any number of products. Siebel Financial
Services also tracks security or product line interests of a contact, as well as the securities held by
an organization unit (such as a company). Siebel Financial Services creates many-to-many
relationships when storing the literature associated with employees, activities, and products. A
position can send any number of pieces of literature to a contact within one activity.
Table 52 lists the entities in this ERD and their corresponding tables.
Entity Table
Activity S_EVT_ACT
Industry S_INDUST
Literature S_LIT
Product S_PROD_INT
128 Siebel Data Model Reference for Industry Applications Version 8.1
Title : Institutional Sales
Author : Oracle, Confidential
PRODUCT LINE
Figure 53. Institutional Sales
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
SECURITY
12 9
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Injury S_INSCLM_INJURY
130 Siebel Data Model Reference for Industry Applications Version 8.1
Logical Model ■ Entity Relationship Diagrams and Descriptions
Entity Table
Organization S_ORG_EXT
S_PARTY
S_ORG_EXT_FNX
Party S_PARTY
Payment S_SRC_PAYMENT
S_SRCPAYMT_CON
S_SRCPAYMT_ORG
S_INVC_PAYMENT
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 %%
$"$
'%%
Logical Model ■ Entity Relationship Diagrams and Descriptions
'%% %>
&^)
'" >$
%' '"'"$ ! 7&%T
14
13 1
6
13
14 14
14 14 14
%> !
13
2
14 6
14 14 14
14 14
14
Insurance Policies
This ERD (shown in Figure 55) illustrates how Siebel Financial Services supports generation of
insurance policies and related insurance policy items. The major entities are depicted in the bottom
half of the diagram (insurance policy and insurance policy items). Insurance policies relate to
households as well as contacts. Policy coverages, discounts, payment plans, and claim summaries
are also supported.
Table 54 lists the entities in this ERD and their corresponding tables.
Entity Table
Condition S_INSITEM_CNDTN
Contact S_CONTACT,S_PARTY
Discount S_APPLD_DISCNT
134
DISCOUNT
HOUSEHOLD CONTACT
applied to applied to
membership in membership of
LICENSE
RESTRICTION
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
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Activity S_EVT_ACT
Address S_ADDR_PER
Agreement S_DOC_AGREE
Asset S_ASSET
Invoice S_INVOICE
Order S_ORDER
Payment S_SRC_PAYMENT
Shipment S_SHIPMENT
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
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
Logical Model ■ Entity Relationship Diagrams and Descriptions
billed to contact of
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Activity S_EVT_ACT
Agreement S_DOC_AGREE
Expense S_EXP_ITEM
Invoice S_INVOICE
Order S_ORDER
Payment S_SRC_PAYMENT
Period S_PERIOD
Product S_PROD_INT
Project S_PROJ
Shipment S_SHIPMENT
INVOICE
Figure 57. Invoices
reason for
for billed via
SERVICE REQUEST
for billed via reason for
PART REPAIR
for billed via
billed via reason for
EXPENSE
for ORDER
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
Table 57 lists the entities in this ERD and their corresponding tables.
Entity Table
Activity S_EVT_ACT
Assessment S_ASSESS
Beneficiary S_FN_CVRG_ROLE
Holding S_FN_HLDNG
Product S_PROD_INT
Withdrawal/Surrender S_PAYMT_REQ
140
Author : Oracle, Confidential
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
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
for
subject associated
subject contact subject subject owned
of owned subject of with has
of of of subject of by includes basis of
by
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.
■ 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.
■ 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.
■ 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.
■ 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 lists the entities in this ERD and their corresponding tables.
Entity Table
Account S_ORG_EXT
Activity S_EVT_ACT_LOYX
Bucket S_LOY_BUCKET
Hosting Company S_ORG_EXT
Household S_ORG_GROUP
Individual S_CONTACT
Loan S_LOY_LOAN
142 Siebel Data Model Reference for Industry Applications Version 8.1
Logical Model ■ Entity Relationship Diagrams and Descriptions
Entity Table
Product S_PROD_INT
Statement S_LOY_STMT
Tier S_LOY_TIER
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
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
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Formulary S_INSPLN_FRMLY
child of
is PRODUCT
FORMULARY PRODUCT
for
parent to
for
contains of has
for
composed of
accepted by provided by
acceptor of provider of
146 Siebel Data Model Reference for Industry Applications Version 8.1
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Activity S_EVT_ACT
Opportunity S_OPTY
Opportunity Contact S_OPTY_CON
Order S_ORDER
Response S_COMMUNICATION
Territory S_ASGN_GRP
148
Author :Oracle, Confidential
associated with
for of
RESPONSE generated by CAMPAIGN CONTACT
targeted at ORDER originator of
generated by originator of
ACTIVITY OPPORTUNITY
generated by originator of
for primarily from
initiated by
MARKETING EVENT OR ACTIVITY of of
part of initiator of CALL LIST
introduction to targeted at MEMBER
conducted as
MARKETING CAMPAIGN
FULFILLMENT of source of
RECIPIENT FULFILLMENT in
for made up of
REQUEST part of of
Figure 61. Marketing Campaign
of
addressed to
subject of CALL LIST
part of
FULFILLMENT
REQUEST ITEM made up
of
made up of
responsible for a report to
for of subject
assigned to sell in
for of
ORGANIZATION UNIT subject
composed of a parent CAMPAIGN CALL LIST subject of
to of
subject of subject of
PERSON
PROSPECTIVE CONTACT
recipient of
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Opportunity S_OPTY
Order S_ORDER
Quote S_DOC_QUOTE
Response S_COMMUNICATION
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
item of collaboration for
generated from
lead to
responsible for
OPPORTUNITY
responsibility of collaborating on
responsible for
created for
OTHER PARTY
150 Siebel Data Model Reference for Industry Applications Version 8.1
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Issue S_ISS
152
Author : Oracle, Confidential
subject of characterized by
competitor of competitor of subject of reference to reference to
produced by
DECISION
ISSUE
subject of
COMPETITIVE METRIC
classification for
classification for
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Activity S_EVT_ACT
Order S_ORDER
Quote S_DOC_QUOTE
Entity Table
154 Siebel Data Model Reference for Industry Applications Version 8.1
2613 26
"52 >$! >$!
Oracle
>$! %$
** %> >;
14
14
$[$ 14
$!
&$ "7&"$
13
2
>'.'+ ;'%
21
$ ''!
1
2
%$ $
15 5
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Period S_PERIOD
156 Siebel Data Model Reference for Industry Applications Version 8.1
Title : Marketing Plans
Author : Oracle, Confidential
PLANNED attributed to
MARKETING MARKETING EVENT
DEVELOPMENT has OR ACTIVITY
FUND ALLOC MARKETING
GOAL
MARKETING
PLAN
estimated for
Figure 65. Marketing Plans
consists of
part of basis of
made up of based on created from
PRODUCT
PROMOTION source of
INVOICE
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
user of
Logical Model ■ Entity Relationship Diagrams and Descriptions
15 7
Logical Model ■ Entity Relationship Diagrams and Descriptions
Table 65 lists the entities in this ERD and their corresponding tables.
Table 65. Medical Education Event Management ERD Entities and Tables
Entity Table
Activity S_EVT_ACT
Event S_ME_EVT_LS
Literature S_ME_SES_LIT_LS
Material S_ME_SES_MAT_LS
Period S_PERIOD
Plan S_ME_PLN_LS
Session S_ME_SES_LS
Session Invitee S_ME_SES_INV_LS
158 Siebel Data Model Reference for Industry Applications Version 8.1
Title : Medical Education Event Management
Author : Oracle, Confidential
POSITION
PRODUCT
child of parent of
FUND PLAN
allocated to PERIOD
using
in
for
ACTIVITY for
EVENT
source of subject
to
promoted at team
composed of
promotion of EVENT POSITION of
usage of LITERATURE
promoted at
15 9
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Objective S_SRC
Position S_POSTN
160 Siebel Data Model Reference for Industry Applications Version 8.1
Logical Model ■ Entity Relationship Diagrams and Descriptions
Title : OBJECTIVES
Author : Oracle, Confidential
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Address S_ADDR_PER
Agreement S_DOC_AGREE
Event S_EVT_ACT
Issue S_ISS
Opportunity S_OPTY
Product S_PROD_INT
Quote S_DOC_QUOTE
Territory S_ASGN_GRP
162 Siebel Data Model Reference for Industry Applications Version 8.1
Title : Opportunity Management
Author : Oracle, Confidential
ADDRESS
for for
located at
in partnership with a partner to a report to a parent to located at
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
Logical Model ■ Entity Relationship Diagrams and Descriptions
Table 68 lists the entities in this ERD and their corresponding tables.
Entity Table
Invoice S_INVOICE
Opportunity S_OPTY
Order S_ORDER
Quote S_DOC_QUOTE
164 Siebel Data Model Reference for Industry Applications Version 8.1
Title : Order Life Cycle
Author : Oracle, Confidential
ACCOUNT
for
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
PRODUCT OR SERVICE
16 5
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Activity S_EVT_ACT
Asset S_ASSET
Order S_ORDER
166 Siebel Data Model Reference for Industry Applications Version 8.1
Title : Orders
Author : Oracle, Confidential
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
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
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Collaboration S_PARTY_GROUP
Party S_PARTY
Position S_POSTN
168 Siebel Data Model Reference for Industry Applications Version 8.1
1
Oracle,
.&%$%%$% $""".
.&%$%%$% $
+
Figure 71. Partner Collaboration
3
$[$&$
''.$%9!%&
%$ 3
%9!%$* ''.$
$$'0$
$[$
%9!
$[$* ''.$
''.$
1
"%%
''.$$>$
14
13
9
$[O$
&$
9"%%
9+
16 9
Logical Model ■ Entity Relationship Diagrams and Descriptions
Table 71 lists the entities in this ERD and their corresponding tables.
Entity Table
Partner S_ORG_EXT
170 Siebel Data Model Reference for Industry Applications Version 8.1
Oracle,
'$
&
$
"
14
'&"
14
"<
%
"$
2 2
''% 9 !!$!
"
$
"' $
6
14
.%
"
>''%
14
'
.'+'%
14
' $
>'" $;'%
14
6
%$
"" '
'
+
17 1
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Group S_PARTY
Party S_PARTY
172 Siebel Data Model Reference for Industry Applications Version 8.1
Logical Model ■ Entity Relationship Diagrams and Descriptions
%$'$%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 lists the entities in this ERD and their corresponding tables.
Entity Table
Invoice S_INVOICE
Order S_ORDER
Party S_PARTY
Payment S_SRC_PAYMENT
174 Siebel Data Model Reference for Industry Applications Version 8.1
Logical Model ■ Entity Relationship Diagrams and Descriptions
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
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Competency S_CMPTNCY
Party S_PARTY
Period S_PERIOD
176 Siebel Data Model Reference for Industry Applications Version 8.1
Logical Model ■ Entity Relationship Diagrams and Descriptions
Entity Table
178
Oracle
*"$ "%&"$"
>;"
6
"$ +
2 3
|}~>'&$ >;"' "$$
3
>; "$$
Figure 75. Performance Review
213
?
2
>'&$%
14
>; >;$
$
% ' >; "$$
1
313 "$$ +
'$
&
"'+*"$
"%&"$
1
>;"'
"'+ ! >;
*"$ >;
+
%$
14
9%$
2
14
$[$&$
$$'0$
"'+0
$ %$
$[$
13
313
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Activity S_EVT_ACT
Opportunity S_OPTY
Product S_PROD_INT
user of
used by
for party on
source of
defined for
source of applicable to
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
180 Siebel Data Model Reference for Industry Applications Version 8.1
Logical Model ■ Entity Relationship Diagrams and Descriptions
Table 76 lists the entities in this ERD and their corresponding tables.
Entity Table
Activity S_EVT_ACT
Opportunity S_OPTY
Product S_PROD_INT
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
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
Table 77 lists the entities in this ERD and their corresponding tables.
Entity Table
Objective S_SRC
Offer S_DMND_CRTN_PRG
Period S_PERIOD
Position S_PARTY, S_POSTN
Product S_PROD_INT
184
for
MESSAGING
PRODUCT
PLAN associated to
has
parent of
ASSESSMENT TEMPLATE
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
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Opportunity S_OPPTY
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
PRODUCT
EXTENDED for
TIER PRICE VALUE ATTRIBUTE
described by
subject of
for based on classified as
have types
of
186 Siebel Data Model Reference for Industry Applications Version 8.1
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
188
Author : Oracle, Confidential
for PRODUCT OR
an assembly of
adjusted via SERVICE of
STRUCTURE
PRICE LIST of a component of
ITEM
subject of
PRICE LIST
for
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
Logical Model ■ Entity Relationship Diagrams and Descriptions
of object class
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 lists the entities in this ERD and their corresponding tables.
Entity Table
190
Author : Oracle, Confidential
PRODUCT PROMOTION ITEM ATTRIBUTE PRODUCT PROMOTION PRICING MATRIX RULE for ADJUSTMENT GROUP
VALUE
contain
PRODUCT
PRODUCT PROMOTION
Table 81 lists the entities in this ERD and their corresponding tables.
Entity Table
Activity S_EVT_ACT
Project S_PROJ
192
Author : Oracle, Confidential
OTHER
PROJECTS
OTHER
reported for planned to in environment of reported by owned by ORGANIZATION
be fixed in UNIT
owner of
PERSON
part of
Logical Model ■ Entity Relationship Diagrams and Descriptions
PRODUCT OR SERVICE
target EXTERNAL PRODUCT
afflicted fix for
with a component of an assembly of
actual fix for
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Communication S_COMMUNICATION
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
194 Siebel Data Model Reference for Industry Applications Version 8.1
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Catalog S_CTLG
Language S_LANG
196
Author : Oracle, Confidential
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
of
PRODUCT OR SERVICE
an a
assembly component described subject subject
part of categorized in of of via of of translated
subject of into
Logical Model ■ Entity Relationship Diagrams and Descriptions
a report to
produced by VENDOR
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Activity S_EVT_ACT
Address S_ADDR_PER
Invoice S_INVOICE
Opportunity S_OPTY
Organization Unit S_ORG_EXT, S_PARTY
Project S_PROJ
Skill S_PROJRSRC_SKL
198
Author : Oracle, Confidential
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
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
Logical Model ■ Entity Relationship Diagrams and Descriptions
for
INTERNAL/PARTNER OTHER
subcontracted to the client of ORGANIZATION ORGANIZATION
UNIT
responsibility of a partner for
responsible for
accessible to
accessor of
■ 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 lists the entities in this ERD and their corresponding tables.
Table 85. Public Sector Case Lead Management ERD Entities and Tables
Entity Table
PARTY S_PARTY
ACTIVITY S_EVT_ACT
DISEASE S_DISEASE
INCIDENT S_INCIDENT
Table 85. Public Sector Case Lead Management ERD Entities and Tables
Entity Table
APPLICATION S_PS_APPL
200 Siebel Data Model Reference for Industry Applications Version 8.1
Title : Public Sector Case Lead Management PERSON DESCRIPTION
Author : Oracle, Confidential
has
for
EVIDENCE / SUPPORTING DOCUMENT
APPLICATION supported by INCIDENT
ATTACHMENT
for supported by
related to
CASE
based on basis for serviced through
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
related to
PERSON
ORGANIZATION/GROUP POSITION
responsibility of
AGENCY OTHER AGENT SUSPECT
OTHER SUSPICIOUS
ORGANIZATION GROUP responsible for PERSON
20 1
Logical Model ■ Entity Relationship Diagrams and Descriptions
Table 86 lists the entities in this ERD and their corresponding tables.
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
202 Siebel Data Model Reference for Industry Applications Version 8.1
1%
3
Oracle
6
>%
613
$[$0
&
%%&$
$ + 9% *$+
2
+
$
20 3
Logical Model ■ Entity Relationship Diagrams and Descriptions
Table 87 lists the entities in this ERD and their corresponding tables.
Table 87. Public Sector Evidence Management ERD Entities and Tables
Entity Table
PARTY S_PARTY
ORGANIZATION/GROUP S_ORG_EXT
POSITION S_POSTN
ADDRESS S_ADDR_PER
QUOTE S_DOC_QUOTE
ORDER S_ORDER
SERVICE REQUEST S_SRV_REQ
ACTIVITY S_EVT_ACT
INCIDENT S_INCIDENT
CASE S_CASE
204 Siebel Data Model Reference for Industry Applications Version 8.1
1%
2"
Oracle
%>
13 7&% 2
$>%
>
2
'!
$ !$
>+
2 1
13
6
6
1
1
213
13
13
14
!!%%
9+% '
.=
9
$ + 9&%9'! %$
1
$ %&% 9%$
$[$
13
%&% &%
&
20 5
Logical Model ■ Entity Relationship Diagrams and Descriptions
Table 88 lists the entities in this ERD and their corresponding tables.
Table 88. Public Sector Incident Management ERD Entities and Tables
Entity Table
INCIDENT S_INCIDENT
PARTY S_PARTY
ORGANIZATION/GROUP S_ORG_EXT
INJURY S_INCTCON_INJRY
CIRCUMSTANCE S_CIRCUMSTANCE
ACTIVITY S_EVT_ACT
ARREST S_ARREST
OFFENSE S_OFFENSE
206 Siebel Data Model Reference for Industry Applications Version 8.1
1%
" **$% "$' >+
Oracle
**$%
$ !$
13
14
14
2
2
2
2
6
+
$[$0
& %$
20 7
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Agreement S_DOC_AGREE
Invoice S_INVOICE
Opportunity S_OPTY
Project S_PROJ
208 Siebel Data Model Reference for Industry Applications Version 8.1
Title : Revenue
Author : Oracle, Confidential
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
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
Logical Model ■ Entity Relationship Diagrams and Descriptions
Table 90 lists the entities in this ERD and their corresponding tables.
Table 90. Routes and Best Call Hours ERD Entities and Tables
Entity Table
Route S_ACCNTRT
210 Siebel Data Model Reference for Industry Applications Version 8.1
Logical Model ■ Entity Relationship Diagrams and Descriptions
part of
EXTERNAL ORGANIZATION
made up of
SYNDICATE GROUP
RETAILER
STORE
Table 91 lists the entities in this ERD and their corresponding tables.
Table 91. Sales Hierarchy and Credit Assignment ERD Entities and Tables
Entity Table
212 Siebel Data Model Reference for Industry Applications Version 8.1
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
subject of version of
parent of version of
OTHER PARTY
SALES HIERARCHY
21 3
Logical Model ■ Entity Relationship Diagrams and Descriptions
Table 92 lists the entities in this ERD and their corresponding tables.
Entity Table
Category S_CTLG_CAT
Period S_PERIOD
214 Siebel Data Model Reference for Industry Applications Version 8.1
Logical Model ■ Entity Relationship Diagrams and Descriptions
have
SUPPLIER
for an
at
AUTHORIZED AUTHORIZED
PRODUCT DETAIL PRODUCT subject of
for STORE
subject of
RETAILER
SYNDICATE
GROUP
OTHER
PRODUCT MOVEMENT
part of ORGANIZATION
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Call S_EVT_ACT
216 Siebel Data Model Reference for Industry Applications Version 8.1
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
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
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Agreement S_DOC_AGREE
Asset S_ASSET
Material S_PROD_INT
Order S_ORDER
Product S_PROD_INT
218 Siebel Data Model Reference for Industry Applications Version 8.1
Title : Agreement Entitlement
Author : Oracle, Confidential
for PRODUCT
PRICE ADJUSTMENT
subject of
based on
ENTITLED PRODUCT OR ASSET for
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
21 9
Logical Model ■ Entity Relationship Diagrams and Descriptions
Table 95 lists the entities in this ERD and their corresponding tables.
Table 95. Service Calendars and Work Shifts ERD Entities and Tables
Entity Table
220 Siebel Data Model Reference for Industry Applications Version 8.1
Logical Model ■ Entity Relationship Diagrams and Descriptions
EMPLOYEE
EXCEPTION
HOURS
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Activity S_EVT_ACT
222 Siebel Data Model Reference for Industry Applications Version 8.1
made up of part of
Title : Service Request
Author : Oracle, Confidential
ACTIVITY
SERVICE REQUEST ACTIVITY OTHER ACTIVITY
for responsibility of
responsibility of
part of
made up of subject of
PERSON
Figure 97. Service Request
responsible for
responsible for
OTHER PERSON
reported by
reporter of
OTHER PARTY
at
22 3
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Shipment S_SHIPMENT
224 Siebel Data Model Reference for Industry Applications Version 8.1
%
Oracle
13
!">"$
!&
613 $$'
%9"$'$"
3
">"$
!"!'>+"% +
3
Figure 98. Shipment
9">"$
7&"
!'>+
!" 7&"
"%
!'>+7&% !'>+7&%
13
1
232
213
!
1
7&
1
$>$+' $
22 5
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Activity S_EVT_ACT
Assessment S_ASSESS
226 Siebel Data Model Reference for Industry Applications Version 8.1
Title : Siebel Assistant
Author : Oracle, Confidential
part of made up of
a component of
for instance of
ASSESSMENT
for
container of made up of instantiated as of
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
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Period S_PERIOD
Plan S_INS_PLAN
Product S_PROD_INT
Region S_REGION
Territory S_ASGN_GRP
228 Siebel Data Model Reference for Industry Applications Version 8.1
Title : Syndicated Data
Author : Oracle, Confidential
for AREA
SYNDICATED DATA
PERIOD subject of
for
in SALES
Figure 100.Syndicated Data
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
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Activity S_EVT_ACT
Bait S_FN_BAIT
Container S_FN_CONTAINER
230 Siebel Data Model Reference for Industry Applications Version 8.1
Title : Teller Administration
Author : Oracle, Confidential
LIMITS
ACTIVITY
EMPLOYEE TRANSACTION CONTAINER
TELLER LIMITS LIMITS LIMITS
to
for
for for
BAIT/TRAP
has
used by
BRANCH
23 1
Logical Model ■ Entity Relationship Diagrams and Descriptions
Table 101 lists the entities in this ERD and their corresponding tables.
Entity Table
Territory S_TERRITORY
Period S_PERIOD
232 Siebel Data Model Reference for Industry Applications Version 8.1
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&
23 3
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Account S_ORG_EXT
Asset S_ASSET
Contact S_CONTACT
Division S_ORG_EXT
Position S_POSTN
Position Territory Assignment S_TERR_POSITION
Region S_REGION
Territory S_TERRITORY
Zipcode (None)
234 Siebel Data Model Reference for Industry Applications Version 8.1
3"
Oracle
+
%$+
%%
$"$
13
+"$
$ """.
+
Figure 103.Territory Management
>%$
2
&$""".
13
9 '
%%" $
"".
[ ! +
9 9+
13
&$
$ 13
13
.&%$%%&$
%%
@13
1
%$ !>%$
13 9!>%$ %'%*
23 5
Logical Model ■ Entity Relationship Diagrams and Descriptions
Table 103 lists the entities in this ERD and their corresponding tables.
Entity Table
Account S_ORG_EXT
Activity S_EVT_ACT
Contact S_CONTACT
Division S_ORG_EXT
Position S_POSTN
Territory S_TERRITORY
236 Siebel Data Model Reference for Industry Applications Version 8.1
3"^% %{
Oracle
%$+%%
$"$ +
13
14
>+ +>%$ 2
+
%$
'
14
'
+ &$
&$0 $ 0
"$
"$
Figure 104.Territory Management - Consumer Sector
&$"'
+
$ """.
9 9+
14
14
14
13
%$' &$"
"".
13
$ .&%$%%&$
23 7
Logical Model ■ Entity Relationship Diagrams and Descriptions
Table 104 lists the entities in this ERD and their corresponding tables.
Entity Table
Account S_ORG_EXT
Asset S_ASSET
Contact S_CONTACT
Division S_ORG_EXT
Position S_POSTN
Region S_REGION
Territory S_TERRITORY
Territory Alignment S_TERRALGN
Zipcode (None)
238 Siebel Data Model Reference for Industry Applications Version 8.1
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$
$!$
&$
.&%$%%&$
23 9
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Table 105. Textile, Apparel, and Footwear ERD Entities and Tables
Entity Table
Order S_ORDER
Quote S_DOC_QUOTE
Quote Item S_QUOTE_ITEM
240 Siebel Data Model Reference for Industry Applications Version 8.1
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
24 1
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Activity S_EVT_ACT
Period S_PERIOD
Project S_PROJ
Timesheet S_TMSHT
242 Siebel Data Model Reference for Industry Applications Version 8.1
Title : Time Sheet
Author : Oracle, Confidential
adjusted
ACTIVITY
TIME UNIT
Figure 107.Time Sheet
adjustment
basis for
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
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Note S_NOTE_SRC
Order S_ORDER
244 Siebel Data Model Reference for Industry Applications Version 8.1
Oracle
!"
*&$!
'' $ 14
Figure 108.Trade Promotions
?13
%$
?
&$
"<$
>$ >+ $
13
6
"$'$ "$
!
!&
3
2
"$
&$!& 2
$
!&
!& 8$'
14
14
!& $$'
24 5
Logical Model ■ Entity Relationship Diagrams and Descriptions
Table 108 lists the entities in this ERD and their corresponding tables.
Entity Table
246 Siebel Data Model Reference for Industry Applications Version 8.1
Title : Training Curriculum Course
Author : Oracle, Confidential
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
TRAINING CURRICULUM
part of
composed of
of
categorized into provide training for subject of subject of
Figure 109.Training Curriculum Course
of
COURSE
AVAILABLE
LANGUAGE tracked by
needed by for
CATALOG CATEGORY JOB PROFILE LITERATURE CURRICULUM
PERSON
MARKETING EVENT OR ACTIVITY
based on registered by
instructed by
subject of offered in in need of subject of
subject of instructor of enrolled in
TRAINING COURSE
24 7
Logical Model ■ Entity Relationship Diagrams and Descriptions
Table 109 lists the entities in this ERD and their corresponding tables.
Entity Table
Topic/Objective S_CRSE_TOPIC
248 Siebel Data Model Reference for Industry Applications Version 8.1
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
$!>!&'%%
$$
%
14
7&%$ 0.= >
+
>$' $
6
&%0 &%**$
%
14
"<$
>$ >+ !& %>
1
$$
&%**$
$$
&%
1
9"<$
>$ >+ 9!& %>
24 9
Logical Model ■ Entity Relationship Diagrams and Descriptions
Table 110 lists the entities in this ERD and their corresponding tables.
Entity Table
250 Siebel Data Model Reference for Industry Applications Version 8.1
&2
"
Oracle
.&
&
.& 1
*'!"$
&'%
&&'
.&
&&!9%+
& "!!%%
Figure 111.Universal Customer Master
& "%%
%+*'!.=
8$'$*"$%+%" +
%$
$[$ 9&%9'!
25 1
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Asset S_ASSET
Features S_PROD_SPEC
Option S_PROD_REL
Product S_PROD_INT
Specifications S_PROD_SPEC
252 Siebel Data Model Reference for Industry Applications Version 8.1
Title : Vehicle
Author : Oracle, Confidential
belong to PERSON
FINANCIAL DETAIL
owner of
of of for EMPLOYEE
of
Figure 112.Vehicle
SALES HISTORY
involved in
visible to for
for performed by
of
OTHER
PERSON
Subject of SERVICE REQUEST reported by
for reporter of
composed of INSTALLED
routed to
made into OPTION
of
VEHICLE contains
OPTION
PRODUCT
belongs to
secondarily composed of FEATURES
for
DEALER / PARTNER
OTHER ORGANIZATION
a parent to
a report to
25 3
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
254 Siebel Data Model Reference for Industry Applications Version 8.1
BANKRUPTCY SERVICE REQUEST PROMISE TO PAY VEHICLE INSURANCE
* CASE_NUM * SEQ_NUM * EFF_START_DT
IMPOUND NOTIFICATION
OTHER FINANCIAL
ACCOUNT
assigned to
insured by
ASSET
OTHER VEHICLE
ASSET
PARTY
work on work on insure for
PERSON ORGANIZATION
25 5
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Asset S_ASSET
Contract S_DOC_AGREE
Product S_PROD_INT
256 Siebel Data Model Reference for Industry Applications Version 8.1
ASSET
Title : Vehicle Financing
Author : Oracle, Confidential
in context VEHICLE
SERVICE
REQUEST subject
of
INSPECTION CHARGE
# SEQ_NUM
in context of
subject of for
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
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
25 7
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
258 Siebel Data Model Reference for Industry Applications Version 8.1
Title : Vehicle Sales
Author : Oracle, Confidential
VEHICLE SALE
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
Logical Model ■ Entity Relationship Diagrams and Descriptions
Table 115 lists the entities in this ERD and their corresponding tables.
Entity Table
260 Siebel Data Model Reference for Industry Applications Version 8.1
Title : Versioned Object Definition
Author : Oracle, Confidential
for
have
have ITEM
26 1
Logical Model ■ Entity Relationship Diagrams and Descriptions
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 lists the entities in this ERD and their corresponding tables.
Entity Table
Asset S_ASSET
Order S_ORDER
Product S_PROD_INT
262 Siebel Data Model Reference for Industry Applications Version 8.1
Title : Warranty
Author : Oracle, Confidential
part of by
Figure 117.Warranty
PRODUCT of
WARRANTY
COVERAGE subject of
part of vended by
by
composed of
ORDER
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
Logical Model ■ Entity Relationship Diagrams and Descriptions
264 Siebel Data Model Reference for Industry Applications Version 8.1
4 Physical Model
The Siebel physical model encompasses the tables, their columns, and their indexes. This chapter
covers the following topics.
PREFIX Table names in Siebel Business Applications have a one- to three-letter prefix (EIM_,
S_, W_, and so on) to distinguish them from other tables in your application.
NAME A unique table name that is generally an abbreviation of the entity supertype name.
SUFFIX A supertype name may be followed by the entity subtype. For example, the supertype
EVT (event) has ACT (activity) as one of its subtypes. Thus, the name becomes
S_EVT_ACT.
The prefix indicates the part of the Siebel schema to which a table belongs. Table 117 provides some
of the prefixes and their descriptions.
Prefix Meaning
S_ Siebel base table. (Exception: Tables with names of the form S_<name>_IF are
obsolete interface tables.)
The suffix indicates a table type. Table 118 provides some of the suffixes and their descriptions.
Suffix Meaning
_REL A table that supports a many-to-many relationship from an entity back to itself.
_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.
266 Siebel Data Model Reference for Industry Applications Version 8.1
Physical Model ■ Data Model Naming Conventions
Unique or
Suffix Value Not 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.
Suffix Value
_CD The column value is based on the contents of the List of Values (LOV).
_FLG This column contains a Boolean value where Y indicates Yes or True; N indicates No
or False.
Suffix Value
Siebel System Field One of the Siebel Enterprise Applications system fields described in
Table 126 on page 272.
268 Siebel Data Model Reference for Industry Applications Version 8.1
Physical Model ■ Data Model Type Definitions
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.
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.
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_'.
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.
270 Siebel Data Model Reference for Industry Applications Version 8.1
Physical Model ■ Data Model Type Definitions
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 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.
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.
272 Siebel Data Model Reference for Industry Applications Version 8.1
Physical Model ■ INTEGRATION_ID Columns
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.
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.
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.
Dates Dates must be in the range of January 1, 1753 to December 31, 4712.
274 Siebel Data Model Reference for Industry Applications Version 8.1
Physical Model ■ Party Model Unifies Access to Data
Table 128. S_PARTY Extension Tables and Corresponding EIM Interface Tables
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).
3 In the Name column, enter the name of the table for which the report is to be generated, and
press Enter.
6 Select the output format for the report from the drop-down list.
NOTE: For more information about generating reports, see Siebel Reports Administration Guide.
276 Siebel Data Model Reference for Industry Applications Version 8.1
5 Schema Changes
This chapter lists the table, table column and table index changes in this version of the schema:
278 Siebel Data Model Reference for Industry Applications Version 8.1
Schema Changes ■ Table Changes in This Version
280 Siebel Data Model Reference for Industry Applications Version 8.1
Schema Changes ■ Table Column Changes in This Version
282 Siebel Data Model Reference for Industry Applications Version 8.1
Table 131. New Table Columns in This Version
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
283
Table 131. New Table Columns in This Version
2 84
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
285
Table 131. New Table Columns in This Version
2 86
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
287
Table 131. New Table Columns in This Version
2 88
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
289
Table 131. New Table Columns in This Version
2 90
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
TYPE
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
291
Table 131. New Table Columns in This Version
2 92
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
293
Table 131. New Table Columns in This Version
2 94
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
295
Table 131. New Table Columns in This Version
2 96
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
297
Table 131. New Table Columns in This Version
2 98
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
CD
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
299
Table 131. New Table Columns in This Version
3 00
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
301
Table 131. New Table Columns in This Version
3 02
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
303
Table 131. New Table Columns in This Version
3 04
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
305
Table 131. New Table Columns in This Version
3 06
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
307
Table 131. New Table Columns in This Version
3 08
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
309
Table 131. New Table Columns in This Version
3 10
Data LOV
Table Column Opt Type Len Prec Scale Def LOV Type Bnd
Type of Previous
Table Name Column Change Value New Value
■ “Table Index That Was Deleted from This Version” on page 318
■ A indicates active.
■ U indicates unique.
312 Siebel Data Model Reference for Industry Applications Version 8.1
Schema Changes ■ Table Index Changes in This Version
314 Siebel Data Model Reference for Industry Applications Version 8.1
Schema Changes ■ Table Index Changes in This Version
316 Siebel Data Model Reference for Industry Applications Version 8.1
Schema Changes ■ Table Index Changes in This Version
318 Siebel Data Model Reference for Industry Applications Version 8.1
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
320 Siebel Data Model Reference for Industry Applications Version 8.1
Index ■ E
322 Siebel Data Model Reference for Industry Applications Version 8.1
Index ■ F
324 Siebel Data Model Reference for Industry Applications Version 8.1
Index ■ L
326 Siebel Data Model Reference for Industry Applications Version 8.1
Index ■ R
328 Siebel Data Model Reference for Industry Applications Version 8.1
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
330 Siebel Data Model Reference for Industry Applications Version 8.1