dmr

Siebel Data Model ReferenceVersion 8.1November 2008

Copyright 2005, 2008, Oracle. All rights reserved.

The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.

The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.

PRODUCT MODULES AND OPTIONS. This guide contains descriptions of modules that are optional and for which you may not have purchased a license. Siebels Sample Database also includes data related to these optional modules. As a result, your software implementation may differ from descriptions in this guide. To find out more about the modules your organization has purchased, see your corporate purchasing agent or your Oracle sales representative.

If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS. Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.

ContentsSiebel Data Model Reference 1

Chapter 1: Whats New in This Release

Chapter 2: Data Model Overview

Chapter 3: Logical ModelEntity Relationship Diagram Conventions 11

General Entities 12Exclusive Arc Relationship 12Recursive Relationship 13

Entity Relationship Diagrams and Descriptions 14Account 18Adjustment Group 21Asset Management 23Auction 25Auto Email Response Generator 27CG Promotion Planning 29Compensation Planning Administration 32Compensation Planning Execution 34Competency Management System 36Content Management 38Contract Conditions 40Contracts 42Data Visibility 44Dun & Bradstreet Integration 47Employee KPI 49Expense Reports 51Field Service Inventory 53Field Service Scheduler 55Forecasts 57High Tech Marketing Development Fund 59Invoicable Charges 61Invoices 63Lead Management 65Marketing Budget Request 68Marketing Campaign 70Siebel Data Model Reference Version 8.1 3

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

Contents Chapter 4: Physical ModelData Model Naming Conventions 157

Table Naming Conventions 157Index Naming Conventions 159Column Naming Conventions 159Abbreviations Used in the Physical Model Listings 160

Data Model Type Definitions 160Table Type Definitions 161Table Status Definitions 162Column Type Definitions 163Domain Type Definitions 163

Columns of Numeric Physical Type 164

Siebel System Fields 164

INTEGRATION_ID Columns 165

Include Only Field 165

Siebel Repository 165

Database Schema Version 166

Limit Checking for Data Types 166

Validating the Siebel Schema 166

Party Model Unifies Access to Data 167

Generating a Report about Tables 167

Chapter 5: Schema ChangesTable Changes in This Version 169

New Tables in This Version 169Changed Tables in This Version 171

Table Column Changes in This Version 172New Table Columns in This Version 172Changed Table Columns in This Version 181

Table Index Changes in This Version 181New Table Indexes in This Version 181Changed Table Indexes in This Version 183Table Indexes That Were Deleted from This Version 183

IndexSiebel Data Model Reference Version 8.1 5

Contents Siebel Data Model Reference Version 8.16

1 Whats New in This ReleaseWhats New in Siebel Data Model Reference, Version 8.1Table 1 lists changes described in this version of the documentation to support release 8.1 of the software.

Table 1. Whats New in Siebel Data Model Reference, Version 8.1

Topic Description

Lead Management on page 65. Lead management is a new addition to Siebel Marketing that provides an explicit lead-management process within Customer Relationship Management. It improves the alignment between marketing and sales processes.

Marketing Event Driven Dialogue on page 76

This new feature is designed to enable timely communication with customers and deliver sales, marketing, and services planned for their specific needs.

Table Changes in This Version on page 169.

A listing of the table changes in this schema, including the new tables and changes to the existing table definitions.

Table Column Changes in This Version on page 172.

A listing of the column changes in this schema, including the new columns and changes to the existing column definitions.

Table Index Changes in This Version on page 181.

A listing of the index changes in this schema, including the new indexes, deleted indexes, and changes to the existing index definitions.Siebel Data Model Reference Version 8.1 7

Whats New in This Release Siebel Data Model Reference Version 8.18

2 Data Model OverviewOracles Siebel Data Model defines how the data used by Siebel Business Applications is stored in a standard relational DBMS such as Oracle, DB2, or Microsoft SQL Server. The Siebel Data Model also defines some of the data integrity constraints validated by Siebel Business Applications.

NOTE: The terms and conditions of your license agreement with Oracle permits use only of those portions of the Siebel Data Model that correspond to the Siebel products you have purchased. You are not entitled to use any portion of the Siebel Data Model to support Siebel products for which you have not purchased the required licenses.

The Siebel Data Model is designed for speed and performance in data entry, running limited scope queries, and managing processes like call scripting. These tasks are considered transactions, and the database used is called an online transaction processing (OLTP) database.

Optimizing a database used for these purposes requires a design, or schema, that puts each unit of information in a single location in the database. This allows you to update the data efficiently, since you do not have to update the same unit of data in several different locations. Most tables in an OLTP database have links, or join paths, to other tables, sometimes to many other tables.

The database design used in an OLTP database is usually normalized. There are several levels of database normalization, ranging from first to fifth normal form. The Siebel database is in third normal form.

The information in this reference is intended as an aid in configuring and using Siebel Business Applications.

CAUTION: Do not attempt to insert or update data in the Siebel Business Applications tables through non-Siebel application products. Doing so can render your Siebel database unusable; additionally, you limit the ability of Oracle to provide you with quality support.

To learn how to configure an application to insert, update, and delete data interactively, read the Siebel Developers Reference. To learn how to insert, update, and delete data in large quantities, see Siebel Enterprise Integration Manager Administration Guide.

NOTE: The Siebel Bookshelf is available on Oracle Technology Network (OTN) and Oracle E-Delivery. It might also be installed locally on your intranet or on a network location.Siebel Data Model Reference Version 8.1 9

Data Model Overview Siebel Data Model Reference Version 8.110

3 Logical ModelThe Siebel logical model represents the following in Siebel Business Applications:

Entities

Relationships between entities

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

Oracle has made and continues to make a significant investment in modeling the business functions of sales, marketing, and service organizations. The entity relationship diagrams included in this chapter represent the logical model for the current release of Siebel Business Applications. In some areas, the model extends beyond the current implementation. Published entities, therefore, might appear in the logical model that may not be implemented in the physical model at the present time.

The ERDs included in this publication are those that are the most useful to individuals involved in implementing or integrating Siebel Business Applications. These diagrams cover the application areas that are most relevant to a functional understanding of the application.

The information on ERDs is organized as follows:

Entity Relationship Diagram Conventions

Entity Relationship Diagrams and Descriptions on page 14

Entity Relationship Diagram ConventionsThis topic describes entity relationship diagram conventions, as follows:

General Entities on page 12

Exclusive Arc Relationship on page 12

Recursive Relationship on page 13Siebel Data Model Reference Version 8.1 11

Logical Model Entity Relationship Diagram ConventionsGeneral EntitiesFigure 1 shows the diagram conventions for general entities used in this publication.

Exclusive Arc RelationshipFigure 2 illustrates an example of the exclusive arc relationship. An exclusive arc is an arc across two or more relationship ends; you can read each exclusive arc relationship as follows:

Figure 1. General Entity Relationship Diagram ConventionsSiebel Data Model Reference Version 8.112

Logical Model Entity Relationship Diagram ConventionsEach [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 RelationshipFigure 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.

Figure 2. Exclusive Arc Relationship Diagram Convention Example

Figure 3. Recursive Relationship Diagram Convention Example

Activity

Entity Relationship Example:

1) Each activity may by made up of one or more activities.2) Each activity may be part of one and only one activity.

Part of

Made up ofSiebel Data Model Reference Version 8.1 13

Logical Model Entity Relationship Diagrams and DescriptionsEntity Relationship Diagrams and DescriptionsERDs represent the significant entities and relevant relationships in a functional area. To enhance their readability, the diagrams do not include every relationship and subtype. Some many-to-many relationships have also been preserved instead of showing them as one-to-many relationships around intersection tables in the logical model.

Table 2 provides a list of ERDs in alphabetic order.

Table 2. Entity Relationship Diagrams

ERD NameFigure Num. and Page Functional Area

Revised in 8.1

Newin 8.1

Account Figure 4 on page 20

General No No

Adjustment Group Figure 5 on page 22

General No No

Asset Management Figure 6 on page 24

General No No

Auction Figure 7 on page 26

General No No

Auto Email Response Generator Figure 8 on page 28

General No No

CG Promotion Planning Figure 9 on page 31

Marketing No No

Compensation Planning Administration Figure 10 on page 33

ERM No No

Compensation Planning Execution Figure 11 on page 35

ERM No No

Competency Management System Figure 12 on page 37

ERM No No

Content Management Figure 13 on page 39

General No No

Contract Conditions Figure 14 on page 41

General No No

Contracts Figure 15 on page 43

General No No

Data Visibility Figure 16 on page 46

General No No

Dun & Bradstreet Integration Figure 17 on page 48

Sales/Marketing No NoSiebel Data Model Reference Version 8.114

Logical Model Entity Relationship Diagrams and DescriptionsEmployee KPI Figure 18 on page 50

ERM No No

Expense Reports Figure 19 on page 52

General No No

Field Service Inventory Figure 20 on page 54

Service No No

Field Service Scheduler Figure 21 on page 56

Service No No

Forecasts Figure 22 on page 58

Sales/Marketing No No

High Tech Marketing Development Fund Figure 23 on page 60

Marketing No No

Invoicable Charges Figure 24 on page 62

Service No No

Invoices Figure 25 on page 64

Service No No

Lead Management Figure 26 on page 67

Sales/Marketing No Yes

Marketing Budget Request Figure 27 on page 69

Marketing No No

Marketing Campaign Figure 28 on page 71

Marketing No No

Marketing Collaboration Figure 29 on page 73

Marketing No No

Marketing Encyclopedia Figure 30 on page 75

Sales/Marketing No No

Marketing Event Driven Dialogue Figure 31 on page 77

Marketing No Yes

Marketing Events Figure 32 on page 80

General No No

Marketing Plans Figure 33 on page 82

Marketing No No

Marketing Program Figure 34 on page 85

Marketing No No

Marketing Resource Management: Document

Figure 35 on page 87

Marketing No No



Revised in 8.1

Newin 8.1Siebel Data Model Reference Version 8.1 15

Logical Model Entity Relationship Diagrams and DescriptionsOpportunity Management Figure 36 on page 89

Sales No No

Order Life Cycle Figure 37 on page 91

General No No

Orders Figure 38 on page 93

General No No

Partner Collaboration Figure 39 on page 95

General No No

Partner Program Registration Figure 40 on page 97

General No No

Party Model Figure 41 on page 99

General No No

Payments Figure 42 on page 101

General No No

Performance Review Figure 43 on page 104

ERM No No

Personal Account Figure 44 on page 106

Industry-Specific No No

Personal Financial Review Figure 45 on page 108

Industry-Specific No No

Pricing Comparison Figure 46 on page 110

Energy No No

Pricing Figure 47 on page 112

General No No

Product Promotion Figure 48 on page 114

General No No

Product Quality Tracking Figure 49 on page 116

General No No

Product Recommendation Figure 50 on page 118

General No No

Products or Services Figure 51 on page 120

Service No No

Professional Services Figure 52 on page 122

General No No

Revenue Figure 53 on page 124

General No No



Revised in 8.1

Newin 8.1Siebel Data Model Reference Version 8.116

Logical Model Entity Relationship Diagrams and DescriptionsSales Hierarchy and Credit Assignment Figure 54 on page 126

Sales No No

Sales Portfolio Management Figure 55 on page 128

Sales No No

Service Agreement Figure 56 on page 130

Service No No

Service Calendars and Work Shifts Figure 57 on page 132

Service No No

Service Request Figure 58 on page 134

Service No No

Shipment Figure 59 on page 136

General No No

Siebel Assistant Figure 60 on page 138

General No No

Territory Management Figure 61 on page 140

Sales No No

Territory Quota Rollup Figure 62 on page 142

Sales No No

Textile, Apparel, and Footwear Figure 63 on page 144

Consumer Sector No No

Time Sheet Figure 64 on page 146

General No No

Trade Promotions Figure 65 on page 148

General No No

Training Curriculum Course Figure 66 on page 150

General No No

Training Test Engine Figure 67 on page 152

General No No

Versioned Object Definition Figure 68 on page 154

General No No

Warranty Figure 69 on page 156

Service No No



Revised in 8.1

Newin 8.1Siebel Data Model Reference Version 8.1 17

Logical Model Entity Relationship Diagrams and DescriptionsAccountFigure 4 shows the Account ERD. The account entity is a key entity in the Siebel Data Model. The account entity appears in many diagrams in this publication, and is often referred to as an organization unit.

The account entity is a subtype of party composed of one or more people or contacts. An account is any organization or subset of an organization that can be sold to or serviced. An account might represent a company, a site, a subsidiary, a division, or any other subset of an organization. An account might also represent a governmental agency, club, or other formal or informal group of individuals. Each account might be accessible at one or more addresses.

The account entity supports Global Account Views and Dynamic Hierarchy. This allows a universal

view of all customer interactions. The Global Account Views present accounts in the context of a customizable hierarchy, allowing navigation to parent and child accounts. Roll-up and roll-down functionality gives users access to account-specific information, and aggregate information including child accounts, activities, contacts, opportunities, and the account team.

Dynamic Hierarchy allows the Global Account Views to display a different hierarchy depending on the business unit of the user. Each custom account hierarchy is represented completely in a relationship table. The relationships are then denormalized into a separate table to be used for roll-up support.

Table 3 lists the entities in this ERD and their corresponding tables.

Table 3. Account ERD Entities and Tables

Entity Table

Account S_ORG_EXT, S_PARTY

Account Synonym S_ORG_SYN

Activity S_EVT_ACT

Address S_ADDR_ORG

Assignment Group (Territory) S_ASGN_GRP

Business Unit S_BU, S_ORG_EXT, S_PARTY

Characteristics S_CHRCTR

Dynamic Account Hierarchy S_DYN_HRCHY

Dynamic Account Hierarchy Node S_DYN_HRCHY_REL

Employee/Agent S_EMP_PER, S_CONTACT, S_PARTY

Industry S_INDUST

Market Segment S_MKT_SEG

Party S_PARTY

Payment Term S_PAYMENT_TERM

Person S_CONTACT, S_PARTY

Position S_POSTN, S_PARTYSiebel Data Model Reference Version 8.118

Logical Model Entity Relationship Diagrams and DescriptionsPrice List S_PRI_LST

Sales or Service Team Member S_ACCNT_POSTN

Table 3. Account ERD Entities and Tables

Entity TableSiebel Data Model Reference Version 8.1 19

Logical Model Entity Relationship Diagrams and DescriptionsFigure 4. Account

NA

ME

D H

IER

AR

CH

Y

NA

ME

D H

IER

AR

CH

Y

AC

CO

UN

T

PA

YM

EN

T T

ER

M

AC

CO

UN

T S

YN

ON

YM

IND

US

TR

Y CO

RR

ES

PO

ND

EN

CE

PR

ICE

LIS

T

SA

LES

OR

SE

RV

ICE

T

EA

M M

EM

BE

R

MA

RK

ET

S

EG

ME

NT

DE

CIS

ION

IS

SU

ES

PA

RT

Y

PO

SIT

ION

AC

CO

UN

T

OT

HE

R

PA

RT

YB

US

INE

SS

UN

ITP

ER

SO

N

OT

HE

R P

ER

SO

NE

MP

LOY

EE

/ A

GE

NT

AC

TIV

ITY

AS

SIG

NM

EN

T

GR

OU

P

(TE

RR

ITO

RY

)

AD

DR

ES

S

CH

AR

AC

TE

RIS

TIC

cons

trai

ned

to u

se

aces

sibl

e to

of

mad

e vi

sibl

e th

roug

h

for m

ade

up o

f

a re

port

to

a pa

rent

of

actio

n fo

r

targ

et o

f

clas

sific

atio

n fo

r

type

of

for

part

of

part

icip

ant i

n

targ

et o

f

resp

onsi

ble

for

resp

onsi

bilit

y of

user

cha

ract

eris

tics

for

desc

ribed

in

a re

port

toa

pare

nt o

f

anot

her

nam

e fo

r

know

n as

user

of

curr

ent p

rice

list f

orap

plic

able

to

acce

ss to

for

belo

ng to

addr

esse

d to

part

icip

ate

in

for

loca

ted

at

hold

ers

of

held

by

pay

or p

ayed

by

defa

ult p

aym

ent t

erm

for

com

pose

d of

cont

act o

f

resp

onsi

bilit

y of

resp

onsi

ble

for

Siebel Data Model Reference Version 8.120

Logical Model Entity Relationship Diagrams and DescriptionsAdjustment GroupFigure 5 shows the Adjustment Group ERD. This ERD illustrates the system for managing the various matrices for pricing, compatibility, eligibility, product promotions, and so on. It allows the user to define a matrix, its dimensions, and all of its rules. This new infrastructure allows the adjustment to be any value, not just a price amount.


Table 4. Adjustment Group ERD Entities and Table

Entity Table

Adjustment Group S_ADJ_GROUP

Adjustment Group Dimension S_ADJ_GROUP_DIM

Product Compatibility Matrix Rule S_PRODCOMP_MTRX

Product Eligibility Matrix Rule S_PRODELIG_MTRX

Product Promotion Pricing Matrix Rule S_PROM_PMTRX

Standard Entitlement Pricing Matrix Rule S_STDENTL_PMTRX

Standard Product Pricing Matrix Rule S_STDPROD_PMTRX

Standard Training Pricing Matrix Rule S_STDTRNG_PMTRXSiebel Data Model Reference Version 8.1 21

Logical Model Entity Relationship Diagrams and DescriptionsFigure 5. Adjustment Group

ST

AN

DA

RD

TR

AIN

ING

PR

ICIN

G M

AT

RIX

RU

LE

# M

TR

X_R

ULE

_N

UM

ST

AN

DA

RD

PR

OD

UC

T P

RIC

ING

MA

TR

IX R

ULE

# M

TR

X_R

ULE

_N

UM

ST

AN

DA

RD

EN

TIT

LE

ME

NT

PR

ICIN

G M

AT

RIX

R

ULE

# M

TR

X_R

ULE

_N

UM

PR

OD

UC

T P

RO

MO

TIO

N P

RIC

ING

MA

TR

IX R

ULE

# M

TR

X_R

ULE

_N

UM

PR

OD

UC

T E

LIG

IBIL

ITY

MA

TR

IX R

ULE

# M

TR

X_R

ULE

_N

UM

PR

OD

UC

T C

OM

PA

TA

BIL

ITY

MA

TR

IX R

ULE

# M

TR

X_R

ULE

_N

UM

AD

JU

ST

ME

NT

GR

OU

P

DIM

EN

SIO

N# F

IELD

_N

AM

E

AD

JU

ST

ME

NT

GR

OU

P# A

DJ_G

RO

UP

_N

AM

E

for

conta

in

for

conta

in

for

conta

in

for

conta

in

for

conta

in

for

conta

in

for

conta

inSiebel Data Model Reference Version 8.122

Logical Model Entity Relationship Diagrams and DescriptionsAsset ManagementFigure 6 shows the Asset Management ERD. This ERD illustrates how Siebel Business Applications track instances of assets. Moving counter-clockwise from the lower-right corner, the diagram shows how internal products can be made into assets and associated with an account or a contact to register ownership. Additional relationships between assets and accounts, contacts, and employees are illustrated in the upper-right corner. Additional information such as the related opportunities, the current business or personal address location of the asset, notes, and related assets are shown across the top of the diagram. The left side of the diagram shows the relationships with service requests, activities, and related part movements.


Table 5. Asset Management ERD Entities and Tables

Entity Table

Activity S_EVT_ACT

Activity Part Movement S_ACTPART_MVMT

Asset Contact Relationship S_ASSET_CON

Asset Employee Relationship S_ASSET_EMP

Asset External Organization S_ASSET_ACCNT

Asset Feature S_ASSET_FEA

Asset Modification S_ASSET_TXN

Asset Relationship S_ASSET_REL

Business Address S_ADDR_ORG

Competitive Metric S_CMPT_MTRC

Competitive Product Feature S_CMPT_PROD_FEA

Contact S_CONTACT, S_PARTY

Employee S_EMP_PER, S_CONTACT, S_PARTY

External Product S_PROD_EXT

Internal Product S_PROD_INT

Opportunity S_OPTY

Opportunity Asset S_OPTY_ASSET


Personal Address S_ADDR_PER

Product Instance (Asset) S_ASSET

Service Request S_SRV_REQSiebel Data Model Reference Version 8.1 23

Logical Model Entity Relationship Diagrams and DescriptionsFigure 6. Asset Management

AC

TIV

ITY

PA

RT

MO

VE

ME

NT

AC

TIV

ITY

SE

RV

ICE

R

EQ

UE

ST

AD

DR

ES

S

PE

RS

ON

AL

AD

DR

ES

S

BU

SIN

ES

S

AD

DR

ES

S

NO

TE

CO

MP

ET

ITIV

E

PR

OD

UC

T

FE

AT

UR

E

CO

MP

ET

ITIV

E

ME

TR

IC

OP

PO

RT

UN

ITY

PR

OD

UC

T

INT

ER

NA

L P

RO

DU

CT

NO

N-S

ER

IALIZ

AB

LE

P

RO

DU

CT

SE

RIA

LIZ

AB

LE

P

RO

DU

CT

EX

TE

RN

AL

PR

OD

UC

T

PR

OD

UC

T IN

ST

AN

CE

(A

SS

ET

)

PE

RS

ON

CO

NT

AC

T

EM

PLO

YE

E

OP

PO

RT

UN

ITY

A

SS

ET

AS

SE

T

MO

DIF

ICA

TIO

N

AS

SE

T

RE

LA

TIO

NS

HIP

AS

SE

T

FE

AT

UR

E

AS

SE

T E

MP

LO

YE

E R

ELA

TIO

NS

HIP

AS

SE

T C

ON

TA

CT

RE

LA

TIO

NS

HIP

AS

SE

T E

XT

ER

NA

L O

RG

AN

IZA

TIO

N

EX

TE

RN

AL

OR

GA

NIZ

AT

ION

VE

ND

OR

AC

CO

UN

T

OT

HE

R E

XT

ER

NA

L

OR

GA

NIZ

AT

ION

for

subje

ct of

defined for

subje

ct of

perf

orm

ed o

n

subje

ct of

for

pro

ble

ms w

ith

subje

ct of

for

pro

ble

ms w

ith

subje

ct of

part

of

made u

p o

f

of

moved b

y

of

moved b

y

initia

ted b

y

initia

tor

of

part

of

made u

p o

f

defined for

subje

ct of

locate

d a

t

for

for

subje

ct of

of

cla

ssific

ation for

for

subje

ct of

of

cla

ssific

ation for

for

initia

ted b

y

use o

f

involv

ed in

for

associa

ted w

ith

curr

ently o

wned b

y

ow

ner

of

curr

ently o

wned b

y

ow

ner

of

curr

ently p

ossessed b

y

possessor

of

a c

om

ponent of

an a

ssem

bly

of

insta

nce o

f

made into

child

of

pare

nt

of

pro

duced b

y

vendor

of

to

associa

ted w

ith

of

subje

ct of

to

associa

ted w

ith

of

subje

ct of

of

subje

ct of

to associa

ted w

ith

of

associa

ted w

ith

use o

f

involv

ed in

for

modifie

d b

y

of

initia

tor

of


Logical Model Entity Relationship Diagrams and DescriptionsAuctionFigure 7 shows the Auction ERD. This ERD illustrates how the Siebel Data Model represents the auctioning of goods or services to bidders. An auction item may be a stand-alone offering, or may be a specific instance of an offering of a quantity of product or of a particular asset for sale. An auction item must be listed by a corporate or individual user, but that user may be either internal to or external to the Siebel-owning company. Auction items are displayed to bidders through one or more categories in a catalog. Fulfillment of an auction item to the winning bidders may be tracked through one or more order items. Finally, users may set up watched items, may define alerts, and may rate fellow listers or bidders.


Table 6. Auction ERD Entities and Tables

Entity Table

Asset S_ASSET

Auction Alert Definition S_AUC_ALRT_DEF

Auction Item S_AUC_ITEM

Auction Item Bid S_AUC_BID

Auction Item Promotion S_AUC_ITM_PROMO

Auction Item Watch S_AUC_WATCH

Auction Lister/Bidder Rating S_AUC_RATING

Catalog S_CTLG

Catalog Category S_CTLG_CAT

Catalog Category Item S_CTLG_CAT_PROD, S_CTLGCAT_ASSET, S_CTLG_CAT_AUC

Order S_ORDER

Order Item S_ORDER_ITEM

Party S_PARTY

Person S_CONTACT

Product S_PROD_INT

Triggered Auction Alert Item S_AUC_ALRT

User S_USER, S_CONTACT, S_PARTYSiebel Data Model Reference Version 8.1 25

Logical Model Entity Relationship Diagrams and DescriptionsFigure 7. Auction

ORD

ER

AUCT

ION

LIST

ER/B

IDDE

R RA

TING

TRIG

GER

ED A

UCTI

ON

ITEM

ALE

RT

ORD

ER IT

EM

PART

Y OTH

ER P

ARTY

PERS

ON

OTH

ER P

ERSO

NUS

ER

CATA

LOG

PRO

DUCT AS

SET

CATA

LOG

CAT

EGO

RY IT

EMCA

TALO

G C

ATEG

ORY

AUCT

ION

ITEM

WAT

CH

AUCT

ION

ITEM

PR

OM

OTI

ON

AUCT

ION

ALER

T DE

FINI

TIO

N

AUCT

ION

ITEM

BID

AUCT

ION

ITEM

crea

ted

by

crea

tor o

f

part

of

com

pose

d of

appl

icabl

e to

subj

ect o

f

part

of

mad

e up

of

ratin

g of

subj

ect o

f

mad

e by

crea

tor o

f

plac

ed b

y

plac

er o

f

liste

d by

liste

r of

for

subj

ect o

f for

subj

ect o

f

for

crea

tor o

f

for

alerte

d by

crea

ted

from

gene

sis o

f

for

feat

ured

in

repr

esen

ted

by

disp

layed

as

repr

esen

ted

by

disp

layed

as

crea

ted

from

repr

esen

ted

as

acce

ssed

via

owne

r of

for

owne

r of

prici

ng

mec

hani

sm

for

price

d by

prici

ng

mec

hani

smfo

r

price

d by

fulfil

lmen

t of fu

lfilled

as

for

subj

ect o

f


Logical Model Entity Relationship Diagrams and DescriptionsAuto Email Response GeneratorFigure 8 shows the Auto Email Response Generator ERD. This ERD illustrates the data model for the automatic generation of a response to an inbound communication. Incoming messages (inbound communications) are compared against a database of previously categorized messages to categorize them in one or more categories. The categories are associated with predefined template communication responses, used to generate a default response to each category of message. A notification mechanism can be defined to alert a person whenever the usage of a category or template exceeds a predefined limit.


Table 7. Auto Email Response Generator ERD Entities and Tables

Entity Table

Activity S_EVT_ACT

Catalog S_CTLG

Catalog Category S_CTLG_CAT

Category Usage Notification S_COMM_CTG_NTFY

Communication Template Usage Notification S_COMMTMPL_NTFY


Problem Resolution Document S_RESITEM

Template Communication Response S_DMND_CRTN_PRGSiebel Data Model Reference Version 8.1 27

Logical Model Entity Relationship Diagrams and DescriptionsFigure 8. Auto Email Response Generator

TE

MP

LA

TE

CO

MM

UN

ICA

TIO

N R

ES

PO

NS

E

PR

OB

LE

M

RE

SO

LU

TIO

N

DO

CU

ME

NT

AC

TIV

ITY

OU

TB

OU

ND

RE

SP

ON

SE

INB

OU

ND

CO

MM

UN

ICA

TIO

N

CA

TA

LO

G C

AT

EG

OR

Y

CA

TA

LO

G

PE

RS

ON

CO

MM

UN

ICA

TIO

N T

MP

L U

SA

GE

N

OT

IFIC

AT

ION

CA

TE

GO

RY

U

SA

GE

N

OT

IFIC

AT

ION

for

usage o

f

subje

ct of

cate

gorized w

ithin

cla

ssific

ation for

cla

ssific

ation o

f

defa

ult r

esponse for

cate

gorized u

nder cla

ssific

ation for

part

of

made u

p o

f

part

of

made u

p

to n

otify

targ

et of

to n

otify

targ

et of

for

usage o

f subje

ct of


Logical Model Entity Relationship Diagrams and DescriptionsCG Promotion Planning Figure 9 shows the CG Promotion Planning ERD. This ERD illustrates how Siebel Business Applications support the funding of trade promotions in channel management and the Consumer Goods (CG) industry. Marketing development funds (MDFs) are defined for an account, for a product line or product category, and for an accounting period. An MDF can be a fixed sum of money, an accrual fund, or a mixture of the two. The value of the accrual fund is typically determined based on an accrual rate multiplied by either the number of units sold, or the revenue in a given period from one or more specific products that are representative of the product line or category of the fund. Planned expenses for the various tactics involved in the planning and execution of product promotions can be allocated to one or more MDFs. Allocations that have not yet been approved are considered fund requests. One or more such MDF allocations may be covered by a single payment to the partner account.

Advanced Planning is a feature designed to address the process used by CG organizations to plan sales volume and sales revenue at key accounts. Advanced Planning is part of a broader process called Trade Marketing. Trade Marketing includes planning, executing, and analyzing sales.


Table 8. CG Promotion Planning ERD Entities and Tables

Entity Table

Account S_ORG_EXT, S_PARTY

Authorized Product S_ORG_PROD

Fund Allocation S_MDF_ALLOC

Marketing Development Fund S_MDF

Marketing Event or Activity S_SRC

MDF Accrual S_MDF_ACCRUAL

Payment S_SRC_PAYMENT

Period S_PERIOD


Position S_POSTN, S_PARTY

Price List S_PRI_LST

Price List Item S_PRI_LST_ITEM

Product Internal S_PROD_INT

Product Line S_PROD_LN

Product Structure S_PROD_REL or S_PROD_ITEM

Promotion Plan S_SRC

Promotion S_SRC

Promotion Account S_SRCSiebel Data Model Reference Version 8.1 29

Logical Model Entity Relationship Diagrams and DescriptionsPromotion Product S_SRC

Promotion Category S_SRC

Promotion Account Product S_SRC

Table 8. CG Promotion Planning ERD Entities and Tables

Entity TableSiebel Data Model Reference Version 8.130

Logical Model Entity Relationship Diagrams and DescriptionsFigure 9. CG Promotion Planning

MA

RK

ET

ING

EV

EN

T O

R A

CT

IVIT

Y

PR

OM

OT

ION

PL

AN

PR

OM

OT

ION

AC

CO

UN

T P

RO

DU

CT

PR

OM

OT

ION

AC

CO

UN

T

PR

OM

OT

ION

OT

HE

R M

AR

KE

TIN

G E

VE

NT

OR

A

CT

IVIT

Y

PR

OM

OT

ION

PR

OD

UC

T

PR

OM

OT

ION

CA

TE

GO

RY

PA

YM

EN

T

OT

HE

R P

AY

ME

NT

PR

OM

OT

ION

PA

YM

EN

T

PE

RS

ON

EM

PL

OY

EE

/ A

GE

NT

OT

HE

R P

ER

SO

NP

OS

ITIO

N

AC

CO

UN

T

PR

OD

UC

T L

INE

AU

TH

OR

IZE

D

PR

OD

UC

T

MD

F A

CC

RU

AL

PR

ICE

LIS

T I

TE

M

FU

ND

A

LL

OC

AT

ION

PR

ICE

LIS

T

PR

OD

UC

T

ST

RU

CT

UR

E

MA

RK

ET

ING

D

EV

EL

OP

ME

NT

F

UN

D

MIX

ED

FU

ND

AC

CR

UA

L

FU

ND

FIX

ED

FU

ND

INT

ER

NA

L P

RO

DU

CT

OR

S

ER

VIC

E

PE

RIO

D

sub

allo

cate

d t

o

sub

allo

catio

n o

f

pa

rt o

f

ma

de

of

of

pro

mo

ted

via

de

fine

d f

or

sub

ject

of

use

r o

f

use

d b

y

targ

et

of

ava

ilab

le t

o

de

fine

d f

or

sub

ject

of

to

reci

pie

nt

of

for

sub

ject

of

cove

red

by

for

ass

ign

ed

to

resp

on

sib

le f

or

rela

ted

to

rela

tion

of

ap

pro

ved

by

ap

pro

ver

of

req

ue

ste

d b

y

req

ue

sto

r o

f

of

sub

ject

of

ea

rne

d in

sub

ject

of

ma

de

up

of

pa

rt o

f

at

sub

ject

of

de

sig

na

ted

to

targ

et

of

com

po

sed

of

pa

rt o

f

sub

ject

to

ap

plic

ab

le t

o

ass

ign

ed

to

resp

on

sib

le f

or

for

pro

mo

tion

of

sub

ject

of

ea

rne

d b

ye

arn

er

of

ea

rne

d b

ye

arn

er

of

for

fun

de

d t

hro

ug

h

hie

rarc

hy

child

of

hie

rarc

hy

pa

ren

t o

f

of

sub

ject

of

com

po

sed

of

for

ba

sed

on

ba

sis

for

of

sub

ject

of

de

fine

d f

or

sub

ject

of

an

ass

em

bly

of

for a c

om

po

ne

nt

of

of

for

pro

mo

tion

of

sub

ject

of

Ora

cle

Siebel Data Model Reference Version 8.1 31

Logical Model Entity Relationship Diagrams and DescriptionsCompensation Planning AdministrationFigure 10 shows the Compensation Planning Administration ERD. The administration activities of compensation planning involve setting up salary structures such as salary plan, salary grades, and job codes. In addition to salary structures, an organization sets up compensation budgets, compensation types such as merit increase, bonus, promotion, and stock options, planning periods, budget calculation and eligibility rules, guidelines and calculation of budget allocations for employees.


Table 9. Compensation Planning Administration ERD Entities and Tables

Entity Table

Business Unit S_BU

Compensation Budget Definition S_CP_BDGT

Compensation Budget Item S_CP_BDGT_ITEM

Compensation Budget Item For Employee S_CP_BDGT_EMP

Compensation Cycle Planning Period S_CP_PD_BDGTITM

Compensation Guideline Definition S_CP_GDLN

Compensation Guideline Factor LOV

Compensation Guideline Set S_CP_GDLN_SET

Compensation Guideline Table S_CP_GDLN_TBL

Compensation Planning Period S_CP_PERIOD

Compensation Region S_CP_REGN

Compensation Type LOV

Compensation Valid Effectivity Date S_CP_EFF_DATE

Employee Eligibility S_APP_QUERY (PDQ)

Employee/Agent S_EMP_PER

Job Category LOV

Job Code S_JOB

Job Family S_JOB_FAMILY

Job Profile S_JOB_PRFL

Period S_PERIOD

Salary Grade S_SALARY_GRADE, S_SALPLAN_GRADE

Salary Plan S_SALARY_PLANSiebel Data Model Reference Version 8.132

Logical Model Entity Relationship Diagrams and DescriptionsFigure 10. Compensation Planning Administration

Titl

e : C

ompe

nsat

ion

Pla

nnin

g A

dmin

istr

atio

nA

utho

r : O

racl

e, C

onfid

entia

l

PO

SIT

ION

SA

LAR

Y P

LAN

FO

R

SA

LAR

Y G

RA

DE

JOB

F

AM

ILY

JOB

C

AT

EG

OR

Y

CO

MP

EN

SA

TIO

N

RE

GIO

N

JOB

CO

DE

CO

MP

EN

SA

TIO

N G

UID

ELI

NE

D

EF

INIT

ION

CO

MP

EN

SA

TIO

N T

YP

E

SA

LAR

Y P

LAN

BU

SIN

ES

S U

NIT

PE

RIO

DQ

UA

RT

ER

LY P

ER

IOD

AN

NU

AL

PE

RIO

D

CO

MP

EN

SA

TIO

N

CH

AN

GE

EF

FE

CT

IVIT

Y

DA

TE

CO

MP

EN

SA

TIO

N C

YC

LE P

LAN

NIN

G P

ER

IOD

CO

MP

EN

SA

TIO

N P

LAN

NIN

G P

ER

IOD

EM

PLO

YE

E /

AG

EN

TC

OM

PE

NS

AT

ION

BU

DG

ET

IT

EM

FO

R E

MP

LOY

EE

EM

PLO

YE

E E

LIG

IBIL

ITY

(P

DQ

)

CO

MP

EN

SA

TIO

N B

UD

GE

T IT

EM

CO

MP

EN

SA

TIO

N B

UD

GE

T D

EF

INIT

ION

CO

MP

EN

SA

TIO

N

GU

IDE

LIN

E

FA

CT

OR

CO

MP

EN

SA

TIO

N G

UID

ELI

NE

TA

BLE

CO

MP

EN

SA

TIO

N

GU

IDE

LIN

E S

ET

SA

LAR

Y G

RA

DE

supp

ort

man

age

by

sala

ry p

lan

grad

e de

fined

in fo

r

sala

ry p

lan

for

defin

ed in

sala

ry g

rade

s fo

rha

ve

defin

ed fo

r

used

by

perio

d fo

r

have

part

of

grou

ping

for

cate

goriz

ed

in

cate

gory

for

have

defin

ed fo

r

has

job

code

for

loca

ted

in

com

pens

atio

n lo

catio

n fo

r

sala

ry

grad

e de

fined

in

for

sala

ry

defin

ed

in

for

defin

ed

for

com

pone

nt o

f

type

of

type

for

valu

es fo

r

have 2

fact

or

defin

ed

in

used

in

1 fa

ctor

de

fined

in

used

in

type

of

type

for

cons

trai

ned

by

defin

ed fo

r

budg

et fo

rha

ve

empl

oyed

by

empl

oyer

of

sub-

org

of

com

pose

d of

defin

ed fo

rus

ed in

defin

ed fo

r

used

in

valid

dat

e fo

rha

ve

defin

ed fo

r

user

of

defin

ed fo

rus

ed b

ysu

bjec

t of

cont

aine

r fo

r

allo

cate

d fo

r

has

budg

et a

lloca

tion

for

has

cons

trai

ned

by

defin

ed fo

r

subj

ect o

f

cont

aine

r fo

r

defin

ed

for

com

pone

nt o

f

subj

ect o

f

cont

aine

r fo

r


Logical Model Entity Relationship Diagrams and DescriptionsCompensation Planning ExecutionFigure 11 shows the Compensation Planning Execution ERD. In the execution phase of compensation planning, a workbook is created for each of the authorized managers with the list of employees who report to them. The manager goes through the planning process and decides on the merit, bonus, promotion, and stock option changes that he may grant to his employees. Authorized persons such as managers, or HR personnel approve the plans. Totals are maintained for each manager and organization.


Table 10. Compensation Planning Execution ERD Entities and Tables

Entity Table

Business Unit S_BU

Compensation Budget Definition S_CP_BDGT

Compensation Budget Item S_CP_BDGT_ITEM

Compensation Budget Item For Employee S_CP_BDGT_EMP

Compensation Cycle Planning Period S_CP_PD_BDGTITM

Compensation Guideline Definition S_CP_GDLN

Compensation Guideline Set S_CP_GDLN_SET

Compensation Guideline Table S_CP_GDLN_TBL

Compensation Plan S_CP_PLAN

Compensation Plan Comments S_NOTE_CP_PLAN

Compensation Plan For Employee S_CP_PLAN_EMP

Compensation Plan Item Detail S_CP_PLNITM_DTL

Compensation Plan Item For Employee S_CP_PLAN_ITEM

Compensation Plan Total S_CP_PLNITM_TOT

Compensation Planning Period S_CP_PERIOD

Compensation Type LOV

Compensation Valid Effectivity Date S_CP_EFF_DATE

Plan Approval S_CP_APPROVAL

Proxy Access To Plan S_USER_PROXYSiebel Data Model Reference Version 8.134

Logical Model Entity Relationship Diagrams and DescriptionsFigure 11. Compensation Planning Execution

O

racle

!

"

$

%

$

&!

'$

!

*$

$

"

$

%

$

'

$

'

"

$

%

$

+

.&

%$

%

%

&$

"

$

%

$

'

$

"

"

$

%

"

$

%

$

'

$

"

*

"

'

+

"

$

%

$

'

$*

"

'

+

"

$

%

$

'

$

"

$

%

$

&

!

'$

%

"

$

%

$

&

!

'$

.

'

"

$

%

$

.&

!

!

*

$

$

"

$

%

$

.&

!

"

"

$

%

$

.&

!

"

*

"

'

+

"

'

+

0

$

"

$

%

$

'

$$

$

!

"

$

%

$

+

'

'

$$

$

!

1

2

2

1

1

3

1

3

2

2

1

3

3

14

14

1

3

14

1

3

14

3

3

21

3

2

3

1

3

51

3

6

1

2

31

3

3

2

2

6

1

3

6

14


Logical Model Entity Relationship Diagrams and DescriptionsCompetency Management SystemFigure 12 shows the Competency Management System ERD. An organization can define a set of competencies that employees can have or acquire over a period of time and an evaluation of employees' skill levels in those competencies, In addition, information about an employee's past work experience, merits, honors, professional memberships and education qualifications can be maintained. An organization can also define a list of courses and related skills which can be associated with an employee when they complete those courses.


Table 11. Competency Management System ERD Entities and Tables

Entity Table

Career Path S_JOB_PRFL_TRNS

Competency, Competency Category, Root Competency Category

S_CMPTNCY

Educational Qualification S_PER_EDU_QUAL

Employee Competency S_EMP_CMPTNCY

Employee Competency Change S_EMP_CMPT_CHG

Employee/Agent S_EMP_PER

Honors And Awards S_PER_AWARD

Job Code S_JOB

Job Profile S_JOB_PROFILE, S_JOBPRFL_CMPT

Past Work Experience S_PER_WRK_EXP

Person S_USER, S_CONTACT

Professional Membership S_PER_PROF_MBR

Professional Qualification S_PER_PROF_CERT

Review Rating S_PERF_RATING

Review Rating Scale S_PERF_RTNG_SCL

Team Competency S_TEAM_CMPTNCY

Training Course S_PROD_INT_CRSESiebel Data Model Reference Version 8.136

Logical Model Entity Relationship Diagrams and DescriptionsFigure 12. Competency Management System

3"

%

3

O

racle

"

"

$

+

7&

'*

$

8

$

*

%

%

$

'"

"

.

%

9

9

$

%

$

!

;

!

%

*

%

%

$

'

*

$

%

;

+

7&

"%!"

9"%!"

'%

'&"

!&

613

6

1

6

1

@6

@

6

13

13

1

@Siebel Data Model Reference Version 8.146

Logical Model Entity Relationship Diagrams and DescriptionsDun & Bradstreet IntegrationThis ERD (shown in Figure 17) illustrates how Siebel Business Applications integrate with Dun & Bradstreet Organization information. A D & B organization may be classified as doing business in one or more industries, may provide information about contacts at the organization and their management responsibilities. In addition, a D & B organization may indicate its direct parent organization, its ultimate domestic parent, and its ultimate global parent. A Siebel organization unit (for example, an account) can be related to its equivalent D & B organization and its associated parent organizations. Contact information from one or more D & B organizations can be used to create one or more call lists.


Table 16. Dun & Bradstreet Integration ERD Entities and Tables

Entity Table

Call List S_CALL_LST

Call List D & B Organization S_DNB_ORG_LST

D & B Contact Responsibility S_DNB_CON_MRC

D & B Management Responsibility Type S_DNB_MRC

D & B Organization S_DNB_ORG

D & B Organization Industry Classification S_DNB_ORG_SIC

D & B Standard Industry Classification S_DNB_SIC

Industry S_INDUST

Organization Industry Classification S_ORG_INDUST

Organization Unit S_ORG_EXT, S_PARTY

Prospect S_PRSP_CONTACTSiebel Data Model Reference Version 8.1 47

Logical Model Entity Relationship Diagrams and DescriptionsFigure 17. Dun & Bradstreet Integration

Title

: D

un

& B

rad

str

ee

t In

teg

ratio

nA

uth

or

: O

racle

, C

on

fid

en

tia

l

PR

OS

PE

CT

D&

B C

ON

TA

CT

OT

HE

R

PR

OS

PE

CT

CA

LL

LIS

T

CA

LL

LIS

T D

&B

O

RG

AN

IZA

TIO

N

OR

GA

NIZ

AT

ION

UN

IT

IND

US

TR

Y

OR

GA

NIZ

AT

ION

IN

DU

ST

RY

CL

AS

SIF

ICA

TIO

N

D&

B M

AN

AG

EM

EN

T

RE

SP

ON

SIB

ILIT

Y T

YP

E

D&

B C

ON

TA

CT

RE

SP

ON

SIB

ILIT

Y

D&

B S

TA

ND

AR

D I

ND

US

TR

Y

CL

AS

SIF

ICA

TIO

N

D&

B O

RG

AN

IZA

TIO

N I

ND

US

TR

Y C

LA

SS

IFIC

AT

ION

D&

B O

RG

AN

IZA

TIO

N

aff

iliate

d w

ith

com

posed o

f

com

posed o

f

mem

ber

in

for

beare

r of

direct

child

of

direct

pare

nt

of

prim

arily

a

bankin

g

custo

mer

of

a b

ank f

or

of

sourc

e o

f

for

cre

ate

d fro

m

equiv

ale

nt to

equiv

ale

nt

to

glo

bal pare

nt of

glo

bal child

of

dom

estic p

are

nt of

dom

estic c

hild

of

pare

nt of

child

of

specifie

r of

cla

ssific

ation f

or

cla

ssifie

r of

cla

ssifie

d w

ithin

of

assig

ne

d to

glo

bal child

of

glo

bal

pare

nt

of

dom

estic

child

of

dom

estic

pare

nt

of

sp

ecifie

r o

f

cla

ssific

atio

n fo

r

cla

ssifie

r of

cla

ssifie

d

withinSiebel Data Model Reference Version 8.148

Logical Model Entity Relationship Diagrams and DescriptionsEmployee KPIThis ERD (shown in Figure 18) illustrates that Key Performance Indicators (KPI) can be defined and associated with the objectives of an employee so that the employee and the manager of the employee manager can measure achievement or current values against the goals set in the objectives of the employee.


Table 17. Employee KPI ERD Entities and Tables

Entity Table

BUSINESS UNIT S_BU

EMPLOYEE PERFORMANCE MEASUREMENT

S_EMP_PERF_MEAS

GROUP, ACCESS GROUP S_PARTY

KEY PERFORMANCE INDICATOR DEFINITION

S_KPI, S_KPI_AGRP

KPI VALUE FOR EMPLOYEE S_EMP_KPI

KPI VALUE FOR OBJECTIVE S_PERF_MITM_KPI

KPI VALUE HISTORY S_EMPKPI_SNPSHT

ORGANIZATION UNIT, DIVISION S_ORG_EXT

PERFORMANCE MEASUREMENT ITEM S_PERF_MEAS_ITM

PERSON, EMPLOYEE/AGENT, OTHER PERSON

S_CONTACT, S_EMP_PER, S_USERSiebel Data Model Reference Version 8.1 49

Logical Model Entity Relationship Diagrams and DescriptionsFigure 18. Employee KPI

Title : Employee KPIAuthor : Oracle, Confidential

KPI VALUE HISTORY

KPI VALUE FOR EMPLOYEE

KPI VALUE FOR OBJECTIVE

KEY PERFORMANCE INDICATOR DEFINITION

PARTY

GROUP

ACCESS GROUP

ORGANIZATION UNIT

DIVISION

OTHERPARTY

PERSON

OTHER PERSON

EMPLOYEE / AGENT

PERFORMANCE MEASUREMENT ITEM

EMPLOYEE PERFORMANCE MEASUREMENT

objective for

subject of

history for

has

history for

has

user of

source for

defined for

have

contain value for

measured in

contain value for

used to generate valuefor

measurement of

subject of

approved by

approver of

child visibility node of

parent visibility node of

accessed by

have access toSiebel Data Model Reference Version 8.150

Logical Model Entity Relationship Diagrams and DescriptionsExpense ReportsThis ERD (shown in Figure 19) illustrates how Siebel Business Applications track employee expense reports. Employees (for example, sales representatives, field service engineers, and professional services personnel) can track expense items incurred for business purposes. These expenses can be associated with an account, an opportunity, or a project, and may be related to an activity. Other employees or contacts involved in the expense can be associated with the expense. The expenses in a specified reporting period can then be reported on an expense report for reimbursement.


Table 18. Expense Reports ERD Entities and Tables

Entity Table

Activity S_EVT_ACT


Expense Item S_EXP_ITEM

Expense Item Type S_EXP_ITM_TYPE

Expense Report S_EXP_RPT

Expense Report Approval S_EXP_RPT_APPR

Opportunity S_OPTY


Party S_PARTY


Project S_PROJSiebel Data Model Reference Version 8.1 51

Logical Model Entity Relationship Diagrams and DescriptionsFigure 19. Expense Reports

Title : Expense ReportsAuthor : Oracle, Confidential

PARTY

PERSON

EMPLOYEE / AGENT

OTHER PERSON

ORGANIZATION UNIT

INTERNAL ORGANIZATION / PARTNER

OTHER ORGANIZATION UNIT

ACTIVITY

EXPENSE REPORT APPROVAL

PERIOD

PROJECT

OPPORTUNITY

EXPENSE REPORT

EXPENSE ITEM TYPE

EXPENSE ITEM

reported for

the reporting period for

reported by

reporter ofaccounting approval by

approver of

charged to

charged with

by

provider of

involved in

involver of

incurred for

subject of

of

classification for

incurred during

source of

incurred for

subject of

incurred by

incurrer of

for

source of

for

subject of

incurred for

subject of

of

subject of

reported on

composed of

made up of

part ofSiebel Data Model Reference Version 8.152

Logical Model Entity Relationship Diagrams and DescriptionsField Service InventoryThis ERD (shown in Figure 20) illustrates how Siebel Business Applications track field service parts inventory. Parts may be tracked in inventory as serialized assets or as nonserialized quantities of products. An instance of product inventory defines a quantity of product in a given location with a given status and availability. Inventory quantities cannot be modified directly. Instead, they are modified through inventory transactions that reflect each movement of parts between locations, statuses, and availabilities. Inventory locations may be located at a third-party provider, as well as within the internal organization. They may also be related to other inventory locations for the purposes of replenishment or fulfillment.


Table 19. Field Service Inventory ERD Entities and Tables

Entity Table

Address S_ADDR_ORG

Asset S_ASSET

Business Unit S_BU, S_ORG_EXT, S_PARTY

Inventory Location S_INVLOC

Inventory Transaction S_INV_TXN


Party S_PARTY



Product Inventory S_PROD_INV

Product Inventory Category S_PROD_INV_CAT

Product Inventory Location S_PROD_INVLOC

Product or Service S_PROD_INTSiebel Data Model Reference Version 8.1 53

Logical Model Entity Relationship Diagrams and DescriptionsFigure 20. Field Service Inventory

Title

: F

ield

Serv

ice Invento

ry

Au

tho

r :

Ora

cle

, C

on

fid

en

tia

lIN

VE

NT

OR

Y

TR

AN

SA

CT

ION

TY

PE

INV

EN

TO

RY

TR

AN

SA

CT

ION

NO

N-S

ER

IALIZ

ED

TR

AN

SA

CT

ION

SE

RIA

LIZ

ED

TR

AN

SA

CT

ION

PR

OD

UC

T IN

VE

NT

OR

Y

LO

CA

TIO

N

PR

OD

UC

T

INV

EN

TO

RY

CA

TE

GO

RY

PR

OD

UC

T IN

VE

NTO

RY

AS

SE

T (P

RO

DU

CT

INS

TA

NC

E)

PE

RS

ON

AD

DR

ES

S

OR

GA

NIZ

AT

ION

UN

IT

INT

ER

NA

L/P

AR

TN

ER

OR

GA

NIZ

AT

ION

OTH

ER

OR

GA

NIZ

AT

ION

PO

SIT

ION

BU

SIN

ES

S

UN

IT

INV

EN

TO

RY

LO

CA

TIO

N T

YP

E

PR

OD

UC

T O

R S

ER

VIC

E

PR

OD

UC

T IN

TE

RN

AL

SE

RIA

LIZ

AB

LE

PR

OD

UC

T

NO

N-S

ER

IALIZ

AB

LE

PR

OD

UC

T

INV

EN

TO

RY

LO

CA

TIO

N

VIR

TU

AL I

NV

EN

TO

RY

LO

CA

TIO

N

OT

HE

R IN

VE

NT

OR

Y

LO

CA

TIO

N

WA

RE

HO

US

E

PE

RS

ON

AL (

TR

UN

K)

INV

EN

TO

RY

LO

CA

TIO

N

rep

len

ish

ed

fro

mre

ple

nis

hm

ent

so

urc

e f

or

is a

is m

ade in

to

of

for

typ

e o

f

loca

ted

at

an

asse

mb

ly o

fa c

om

ponent of

pa

rt o

fm

ade u

p

vis

ible

to

acce

sso

r o

f

resp

on

sib

ility

of

resp

on

sib

le

for

loca

ted

at

for

rep

len

ish

ed

fro

m

su

pp

lier

of

pa

rtic

ipa

tes in

for

de

fin

es m

ove

me

nt

fro

m

is a

ffe

cte

d b

y

de

fin

es

move

ment to

is a

ffe

cte

d

by

at

sto

res

of

sto

red

in

co

un

ts p

rod

uct

for

are

co

un

ted

via

cu

rre

ntly in

inve

nto

ry a

t

sta

tus o

f

typ

e o

f

for

held

by

ho

lde

r o

fa

ffili

ate

d

wit

h

co

mp

ose

d

of

for

loca

ted

at

acce

sse

d b

y

resp

on

sib

le

for

resp

on

sib

ility

of

resp

on

sib

le

for

for

co

mp

ose

d o

f

su

b-o

rg

of

co

mp

ose

d o

f

typ

e o

f

for


Logical Model Entity Relationship Diagrams and DescriptionsField Service SchedulerThis ERD (shown in Figure 21) illustrates how the Siebel Data Model supports the scheduling of employees to perform service activities within configured service regions. A service region corresponds to one or more ZIP codes or other geographical representation, but may only be associated with a single time zone. The service region defines a number of parameters, time duration maps, cost functions, and rule sets that constrain the scheduling of resources within the region. A given service request or activity is assigned to a service region and then to an employee, based on the employee's working hours and current schedule.


Table 20. Field Service Scheduler ERD Entities and Tables

Entity Table

Address S_ADDR_ORG


Employee Exceptional Work Hours S_EMP_EXCPT_HRS

Scheduler Cost Function S_SCH_CSTFN

Scheduler Cost Function Variable S_SCH_CSTFN_VAR

Scheduler Parameter S_SCH_PARAM

Scheduler Parameter Set S_SCH_PARAM_SET

Scheduler Rule S_SCH_RULE

Scheduler Rule Node S_SCH_RULENODE

Scheduler Rule Set S_SCH_RLST

Scheduler Time Map S_SCH_TMMAP

Scheduler Time Map Duration S_SCH_TMMAP_DUR

Service Activity S_EVT_ACT

Service Region S_SRV_REGN

Service Request S_SRV_REQ

Timezone S_TIMEZONE

Work Shift S_SCHED_CAL

Work Shift Exception S_EXCPT_CAL

Work Shift Exception Hour S_EXCPT_CAL_HRS

Work Shift Hour S_SCHED_CAL_HRS

Zipcode S_ZIPCODESiebel Data Model Reference Version 8.1 55

Logical Model Entity Relationship Diagrams and DescriptionsFigure 21. Field Service Scheduler

Title : Field Service SchedulerAuthor : Oracle, Confidential

ZIPCODE

SERVICE REQUEST

SERVICE ACTIVITY

ADDRESS

SCHEDULER RULE NODE SCHEDULER RULESCHEDULER RULE SET

EMPLOYEE EXCEPTIONAL WORK HOURS

WORK SHIFT EXCEPTION HOUR

WORK SHIFT EXCEPTION TIMEZONE

EMPLOYEE

WORK SHIFT HOUR WORK SHIFT

SCHEDULER PARAMETER SET

SCHEDULER PARAMETER

SCHEDULER TIME MAP DURATION

SCHEDULER TIME MAP

SCHEDULER COSTFUNCTION VARIABLE

SCHEDULER COST FUNCTION

SERVICE REGION

in

for

with

for

assigned to

assigned with

assigned to

owner of

in

for

for

subject of

ending at

for

starting

for

user of

used by

for

with

at

for

in

for

defined for

defined by

with

for

defined for

defined by

infor

in

for

underabove

for

subject of

within

made up of

within

made up of

defined for

subject of

defined for

subject of

in

for

user of

used by

user of

used by

user of

used bySiebel Data Model Reference Version 8.156

Logical Model Entity Relationship Diagrams and DescriptionsForecastsThis ERD (shown in Figure 22) illustrates the process of generating forecasts. A forecast series defines a set of forecast periods in which forecasts must be submitted, and describes the appropriate number of periods to forecast into the future for each forecast period. One or more positions are then assigned to submit forecasts under the defined forecast series. When a forecast series is accessible to the public, it means the forecast series can be shared across organizations. Each participant submits a forecast each period that is made up of forecast items. Each forecast item may be attributed to different kinds of business transactions, and may be defined at any of a number of levels based on business rules. These forecast items may be generated based on known revenue items. Forecasts that managers make can contain items from the forecasts of their subordinates.


Table 21. Forecasts ERD Entities and Tables

Entity Table

Agreement S_DOC_AGREE

Forecast S_FCST

Forecast Item Detail S_FCST_ITEM_DTL

Forecast Period S_FCSTSER_DATE

Forecast Series S_FCSTSER

Forecasted Item S_FCST_ITEM

Marketing Event S_SRC

Opportunity S_OPTY




Product Line S_PROD_LN

Product or Service S_PROD_INT

Project S_PROJ

Quote S_DOC_QUOTE

Revenue Item S_REVN

Service Request S_SRV_REQSiebel Data Model Reference Version 8.1 57

Logical Model Entity Relationship Diagrams and DescriptionsFigure 22. Forecasts

Titl

e : F

orec

asts

Aut

hor

: Ora

cle

, Con

fiden

tial

AG

GR

EG

AT

E

DIM

EN

SIO

N

FO

RE

CA

ST

RE

VE

NU

E IT

EM

FO

RE

CA

ST

SE

RIE

S

FO

RE

CA

ST

PE

RIO

D

FO

RE

CA

ST

ED

ITE

M

FO

RE

CA

ST

ITE

M D

ET

AIL

OP

PO

RT

UN

ITY

PO

SIT

ION

PE

RS

ON

EM

PLO

YE

E /

AG

EN

T

OT

HE

R P

ER

SO

N

QU

OT

EA

GR

EE

ME

NT

SE

RV

ICE

RE

QU

ES

T

OR

GA

NIZ

AT

ION

UN

IT

OT

HE

R

OR

GA

NIZ

AT

ION

U

NIT

INT

ER

NA

L O

RG

AN

IZA

TIO

N

UN

IT

PR

OD

UC

T L

INE

PR

OD

UC

T O

R

SE

RV

ICE

PR

OJE

CT

MA

RK

ET

ING

E

VE

NT

OR

A

CT

IVIT

Y

defin

ed f

or

aggr

egat

ed b

y

gove

rned

by

appl

icab

le to

for at

trib

uted

to

for

subj

ect o

f

gene

rate

d fo

r

fore

cast

ed v

ia

subm

itted

by

subm

itter

of

for

part

ner

attr

ibut

ed to

defin

ed b

y

auth

or o

f

for ac

coun

t attr

ibut

ed to

part

icip

ant o

f

for

owne

d by

owne

r of

subm

itted

for

perio

d fo

r

for

attr

ibut

ed to

for attr

ibut

ed to

for

attr

ibut

ed to

for

attr

ibut

ed to

for

attr

ibut

ed to

for

attr

ibut

ed to

for

attr

ibut

ed to

for

subj

ect o

f

a re

port

to

man

ager

of

valid

per

iod

for

subj

ect o

f

mem

ber

ofor

igin

al fo

reca

st o

f

mem

ber

ofsu

mm

ary

of

subo

rdin

ator

's fo

reca

st o

f

man

ager

's fo

reca

st o

f


Logical Model Entity Relationship Diagrams and DescriptionsHigh Tech Marketing Development FundThis ERD (shown in Figure 23) illustrates how Siebel Business Applications support the funding of trade promotions in the high technology industry. Marketing Development Fund (MDF) is a pool of money made available to partners for the organization of marketing activities (campaigns, events, and so on). An MDF may be a partner-specific fund or general fund. MDFs (Programs) provide the brand owner with the ability to make marketing funds available to partners in a programmatic way. Partner Specific funds are child funds of Programs. Within each Partner Specific fund, the partner accrues funds under the given program. The partner creates a partner event activity (pre-approval) with several associated event items. Event Items add granularity to the partner event activity. Partners create claims to redeem the money in their partner-specific funds for marketing activities that were pre-approved by the brand owner.


Table 22. High Tech Marketing Development Fund ERD Entities and Tables

Entity Table

Account, Partner, Other Account S_ORG_EXT

Claim Item S_SRC_PAYITM

Claim, Payment, Other Payment S_SRC_PAYMENT

Event Item S_SRC_COST

Fund Allocation S_MDF_ALLOC

General Fund S_MDF

Internal Product or Service S_PROD_INT

Market Segment S_MKT_SEG

Marketing Development Fund S_MDF

Marketing Event or Activity S_SRC

MDF Snapshot S_MDF_PERIOD

MDF Transaction S_MDF_TXN

Partner Event Activity S_SRC

Partner Program S_PRTNR_PROG

Partner Program Application S_PRTNRPRG_APPL

Partner Specific Fund S_MDF

Position S_POSTNSiebel Data Model Reference Version 8.1 59

Logical Model Entity Relationship Diagrams and DescriptionsFigure 23. High Tech Marketing Development Fund

Title

: H

igh T

ech M

ark

eting D

evelo

pm

ent F

und

Auth

or

: O

racle

, C

onfidential

PA

RT

NE

R

PR

OG

RA

M

PA

RT

NE

R

PR

OG

RA

M

AP

PLIC

AT

ION

PO

SIT

ION

MA

RK

ET

S

EG

ME

NT

MD

F

SN

AP

SH

OT

EV

EN

T IT

EM

CLA

IM IT

EM

MD

F T

RA

NS

AC

TIO

N

DE

BIT

CR

ED

IT

MA

RK

ET

ING

EV

EN

T O

R

AC

TIV

ITY

OT

HE

R M

AR

KE

TIN

G

EV

EN

T O

R A

CT

IVIT

Y

PA

RT

NE

R E

VE

NT

A

CT

IVIT

Y

PA

YM

EN

T

CLA

IM

OT

HE

R P

AY

ME

NT

AC

CO

UN

T

OT

HE

R

AC

CO

UN

T

PA

RT

NE

R

PR

OD

UC

T

LIN

E

FU

ND

ALLO

CA

TIO

N

MA

RK

ET

ING

D

EV

ELO

PM

EN

T

FU

ND GE

NE

RA

L

FU

ND

PA

RT

NE

R

SP

EC

IFIC

F

UN

D

INT

ER

NA

L P

RO

DU

CT

OR

S

ER

VIC

E

for

belo

ngs to

.

for

for

belo

ngs to

for

belo

ngs to

for

has

for

subje

ct of

defined for

subje

ct of

part

of

has

belo

ngs to

has

for

basis

for

of

subje

ct of

belo

ngs

has

.

.

defined for

subje

ct of

targ

et of

available

to

for

funded thro

ugh

earn

ed b

y

earn

er

of

earn

ed b

y

earn

er

of

for

pro

motion o

f

subje

ct of

for

pro

motion o

f

subje

ct of

com

posed o

f

part

of

desig

nate

d to

targ

et of

to has

part

of

.

part

ofm

ade o

f

of

pro

mote

d v

ia

to

recip

ient of

hie

rarc

hy c

hild o

f

hie

rarc

hy p

are

nt of


Logical Model Entity Relationship Diagrams and DescriptionsInvoicable ChargesThis ERD (shown in Figure 24) illustrates how financial transactions, such as charges and credits, are handled. Any charge or credit that could be invoiced is added to this table. This is based on defined consolidation plan rules to consolidate charges and credits into invoice and invoice items.


Table 23. Invoicable Charges ERD Entities and Tables

Entity Table

Activity S_EVT_ACT

Address S_ADDR_ORG

Agreement S_DOC_AGREE

Agreement Entitlement S_ENTLMNT

Agreement Line Item S_AGREE_ITEM

Asset S_ASSET

Auction Item S_AUC_ITEM

Expense Item S_EXP_ITEM

Invoicable Charge S_INVOICE_CHRG

Invoice S_INVOICE

Invoice Item S_INVOICE_ITEM

Invoice Item Reconciliation Entry S_INVC_ITM_DTL

Order S_ORDER

Order Line Item S_ORDER_ITEM

Part Movement S_ACTPART_MVMT, S_ORDPART_MVMT

Part Repair S_PART_RPR

Party S_PARTY, S_ORG_EXT, S_CONTACT, S_USER, S_BU

Payment S_SRC_PAYMENT

Payment Term S_PAYMENT_TERM

Product or Service S_PROD_INT

Project Item S_PROJITEM

Project Team Role S_PROJ_RSRC

Service Request S_SRV_REQ

Shipment S_SHIPMENT

Time Sheet Item S_TMSHT_ITEMSiebel Data Model Reference Version 8.1 61

Logical Model Entity Relationship Diagrams and DescriptionsFigure 24. Invoicable Charges

Titl

e : I

nvoi

cabl

e C

harg

esA

utho

r : O

racl

e, C

onfid

entia

l

PA

YM

EN

T

INV

OIC

E IT

EM

R

EC

ON

CIL

IAT

ION

EN

TR

Y

INV

OIC

E IT

EM

D

ET

AIL INV

OIC

E IT

EM

IN

VO

ICA

BLE

C

HA

RG

E

AD

DR

ES

S

EX

PE

NS

E IT

EM

TIM

E S

HE

ET

ITE

M

PR

OJE

CT

T

EA

M R

OLE

PR

OJE

CT

IT

EM

AU

CT

ION

ITE

M

PA

RT

Y

OR

GA

NIZ

AT

ION

UN

IT

OT

HE

R

OR

GA

NIZ

AT

ION

U

NIT

AC

CO

UN

T

OT

HE

R

PA

RT

Y

PE

RS

ON

INV

OIC

E IT

EM

INV

OIC

E

PA

YM

EN

T T

ER

M

AG

RE

EM

EN

T

LIN

E IT

EM

AG

RE

EM

EN

T

SE

RV

ICE

R

EQ

UE

ST

SH

IPM

EN

T

PR

OD

UC

T O

R

SE

RV

ICE

PA

RT

RE

PA

IR

OR

DE

R L

INE

IT

EM

OR

DE

R

AG

RE

EM

EN

T

EN

TIT

LEM

EN

T

AS

SE

T

AC

TIV

ITY

PA

RT

MO

VE

ME

NT

AC

TIV

ITY

P

AR

T

MO

VE

ME

NT

OR

DE

R

PA

RT

M

OV

EM

EN

T

INV

OIC

AB

LE C

HA

RG

E

for

subj

ect o

f

bille

d to

cont

act o

f

bille

d to

prim

ary

dmr

Documents