DMR

Siebel Data Model Reference

Version 8.0, Rev. AMay 2008

Copyright © 2005, 2008, Oracle. All rights reserved.

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

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

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

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

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

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

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

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

Siebel Data Model Reference Version 8.0, Rev. A 3

Contents

Siebel Data Model Reference 1

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

Siebel Data Model Reference Version 8.0, Rev. A

Contents ■

4

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

Contents ■


Chapter 4: Physical ModelData Model Naming Conventions 153

Table Naming Conventions 153Index Naming Conventions 155Column Naming Conventions 155Abbreviations Used in the Physical Model Listings 156

Data Model Type Definitions 156Table Type Definitions 157Table Status Definitions 158Column Type Definitions 159Domain Type Definitions 159

Columns of Numeric Physical Type 160

Siebel System Fields 160

INTEGRATION_ID Columns 161

Include Only Field 161

Siebel Repository 161

Database Schema Version 161

Limit Checking for Data Types 162

Validating the Siebel Schema 162

Party Model Unifies Access to Data 162

Chapter 5: Schema ChangesTable Changes in This Version 165

New Tables in this Version 165Modified Tables in This Version 171

Table Column Changes in This Version 171New Table Columns in This Version 171New System Columns in This Version 184Modified Table Columns in This Version 184

Table Index Changes in This Version 185New Table Indexes in This Version 185Modified Table Indexes in This Version 187Table Indexes Deleted from This Version 190

Index


Contents ■

6


1 What’s New in This Release

What’s New in Siebel Data Model Reference, Version 8.0, Rev. ATable 1 lists changes described in this version of the documentation to support release 8.0 of the software.

Table 2 lists changes described in this version of the documentation to support release 8.0 of the software.

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

Topic Description

High Tech Special Pricing Authorization Entity Relationship Diagram (ERD)

Removed this ERD as it is not available in this version of the software.

Marketing Program ERD, see Table 33 on page 79

Corrected listing to show changes for offers, treatments, and campaigns in Marketing Program entities and tables.

Party model, see Table 80 on page 162

Removed row containing EIM_PARTY table as it is no longer part of the database installation.

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

Topic Description

Marketing Budget Request ERD

See “Marketing Budget Request” on page 66.

A new entity-relationship diagram.

This ERD illustrates the Marketing Resource Management budget request process.

Marketing Program ERD

See “Marketing Program” on page 79.

This entity-relationship diagram has been modified.

A new entity Offer has been added and campaign targeting is now performed at the offer level.

Marketing Resource Management: Document ERD

See “Marketing Resource Management: Document” on page 82.


This ERD illustrates the Marketing Resource Management marketing content process.


What’s New in This Release ■

8

Sales Portfolio Management ERD

See “Sales Portfolio Management” on page 123.


The Portfolio Management Process allows portfolio managers to manage a group of strategic accounts by:

■ Assessing the potential of their assigned accounts

■ Engaging the high-potential accounts within their portfolio

■ Directing and managing the resources at their disposal

■ Managing ongoing relationships with customers and partners

Table changes

See “Table Changes in This Version” on page 165.

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

Table column changes

See “Table Column Changes in This Version” on page 171.

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

Table index changes

See “Table Index Changes in This Version” on page 185.

A listing of the index changes in this schema including the new indexes, deprecated indexes, and changes to the existing index definitions.

Territory Management ERD

See “Territory Management” on page 135.

The relationship from Territory to Territory Hierarchy has been changed from mandatory to optional and moved out of the Territory user key. Territory is now multi-org enabled.

Territory Quota Rollup

See “Territory Quota Rollup” on page 137.


This data model supports quota assignment and quota rollup to a territory. Users can define quotas, spread them over several periods, and assign them to contacts, accounts, regions, and ZIP codes.

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

Topic Description


2 Data Model Overview

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

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

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

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

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

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

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

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


Data Model Overview ■

10


3 Logical Model

The Siebel logical model represents the following in Siebel Business Applications:

■ Entities

■ Relationships between entitiesThis 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 13


Logical Model ■ Entity Relationship Diagram Conventions

12

General 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 Conventions

Logical Model ■ Entity Relationship Diagram Conventions


Each [entity] must be [relationship name] either to one and only one [entity] or [relationship name] to one and only one [entity]. For example, each Product Comparison must be to either one and only one Product Internal or to one and only one Product External as shown in Figure 2.

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 of


Logical Model ■ Entity Relationship Diagrams and Descriptions

14

Entity 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 3 provides a list of ERDs in alphabetic order.

Table 3. Entity Relationship Diagrams

ERD NameFigure Num. and Page Functional Area

Revised in 8.0

Newin 8.0

Account Figure 4 on page 19

General

Adjustment Group Figure 5 on page 21

General

Asset Management Figure 6 on page 23

General

Auction Figure 7 on page 25

General

Auto Email Response Generator Figure 8 on page 27

General

CG Promotion Planning Figure 9 on page 30

Marketing

Compensation Planning Administration Figure 10 on page 32

ERM

Compensation Planning Execution Figure 11 on page 34

ERM

Competency Management System Figure 12 on page 36

ERM

Content Management Figure 13 on page 38

General

Contract Conditions Figure 14 on page 40

General

Contracts Figure 15 on page 42

General

Data Visibility Figure 16 on page 45

General

Dun & Bradstreet Integration Figure 17 on page 47

Sales/Marketing



Employee KPI Figure 18 on page 49

ERM

Expense Reports Figure 19 on page 51

General

Field Service Inventory Figure 20 on page 53

Service

Field Service Scheduler Figure 21 on page 55

Service

Forecasts Figure 22 on page 57

Sales/Marketing

High Tech Marketing Development Fund Figure 23 on page 59

Marketing

High Tech Special Pricing Authorization Figure 24 on page 61

Sales

Invoicable Charges Figure 25 on page 63

Service

Invoices Figure 26 on page 65

Service

Marketing Budget Request Figure 27 on page 67

Marketing Yes

Marketing Campaign Figure 28 on page 69

Marketing

Marketing Collaboration Figure 29 on page 71

Marketing

Marketing Encyclopedia Figure 30 on page 73

Sales/Marketing

Marketing Events Figure 31 on page 76

General

Marketing Plans Figure 32 on page 78

Marketing

Marketing Program Figure 33 on page 81

Marketing Yes

Marketing Resource Management: Document

Figure 34 on page 83

Marketing Yes

Opportunity Management Figure 35 on page 85

Sales



Revised in 8.0

Newin 8.0



16

Order Life Cycle Figure 36 on page 87

General

Orders Figure 37 on page 89

General

Partner Collaboration Figure 38 on page 91

General

Partner Program Registration Figure 39 on page 93

General

Party Model Figure 40 on page 95

General

Payments Figure 41 on page 97

General

Performance Review Figure 42 on page 100

ERM

Personal Account Figure 43 on page 102

Industry-Specific

Personal Financial Review Figure 44 on page 104

Industry-Specific

Pricing Comparison Figure 45 on page 106

Energy

Pricing Figure 46 on page 108

General

Product Promotion Figure 47 on page 110

General

Product Quality Tracking Figure 48 on page 112

General

Product Recommendation Figure 49 on page 114

General

Products or Services Figure 50 on page 116

Service

Professional Services Figure 51 on page 118

General

Revenue Figure 52 on page 120

General

Sales Hierarchy and Credit Assignment Figure 53 on page 122

Sales



Revised in 8.0

Newin 8.0



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

Sales Portfolio Management Figure 54 on page 124

Sales Yes

Service Agreement Figure 55 on page 126

Service

Service Calendars and Work Shifts Figure 56 on page 128

Service

Service Request Figure 57 on page 130

Service

Shipment Figure 58 on page 132

General

Siebel Assistant Figure 59 on page 134

General

Territory Management Figure 60 on page 136

Sales Yes

Territory Quota Rollup Figure 61 on page 138

Sales Yes

Textile, Apparel, and Footwear Figure 62 on page 140

Industry-Specific

Time Sheet Figure 63 on page 142

General

Trade Promotions Figure 64 on page 144

General

Training Curriculum Course Figure 65 on page 146

General

Training Test Engine Figure 66 on page 148

General

Versioned Object Definition Figure 67 on page 150

General

Warranty Figure 68 on page 152

Service



Revised in 8.0

Newin 8.0



18

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

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

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

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

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

Table 4. Account ERD Entities and Tables

Entity Tables

Account S_ORG_EXT, S_PARTY

Account Synonym S_ORG_SYN

Activity S_EVT_ACT

Address S_ADDR_ORG

Assignment Group (Territory) S_ASGN_GRP

Business Unit S_BU, S_ORG_EXT, S_PARTY

Characteristics S_CHRCTR

Dynamic Account Hierarchy S_DYN_HRCHY

Dynamic Account Hierarchy Node S_DYN_HRCHY_REL

Employee/Agent S_EMP_PER, S_CONTACT, S_PARTY

Industry S_INDUST

Market Segment S_MKT_SEG

Party S_PARTY

Payment Term S_PAYMENT_TERM

Person S_CONTACT, S_PARTY

Position S_POSTN, S_PARTY

Price List S_PRI_LST

Sales or Service Team Member S_ACCNT_POSTN



Figure 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



20

Adjustment 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 5. Adjustment Group ERD Entities and Tables

Entity Tables

Adjustment Group S_ADJ_GROUP

Adjustment Group Dimension S_ADJ_GROUP_DIM

Product Compatibility Matrix Rule S_PRODCOMP_MTRX

Product Eligibility Matrix Rule S_PRODELIG_MTRX

Product Promotion Pricing Matrix Rule S_PROM_PMTRX

Standard Entitlement Pricing Matrix Rule S_STDENTL_PMTRX

Standard Product Pricing Matrix Rule S_STDPROD_PMTRX

Standard Training Pricing Matrix Rule S_STDTRNG_PMTRX



Figure 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

in



22

Asset 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 6. Asset Management ERD Entities and Tables

Entity Tables

Activity S_EVT_ACT

Activity Part Movement S_ACTPART_MVMT

Asset Contact Relationship S_ASSET_CON

Asset Employee Relationship S_ASSET_EMP

Asset External Organization S_ASSET_ACCNT

Asset Feature S_ASSET_FEA

Asset Modification S_ASSET_TXN

Asset Relationship S_ASSET_REL

Business Address S_ADDR_ORG

Competitive Metric S_CMPT_MTRC

Competitive Product Feature S_CMPT_PROD_FEA

Contact S_CONTACT, S_PARTY

Employee S_EMP_PER, S_CONTACT, S_PARTY

External Product S_PROD_EXT

Internal Product S_PROD_INT

Opportunity S_OPTY

Opportunity Asset S_OPTY_ASSET


Personal Address S_ADDR_PER

Product Instance (Asset) S_ASSET

Service Request S_SRV_REQ



Figure 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



24

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


Table 7. Auction ERD Entities and Tables

Entity Tables

Asset S_ASSET

Auction Alert Definition S_AUC_ALRT_DEF

Auction Item S_AUC_ITEM

Auction Item Bid S_AUC_BID

Auction Item Promotion S_AUC_ITM_PROMO

Auction Item Watch S_AUC_WATCH

Auction Lister/Bidder Rating S_AUC_RATING

Catalog S_CTLG

Catalog Category S_CTLG_CAT

Catalog Category Item S_CTLG_CAT_PROD, S_CTLGCAT_ASSET, S_CTLG_CAT_AUC

Order S_ORDER

Order Item S_ORDER_ITEM

Party S_PARTY

Person S_CONTACT

Product S_PROD_INT

Triggered Auction Alert Item S_AUC_ALRT

User S_USER, S_CONTACT, S_PARTY



Figure 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



26

Auto 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 8. Auto Email Response Generator ERD Entities and Tables

Entity Tables

Activity S_EVT_ACT

Catalog S_CTLG


Category Usage Notification S_COMM_CTG_NTFY

Communication Template Usage Notification S_COMMTMPL_NTFY


Problem Resolution Document S_RESITEM

Template Communication Response S_DMND_CRTN_PRG



Figure 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



28

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

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


Table 9. CG Promotion Planning ERD Entities and Tables

Entity Tables


Authorized Product S_ORG_PROD

Fund Allocation S_MDF_ALLOC

Marketing Development Fund S_MDF

Marketing Event or Activity S_SRC

MDF Accrual S_MDF_ACCRUAL

Payment S_SRC_PAYMENT

Period S_PERIOD




Price List Item S_PRI_LST_ITEM

Product Internal S_PROD_INT

Product Line S_PROD_LN

Product Structure S_PROD_REL or S_PROD_ITEM

Promotion Plan S_SRC

Promotion S_SRC

Promotion Account S_SRC



Promotion Product S_SRC

Promotion Category S_SRC

Promotion Account Product S_SRC

Table 9. CG Promotion Planning ERD Entities and Tables

Entity Tables



30

Figure 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

��

�

��

��

�



Compensation 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 10. Compensation Planning Administration ERD Entities and Tables

Entity Tables

Business Unit S_BU

Compensation Budget Definition S_CP_BDGT

Compensation Budget Item S_CP_BDGT_ITEM

Compensation Budget Item For Employee S_CP_BDGT_EMP

Compensation Cycle Planning Period S_CP_PD_BDGTITM

Compensation Guideline Definition S_CP_GDLN

Compensation Guideline Factor LOV

Compensation Guideline Set S_CP_GDLN_SET

Compensation Guideline Table S_CP_GDLN_TBL

Compensation Planning Period S_CP_PERIOD

Compensation Region S_CP_REGN

Compensation Type LOV

Compensation Valid Effectivity Date S_CP_EFF_DATE

Employee Eligibility S_APP_QUERY (PDQ)

Employee/Agent S_EMP_PER

Job Category LOV

Job Code S_JOB

Job Family S_JOB_FAMILY

Job Profile S_JOB_PRFL

Period S_PERIOD

Salary Grade S_SALARY_GRADE, S_SALPLAN_GRADE

Salary Plan S_SALARY_PLAN



32

Figure 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



Compensation 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 11. Compensation Planning Execution ERD Entities and Tables

Entity Tables

Business Unit S_BU

Compensation Budget Definition S_CP_BDGT

Compensation Budget Item S_CP_BDGT_ITEM

Compensation Budget Item For Employee S_CP_BDGT_EMP

Compensation Cycle Planning Period S_CP_PD_BDGTITM

Compensation Guideline Definition S_CP_GDLN

Compensation Guideline Set S_CP_GDLN_SET

Compensation Guideline Table S_CP_GDLN_TBL

Compensation Plan S_CP_PLAN

Compensation Plan Comments S_NOTE_CP_PLAN

Compensation Plan For Employee S_CP_PLAN_EMP

Compensation Plan Item Detail S_CP_PLNITM_DTL

Compensation Plan Item For Employee S_CP_PLAN_ITEM

Compensation Plan Total S_CP_PLNITM_TOT

Compensation Planning Period S_CP_PERIOD

Compensation Type LOV

Compensation Valid Effectivity Date S_CP_EFF_DATE

Plan Approval S_CP_APPROVAL

Proxy Access To Plan S_USER_PROXY



34

Figure 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��

��

��

��

2��1

3

��

2��

� �

��

��3��

��1

3

��

��

� �

� �5��1

3

��

�� 6

��

� �

1��

�

��2�

��

��

3��1

3

��

��

3��

�

� �

��2�

��

��

��

��

��2�

� �

� ��

�

��

� �

��

� �

� �

� ��

�

6

��1

3

6

��

�

��14�

��

� ��

��

� �

��

��

��

��



Competency 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 12. Competency Management System ERD Entities and Tables

Entity Tables

Career Path S_JOB_PRFL_TRNS

Competency, Competency Category, Root Competency Category

S_CMPTNCY

Educational Qualification S_PER_EDU_QUAL

Employee Competency S_EMP_CMPTNCY

Employee Competency Change S_EMP_CMPT_CHG

Employee/Agent S_EMP_PER

Honors And Awards S_PER_AWARD

Job Code S_JOB

Job Profile S_JOB_PROFILE, S_JOBPRFL_CMPT

Past Work Experience S_PER_WRK_EXP

Person S_USER, S_CONTACT

Professional Membership S_PER_PROF_MBR

Professional Qualification S_PER_PROF_CERT

Review Rating S_PERF_RATING

Review Rating Scale S_PERF_RTNG_SCL

Team Competency S_TEAM_CMPTNCY

Training Course S_PROD_INT_CRSE



36

Figure 12. Competency Management System

��

��

�

��

��3�"

��

��%

3��

��

��

��

��O

racle

��

��

��

�"

��

"�

��

�$

+

�

7&

�'�*

��

��

$��

��

8�

��

��$

�

��

�*

�%

%��

$�

'�"

�"

.�

�%

9��

9�

$�

�%

��$

!��

;�

�!

%

��

�*

�%

%��

$�

'�

��

��*

��

��

$

��

%�

�;�

�<

��8

��

��

$

�

�!

&

��

��$

�'�7

&�

'�*

��

��

$

�"

�'�

+�

��

�"

��

��

$

+�

9

�$

�

�"

�'�

+�

��

&�

��

$�

��

"�

��

�$

+

�

"�

��

�$

+

��

��

�

�+

��

��

��

"�

��

�$

+

��

��

�

�+

�

"�

��

�$

+

=�

.�

�!

�

��

>��

;��

��

�$

�%

�'�

��

>��

;��

��

�$

��

��$

�$

��

&�

%�

�

��

��

��

�9

=�

.��

��

*�'

�

��

�%

�$

�"

�'�

+�

��

0��

�

$�

��

9�

��

��

�%

�$

� �

��14�

��

��?��

��

��

��?��

��

� �

��?��

�

��

� �

� �

� ��

�

��

� ��@��

��

��

� �3

��

� �

��

�

��

� �

��

� �

��

� �

��

��

��

�

��

��

��

��

� �

� �

� ��

�

��2��

6��1

3

��2��

6��

� �

6 �5

�� 6

��

�

��

��

��

�

� ��

��1

3

� ��

��

��

��

3��

��

��

��

��

� �

� �

� ��

��

��

��

��

��5��1

3

��

��

��

��

2��

��

��

��

��1

3

��

��3��

��

��

��

��3��

��

�13

��

��

�

��

��

��

��

� 2��

��

��

� �

��14�

��

��

�13 �

��

��

�



Content ManagementFigure 13 shows the Content Management ERD. This ERD illustrates how the Siebel Data Model supports the process of creating and maintaining content through projects. A content project is made up of one or more content project items that represent an item of master data, such as a product definition or an item of literature. Each content project item is an instance of a content item type that is part of a content object. A content object is based on a business object and is published to the production system through an EAI integration object. A workflow process governs the flow of the items in a content project from conception through publication. Each item may be the responsibility of, reviewed by, or approved by one or more Positions.


Table 13. Content Management ERD Entities and Tables

Entity Tables

Content Item Type S_CONTENT_TYPE

Content Object S_CONTENT_OBJ

Content Project S_CONTENT_PROJ

Content Project Item S_CONTENT_ITEM

Literature S_LIT



Product S_PROD_INT



38

Figure 13. Content Management

Title

: C

onte

nt M

anagem

ent

Auth

or

: O

racle

, C

onfidential

MA

ST

ER

DA

TA

IT

EM

OT

HE

R M

AS

TE

R

DA

TA

IT

EM

PR

OD

UC

T

LIT

ER

AT

UR

E

PO

SIT

ION

BU

SIN

ES

S

OB

JE

CT

PIC

K L

IST

CO

NT

EN

T O

BJE

CT

CO

NT

EN

T

PR

OJE

CT

CO

NT

EN

T

PR

OJE

CT

IT

EM

PE

RS

ON

VIE

W

PIC

K A

PP

LE

T

WO

RK

FLO

W P

RO

CE

SS

E

AI

INT

EG

RA

TIO

N

OB

JE

CT

CO

NT

EN

T IT

EM

T

YP

E

for

managin

g

changes to managed b

y

held

by

hold

er

of

pic

ked v

ia

used b

y

genera

lly

contr

olle

d

by

genera

lly follo

wed

by

responsib

le

for

responsib

ility

of

genera

lly r

esponsib

le for

genera

lly the r

esponsib

ility

of

vie

wed v

ia

used b

y

used b

y

vie

wed v

ia

pro

duced b

y

pro

ducer

of

ow

ned b

y

ow

ner

of

based o

n

basis

for

pic

ked v

ia

used b

y

pic

ked v

ia

used b

y

pic

ked v

ia

used b

y

pic

ked v

ia

used b

y

contr

olle

d b

y

follo

wed b

y

part

of m

ade

up o

f

an e

xam

ple

of

type for

pic

ked v

ia

used b

y

publis

hed v

ia

used b

y



Contract ConditionsFigure 14 shows the Contract Conditions ERD. This ERD illustrates the usage of templates to create agreements. An agreement could comprise one or more entitlements. A contracts administrator may define template entitlements, template benefits and template conditions in addition to template terms. Template benefits and conditions could be for a specific product or product line or product class or category. An entitlement could be created using the entitlement template and this would create the corresponding benefits and conditions based on the corresponding template benefits and conditions. The terms governing the agreement could be based on template terms.


Table 14. Contract Conditions ERD Entities and Tables

Entity Tables

Agreement S_DOC_AGREE

Benefit S_AGREE_BNFT

Category S_CTLG_CAT

Condition S_AGREE_COND

Condition Compliance S_AGR_COND_CMPL

Contract S_DOC_AGREE

Entitlement S_ENTLMNT

Entitlement Template S_ENTL_TMPL

Object Class S_VOD, S_VOD_VER

Product S_PROD_INT


Template Benefit S_ENTL_BNFTTMPL

Template Condition S_ENTL_CONDTMPL

Template Term S_AGR_TERM_TMPL

Term S_AGR_TERM_DESC



40

Figure 14. Contract Conditions

Titl

e : C

ontr

act L

ifecy

cle

Man

agem

ent

Aut

hor

: Ora

cle,

Con

fiden

tial

CO

NT

RA

CT

CO

ND

ITIO

N

OB

JEC

T

CA

TE

GO

RY

OB

JEC

T C

LAS

S

PR

OD

UC

T

PR

OD

UC

T L

INE

CO

NT

RA

CT

AG

RE

EM

EN

TO

TH

ER

C

ON

TR

AC

T

TE

RM

TE

MP

LAT

E T

ER

M#

TE

RM

_NU

M

TE

MP

LAT

E C

ON

DIT

ION

# S

EQ

_NU

M

TE

MP

LAT

E B

EN

EF

IT#

SE

Q_N

UM

CO

ND

ITIO

N C

OM

PLI

AN

CE

# C

OM

PL_

NU

M

CO

ND

ITIO

N#

SE

Q_N

UM

BE

NE

FIT

# S

EQ

_NU

M

EN

TIT

LEM

EN

T T

EM

PLA

TE

# N

AM

EE

NT

ITLE

ME

NT

# N

AM

E

in r

efer

ence

tosu

bjec

t of

in r

efer

ence

to

subj

ect o

f

in r

efer

ence

to

subj

ect o

f

in r

efer

ence

to

subj

ect o

f

in c

onte

xt o

f

com

pose

d of

base

d on

used

by

base

d on

used

by

belo

ng to

com

pose

d of

corr

espo

nd to

used

by

appl

icab

le to

com

pris

e

appl

icab

le to

com

pris

e

in r

efer

ence

to

subj

ect o

f

appl

icab

le to

gove

rned

by

appl

icab

le to

gove

rned

by

appl

icab

le to

subj

ect o

f

appl

icab

le to

subj

ect o

f

base

d on

used

in

depe

nden

t upo

n

com

pris

e

in r

efer

ence

to

subj

ect o

f

in r

efer

ence

to

basi

s fo

r



ContractsFigure 15 shows the Contracts ERD. This ERD illustrates the significant entities related to general business contracts (quotes, orders, agreements, and others). A contract is an agreement between two parties, usually to deliver goods or services in exchange for payment. For example, a quote is an agreement between a company and a customer to guarantee a price for a particular set of items if acted on within a specified timeframe. The customer is usually an account, but may be a person. The party on the other side of the contract is an internal or partner organization (or business unit). A contract is composed of contract line items that specify the internal products, services, or assets to be covered under the terms of the contract.


Table 15. Contracts ERD Entities and Tables

Entity Tables


Asset S_ASSET


Contract S_DOC_AGREE, S_DOC_QUOTE, S_ORDER

Contract Line Item S_AGREE_ITEM, S_QUOTE_ITEM, S_ORDER_ITEM

Internal Product or Service S_PROD_INT







42

Figure 15. Contracts

Title

: C

on

tra

cts

Au

tho

r :

Ora

cle

, C

on

fid

en

tia

l

PO

SIT

ION

PE

RS

ON

BU

SIN

ES

S U

NIT

AS

SE

TIN

TE

RN

AL

P

RO

DU

CT

OR

S

ER

VIC

E PA

YM

EN

T

TE

RM

PR

ICE

LIS

T

AC

CO

UN

T

CO

NT

RA

CT

LIN

E I

TE

M

OR

DE

R L

INE

IT

EM

AG

RE

EM

EN

T L

INE

IT

EM

QU

OT

E L

INE

IT

EM

OT

HE

R C

ON

TR

AC

T L

INE

IT

EM

CO

NT

RA

CT

AG

RE

EM

EN

T

OT

HE

R C

ON

TR

AC

T

QU

OT

EO

RD

ER

for

su

bje

ct

of

pa

rt o

fco

mp

ose

d o

f

pa

rt o

f

co

mp

ose

d o

f

for

su

bje

ct

of

invo

lve

d b

y

prim

ary

co

nta

ct

for

resp

on

sib

ility

of

resp

on

sib

le f

or

for

su

bje

ct

of

pa

rt o

fco

mp

ose

d o

f

price

d b

y

pricin

g

me

tho

d f

or

price

d b

y

de

fau

lt p

ricin

g f

or

an

in

sta

nce

of

ma

de

in

to

em

plo

ye

r o

f

em

plo

ye

d a

t

resp

on

sib

ility

of

resp

on

sib

le f

or

su

bje

ct

to for

su

bje

ct

to

for

price

d b

y

pricin

g f

or

ap

plic

ab

le t

o

su

bje

ct

to



Data VisibilityThe main business entities represented (shown in Figure 16) in the Siebel Data Model fall into one of two super-types: Master Data Item or Customer Data Item. A Master Data Item represents data set up and administered by the company using Siebel Business Applications such as products, literature, and price Lists. Master Data Items are often categorized to make information more accessible. A user gains visibility to this data either through the person's association with a business unit (multiple organization visibility) or through the person's access to items in a catalog (access control). Access to items in a catalog is provided by making the category public, or by granting access to the category to one or more access groups. Each access group may be made up of smaller access groups and may be made up of one or more groups of users. Categories granted to a parent access group are automatically granted to all of its child access groups, but categories granted to a child are not granted to its parents.

A Customer Data Item represents transactional data collected during the normal course of doing business such as opportunities, quotes, orders, agreements, service requests, and activities. A user gains visibility to this data either through the person's association with a business unit (multiple organization visibility) or more commonly through a direct assignment of the person or the person's position to the item. A Customer Data Item is usually accessible to one business unit, but is occasionally accessible to two or more business units. Each business unit may be made up of smaller business units. A given type of customer data item is usually assigned to employees through position or directly to the employee, but rarely both. Managers can be granted access to customer data items assigned to their subordinates.


Table 16. Data Visibility ERD Entities and Tables

Entity Tables

Access Group S_PARTY

Account S_ORG_EXT

Activity S_EVT_ACT



Catalog S_CTLG

Category S_CTLG_CAT

Dynamic Account Hierarchy S_DYN_HRCHY

Dynamic Account Hierarchy Node S_DYN_HRCHY_REL


Group S_PARTY

Internal/Partner Organization Unit S_ORG_EXT

Literature Item S_LIT

Opportunity S_OPTY



44

Order S_ORDER

Organization Unit S_ORG_EXT, S_PARTY

Party S_PARTY



Product S_PROD_INT

Quote S_DOC_QUOTE


Table 16. Data Visibility ERD Entities and Tables

Entity Tables



Figure 16. Data Visibility

��!��>��1��3�� Oracle� ��

��'�

��+

��+

��9��+

��&�

��9��&�

��%��$

��$�[��$�&$��

�$��$�'0��$��$�[��$�&$��

��9��$��$�'0��$��$�[��$�&$��

.&%�$�%%�&$��

��9��$�[��$�&$��

��%%��&�

��%�$

�"�'�+��0��$� ��9��%�$

&%��"��!��"

%��>��7&�%�

��&$��+ ��"�$�

��9��&%��"��!��"

��!��

��>��+

7&��

"�%��!��"

��9��"�%��!��"

��'�%�

'��&��"

��!&�

6��13

6��

��1��

� ��

��

��

��

��

��6��

� ��

��

��1��

��

��

��@��6��

��@��

��

��

��

��

��

��

��

6��

�� 1��3� �

��

�� 1��3� �

��

��1��

��

��

��

��

�� @��



46

Dun & 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 17. Dun & Bradstreet Integration ERD Entities and Tables

Entity Tables

Call List S_CALL_LST

Call List D & B Organization S_DNB_ORG_LST

D & B Contact Responsibility S_DNB_CON_MRC

D & B Management Responsibility Type S_DNB_MRC

D & B Organization S_DNB_ORG

D & B Organization Industry Classification S_DNB_ORG_SIC

D & B Standard Industry Classification S_DNB_SIC

Industry S_INDUST

Organization Industry Classification S_ORG_INDUST


Prospect S_PRSP_CONTACT



Figure 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

within



48

Employee 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 18. Employee KPI ERD Entities and Tables

Entity Tables

BUSINESS UNIT S_BU

EMPLOYEE PERFORMANCE MEASUREMENT

S_EMP_PERF_MEAS

GROUP, ACCESS GROUP S_PARTY

KEY PERFORMANCE INDICATOR DEFINITION

S_KPI, S_KPI_AGRP

KPI VALUE FOR EMPLOYEE S_EMP_KPI

KPI VALUE FOR OBJECTIVE S_PERF_MITM_KPI

KPI VALUE HISTORY S_EMPKPI_SNPSHT

ORGANIZATION UNIT, DIVISION S_ORG_EXT

PERFORMANCE MEASUREMENT ITEM S_PERF_MEAS_ITM

PERSON, EMPLOYEE/AGENT, OTHER PERSON

S_CONTACT, S_EMP_PER, S_USER



Figure 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 to



50

Expense 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 19. Expense Reports ERD Entities and Tables

Entity Tables

Activity S_EVT_ACT


Expense Item S_EXP_ITEM

Expense Item Type S_EXP_ITM_TYPE

Expense Report S_EXP_RPT

Expense Report Approval S_EXP_RPT_APPR

Opportunity S_OPTY


Party S_PARTY


Project S_PROJ



Figure 19. Expense Reports

Title : Expense 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 of



52

Field 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 20. Field Service Inventory ERD Entities and Tables

Entity Tables

Address S_ADDR_ORG

Asset S_ASSET


Inventory Location S_INVLOC

Inventory Transaction S_INV_TXN


Party S_PARTY



Product Inventory S_PROD_INV

Product Inventory Category S_PROD_INV_CAT

Product Inventory Location S_PROD_INVLOC

Product or Service S_PROD_INT



Figure 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



54

Field 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 21. Field Service Scheduler ERD Entities and Tables

Entity Tables

Address S_ADDR_ORG


Employee Exceptional Work Hours S_EMP_EXCPT_HRS

Scheduler Cost Function S_SCH_CSTFN

Scheduler Cost Function Variable S_SCH_CSTFN_VAR

Scheduler Parameter S_SCH_PARAM

Scheduler Parameter Set S_SCH_PARAM_SET

Scheduler Rule S_SCH_RULE

Scheduler Rule Node S_SCH_RULENODE

Scheduler Rule Set S_SCH_RLST

Scheduler Time Map S_SCH_TMMAP

Scheduler Time Map Duration S_SCH_TMMAP_DUR

Service Activity S_EVT_ACT

Service Region S_SRV_REGN


Timezone S_TIMEZONE

Work Shift S_SCHED_CAL

Work Shift Exception S_EXCPT_CAL

Work Shift Exception Hour S_EXCPT_CAL_HRS

Work Shift Hour S_SCHED_CAL_HRS

Zipcode S_ZIPCODE



Figure 21. Field Service SchedulerTitle : 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 by



56

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


Table 22. Forecasts ERD Entities and Tables

Entity Tables


Forecast S_FCST

Forecast Item Detail S_FCST_ITEM_DTL

Forecast Period S_FCSTSER_DATE

Forecast Series S_FCSTSER

Forecasted Item S_FCST_ITEM

Marketing Event S_SRC

Opportunity S_OPTY






Project S_PROJ

Quote S_DOC_QUOTE

Revenue Item S_REVN




Figure 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



58

High 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 23. High Tech Marketing Development Fund ERD Entities and Tables

Entity Tables

Account, Partner, Other Account S_ORG_EXT

Claim Item S_SRC_PAYITM

Claim, Payment, Other Payment S_SRC_PAYMENT

Event Item S_SRC_COST


General Fund S_MDF

Internal Product or Service S_PROD_INT

Market Segment S_MKT_SEG



MDF Snapshot S_MDF_PERIOD

MDF Transaction S_MDF_TXN

Partner Event Activity S_SRC

Partner Program S_PRTNR_PROG

Partner Program Application S_PRTNRPRG_APPL

Partner Specific Fund S_MDF

Position S_POSTN



Figure 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



60

High Tech Special Pricing AuthorizationThis ERD (shown in Figure 24) illustrates the special pricing authorization business process for Siebel High Tech, which uses the Meet Competition Quote and Design Registration features. The quote or design registration opportunity leads to an Agreement with Entitlements for discounts on products. Point of sale data includes claim items, which can refer to agreed upon entitlements.


Table 24. High Tech Special Pricing Authorization ERD Entities and Tables

Entity Tables

Account S_ORG_EXT

Address S_ADDR_PER


Claim Item S_POS_CLAIM_ITM

Design Registration S_OPTY_DSGN_REG

Entitlement S_ENTLMNT

Entitlement Product Price S_ENTL_PRDPRI

Meet Competition Quote S_DOC_QUOTE

Opportunity S_OPTY

Point of Sale Header S_POS

Point of Sale Item S_POS_ITEM

Product S_PROD_INT

Quote Line Item S_QUOTE_ITEM



Figure 24. High Tech Special Pricing Authorization

Titl

e :

Hig

h T

ech

Spe

cial

Pric

ing

Aut

horiz

atio

n A

utho

r :

Ora

cle,

Con

fiden

tial

AD

DR

ES

S

PR

OD

UC

TP

OIN

T O

F S

ALE

ITE

M

OT

HE

R P

OS

IT

EM

CLA

IM IT

EM

PO

INT

OF

S

ALE

H

EA

DE

R

OP

PO

RT

UN

ITY

OT

HE

R

OP

PO

RT

UN

ITY

DE

SIG

N

RE

GIS

TR

AT

ION

QU

OT

E L

INE

IT

EM

AC

CO

UN

T

EN

TIT

LEM

EN

T

PR

OD

UC

T P

RIC

E

EN

TIT

LEM

EN

T

AG

RE

EM

EN

TM

EE

T

CO

MP

ET

ITIO

N

QU

OT

E

for

sub

ject

of

for

loca

ted

at

des

igne

d

for

sub

ject

of

spec

ially

quo

ted

for

sub

ject

of

for

sub

ject

of

refe

renc

ing

sup

por

t fo

r

for

havi

ng

for

com

pos

ed

of

for

asso

ciat

ed

with

crea

ted

for

sub

ject

of

par

t of

com

pos

ed

of

initi

ated

b

y

sub

ject

of

for

sub

ject

of

for

havi

ng

for

mad

e up

of

for

asso

ciat

ed

with



62

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


Table 25. Invoicable Charges ERD Entities and Tables

Entity Tables

Activity S_EVT_ACT

Address S_ADDR_ORG


Agreement Entitlement S_ENTLMNT

Agreement Line Item S_AGREE_ITEM

Asset S_ASSET

Auction Item S_AUC_ITEM

Expense Item S_EXP_ITEM

Invoicable Charge S_INVOICE_CHRG

Invoice S_INVOICE

Invoice Item S_INVOICE_ITEM

Invoice Item Reconciliation Entry S_INVC_ITM_DTL

Order S_ORDER

Order Line Item S_ORDER_ITEM

Part Movement S_ACTPART_MVMT, S_ORDPART_MVMT

Part Repair S_PART_RPR

Party S_PARTY, S_ORG_EXT, S_CONTACT, S_USER, S_BU




Project Item S_PROJITEM

Project Team Role S_PROJ_RSRC


Shipment S_SHIPMENT

Time Sheet Item S_TMSHT_ITEM



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

billi

ng c

onta

ct o

f

mad

e fo

r

fulfi

lled

by

part

of

mad

e up

of

for

char

ged

via

for

subj

ect o

f

bille

d to

for

for

loca

ted

atbille

d to for

for

char

ged

via

for

char

ged

via

base

d on

for

for

char

ged

via

for

char

ged

via

for

char

ged

via

obje

ct fo

rof

of orde

red

on

part

of

com

pose

d of

for

char

ged

via

for

char

ged

via

for

subj

ect o

f

invo

iced

into

for

for

char

ged

via

for

char

ged

via

for

char

ged

via

part

of

com

pose

d of

for

fulfi

lled

by

for

char

ged

via

for

char

ged

via

base

d on

basi

s of

part

of

mad

e up

of

part

of

mad

e up

of

for

char

ged

via

base

d on

basi

s fo

r

for

char

ged

via

for

char

ged

via

part

of

com

pose

d of



64

InvoicesThis ERD (shown in Figure 26) illustrates the invoicing and payment processes. An invoice may be considered a receivable or a payable for the company. It may be generated to bill for an order, a project, a part repair, an agreement, a service request, an activity, or a period of time for products or services delivered within a specific period of time. Items on the invoice may be reconciled with one or more other entities as well. A payment may be made for one or more Invoices, and an invoice may be paid through one or more payments.


Table 26. Invoices ERD Entities and Tables

Entity Tables

Activity S_EVT_ACT


Expense S_EXP_ITEM

Invoice S_INVOICE

Invoice Attachment S_INVOICE_ATT


Order S_ORDER


Part Movement S_ORDPART_MVMT

Part Repair S_PART_RPR


Period S_PERIOD

Product S_PROD_INT

Project S_PROJ


Shipment S_SHIPMENT



Figure 26. Invoices

Title

: I

nvo

ice

sA

uth

or

: O

racle

, C

on

fid

en

tia

l

PR

OJE

CT

INV

OIC

E A

TT

AC

HM

EN

T

SH

IPM

EN

T

PE

RIO

D

AC

TIV

ITY

PA

RT

MO

VE

ME

NT

SH

IPP

ED

PA

RT

EX

PE

NS

E

UN

IT O

F

LA

BO

R

INV

OIC

E IT

EM

INV

OIC

E

OT

HE

R IN

VO

ICE

PA

YA

BLE

IN

VO

ICE

RE

CE

IVA

BLE

IN

VO

ICE

PA

RT

RE

PA

IR

PA

YM

EN

T

TE

RM

SE

RV

ICE

RE

QU

ES

T

AG

RE

EM

EN

T

PR

OD

UC

T

OR

DE

R IT

EM

OR

DE

R

PA

YM

EN

T

genera

ted for

reason for

genera

ted

for

reason for

for

bill

ed v

ia

for

bill

ed v

ia

for

sourc

e for

for

deta

il fo

r

for

bill

ed v

ia

part

of

com

posed

of

obje

ct fo

r

for

fulfill

ment fo

r

fulfill

ed b

y

genera

ted

for

reason for

genera

ted

for

reason for

for

bill

ed v

ia

for

bill

ed v

ia

for

bill

ed v

iafo

rbill

ed v

ia

genera

ted

for reason for

genera

ted

for

reason for

for

bill

ed v

ia

for

bill

ed v

ia

made for

fulfill

ed b

y

of

ord

ere

d o

npart

of

com

posed o

f

part

of

com

posed

of

for

bill

ed v

ia

for

bill

ed v

ia

based o

n

for

genera

ted

for

reason for



66

Marketing Budget RequestThis ERD (shown in Figure 27) covers the Marketing Resource Management: budget request process. It illustrates the relationships between budget requests and marketing tactics, marketing funds, and purchase orders. A budget request can be managed by a team and defined against a dedicated marketing fund for a period and a region. It can be associated with one or more industries, products, and product lines.


Table 27. Marketing Budget Request ERD Entities and Tables

Entity Tables

Budget Request S_MKTG_BDGT_REQ

Purchase Request S_ORDER


Marketing Plan S_SRC

Marketing Fund S_MDF

Marketing Tactics S_SRC

Tactics Expense S_SRC_COST

Purchase Request Line Item S_ORDER_ITEM



Figure 27. Marketing Budget Request

��

��"

��5

��

��.

��

��

��

�?

��

��

��

��

��

Ora

cle

��

�

��

��

��

�

��

��

!

��

��

$

��

�

�%

��8

��

$%

�

�&

�

9�

%�

��

�7

&�

%�

�'�$

��

��

"

�$!

&%

��

+

��

�!

&

��'

�$�

��

�!

&

��

�%

��

$

"�

�<

��

�$

��

�

�%

�&

�

9�

%�

��

7&

�%

�

"�

�<

��

�$

��'

�$

�$>

��

�

.&

%�$

�%

%�&

$��

"�

�<

��

�$

�*

&$

!

"�

�<

��

�$

�!�

>�

'�

�"

�$

��*

&$

!

.&

!

��

��

7&

�%

�

1�

� �

��

�

2�

��

1�

� �

��

�

2�

��

1�

� �

��

�

2�

��

1�

� �

��

��

��

��

��

��

1�

� �

��

��

��

��

��

��

��

��

��

�

��

14�

��

�

��

��

��

�

��

14�

��

�

��

��

��

��

��

14�

��

�

��

��

��

��

13

�

��

��

��

14�

��

�

��

��

��

�

��

��

��

��

14�

��

�

� �

��

14�

��

�

��

��

��1

3

� �

� �

��

14�

��

�

��

14�

��

�

� �

��

��

��1

3

� �

��

��

��

�

��

14�

��

�

��

��

�

�

��

��

�

��

��

��

��1

3

� �

��

��

��

�

�

��

��

��

��

��

�

��



68

Marketing Campaign This ERD (shown in Figure 28) illustrates campaign management, execution, and evolution. Campaign management may involve the focus of the campaign on a territory, as well as the responsibility of the various internal divisions and teams for successful execution. Execution may include the production and distribution of literature to the appropriate campaign contacts. Campaign evolution tracks the usage of call lists to identify campaign contacts and generate leads. Campaign contacts may include prospective contacts purchased on a call list. If a prospective contact is not promoted to a customer before the call list that names them expires, they are typically deleted from the database.


Table 28. Marketing Campaign ERD Entities and Tables

Entity Tables

Activity S_EVT_ACT


Call List Member S_CALL_LST_CON

Campaign Call List S_CAMP_CALL_LST

Campaign Contact S_CAMP_CON

Fulfillment Recipient S_FUL_RECIP

Fulfillment Request S_EVT_FUL_REQ

Fulfillment Request Item S_FUL_REQ_ITEM



Opportunity S_OPTY

Opportunity Contact S_OPTY_CON

Order S_ORDER




Prospective Contact S_PRSP_CONTACT

Response S_COMMUNICATION

Territory S_ASGN_GRP



Figure 28. Marketing Campaign

Titl

e : M

arke

ting

Cam

paig

nA

utho

r : O

racl

e, C

onfid

entia

l

RE

SP

ON

SE

OR

DE

R

MA

RK

ET

ING

EV

EN

T O

R A

CT

IVIT

Y

OT

HE

R

MA

RK

ET

ING

E

VE

NT

OR

A

CT

IVIT

Y

MA

RK

ET

ING

CA

MP

AIG

NF

ULF

ILLM

EN

T

RE

CIP

IEN

T

FU

LFIL

LME

NT

R

EQ

UE

ST

ITE

M

LIT

ER

AT

UR

E

ITE

M

FU

LFIL

LME

NT

R

EQ

UE

ST

CA

LL L

IST

M

EM

BE

R

AC

TIV

ITY

CA

MP

AIG

N C

ON

TA

CT

OP

PO

RT

UN

ITY

CO

NT

AC

T

OP

PO

RT

UN

ITY

CA

MP

AIG

N

TE

AM

ME

MB

ER

CA

LL L

IST

MA

RK

ET

ING

S

EG

ME

NT

PU

RC

HA

SE

D

LIS

T

PE

RS

ON

OT

HE

R P

ER

SO

N

PR

OS

PE

CT

IVE

CO

NT

AC

T

TE

RR

ITO

RY

PO

SIT

ION

OR

GA

NIZ

AT

ION

UN

IT

NO

TE

CA

MP

AIG

N C

ALL

LIS

T

gene

rate

d by

orig

inat

or o

f

gene

rate

d by

orig

inat

or o

f

gene

rate

d by

orig

inat

or o

f

part

of

mad

e

for

user

of

resp

onsi

bilit

y of

resp

onsi

ble

for

asso

ciat

ed w

ith

intr

oduc

tion

to

for

targ

eted

at

rele

vant

to

prom

oted

via

part

of

subj

ect o

f

part

of

cond

ucte

d as

initi

ator

of

initi

ated

by

for

subj

ect o

f

addr

esse

d to

reci

pien

t of

of

subj

ect o

f

part

of

mad

e up

of

of

for

of

subj

ect o

f

of

subj

ect o

f

of

subj

ect

of

for

targ

eted

at

assi

gned

to

role

pla

yed

bym

anag

ed w

ithin

focu

s of

assi

gned

to

assi

gned

to s

ell i

n

assi

gned

to

assi

gned

to

for

com

pose

d of

part

of

mad

e up

of

a re

port

to a pa

rent

to

of

subj

ect

of

of

used

in

inm

ade

up o

f

prim

arily

from

sour

ce o

f

of

subj

ect

of



70

Marketing CollaborationCollaborative marketing (shown in Figure 29) assists marketers in maintaining the balance between the need for consistent customer management among partners and effective brand building with local expertise. It consists of two features. Marketing program collaboration allows companies to develop marketing programs in a more collaborative environment, resulting in reduced costs. It encourages collaboration on programs through the sharing of information with key action groups (internal and external). Partner marketing enhancements provides the ability to associate and track partner participation in marketing programs and campaigns to measure and report on opportunities, orders, and ROI. It also closes the loop by providing the ability to track partner sources for responses/opportunities orders.


Table 29. Marketing Collaboration ERD Entities and Tables

Entity Tables

Internal Partner/Organization S_ORG_EXT, S_PARTY


Opportunity S_OPTY

Order S_ORDER

Organization Unit, Other Organization Unit S_ORG_EXT, S_PARTY

Partner Organization S_BU, S_PARTY

Party, Other Party S_PARTY

Quote S_DOC_QUOTE




Figure 29. Marketing Collaboration

Title : Marketing CollaborationAuthor : Oracle, Confidential

QUOTE

MARKETING EVENT OR ACTIVITY

OPPORTUNITY

ORDER

RESPONSE

PARTY

OTHER PARTY

ORGANIZATION UNIT

OTHER ORGANIZATION UNIT

INTERNAL / PARTNER ORGANIZATION

PARTNER ORGANIZATION

generated from

source of

generated from

source of

created for

source of

generated from

lead to

basis for based on

item of collaboration for

collaborating on


collaborating on


collaborating on


collaborating on

responsibility of

responsible for

responsibility of

responsible for

responsibility of

responsible for

responsibility of

responsible for


collaborating onresponsibility of

responsible for



72

Marketing EncyclopediaThis ERD (shown in Figure 30) illustrates how Siebel Business Applications track competitive information about products and companies. A standard set of metrics may be defined against which competitive organizations and their products can be rated in comparison with the internal organization and products, respectively. Detailed product specifications can be recorded. In addition, competitive literature may be associated both with organizations and with products. The relevance of key decision issues to the various competitive metrics may be defined.


Table 30. Marketing Encyclopedia ERD Entities and Tables

Entity Tables

Company Literature S_CO_LIT

Competitive Company Feature S_CMPT_CO_FEA

Competitive Metric S_CMPT_MTRC

Competitive Product Feature S_CMPT_PROD_FEA

Issue S_ISS



Product Comparison S_PROD_CMP

Product Detail S_PROD_SPEC

Product External S_PROD_EXT


Product Literature S_PROD_LIT



Figure 30. Marketing Encyclopedia

Titl

e : M

arke

ting

Enc

yclo

pedi

aA

utho

r : O

racl

e, C

onfid

entia

l

CO

MP

AN

Y

LIT

ER

AT

UR

EP

RO

DU

CT

LI

TE

RA

TU

RE

PR

OD

UC

T

DE

TA

ILC

OM

PE

TIT

IVE

C

OM

PA

NY

F

EA

TU

RE

CO

MP

ET

ITIV

E

PR

OD

UC

T

FE

AT

UR

E

CO

MP

ET

ITIV

E M

ET

RIC

CO

MP

ET

ITIV

E P

RO

DU

CT

ME

TR

ICC

OM

PE

TIT

IVE

CO

MP

AN

Y M

ET

RIC

OR

GA

NIZ

AT

ION

UN

IT

INT

ER

NA

L / P

AR

TN

ER

O

RG

AN

IZA

TIO

N U

NIT

EX

TE

RN

AL

OR

GA

NIZ

AT

ION

UN

IT

LIT

ER

AT

UR

E IT

EM

DE

CIS

ION

IS

SU

E

PR

OD

UC

T O

R S

ER

VIC

E

EX

TE

RN

AL

PR

OD

UC

TIN

TE

RN

AL

PR

OD

UC

T

OR

SE

RV

ICE

PR

OD

UC

T C

OM

PA

RIS

ON

abou

t

subj

ect o

f

usag

e of

refe

renc

e to

abou

t

subj

ect o

f

usag

e of

refe

renc

e to

for

subj

ect o

f

of

clas

sific

atio

n fo

r

rele

vant

to

subj

ect o

f

of

clas

sific

atio

n fo

r

for

subj

ect o

f

of

char

acte

rized

by

prod

uced

by

vend

or o

f

of

com

petit

or o

f

to

com

petit

or o

f



74

Marketing EventsThis ERD (shown in Figure 31) illustrates how Siebel Business Applications support marketing events and activities planning. A marketing event may be composed of one or more sessions, held at one or more venues such as a hotel or convention center. The room for each session of an event may be chosen based on the size and equipment requirements of the session matched to the size and available equipment of each room. Users can also create travel plans for customers attending the events. Event vendors and sponsors can be tracked as well as the various offers or services they provide. The event staff can be planned and attendees invited. Attendees may then register for the event or even for specific sessions. Attendees may be quoted registration prices through a quote and purchase tickets to the event through an order.


Table 31. Marketing Events ERD Entities and Tables

Entity Tables

Activity S_EVT_ACT

Contract Line Item S_ORDER_ITEM, S_QUOTE_ITEM

Equipment Requirement S_SRC_REQ_EQUIP

Event S_SRC_EVT, S_SRC

Event Cost S_SRC_COST

Event Location S_EVTLOC

Event Registration S_SRC_EVT_REG

Event Session S_SRC_EVT, S_SRC

Event Vendor S_SRC_ORG

Event Venue S_SRC_VENUE


Location Room S_EVTLOC_ROOM


Order S_ORDER


Parent Event S_SRC_EVT, S_SRC



Quote S_DOC_QUOTE

Room Avail Equipment S_EVTLOC_RM_EQP

Travel Participant S_EVT_TRVL_PER

Travel Plan S_EVT_TRVL_PLAN



Vendor Offer S_EVT_VNDR_OFR

Vendor Review S_EVT_VNDR_RVW

Vendor Service S_EVT_VNDR_SVC

Venue S_ORG_EXT, S_PARTY

Venue Offer S_EVT_VENUE_OFR

Venue Review S_EVT_VENUE_RVW

Venue Service S_EVT_VENUE_SVC

Table 31. Marketing Events ERD Entities and Tables

Entity Tables



76

Figure 31. Marketing Events

��

��"

��5

��

��

2�

��

��

��

��

Ora

cle

��

�

��

��

��

�

��

�

$�[

��

��$

�&

$��

�>

�$

��'

�

��

��$

��

9�

��'

�

>�

$&

�

�>

�$

��

�%

�

��

�>

�'�

��

��

��

�$

��

��

>�

'��

'�

$

>�

$&

��

%�

�>

��

��

�!

&

��

��%

��

>�

�

�>

�$

��

��

!&

�

��

9�

��

��

!&

�

��

�%

��

>�

�

�>

�$

��>

�$

!�

�

��

%��

��$

�

$�

��

�

��

9�

��

�

$�

��

�

7&

��

�

��

!�

�

�

$�

��

�

�'�$

��

��

"

��

�%

�$

�>

�$

��

��

�%

��

��

��$

�

$

�'

'�

!�

��

�%

��

�$

�

��

��

$!

��

;�

��'

�%�

'��

��

��

&�

��

��

"

�7

&��

"�

$�

��

�7

&��

�"

�$

��

�

�>��

+

'�

�

��

$��

��

"

>�

$!

��

��

�>

��;

>�

$!

��

��

**

��

>�

$!

��

�%

��

>�

�

�>

�$

��>

�$

&�

>�

$&

��

�*

*�

�>

�$

&�

��

�>

��;

��

�"

��7

&��

"�

$�

��

>�

�'�

.�'

��+

�

"�

�<

��

�$

��>

�$

��

��

�

�>��

+

��

9�

��"

��

<�

��$

�

�>

�$

��

��

�

�>��

+�

>�

$�

�%�

%%

��$

�>

�$

��

��

�$

��

�>

�$

�

1�

� �

��

��

��

��

��

��

3�

�

��

��1

3

��

� �

�

��

��

��

�

��

��

��

��

�

�

� �

��

��

��1

3

��

�

��

��

��1

3

��

�

��

�

��

��

��

�6��

��

��

1�

��

�

��

��

��

��

��

��

��

��

2�

��

�2��

��

�13

��

�2��

�

��

��

��

�

��

2�

��

��

��1

3

��

2��

��

�

��

��

��1

3

��

��

��

�

��2��

��

��

2��

��

� �

�

��

��

��

�

� �

��

14�

��

�

��

��

��1

3

��

2��

��

�

��

��

��1

3

��

2��

��

�

� �

��

14�

��

�

��2��

6�

��1

3��

2��

6�

��

�

��?

��

��1

3��

��

��

� �

� �

��

14�

��

�

��

14�

��

��

��

��

��

�

��

��

��1

3

� �

��

14�

��

�

� �

��

14�

��

�

�2�

��1

��

�?

��

��

��6

��

��

2�

��

�

��

�

��

�2��

��

�

��1

��

�

��

�

��1

��3

� �

� �

��

14�

��

�

��

��

�

� ��

��

��

�

� �

�

��

��

��

�

��2��

6�

��1

3��

2��

6�

��

�

��

��

��

�

��

14�

��

�

� ��

��

��

�

��

��

�

� �

��

14�

��

�



Marketing PlansThis ERD (shown in Figure 32) illustrates how marketing plans are used in conjunction with the financial modeler for the purposes of financial planning. Marketing plans are multilevel groupings of plan elements (campaigns) or sub-plans. Financial goals and costs can be forecasted for each level of the plan, tracked against actual achievement after campaign execution, and rolled up to the top-level plan. Funds can also be allocated for different plans in different periods and used as inputs for accounting purposes or in financial calculations.


Table 32. Marketing Plans ERD Entities and Tables

Entity Tables



Marketing Event Cost S_SRC_COST

Marketing Event or Activity, Marketing Plan, Other Marketing Plan or Activity

S_SRC

Marketing Goal S_SRC_GOAL

Period S_PERIOD

Planned Marketing Development Fund Allocation S_MDF_ALLOC

Product or Service, Product Line, Other Product or Service S_PROD_INT, S_PROD_LN

Product Promotion S_PROD_INT_SRC



78

Figure 32. Marketing Plans

Titl

e : M

arke

ting

Pla

nsA

utho

r : O

racl

e, C

onfid

entia

l

BU

DG

ET

R

EQ

UE

ST

INV

OIC

E IT

EM

INV

OIC

E

PE

RIO

D

CA

MP

AIG

N

CA

LL L

IST

CA

LL L

IST

PR

OD

UC

T O

R S

ER

VIC

E

PR

OD

UC

T

PR

OM

OT

ION

MA

RK

ET

ING

G

OA

L

MA

RK

ET

ING

E

VE

NT

CO

ST

MA

RK

ET

ING

EV

EN

T

OR

AC

TIV

ITY

MA

RK

ET

ING

P

LAN

OT

HE

R

MA

RK

ET

ING

E

VE

NT

OR

A

CT

IVIT

Y

PLA

NN

ED

M

AR

KE

TIN

G

DE

VE

LOP

ME

NT

FU

ND

ALL

OC

MA

RK

ET

ING

D

EV

ELO

PM

EN

T

FU

ND

for

uses

FO

R

SU

BJE

CT

OF

basi

s of

base

d on

part

of

mad

e up

of

belo

ng to

com

pose

of

laun

ched

in

defin

ed fo

r la

unch

of

valid

in

defin

ed fo

r

valid

in

defin

ed fo

r th

e bu

dget

of

valid

inde

fined

for

defin

ed fo

r

has

attr

ibut

ed to

has

used

for

user

of

type

of

owne

r fo

r

crea

ted

for

prom

otio

n ite

m fo

r

crea

ted

from

sour

ce o

fcr

eate

d fo

r

requ

irer

of

crea

ted

from so

urce

of

estim

ated

for

cons

ists

of

attr

ibut

ed to

incu

r

rese

rved

from

sour

ce o

f



Marketing ProgramThis ERD (shown in Figure 33) illustrates how Siebel Business Applications support the more complex program planning and execution used for Database Marketing. Marketing segments are dynamic lists of people defined by a set of database criteria and available to marketing programs. These criteria may be defined on measures and attributes based on complex mathematical scores, ratios, and formulas applied to customer demographics or behavior data sourced from the Siebel database or from external applications such as a data warehouse.

After a data dictionary describing the external data store has been defined, segment definitions can be created and attached to one or more campaigns, together with purchased lists. Filters allow the exclusion of segment members based on predefined clauses. Segment prioritization and deduplication make sure that individuals qualified for more than one segment do not receive conflicting messages from more than one campaign. Waves can be generated as a subset of the qualifying people within the targeted segments.

Recurring marketing programs can be defined in which each stage may be based on customer response behavior or any other event. Marketers can define customer hierarchies, so that campaigns can be driven by data summarized from any level of the hierarchy (for example household level and customer level). People to be contacted are listed as campaign contacts for a specific campaign or wave.

Each campaign may be presented with one or more offers. An offer is a type of demand creation program that is directly presented to a target audience. It is intended to generate awareness of or demand for one or more products. Responses are tracked through Communications.


Table 33. Marketing Program ERD Entities and Tables

Entity Tables

Assignment Rule Group S_ASGN_RULE_GRP


Campaign Allocation S_CAMP_CALL_LST

Campaign Contact S_CAMP_CON

Campaign Load S_CAMP_LD_WAVE

Campaign Offer S_SRC_OFFR

Campaign Wave S_DD_CAMP_WAVE


Contact Status S_ SRCDCP_CONSTA

Deal S_DEAL

Filter S_DD_FILTER

Filter Clause S_DD_FILTER_DTL

Load Wave S_CAMP_LD_WAVE



80

Marketing Activity S_SRC

Marketing Segment S_CALL_LST

Offer S_MKTG_OFFR

Offer Media Package S_DMND_CRTN_PRG

Program Segment S_CAMP_CALL_LST

Prospective Contact S_PRSP_CONTACT

Purchased List S_CALL_LST


Table 33. Marketing Program ERD Entities and Tables

Entity Tables



Figure 33. Marketing Program

��

��"

��5

��

� ��

��

��

��

��O

racle

��

��

.&

%�$

�%

%�&

$��

��

�!

&

��

��%

��

>�

�

�*

*�

��"

�!

��

�

<�

�

�

"�

��

$�'

�%�

�!

�%�

��.

&�

��$

�

�'

'�

�!

�;�

>�

%�

&�

�

��

!�

*�

�"

��

%�

&�

�

��

!�

�'�

"�

$�

��

��

+

��

�

$�[

��

��$

�&

$��

��

�%

�$ �

��

%�

�

��>

�

�$

��

�

��

9�

��

��

�%

�$

��

%��

��$

�

"�

��

$�'

��

!

�

''�'

�%�

%�

"

�$

�

�&

�

9�

%�

!�

'�%

�

�

"�

��

$��

**

��

�*

*�

�

�

"�

��

$�

�$

��

�

��

�

��

"�

%�

"

�$

�

'�

�!

�%�

&�

�

"�

�<

��

�$

��

>�

$�

"�

�<

��

�$

��

"�

��

$

"�

�<

��

�$

�%

��

�

"�

�<

��

�$

��

��

�

�"

"�

�<

��

�$

��

'�

$

�

"�

��

$�

;�

>�

��

��

��

� ��

��

1��

�� 6

�

� �

��2

��

��

��

��

��

2��

��

� ��

��2

��

��

� �� 2

��

��

��

� �

��

��

�

��

� �

��

��

��

� �

��

��

�

� �

��

��3

� ��

��

��1

3��

��

� �

��

��

��

� �� 2

��

��

��

� ��

��2

��

1��

��

��14�

��

�

1��

��

��14�

��

�

��

��

��

��

��

��

� �

� ��

��

��

� �

� ��

��

��

� �

��

��

��

� �

��

��

�

��

��

��

��

��

�

��14�

��

��

��

��14�

��

��

� � �

� �

��

�

��

��14�

��

��

��14�

��

��

��

� �

��14�

��

��

��

�

�

��14�

��

��

�

�

��

��



82

Marketing Resource Management: DocumentThis ERD (shown in Figure 34) illustrates the marketing content processing of the enhanced Marketing Resource Management module. It shows the relationship between the content and various entities such as project, offer media package, and lead source. It also illustrates the process of managing content inventory by region and location, and shows how fulfillment requests are completed through vendor bidding.


Table 34. Marketing Resource Management: Document ERD Entities and Tables

Entity Tables

Marketing Material S_CB_ASSET

Material Inventory by Location S_MKTG_DOC_INVT


Region S_REGION

Material Fulfillment Request S_EVT_FUL_REQ

Material Fulfillment Item S_FUL_REQ_ITEM

Mat Fulfill Request Attachment S_NOTE_FUL_REQ

Vendor Bidding S_FUL_REQ_BID

Vendor Bidding Item S_FR_BID_LITM

External Organization S_ORG_EXT

Offer Media Package S_DMND_CRTN_PRG

Offer Document S_OFFR_CBAST

Lead Source S_SRC

Lead Source Document S_SRC_CBAST

Project S_PROJ

Project Document S_PROJ_CBAST



Figure 34. Marketing Resource Management: Document

��

��"

�"

�! ��

��"

��

��

��

��

� Ora

cle

��

��

��

�=�

�

�!

�

&"

�$

�

'�

�!

�%�

&�

�

�!�

&

"�

$�

�*

*�

��

!�

&

"�

$�

"�

��*

&'*

�''�

��

7&

�%

��

��

��

9

"�

$�

�8

��

�$

�'�

��

�

$�[

��

��$

�*

*�

��

�"

��

�$

'�

�!

�%�

&�

�

�*

*�

��"

�!

��

��

<

�

��

��

=�

�

>�

$!

��

�.�!

!�$

��

�"

>�

$!

��

�.�!

!�$

��

��

$

"�

��

��

'��$

>�

$�

��

+�.

+�'

�

��

��$ �

>�

$�

�'�

�

��

$

"�

��

��

'�

*&

'*

�''"

�$

��

��

"

"�

�<

��

�$

�"�

��

��

'�

"�

��

��

'�*

&'*

IL'"

�$

��

�7

&�

%�

��

��

2��

��

��

� �

� ��

��

��2

��

� ��

��

��

� �

� ��

��

��

2��

� ��

��

��

� �

� ��

��

�2��

� ��

��

��

��

��

��

��2

��

� �

��

��

13

��14�

��

�

� �

��

� �

��

��

� ��1

3

��1�

��

� �3�

�

��14�

��

�

��

� �

� ��

��

��3��

��3

��

��

��

��1

��

��

��

� �

1��

��

� 2��

� ��

��

��

��

� �

��

��

��

��

��

�

��

� � �

��

��

� �

6��

��

��3

��

��

��

� �



84

Opportunity ManagementThis ERD (shown in Figure 35) illustrates the significant entities related to an opportunity (or lead), including relationships to contacts, employees (generally sales representatives), products, accounts, and so on.


Table 35. Opportunity Management ERD Entities and Tables

Entity Tables

Address S_ADDR_ORG




Event S_EVT_ACT

External Organization Unit S_ORG_EXT, S_PARTY

Issue S_ISS

Opportunity S_OPTY

Opportunity Relationship S_OPTY_REL



Product S_PROD_INT

Quote S_DOC_QUOTE

Sales Stage S_STG

Source S_SRC

Territory S_ASGN_GRP



Figure 35. Opportunity Management

Titl

e : O

ppor

tuni

ty M

anag

emen

tA

utho

r : O

racl

e, C

onfid

entia

l

OP

PO

RT

UN

ITY

ISS

UE

EV

EN

T A

CT

IVIT

Y

SA

LES

DO

CU

ME

NT

CO

RR

ES

PO

ND

EN

CE

QU

OT

EA

GR

EE

ME

NT

SA

LES

M

ET

HO

DO

LOG

Y

ISS

UE

MA

RK

ET

ING

EV

EN

T O

R

AC

TIV

ITY

OR

GA

NIZ

AT

ION

UN

IT

INT

ER

NA

L / P

AR

TN

ER

O

RG

AN

IZA

TIO

N U

NIT

OT

HE

R O

RG

AN

IZA

TIO

N U

NIT

PE

RS

ON

OT

HE

R

PE

RS

ON

EM

PLO

YE

E /

AG

EN

T

PR

OD

UC

T O

R

SE

RV

ICE

PR

OD

UC

T

ST

RU

CT

UR

E

SA

LES

S

TA

GE

TE

RR

ITO

RY

OP

PO

RT

UN

ITY

AD

DR

ES

S

OP

PO

RT

UN

ITY

R

ELA

TIO

NS

HIP

subj

ect o

f

rele

vant

to

rele

vanc

e of

rele

vant

as

owne

d by

reso

urce

for

targ

eted

at

subj

ect o

f

perf

orm

ed b

y

perf

orm

er o

f

owne

d by

resp

onsi

ble

for

for

sour

ce o

f

for

loca

ted

at

for

com

pose

d of

of colle

ctio

n of

for

part

of

on

invo

lver

of

with

in

subj

ect

to

cons

ider

atio

n on

subj

ect

to

cons

ider

ed o

n

cons

ider

atio

n ofpr

oduc

ed b

y

vend

or o

f

for

a co

llect

ion

of

of

a co

mpo

nent

of

com

pose

d of

affil

iate

d w

ith

clas

sific

atio

n of

clas

sifie

d in

driv

er o

f

driv

en b

y

initi

ator

of

initi

ated

by

invo

lved

on

nvol

ver

of

for

loca

ted

at

base

d on ba

sis

for

a re

port

to

a pa

rent

to

part

of

mad

e up

of

mad

e up

of

part

of

a re

port

to

man

ager

of

in p

artn

ersh

ip w

itha

part

ner

to



86

Order Life CycleThis ERD (shown in Figure 36) illustrates how orders are tracked through their full life cycle by Siebel Business Applications. The cycle starts with an opportunity that tracks the consideration of purchase of one or more products. This opportunity leads to one or more quotes, composed of one or more quoted product items. A quote may then lead to one or more orders. An order is composed of one or more ordered product items. Fulfillment of the order can be tracked through a set of part movements of various types, culminating in a shipment of products to the customer, and the invoicing for shipped goods.


Table 36. Order Life Cycle ERD Entities and Tables

Entity Tables


Invoice S_INVOICE


Opportunity S_OPTY

Opportunity Product S_REVN

Order S_ORDER


Order Part Movement S_ORDPART_MVMT


Quote S_DOC_QUOTE

Quote Item S_QUOTE_ITEM

Shipment S_SHIPMENT



Figure 36. Order Life Cycle

Title

: O

rder

Life

Cyc

leA

utho

r : O

racl

e, C

onfid

entia

l

AC

CO

UN

T

PR

OD

UC

T O

R S

ER

VIC

E

INV

OIC

E IT

EM

INV

OIC

E

QU

OTE

OP

PO

RTU

NIT

Y

PR

OD

UC

T

SH

IPM

EN

T

OR

DE

R P

AR

T M

OV

EM

EN

T

RE

CE

IPT

MV

MT

SH

IP

MV

MT

ALL

OC

ATI

ON

OTH

ER

PA

RT

MO

VE

ME

NT

OR

DE

R IT

EM

QU

OTE

ITE

M

OR

DE

RO

PP

OR

TUN

ITY

gene

rate

d fo

r

reas

on fo

r

for

bille

d vi

a

take

n fo

r

targ

et o

f

prep

ared

for

rece

iver

of

targ

et o

f

of

part

of

com

pose

d of

for

cons

ider

atio

n of

pur

chas

e of

for

com

pose

d of

of

quot

ed fo

r pu

rcha

se o

n

of

cons

ider

ed fo

r pu

rcha

se o

n

of

deliv

ered

by

for

bille

d vi

a

of

orde

red

on

for

bille

d vi

afo

r

bille

d vi

a

com

pose

d offor

for

bille

d vi

a

from

subj

ect o

f

for

lead

to

lead

to

for

crea

ted

from

lead

to

for

lead

to

part

of

com

pose

d of

prec

eded

by

follo

wed

by

a st

ep to

war

d th

e fu

lfillm

ent o

f

fulfi

lled

by

on

vehi

cle

for

fulfi

llmen

t of

part

of

mad

e up

of

part

of

com

pose

d of

part

of

com

pose

d of



88

OrdersThis ERD (shown in Figure 37) illustrates the relationships between orders and significant entities related to orders such as assets, products, inventory locations, part movements, inventory transactions, activities, and parties. Orders include sales orders, service orders, purchase orders, and return material authorizations (RMAs) among others. The fulfillment of an order results in one or more part movements according to the instructions of the order. Each part movement results in one or more inventory transactions. Each order is usually the responsibility of a single internal or partner organization, but sometimes two or more. An order may be assigned or credited to one or more positions.


Table 37. Orders ERD Entities and Tables

Entity Tables

Activity S_EVT_ACT

Asset S_ASSET


Inventory Transaction S_INV_TXN

Inventory Transaction Type S_INV_TXN_TYPE

Order S_ORDER


Order Type S_ORDER_TYPE

Part Movement S_ACTPART_MVMT, S_ORDPART_MVMT

Part Movement Type S_PARTMVMT_TYPE

Party S_PARTY, S_ORG_EXT, S_POSTN, S_CONTACT

Product S_PROD_INT



Figure 37. Orders

Titl

e : O

rder

sA

utho

r : O

racl

e, C

onfid

entia

l

AS

SE

T

PR

OD

UC

T

INV

EN

TO

RY

T

RA

NS

AC

TIO

N

TY

PE

PA

RT

YO

RG

AN

IZA

TIO

N U

NIT

OT

HE

R O

RG

AN

IZA

TIO

N

INT

ER

NA

L/P

AR

TN

ER

OR

GA

NIZ

AT

ION

PO

SIT

ION

PE

RS

ON

OT

HE

R

PA

RT

Y

INV

EN

TO

RY

T

RA

NS

AC

TIO

N

PA

RT

MO

VE

ME

NT

OR

DE

R P

AR

T M

OV

EM

EN

TO

TH

ER

PA

RT

M

OV

EM

EN

TA

CT

IVIT

Y P

AR

T

MO

VE

ME

NT

AC

TIV

ITY

INV

EN

TO

RY

LO

CA

TIO

N

OR

DE

R IT

EM

PA

RT

M

OV

EM

EN

T

TY

PE

OR

DE

R T

YP

EO

RD

ER

SE

RV

ICE

OR

DE

R

SA

LES

OR

DE

R

PU

RC

HA

SE

OR

DE

R

RM

A

OT

HE

R O

RD

ER

for

prim

ary

cont

act f

or

for

cust

omer

of

resu

lt of

caus

e of

of

subj

ect t

o

of

mov

ed o

n

for

subj

ect o

f

for

subj

ect o

f

an in

stan

ce o

fm

ade

into

to

dest

inat

ion

of

from

sour

ce o

f

to

dest

inat

ion

of

of

for

resp

onsi

bilit

y of

resp

onsi

ble

for

resp

onsi

bilit

y of

resp

onsi

ble

for

proc

eded

by

follo

wed

by

part

of

com

pose

d of

of

for

for

subj

ect o

f

of

for

rela

ted

to

rela

ted

to

from

sour

ce o

f

for

fulfi

lled

by

part

of

com

pose

d of

part

of

com

pose

d of



90

Partner CollaborationPartner collaboration (shown in Figure 38) allows the brand owner's partner companies to give other partners visibility to their data. With this functionality, partners can more easily collaborate with other partners, without any required intervention from the brand owner company. Partner companies can start collaborations and invite other partners of the brand owner to join their collaborations. Once the invitation is accepted, individual partner companies who are now part of the collaboration can pledge resources (Positions) to the collaboration, making the resources available to all partners in the collaboration who may want to add the resource to a project or an opportunity.


Table 38. Partner Collaboration ERD Entities and Tables

Entity Tables

Business Unit S_BU

Collaboration S_PARTY_GROUP

Collaboration Resource S_PARTY_PER

Collaboration Invitation S_BRDCST_MSG

Party S_PARTY

Position S_POSTN



Figure 38. Partner Collaboration

��

��

��

��

��

1 ��

��

��

��

��O

racle

,�

��

.&

%�$

�%

%��

��

$%

�

��

$��

��

"�"

�"

.�

�

.&

%�$

�%

%��

��

$%

^��

�%

��

$%

�.'�

��

�

�$

�[�

��

$.

&%

�$�

%%

��

�$

%^��

�%

��

$%

�.'�

��

�%

��

$

.&

%�$

�%

%��

��

$%

�

��

$

"�

%%

�

�

��

9�

��"

�%

%�

�

�

''�

.�

��

��

$��$

>��

��

��$

��

��

+

��

9�

��

��

�+

��

%��

��$

��

�

$�[

��

��$

�&$

��

��

9�

��

�

�$

�[�

��O

$�

&$

��

�$�

��

$�

'0�

��

�$

��

��

�

�$

�[�

��

$

�

''�

.�

��

��

$

�

''�

.�

��

��

$�%

9�

��

!��

�%

�&

�

�

%9

��

�!

��

�

$�[

��

��$

�*�

��

�''�

.�

��

��

$

%9

��

�!

��

%��

��$

�*�

��

�''�

.�

��

��

$

��

3��1

3

��

3��

�

��

3��1

3

��

3��

�

�� 1

��

��

��

� �

� ��

�

��

1��

�

� �

��14�

��

� �

��

��

��13

��

�

� �

��

��

�

� �

��

��

�

� �

� ��

��

�



92

Partner Program RegistrationPartner Program Registration (shown in Figure 39) provides a system for the process of configuration and deployment of registration of partner programs. Partner Program Registration consists of three smaller and more manageable processes: a user registration process, a company registration process, and a partner program registration process.


Table 39. Partner Program Registration ERD Entities and Tables

Entity Tables

Application Approval Team S_PRG_APPL_PSTN

Application Attachment S_PRG_APPL_ATT

Application Question Answer S_PRG_APPL_QA

Approval List S_PRTNRPRG_PRTN

Eligibility List S_PRTNRPRG_PRTN

Partner S_ORG_EXT

Partner Program S_PRTNR_PROG

Partner Program Application S_PRTNRPRG_APPL

Partner Program Group S_PRTNRPRG_GRP

Partner Program Membership S_PRTNRPRG_MBR

Program Team S_PRTNRPRG_PSTN

Renew List S_PRTNRPRG_PRTN



Figure 39. Partner Program Registration

��

��

��

��

��

��

��

��

��

��

��

��O

racle

,�

��

��

�'�

��

��$

��

��

�

9"

�$

�

"�

�<

��

�%

�

"�

$�

��

�!

&

��'

�$�

.&

%�$

�%

%�&

$��

��

�

��

"��

��

"

'��

��

��

&�

��

�"

��

$�

;�'

�%�

��

��

�>

�'�'

�%�

�'�

�.�'

��+

�'�%

�

'�

$

&�

�

�

��

'�

�

�

��

�

�+

��

�"

�

��

'�

�

�

��

�

�+

�

��

'�

�

''�

%

��

��

&$

�

''�%

�

��

��

�9

��

%��

��$

��

��

$�

��

��

�

�"

��

�'�

��

��$

��

�'�

��

��$

7&

�%

��

$�

�$

%;

��

��

�'�

��

��$

��

��

��

>�

'��

��

"

��

��

$�

��

��

�

�"

�

��

&�

��

��

$�

��

��

�

�"

.�

%�

��

�

��

"

�!

!�

$!

��

��

�

�"

��

��

$�

�

��

��

$�

��

��

�

�"

�"�

".

��

%9

��

� �

��

��

2��

1��

��

�

6

�

� �

��

��

� �

��

��

� �

��14�

��

� �

��14�

��

��

��

��

�

� �

1��

��

�

6

�

� �

��14�

��

� ��

��

�

� ��

��

�

� �

��14�

��

� ��

��

�

� �

��14�

��

� �

��

��

��

�

��

��

�

��

��

��

��

��

��

6��

��

� � ��

��

�

��3

��

��1�

��

��1

3

� �

��

��

2��

� �

��6

��

��

�

��d

��

� �

��

�

��

��

��

��

� ��

��

�

� �

��

��

��

� �

��

��

��

��

2��

13

� �

��14�

��

��

� �

� �

��14�

��

� ��

��

��

1��

�



94

Party ModelThis ERD (shown in Figure 40) illustrates the structure of the party entity, its significant subtypes, and relationships. A party is either a person or some grouping of people such as an organization, a household, a position or a list of users. A person may be an employee or agent of the company using Siebel Business Applications. A person may also be considered a user if he or she has been granted user login credentials. An access group is a type of party that is made up of one or more groups. Addresses may be tracked for a person, a household, or an organization.


Table 40. Party Model ERD Entities and Tables

Entity Tables



Business Address S_ADDR_ORG


Group S_PARTY

Household S_ORG_GROUP, S_PARTY

Organization Relationship S_ORG_REL


Party S_PARTY

Party Relationship S_PARTY_REL


Person Relationship S_PARTY_REL or S_CONTACT_REL



User List S_PARTY

User Login S_USER



Figure 40. Party Model

��3�" �� Oracle��

�!!��%%

.&%�$�%%��!!��%%��%�$�'��!!��%%

��+��'��$%9��

��%�$��'��$%9��

��9��'��$%9��

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

��+

��&�

9�&%�9�'!

��%��$

&%��'�%�

��$�[��$�&$��

��&$�

��9��$�[��$�&$��

��9��&�

��%%��&�

��9��+

&%��'��$

��%�$

�"�'�+��0��$�

��9��%�$

��

��

��1��

� ��

��

��1��

��

��

��

��

��

��

� �

� ��

� �

� ��

� �

� ��

� �

� ��

6��

��

�

��

��

��



96

PaymentsThis ERD (shown in Figure 41) illustrates the support for payments provided in the Siebel Data Model. The payment entity supports payments made by customers to the company, as well as payments made by the company to customers, vendors, or others. A payment may be made to directly settle an order or to settle one or more Invoices. An invoice may be paid through one or more payments. A payment may be taken as a deduction from a prepayment balance available to the paying party.


Table 41. Payments ERD Entities and Tables

Entity Tables

Address S_ADDR_ORG

Invoice S_INVOICE

Order S_ORDER


Party S_PARTY



Prepayment Balance S_PREPAY_BAL



Figure 41. Payments

Title : PaymentsAuthor :Oracle, Confidential

PARTY

ORGANIZATION UNIT

ACCOUNTOTHER ORGANIZATION

PERSON

PREPAYMENT BALANCE

ADDRESS

INVOICE

ORDER

PAYMENT

INBOUND PAYMENT

OUTBOUND PAYMENT

for

located at

addressed to

receiver of

paid to

receiver of

received from

source for

debited from

source of

available to

entitled to

in settlement of

paid by

in settlement of

paid by

addressed to

used in

generated for

billed via



98

Performance ReviewThis ERD (shown in Figure 42) illustrates how the Siebel Data Model supports employee performance reviews. Review templates of various types (such as annual review, periodic review, customer satisfaction, MBO, KSO, and service level) can be specified to contain one or more Components (such as shared objectives, training plan, rollup, 360-degree evaluation, individual objectives, and skills). Components may be made up of standard review metrics. The performance review can then be created for a given employee and employee-specific objectives can be defined. At the end of the review period, the performance review can be completed and ratings given for assigned objectives and for the standard review metrics. Different rating scales can be defined and used for different types of reviews. Review templates can be specified for different job families and internal organizations. An employee may optionally be separately reviewed for performance in each of his or her assigned Positions.

This diagram also illustrates how the Siebel Data Model supports employee performance review by other employees within an organization. These employees can be employees at the same level, a higher level, or a lower level who may provide performance reviews for an employee to the manager of that employee. A set of evaluation questions can be defined and associated with different sets of employees. The reviewers answer the questions to evaluate the performance of the employee.


Table 42. Performance Review ERD Entities and Tables

Entity Tables

360 Evaluation S_PERF_360_EVAL

Competency S_CMPTNCY

Employee Criteria (PDQ) S_APP_VER, S_RVW_360_CS


Evaluation Script S_CS_PATH, S_CS_PATH_SCPT

Evaluation Script Answer S_CS_RUN, S_CS_RUN_ANSWR

Job Family S_JOB_FAMILY


Party S_PARTY

Performance Measurement Item S_PERF_MEAS_ITM

Performance Review S_EMP_PERF_MEAS

Period S_PERIOD



Review Component S_PERF_RVW_CMP

Review Component Language S_RVW_COMP_LANG

Review For Skill Item S_PERF_CMPTNCY



Review Metric S_PERF_RVW_MTRC

Review Rating S_PERF_RATING

Review Rating Scale S_PERF_RATING_SCL

Review Template S_PERF_RVW_TMPL

Review Template Component S_PERF_RVW_COMP

Table 42. Performance Review ERD Entities and Tables

Entity Tables



100

Figure 42. Performance Review

��

��

��

��

��

�2��

6�

��

��

��O

racle

��

��

�"

�'�

+�

��

�

��

��

�`�

!7

{

�>

�'&

��

��$

�%

��

��

�$

%;

��

�>

�'&

��

��$

�%

��

�

|}~��

>�

'&

��

��$

��

>��

;�

�

"�

�$

�$

��

'�

$

&�

�

=�

.�*

�"

�'+

��

>��

;��

��

�$

�%

�

'�

�

"�

�$

�$

��

�+

��

��

��

!��

+�

�

��

>��

;��

�"

�'�

��

��

��

!�

��

>��

;

�$

$&

�'��

�>

��;

".

��

�9

��

��

>��

;��

+�

�

�"

�'�

+�

��

��

*�

�"

�$

�

�"

��

%&

��

"�

$�

��

9�

��

"�

'�

+�

��

��

�*

��

"�

$

��

"�

�%

&�

�"

�$

�

�"

�'�

+�

��

��

�*

��

"�

$

��

�>

��;

�"

�'�

+�

��

&%

��

"�

��

%�

��%

*�

�

��$

�%

��

�

��

>��

;�

�"

��

$�

$�

��

>��

;�"

��

��

��

��

!

��

�*

��

"�

$

��"

��

%&

��

"�

$�

��

�"

��

�*

��

"�

$

��

�.

=�

�

�>�

��

�*

��

"�

$

��

��

>��

;�"

��

��

��

>��

;�*

��

�%<

�''��

�"

��

>��

;�

��

��$

��

��

+

��

%��

��$

��

�

$�[

��

��$

�&$

��

.&

%�$

�%

%�&

$��

��

9�

��

�

�$

�[�

��

$

�$�

��

$�

'0�

��

�$

��

��

�

�$

�[�

��

$

��

�%

�$ �

"�

'�

+�

��0��

�

$�

��

9�

��

��

%�

$

��

>��

;��

�"

�'�

��

��

"�

�$

�$

�

�

"�

��

�$

+

��

�1��

��

��

3��

��1

3

��

�2��

��

��1

3

�2��

��

��

�

��6

��

� �

�2��

��

��

��

�

?��

� �

�3��

�

� �

�3��

�

1��

�1��

��

1��

�1��

��

��2��

6��

��14�

��

��

��2

��

��

��

��

��

��

��

��

��14�

��

��

�1��

�

��

��

�1��

��

��

��

��

��

��

��

�

��

� �

� �

� ��

�

��

2��

��

2��

�

� �

��

�

��

��

��

��

��

��

�1��

�

��14�

��

��

��

��14�

��

��

��

��

��

��

��

��

��

��

��

3��1

3

��

��

3��

�

��

��

14�

��2��

��14�

��

� �

��

��

�

� ��

��

��

��

�

� ��

��

�

��

�13

� �

� �

� ��

�

1��

�

��

��

��



Personal AccountThis ERD (shown in Figure 43) illustrates how personal accounts (such as financial accounts or insurance policies) are accessible by contacts and associated with accounts, and how addresses are relevant for each of these. Also supported are associations between contacts and the membership of contacts in groups. Opportunities are associated with personal accounts to track the source of existing business.


Table 43. Personal Account ERD Entities and Tables

Entity Tables


Activity S_EVT_ACT


Opportunity S_OPTY


Personal Account S_ASSET

Personal Account Contact S_ASSET_CON


Product S_PROD_INT




102

Figure 43. Personal Account

Title : Personal AccountAuthor : Oracle, Confidential

CONTACT

SERVICE REQUESTACTIVITY

PERSONAL ADDRESS

ADDRESS USAGE

ORGANIZATION UNIT

PRODUCT OR SERVICE

OPPORTUNITY

PERSONAL ACCOUNT CONTACT

PERSONAL ACCOUNT

GROUP

ACCOUNT

for

named as

owner of

defined for

member of

made up of

by

user of

of

subject of

user of

used by

party on

accessed by

applicable to

subject of

parent ofpart of

user of

used by

for

source of

derived from

source ofdefined for

subject of

of

subject of

by

user of



Personal Financial ReviewThis ERD (shown in Figure 44) illustrates the information captured during the process of reviewing the financial status of an individual customer. The financial review process itself is tracked as an activity and becomes the source of the rest of the personal financial information of the contact, including assets, liabilities, income, expenses, and financial needs (such as retirement savings). When the financial needs of the contact are not fully addressed by his or her current financial product holdings, assets, or liabilities, the salesperson makes one or more financial recommendations. When a financial recommendation leads to a purchased product, such as a savings account or mortgage, the product instance can be associated with the recommendation that led to it. Assets may be located at a personal address and may be a source of income. Similarly, a liability, such as a mortgage, may be secured by an associated asset and may have periodic expenses associated with the liability.


Table 44. Personal Financial Review ERD Entities and Tables

Entity Tables

Activity S_EVT_ACT

Activity Product Instance S_ACT_ASSET

Asset (Liability) S_FN_ASSET_LIAB

Asset (Liability) Contact S_FN_ASSET_LIAB_CON


Contact Relationship S_CONTACT_REL

Financial Need S_FN_NEED

Financial Recommendation S_FN_RCMD

Household/Account S_ORG_GROUP, S_PARTY

Income (Expense) S_FN_INCM_EXP

Income (Expense) Contact S_FN_INCM_EXP_CON

Need Contact S_FN_NEED_CON

Opportunity S_OPTY


Product S_PROD_INT

Product Instance S_ASSET

Product Instance Contact S_ASSET_CON

Received Product Instance S_FN_RCMD_ASSET

Recommendation Contact S_FN_RCMD_CON



104

Figure 44. Personal Financial Review

Title

: P

ers

onal F

inancia

l R

evie

wA

uth

or

: O

racle

, C

onfidential

AS

SE

T L

IAB

. C

ON

TA

CT

AS

SE

T (

LIA

BIL

ITY

)

NE

ED

CO

NT

AC

T

RC

IVD

PR

OD

. IN

ST

.

AC

TIV

ITY

PR

OD

. IN

ST

.

FIN

AN

CIA

L N

EE

D

AD

DR

ES

SE

D N

EE

D

INC

OM

E (

EX

PE

NS

E)

INC

. E

XP

. C

ON

TA

CT

PE

RS

ON

AL A

DD

RE

SS

AC

TIV

ITY

CO

NT

AC

T

RE

CO

MM

EN

DA

TIO

N C

ON

TA

CT

FIN

AN

CIA

L R

EC

OM

ME

ND

AT

ION

HO

US

EH

OLD

/ A

CC

OU

NT

CO

NT

AC

T

RE

LA

TIO

NS

HIP

OR

G M

EM

BE

R

PR

OD

. IN

ST

. C

ON

TA

CT

PR

OD

UC

T IN

ST

AN

CE

CO

NT

AC

T

AC

TIV

ITY

FIN

AN

CIA

L

RE

VIE

W

PR

OC

ES

S

OP

PO

RT

UN

ITY

OR

GA

NIZ

AT

ION

UN

ITP

RO

DU

CT

OR

SE

RV

ICE

is p

rim

arily

incurr

ed b

y

has

of

associa

ted w

ith

with

has

from

sourc

e o

f

ow

ned b

y

ow

ns

managed b

y

vendor

of

of

incurr

ed b

y

report

ed d

uring

to r

evie

w

locate

d a

t

location o

f

because o

f

sourc

e o

f

with

join

tly h

as

with

associa

ted to

of

of

of

has

of

subje

ct of

ow

ned b

y

ow

ns

consid

ere

d o

n

consid

era

tion o

f

is a

is a

with

subje

ct of

of

from

report

ed d

uring

to r

evie

w

on

has a

of

regard

ing

of

subje

ct of

of

subje

ct of

addre

sses

is a

ddre

ssed b

y

of

subje

ct of

com

munic

ate

d d

uring

to u

nders

tand

for

prim

ary

subje

ct of

part

of

made u

p o

f

with

sourc

e o

f

recom

mended d

uring

sourc

e o

f

fors

ubje

ct of

locate

d a

t

for

in

part

icip

ate

s in

in

involv

es

with

subje

ct of

of

for

in

made u

p o

f

made u

p o

f

mem

ber

of

defined for

head o

f

to

has

of

has

of

mem

ber

of

with

associa

ted to

of

associa

ted w

ith

ow

ned b

y

ow

ns

part

of

made o

f

because o

f

affe

cts

for

sourc

e o

f

part

of

made u

p o

f

pro

duced b

y

vendor

of



Pricing ComparisonThis ERD (shown in Figure 45) illustrates the pricing comparison feature. A competitor's customer is viewed as an opportunity and by creating a quote using that competitor's price list the size of the opportunity can be quantified. Comparison quotes are generated using products and services from the internal price list that are similar to the competitor's offerings, to calculate the savings the customer could achieve by switching from the competitor.

Products and services provided by companies have complex pricing structures including tier-based pricing. Pricing also varies by region, payment method, service type, credit risk, and so on. The tier prices are associated with the attributes of the product or service that is provided.


Table 45. Pricing Comparison ERD Entities and Tables

Entity Tables


Object Class Extended Attribute S_XA_ATTR

Opportunity S_OPPTY



Pricing Matrix S_PRI_MTRX

Pricing Matrix Item S_PRI_MTRX_ITEM

Product Extended Attribute S_PROD_INT_XA


Product or Service Structure S_PROD_ITEM

Quote S_DOC_QUOTE


Quote Item Extended Attribute S_QUOTE_ITEM_XA

Tier Price Value S_VDISCNT_ITEM

Tier Pricing S_VOL_DISCNT



106

Figure 45. Pricing Comparison

Title : Pricing ComparisonAuthor : Oracle, Confidential

PRICING MATRIX

PRICING MATRIX ITEM

TIER PRICING

TIER PRICE VALUE

PRICE LISTINTERNAL PRICE LIST

COMPETITOR PRICE LIST

OBJECT CLASS EXTENDED ATTRIBUTE

PRODUCT EXTENDED ATTRIBUTE

PRICE LIST ITEM

INTERNAL ITEM

COMPETITOR ITEM

PRODUCT OR SERVICE

OBJECT CLASS

QUOTE ITEM EXTENDED ATTRIBUTE

OPPORTUNITY

PRODUCT OR SERVICE STRUCTURE

QUOTE

COMPETITOR

COMPARISON

QUOTE ITEM

for

composed of

comparison for

compared to

for

described by

subclass of

parent class of

part of

composed of

classified as

classification for

based on

basis of

for

have types of

priced via

used byfor

based on

forsubject of

forsubject of

priced via

used by

for

described by

of

componentof

for

assembly of

for

subject of

for

composed of

quotation for

subject of

for

described by

for

subject of



PricingThis ERD (shown in Figure 46) illustrates the pricing capabilities of Siebel Business Applications, including price lists, pricing matrices, and pricing models, and how they are related to simple and complex products or services to be priced. A price list is made up of price list items, each of which tracks the price for a given product or service. The list prices may be adjusted for certain extended attributes as defined in a specified pricing matrix. They may be adjusted based on changes to a customizable product through component price adjustments. They may also be modified through a specified pricing model made up of pricing factors.


Table 46. Pricing ERD Entities and Tables

Entity Tables

Component Price Adjustment S_PRI_CFG_ITEM


Object Class Extended Attribute S_XA_ATTR



Pricing Factor Item S_PRIFCTR_ITM

Pricing Factor Item Attrib S_PRIFCTITM_ATR

Pricing Matrix S_PRI_MTRX

Pricing Matrix Attribute S_PRI_ATTR

Pricing Matrix Item S_PRI_MTRX_ITEM

Pricing Matrix Value S_PRI_MTRX_VAL

Pricing Model S_PRIMDL

Pricing Model Factor S_PRIMDL_FCTR

Product Extended Attribute S_PROD_INT_XA


Product or Service Structure S_PROD_ITEM



108

Figure 46. Pricing

Titl

e : P

ricin

gA

utho

r : O

racl

e, C

onfid

entia

l

INT

ER

NA

L P

RO

DU

CT

OR

S

ER

VIC

E

PR

OD

UC

T O

R

SE

RV

ICE

S

TR

UC

TU

RE

CO

MP

ON

EN

T P

RIC

E

AD

JUS

TM

EN

T

PR

ICIN

G F

AC

TO

R

ITE

M A

TT

RIB

PR

ICIN

G F

AC

TO

R IT

EM

PR

ICIN

G M

AT

RIX

PR

ICE

LIS

T

PR

ICE

LIS

T

ITE

M

PR

ICIN

G M

OD

EL

FA

CT

OR

PR

OD

UC

T

EX

TE

ND

ED

A

TT

RIB

UT

E

OB

JEC

T C

LAS

S

EX

TE

ND

ED

A

TT

RIB

UT

E

OB

JEC

T C

LAS

S

PR

ICIN

G M

OD

EL

PR

ICIN

G M

AT

RIX

V

ALU

E

PR

ICIN

G M

AT

RIX

IT

EM

PR

ICIN

G M

AT

RIX

A

TT

RIB

UT

E

an a

djus

tmen

t for

the

subj

ect o

f

of

a co

mpo

nent

of

for

an a

ssem

bly

of

of

subj

ect o

f

defin

ed fo

r

refe

renc

ed b

y

for de

scrib

ed b

y

conf

igur

ed v

ia

used

by

base

d on

basi

s of

clas

sifie

d as

clas

sific

atio

n fo

r

for

adju

sted

via

cons

trai

nt fo

r

cons

trai

ned

by

for

mad

e up

of

for

base

d on

part

of

mad

e up

of

of o

bjec

t cla

ss

have

type

s

pric

ed v

ia

used

by

for

com

pose

d of

for

mad

e up

of

for de

scrib

ed b

y

for

subj

ect o

f

subc

lass

of

pare

nt c

lass

of



Product PromotionProduct Promotion (shown in Figure 47) provides a system for managing product promotions. Production Promotion allows the user to fully define the promotion based on products, product templates, product attributes, and so on. Product Promotion also allows the user to specify other information for the promotion including the terms, charges, and pricing rules.


Table 47. Product Promotion ERD Entities and Tables

Entity Tables

Conditional Charge Prorate Plan S_AGR_PR_PLAN

Product Promotion S_PROD_INT

Product Promotion Charge S_PROM_CHRG

Product Promotion Item S_PROM_ITEM

Product Promotion Item Attribute S_PROM_ITEM_XA

Product Promotion Item Attribute Value S_PROMITM_VAL

Product Promotion Pricing Matrix Rule S_PROM_PMTRX

Product Promotion Term S_PROMITM_TRMS

Product Promotion Term Description S_PROD_TRM_DESC



110

Figure 47. Product Promotion

Title

: P

RO

DU

CT

PR

OM

OT

ION

Au

tho

r :

Ora

cle

, C

on

fid

en

tia

l

CO

ND

ITIO

NA

L C

HA

RG

E

PR

OR

AT

A P

LA

N

PR

OD

UC

T P

RO

MO

TIO

N T

ER

M

DE

SC

RIP

TIO

N

PR

OD

UC

T P

RO

MO

TIO

N P

RIC

ING

MA

TR

IX R

ULE

AD

JU

ST

ME

NT

GR

OU

P

PR

OD

UC

T P

RO

MO

TIO

N T

ER

M

PR

OD

UC

T P

RO

MO

TIO

N C

HA

RG

E

PR

OD

UC

T P

RO

MO

TIO

N IT

EM

AT

TR

IBU

TE

V

ALU

E

PR

OD

UC

T P

RO

MO

TIO

N IT

EM

AT

TR

IBU

TE

PR

OD

UC

T P

RO

MO

TIO

N IT

EM

PR

OD

UC

T

PR

OD

UC

T P

RO

MO

TIO

N

child

of

root of

define for

has

pare

nt of

child

of

associa

te to

associa

te b

y

define for

has

define for

has

define for

has

define for

has

made u

p

conta

in

define for

has

for

conta

in



Product Quality TrackingThis ERD (shown in Figure 48) illustrates the significant entities related to product defect tracking. Defects can be associated with service requests and may have associated activities defined to fix the defect. Associations may be defined with various product or product versions to record which are affected by the defect, which are planned to fix the defect, and which actually fix the defect. Additional relevant associations with external products may be recorded. Defects may be associated with other, related defects.


Table 48. Product Quality Tracking ERD Entities and Tables

Entity Tables

Activity S_EVT_ACT

Defect Symptom S_PRDFCT_SYMP



Product or Service S_PROD_INT, S_PROD_EXT

Product Quality Item S_PROD_DEFECT

Project S_PROJ

Project Item S_PROJITEM

Resolution Item S_RESITEM




112

Figure 48. Product Quality Tracking

Title

: P

rod

uct

Qu

alit

y T

rackin

gA

uth

or

: O

racle

, C

on

fid

en

tia

l

PE

RS

ON

EM

PLO

YE

E / A

GE

NT

OT

HE

R P

ER

SO

N

PR

OJE

CT

PR

OD

UC

T

RE

LE

AS

E

PR

OJE

CT

OT

HE

R

PR

OJE

CT

S

OR

GA

NIZ

AT

ION

UN

IT

OT

HE

R

OR

GA

NIZ

AT

ION

U

NIT

INT

ER

NA

L /

PA

RT

NE

R

OR

GA

NIZ

AT

ION

U

NIT

DE

FE

CT

S

YM

PT

OM

PR

OJE

CT

IT

EM

RE

QU

IRE

D

FE

AT

UR

E

QA

TE

ST

RE

SO

LU

TIO

N IT

EM

PR

OD

UC

T O

R S

ER

VIC

E

EX

TE

RN

AL P

RO

DU

CT

INT

ER

NA

L P

RO

DU

CT

OR

SE

RV

ICE

INT

ER

NA

L P

RO

DU

CT

VE

RS

ION

OT

HE

R IN

TE

RN

AL P

RO

DU

CT

OR

SE

RV

ICE

INT

ER

NA

L P

RO

DU

CT

SE

RV

ICE

RE

QU

ES

TP

RO

DU

CT

QU

ALIT

Y IT

EM

PR

OD

UC

T P

AT

CH

/

EN

HA

NC

EM

EN

T

RE

QU

ES

T

PR

OD

UC

T D

EF

EC

T

OT

HE

R P

RO

DU

CT

QU

ALIT

Y IT

EM

AC

TIV

ITY

SE

RV

ICE

RE

QU

ES

T A

CT

IVIT

Y

QU

ALIT

Y E

NH

AN

CE

ME

NT

A

CT

IVIT

Y

OT

HE

R A

CT

IVIT

Y

report

ed b

y

report

er

of

report

ed b

y

report

er

of

ow

ned b

y

ow

ner

of

ow

ned b

y

ow

ner

of

a c

om

ponent of

an a

ssem

bly

of

report

ed v

iacaused b

y

defined for

handle

d v

ia

based o

n

basis

for

prim

arily

by

prim

ary

of

defined for

fixed v

ia

belo

ng to

inclu

des

resolv

ed by

solu

tion to

part

of

made u

p o

f

solu

tion to

resolv

ed b

y

ow

ned b

y

ow

ner

of

observ

ed for

exhib

itio

n o

f

in e

nvironm

ent of

part

of

vers

ion o

fpro

duced in

part

of

made u

p o

f

rela

ted to

rela

tion

of

duplic

ate

of

duplic

ate

d

as

report

ed for

afflic

ted

with

pla

nned to

be fix

ed in

targ

et

fix for

actu

ally

fix

ed in

actu

al fix for



Product RecommendationProduct Recommendation (shown in Figure 49) provides a system for managing product recommendations for up-sell or cross-sell. Product Recommendation allows the user to clearly define the messages, the set of possible responses, and the recommendation itself.


Table 49. Product Recommendation ERD Entities and Tables

Entity Tables

Communication S_COMMUNICATION

Product Message S_PROD_MSG

Product Message Response S_PROD_MSG_RESP

Product Message Variable S_PROD_MSG_VAR


Product Recommendation S_PROD_RECMNDTN



114

Figure 49. Product Recommendation

Title : Product Recommendation Author : Oracle, Confidential

PRODUCT MESSAGE VARIABLE

COMMUNICATION PRODUCT MESSAGE RESPONSE

PRODUCT MESSAGE

PRODUCT RECOMMENDATION

PRODUCT OR SERVICE

actual response for

have

defined for

utilize

displayed via

template for

for

have

recommendation for

recommended via

for

subject of



Products or ServicesThis ERD (shown in Figure 50) illustrates the significant entities related to a product including product components (product structure), substitute or competitive products (product comparison), the product's vendor, the product line or lines to which the product belongs, and so on. In addition, this diagram illustrates the relationship between products and product prices, as well as the language translations for some of these entities.


Table 50. Products or Services ERD Entities and Tables

Entity Tables

Catalog S_CTLG


Class Attribute S_XA_ATTR

Class of Product or Service S_VOD, S_VOD_VER

Language S_LANG



Product Assembly Port S_PROD_ITEM


Product or Service S_PROD_INT or S_PROD_EXT

Product or Service Attribute S_PROD_INT_XA

Product Structure S_PROD_ITEM

Vendor S_ORG_EXT, S_PARTY



116

Figure 50. Products or Services

Title

: P

rod

ucts

or

Se

rvic

es

Au

tho

r : O

racle

, C

on

fid

en

tia

l

VE

ND

OR

PR

OD

UC

T A

SS

EM

BL

Y

PO

RT

CA

TA

LO

G C

AT

EG

OR

Y

CA

TA

LO

G

LA

NG

UA

GE

PR

OD

UC

T O

R S

ER

VIC

E

AT

TR

IBU

TE

CL

AS

S A

TT

RIB

UT

E CL

AS

S O

F P

RO

DU

CT

OR

S

ER

VIC

E

PR

ICE

LIS

T I

TE

M

PR

OD

UC

T

ST

RU

CT

UR

E

PR

OD

UC

T

LIN

E

PR

OD

UC

T O

R S

ER

VIC

E

EX

TE

RN

AL

PR

OD

UC

T O

R S

ER

VIC

E

INT

ER

NA

L P

RO

DU

CT

OR

SE

RV

ICE

PR

ICE

L

IST

pro

du

ce

d b

y

pro

du

ce

r o

f

a r

ep

ort

to

a p

are

nt

to

tra

nsla

tio

n f

or

tra

nsla

ted

in

to

va

lid f

or

co

nstr

ain

ed

b

yd

efin

ed

fo

r

de

scrib

ed

via

tra

nsla

tio

n f

or

tra

nsla

ted

in

toch

ild o

f

pa

ren

t to

tra

nsla

tio

n f

or

tra

nsla

ted

in

to

ba

se

d o

n

ba

sis

fo

r

tra

nsla

tio

n f

or

tra

nsla

ted

in

to

tra

nsla

tio

n

for

tra

nsla

ted

in

to

for

ca

teg

orize

d in

pa

rt o

f

ma

de

up

of

of

su

bje

ct

of

of

su

bje

ct

of

of

su

bje

ct

of

a c

lassific

atio

n f

or

cla

ssifie

d in

co

mp

ose

d o

f

pa

rt o

f

for

co

mp

ose

d o

f

a c

olle

ctio

n o

f

pa

rt o

f

an

a

sse

mb

ly

of

for

a

co

mp

on

en

t o

f

of



Professional ServicesThis ERD (shown in Figure 51) illustrates how Siebel Business Applications support the planning and execution of Professional Services projects. Projects can be defined for an external or internal client, as the responsibility of one or more internal organizations, subcontracted to one or more partners, associated with a required skill set, and made accessible to one or more positions. The definition of required project team roles allows project billings to be estimated based on the billing rate and the number of hours required from the resource. An employee, a sub-contractor employee or a contact can ultimately fill a team role from the client, but until then, a list of potential project resources can be stored for the project or a specific project team role. Positions and project team roles can be associated with a service billing product to define the billing rate for that entity from a billing rate list. Project issues can be tracked for a project, assigned to a project team role, and detailed as a series of activities. Receivable Invoices billed to the client or payable invoices from subcontractors can be associated with the project.


Table 51. Professional Services ERD Entities and Tables

Entity Tables

Activity S_EVT_ACT

Address S_ADDR_ORG

Billing Rate List S_PRI_LST


Internal/Partner Organization S_ORG_EXT, S_PARTY

Invoice S_INVOICE

Lead Source S_SRC

Opportunity S_OPTY




Potential Project Resource S_PROJ_PTL_RSRC

Project S_PROJ

Project Contact S_PROJ_CON

Project Issue S_PROJ_ISS


Skill S_PROJRSRC_SKL



118

Figure 51. Professional Services

Titl

e : P

rofe

ssio

nal S

ervi

ces

Aut

hor

: O

racl

e, C

onfid

entia

l

AD

DR

ES

SO

RG

AN

IZA

TIO

N U

NIT

OT

HE

R

OR

GA

NIZ

AT

ION

U

NIT

INT

ER

NA

L/P

AR

TN

ER

O

RG

AN

IZA

TIO

N

PE

RS

ON

OT

HE

R

PE

RS

ON

EM

PLO

YE

E /

AG

EN

TIN

VO

ICE

SK

ILL

LEA

D

SO

UR

CE

OP

PO

RT

UN

ITY

BIL

LIN

G R

AT

E

LIS

TS

ER

VIC

E

BIL

LIN

G

PO

SIT

ION

T

YP

E PO

SIT

ION

AC

TIV

ITY

PR

OJE

CT

TE

AM

RO

LE

PR

OJE

CT

ISS

UE

PO

TE

NT

IAL

PR

OJE

CT

R

ES

OU

RC

E

PR

OF

ES

SIO

NA

L S

ER

VIC

E P

RO

JEC

T

PR

OJE

CT

CO

NT

AC

T

for

the

reso

lutio

n of

subj

ect

of

resp

onsi

bilit

y of

resp

onsi

ble

for

acce

ssib

le t

o

acce

ssor

of

subc

ontr

acte

d to

a pa

rtne

r fo

r

for

the

clie

nt o

f

sent

to

for

loca

ted

at

for

for lo

cate

d at

empl

oyed

by

com

pose

d of

fille

d by

assi

gned

to

fill

of

defin

ed a

s

for

subj

ect

of

for

subj

ect

of

requ

ired

by

requ

irer

of

requ

irer

ofrequ

ired

by

bille

d fo

r

bille

d by

bille

d fo

r

bille

d in

of

invo

lved

inoc

cupa

nt o

f held

by

sour

ce o

f

beca

use

of

defin

ed fo

r

requ

irer

of

for

subj

ect

of

defin

ed b

y

subj

ect

ofto

tra

ck w

ork

on

subj

ect

ofso

urce

of

the

outc

ome

of

bille

d as bi

lling

typ

e fo

r

billi

ng t

ype

for

bille

d as

bille

d vi

a

for

assi

gned

to

assi

gned

to

for

targ

eted

at



RevenueThis ERD (shown in Figure 52) illustrates how revenue items are tracked and analyzed in Siebel Business Applications. Revenue Items may be defined for any number of confirmed or likely business transactions such as opportunities, accounts, projects, marketing events or activities, agreements, invoices, and so on. Revenue is generally attributed to a product, service, product line, or some description of the product or service offering. Credit for the revenue can be spread across sales team members by breaking the revenue into a line for each sales team member with their credit amounts. Recurring or incoming revenues over a period of time (weeks, months, or years) can be shown by using the revenue schedule capabilities. A revenue template with detailed items can be created for this purpose.


Table 52. Revenue ERD Entities and Tables

Entity Tables


Agreement Item S_AGREE_ITEM

Invoice S_INVOICE

Invoice Item S_INVC_ITEM


Opportunity S_OPTY






Project S_PROJ

Revenue Item S_REVN

Revenue Template S_REVN_TMPL

Revenue Template Item S_REVN_TMPL_ITM




120

Figure 52. Revenue

Titl

e : R

even

ueA

utho

r : O

racl

e, C

onfid

entia

l

RE

VE

NU

E T

EM

PLA

TE

IT

EM

RE

VE

NU

E T

EM

PLA

TE

RE

VE

NU

E IT

EM

OP

PO

RT

UN

ITY

PO

SIT

ION

PE

RS

ON E

MP

LOY

EE

/ A

GE

NT

OT

HE

R P

ER

SO

N

AG

RE

EM

EN

T

SE

RV

ICE

RE

QU

ES

T

OR

GA

NIZ

AT

ION

UN

IT

INT

ER

NA

L /

PA

RT

NE

R

OR

GA

NIZ

AT

ION

U

NIT

OT

HE

R

OR

GA

NIZ

AT

ION

U

NIT

PR

OD

UC

T L

INE

CO

NT

RA

CT

ITE

M

PR

OJE

CT

INV

OIC

E IT

EM

PR

OD

UC

T O

R S

ER

VIC

E

MA

RK

ET

ING

EV

EN

T O

R

AC

TIV

ITY

INV

OIC

E

for

attr

ibut

ed to

base

d on tem

plat

e ite

m fo

r

base

d on

tem

plat

e fo

r

for

subj

ect o

f

for

attr

ibut

ed to

deta

iled

item

of

reve

nue

plan

for

deta

ils o

f

cons

ist o

f

a re

port

tom

anag

er o

f

for

attr

ibut

ed to

part

of

mad

e up

of

held

by

occu

pant

of

for

owne

r of

for

subj

ect o

f

for

attr

ibut

ed to

for

subj

ect o

f

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

belo

ngs

to

subj

ect o

f

com

pose

d of

part

of



Sales Hierarchy and Credit AssignmentThe Sales Hierarchy Module allows organizations to build sales hierarchies on top of sales territories and to assign sales credits to territories and positions accordingly. A sales hierarchy (shown in Figure 53) consists of sales territories, which are made up of positions and crediting rules. The sales hierarchy can be versioned to accommodate ongoing changes without losing track of its history. A position can be assigned to different territories or the same territory with different start date and end date. A crediting rule can be applied to positions with allocation percentage defined. For a given hierarchy version, the credit assignment engine is able to identify all the positions assigned to the territories and all the applicable crediting rules by effective start date and end date. The crediting rules, their criteria and values are read by Siebel Assignment Manager, which performs the assignments appropriately. The sales hierarchy needs to be approved and validated before taking effect.


Table 53. Sales Hierarchy and Credit Assignment ERD Entities and Tables

Entity Tables

Credit Allocation S_SLSCR_RL_PSTN

Credit Assignment Rule S_SLSCRDT_RULE

Credit Rule Criteria S_SLSCRDT_CRIT

Credit Rule Criteria Value S_SLSCRDT_VAL

Hierarchy Version S_SLS_HIER_VER

Hierarchy Version Territory S_SLS_HIER_TERR


Position Territory Assignment S_SLSTERR_POSTN

Sales Hierarchy S_SLS_HIER

Sales Territory S_SLS_TERR



122

Figure 53. Sales Hierarchy and Credit Assignment

Titl

e : S

ales

Hie

rarc

hy a

nd C

redi

t Ass

ignm

ent

Aut

hor

: Ora

cle,

Con

fiden

tial

PO

SIT

ION

TE

RR

ITO

RY

AS

SIG

NM

EN

T

PA

RT

Y

OT

HE

R P

AR

TY

PO

SIT

ION

CR

ED

IT A

LLO

CA

TIO

N

CR

ED

IT R

ULE

CR

ITE

RIA

V

ALU

E

CR

ED

IT R

ULE

CR

ITE

RIA

CR

ED

IT A

SS

IGN

ME

NT

R

ULE

RU

LE T

YP

E

VA

LID

AT

ION

RU

LE

HIE

RA

RC

HY

VE

RS

ION

T

ER

RIT

OR

Y

HIE

RA

RC

HY

V

ER

SIO

N

SA

LES

TE

RR

ITO

RY

SA

LES

HIE

RA

RC

HY

tran

sfer

to

reci

pien

t of

rollu

p to

reci

pien

t of

subo

rdin

ate

to

pare

nt o

f

part

of

com

pose

d of

assi

gned

terr

itory

assi

gned

to

appl

icab

le to

subj

ect o

f

allo

cate

d to

reci

pien

t of

appr

oved

appr

ove

appr

oved

by ap

prov

e

appr

oved

by

appr

ove

appr

oved

by ap

prov

e

defin

ed fo

r

char

acte

rized

by

defin

ed fo

r

char

acte

rized

by

allo

catio

n of

subj

ect o

f

assi

gnm

ent o

f

cons

ists

of

cate

gorie

d by

subj

ect o

f

appl

ied

to

valid

ated

by

vers

ion

of

assi

gned

to

vers

ion

of

vers

ione

d by

belo

ngs

to

cons

ists

of



Sales Portfolio ManagementThis ERD (shown in Figure 54) illustrates the process of creating and managing sales portfolios for employees in sales positions within the sales organization. It shows the process for creating a sale portfolio, setting target accounts for a given portfolio, and defining the business or service units for each associated account as well as their business drivers and initiatives. Also illustrated are partners and partner's competitors associated with the portfolio accounts. In addition, this ERD covers the marketing campaigns which are targeted at the accounts in the portfolios.


Table 54. Sales Portfolio Management ERD Entities and Tables

Entity Tables

Sales Portfolio S_SLS_PORTFOLIO

Portfolio Category S_PRTFL_CTGRY

Portfolio Account S_PRTFL_ACCNT

Product Offering S_ENT_SOLN

Portfolio Partner S_PRTFL_PRTNR

Portfolio Attachment S_PRTFL_ATT

Portfolio Product Offering S_PRTFL_ENTSOLN

Account Prod Offering S_PRTFL_ACCSOLN

Portfolio Sub_Account S_PRTFL_SUBACC

Portfolio Account Attachment S_PRTFL_ACC_ATT

Portfolio Business Driver S_PRTFL_BU_DRVR

Portfolio Business Initiative S_PRTFL_BU_INTV

Campaign S_SRC

Portfolio Account Campaign S_PRTFL_CAMP

Portfolio Partner Competitor S_PRTFL_CMPTR

Organization Unit S_ORG_EXT



124

Figure 54. Sales Portfolio Management

��

��%

��

��

��

� ��

�"��

��

��

��

��O

racle

��

��

��

�

$�[

��

��$

�&$

��

��

9�

��

�

�

&$

�

��

��

$�

��

��

�

$�[

��

��$

�

"�

��

��

��

��

�

$�[

��

��$

�

�

&$

�

��

��

*�

'��

��

�

&$

��

�"

��

�$

��

��

*�

'��

��

��

�$

��

�

�"

��

��

��

��

��

*�

'��

��

��

�$

��

�

"�

��

$

��

��

*�

'��

�.&

%�$

�%

%�

�$��

��

�>�

��

��

*�

'��

�.&

%�$

�%

%�

!�

�>�

�

��

��

*�

'��

��

�&

$�

��

��

�

9"

�$

�

��

��

*�

'��

��

��

�

9"

�$

�

��

��

*�

'��

�%&

.��

�&

$�

�

�

&$

��

��

!�

�*

*�

��$

��

��

*�

'��

��

�!

&

��

�*

*�

��$

��

��

*�

'��

��

�

&$

�

��

��

*�

'��

�

��

�

��

+

��

�!

&

��

�*

*�

��$

%

�'�

%��

��

�*

�'��

� �

��14�

��

� �

��

��

��

13

� �

��

��

��

� �

��

��

��

� �

��

��

��14�

��

��

��14�

��

� �

��14�

��

��2

��

��2

��

� �

� �

��14�

��

� �

� ��

��

� �

��

��

� �

��

��

�

��

� ��@��

��

� �

� ��

�

� ��

��

��

� �

� �

��

2��

��

6��

�

��

��

� �

��

��

�

��14�

��

1��

��

��2

��

��



Service AgreementThis ERD (shown in Figure 55) illustrates how Siebel Business Applications support service agreements. A service agreement is a contract that entitles one or more contacts at one or more organizations to service or support on one or more items through entitlements. Entitlement items define coverage of products or specified instances of a product. The entitlement can be constrained by a service calendar (to indicate 24x7 coverage, for example), and may be subject to one or more metrics (that describe a guaranteed two-hour response, for example).


Table 55. Service Agreement ERD Entities and Tables

Entity Tables



Agreement Entitlement S_ENTLMNT

Agreement Item S_AGREE_ITEM

Asset S_ASSET


Entitled Product or Asset S_ENTLMNT_ITEM

Entitled Service S_ENTL_ACT_TYPE

Expense Type S_EXP_ITEM_TYPE

Material S_PROD_INT

Order S_ORDER

Preventive Maintenance S_PM_PLNITM

Price Adjustment S_ENTL_PRDPRI

Product S_PROD_INT

Service Calendar S_SCHED_CAL

Service Metric S_SVC_METRIC


Work Type S_PROJ



126

Figure 55. Service Agreement

Titl

e :

Ag

ree

me

nt

En

title

me

nt

A

uth

or

: O

racl

e,

Co

nfid

en

tial

AG

RE

EM

EN

T

ITE

M

AG

RE

EM

EN

T

ITE

M R

EN

EW

AL

TE

RM

SE

RV

ICE

C

ALE

ND

ER

MA

TE

RIA

L

WO

RK

T

YP

E

EX

PE

NS

E

TY

PE

AC

TIO

N

TY

PE

PR

EV

EN

TIV

E

MA

INT

EN

AN

CE

SE

RV

ICE

M

ET

RIC

OR

DE

R

SE

RV

ICE

R

EQ

UE

ST

EN

TIT

LE

D

SE

RV

ICE

AC

CO

UN

TC

ON

TA

CT

AS

SE

T

AG

RE

EM

EN

T

PR

ICE

AD

JUS

TM

EN

TP

RO

DU

CT

EN

TIT

LE

D P

RO

DU

CT

OR

AS

SE

T

AG

RE

EM

EN

T E

NT

ITLE

ME

NT

for

subje

ct of

for su

bje

ct of

base

d on

basi

s for

part

of

made up o

f

const

rain

ed b

y

use

d b

y

em

plo

yed a

t

em

plo

yer

of

bill

able

for

bill

able

as

bill

able

for

bill

able

as

bill

able

for

bill

able

as

defin

ed for

suje

ct o

f

of fo

r

an

inst

ance

of m

ade

into

with

subje

ct o

f

for su

bje

ct o

ffo

r

subje

ct o

f

base

d o

n

basi

s fo

r

cove

red b

y

for

for

cove

red b

y

entit

led b

y

basi

s fo

r

entit

led b

y

basi

s fo

r

base

d o

n basi

s fo

r

base

d o

n basi

s fo

r

base

d o

n

basi

s fo

r

for

subje

ct o

f

part

of

made u

p o

f



Service Calendars and Work ShiftsThis ERD (shown in Figure 56) illustrates the structure of service calendars and work shifts. Both are made up of a set of working hours for each day of the week with a single exception calendar defining planned holidays and other exceptional working days. An employee can be assigned to a work shift to define his or her normal working hours with exceptional working or non-working hours expressed as employee exception hours.


Table 56. Service Calendars and Work Shifts ERD Entities and Tables

Entity Tables

Employee S_CONTACT, S_EMP_PER, S_PARTY

Employee Exception Hours S_EXCPT_CAL_HRS

Exception Calendar S_EXCPT_CAL

Exception Calendar Hours S_EXCPT_CAL_HRS


Schedule Calendar S_SCHED_CAL

Schedule Calendar Hours S_SCHED_CAL_HRS

Service Calendar S_SCHED_CAL

Work Shift S_SCHED_CAL



128

Figure 56. Service Calendars and Work Shifts

Title : Service Calendars and Work ShiftsAuthor : Oracle, Confidential

PERSON

OTHER PERSONEMPLOYEE / AGENT

EMPLOYEE EXCEPTION HOURS

EXCEPTION CALENDAR HOURS

EXCEPTION CALENDAR

SCHEDULE CALENDAR HOURS

SCHEDULE CALENDAR

WORK SHIFT

SERVICE CALENDAR

assigned to

worked by

worked by

contributor of

a report tomanager of

for of

for

of

for

of



Service RequestThis ERD (shown in Figure 57) illustrates how service requests are handled as a series of activities, each owned by a specific employee. Relevant information includes the contact who reported the service request, the product with which assistance is requested along with the customer's environment or profile, and specifically which third-party products are in use and relevant to the service request.


Table 57. Service Request ERD Entities and Tables

Entity Tables

Activity S_EVT_ACT

Asset (Product Instance) S_ASSET

External Product Instance S_ORG_PRDEXT

Party S_PARTY, S_ORG_EXT, S_CONTACT, S_USER

Product or Service S_PROD_INT, S_PROD_EXT

Service Region S_SRV_REGN



130

Figure 57. Service Request

Titl

e : S

ervi

ce R

eque

stA

utho

r :

Ora

cle,

Con

fiden

tial

SE

RV

ICE

R

EG

ION

PA

RT

Y OR

GA

NIZ

AT

ION

UN

IT

INT

ER

NA

L / P

AR

TN

ER

O

RG

AN

IZA

TIO

N U

NIT

OT

HE

R O

RG

AN

IZA

TIO

N

UN

IT

OT

HE

R P

AR

TY

PE

RS

ON O

TH

ER

PE

RS

ON

EM

PLO

YE

E /

AG

EN

T

AS

SE

T (

PR

OD

UC

T

INS

TA

NC

E)

AC

TIV

ITY

OT

HE

R A

CT

IVIT

YS

ER

VIC

E R

EQ

UE

ST

AC

TIV

ITY

EX

TE

RN

AL

PR

OD

UC

T

PR

ES

EN

CE

SE

RV

ICE

RE

QU

ES

T

PR

OD

UC

T O

R S

ER

VIC

E

EX

TE

RN

AL

PR

OD

UC

T O

R

SE

RV

ICE

INT

ER

NA

L P

RO

DU

CT

OR

SE

RV

ICE

at

subj

ect o

f

resp

onsi

bilit

y of

resp

onsi

ble

for

resp

onsi

bilit

y of

resp

onsi

ble

for

resp

onsi

bilit

y of

resp

onsi

ble

for

owne

d by

owne

r of

resp

onsi

bilit

y of

resp

onsi

ble

for

resp

onsi

bilit

y of

resp

onsi

ble

for

in

envi

ronm

ent

of

part

of

prof

ile o

f

of

subj

ect o

f

for

prob

lem

s w

ith

subj

ect o

f

for

prob

lem

s w

ith subj

ect o

f

an in

stan

ce o

f

man

ufac

ture

d in

to

part

of

mad

e up

of

in

envi

ronm

ent

of

part

of

prof

ile o

f

for

subj

ect o

fm

ade

up o

fpa

rt o

f

repo

rted

by

repo

rter

of



ShipmentThis ERD (shown in Figure 58) illustrates the relationship between orders, quote, products, inventory locations, and shipment related to orders. Delivery requests and delivery promises (date of delivery, delivery quantity) can be associated with order items and quote items.


Table 58. Shipment ERD Entities and Tables

Entity Tables


Order S_ORDER, S_ORDER_SHIP

Order Item Delivery Request S_ORDPART_REQ

Order Line Item S_ORDER_ITEM

Order Part Movement S_ORDPART_MVMT, S_SHIPMENT_MVMT

Part Movement Type S_PARTMVMT_TYPE


Quote S_DOC_QUOTE, S_DOC_ORDER

Quote Item Delivery Promise S_QTE_ITM_DLVRQ

Quote Item Delivery Request S_QTE_ITM_DLVRQ

Quote Line Item S_QUOTE_ITEM

Shipment S_SHIPMENT



132

Figure 58. Shipment

��

��%

��

��

��

��

� O

racle

� ��

��

��

�"�

>�

"�

$�

��

+�

�

��

!�

��

��

��"

�>

�"

�$

� ��

9�

��

��

��"

�>

�"

�$

�

��

!�

��

�"

�!�

'�>

��

+��

��

"�%

�

%9

��"

�$

��'

�$�

��

�"

��

!�

��

�"

�!

�'�>

��

+��

�7

&�

%�

%9

��"

�$

��

�!

��

�'�$

��

�"

7&

��

��

�"

�!

�'�>

��

+��

�7

&�

%�

7&

��

��

�"

�!

�'�>

��

+�

��

�"

�%�

7&

��

��'

�$�

��

�"

7&

��

�

��

!�

�

��

�!

&

��

�$�

��

$�

'

�$>

�$

��

�+

�'�

�

��

$

�3��

�

�3��

��

��1

3

� ��

6��1

3

� �

��

��1

3

��

��

��

� �

� ��

�

��

� �

� �

��

1��

�

1��

��

��2

��3

�2��

��

�

��2

��

��1

3

��

� �

� �

� ��

�

� �

��

� �

��

� �

��

� ��

��

�

� ��

��

�

��

� �

� �

� ��

�

1��

��

1��

�

��

� �

� �

� ��

�

�

��

�

� ��

��

�

� ��

��

�

��

��

��

��

��

� �

��

��

��

��

��

��

��

��

��

��

��



Siebel AssistantThis ERD (shown in Figure 59) illustrates how Siebel Business Applications support the Siebel Assistant functionality. Personal or corporate sales planning items can be defined to serve as template assessments or template activity plans. Both types of sales planning items can be defined as relevant to one or more sales stages within one or more sales methodologies. A template assessment contains one or more attributes, optionally validated by a set of valid values. Actual Assessments are created from a template assessment during a specific sales stage to assess an opportunity, an account, or a contact. A template activity plan is made up of one or more template activities. Actual activity plans are created from a template activity plan during a specific sales stage to prompt the user to plan certain activities copied from the template activities.


Table 59. Siebel Assistant ERD Entities and Tables

Entity Tables


Activity S_EVT_ACT

Activity Plan S_EVT_ACT

Activity Plan Template S_TMPL_PLANITEM

Assessment Template S_TMPL_PLANITEM

Assessment S_ASSESS

Assessment Attribute S_ASSESS_ATTRIB

Assessment Attribute Valid Value S_ASSESS_ATTVAL

Assessment Value S_ASSESS_VAL


Opportunity S_OPTY

Opportunity Stage S_OPTY_STG


Sales Methodology S_SALES_METHOD

Sales Stage S_STG

Stage Plan Item S_STG_PLANITEM

Stage Recommendation S_STG_RECOMMEND

Template Activity S_EVT_ACT



134

Figure 59. Siebel Assistant

Title

: S

iebel A

ssis

tant

Auth

or

: O

racle

, C

onfidential

AC

CO

UN

T

AC

TIV

ITY

OT

HE

R A

CT

IVIT

Y

TE

MP

LA

TE

A

CT

IVIT

Y

AC

TIV

ITY

P

LA

N

OP

PO

RT

UN

ITY

ST

AG

E

SA

LE

S

ME

TH

OD

OLO

GY

PE

RS

ON

OT

HE

R

PE

RS

ON

EM

PL

OY

EE

/

AG

EN

T

ST

AG

E

RE

CO

MM

EN

DA

TIO

N

SA

LE

S S

TA

GE

OP

PO

RT

UN

ITY

SA

LE

S P

LA

NN

ING

IT

EM

AC

TIV

ITY

PLA

N T

EM

PLA

TE

AS

SE

SS

ME

NT

T

EM

PLA

TE

ST

AG

E P

LA

N IT

EM

AS

SE

SS

ME

NT

VA

LU

EA

SS

ES

SM

EN

T A

TT

RIB

UT

E

VA

LID

VA

LU

E

AS

SE

SS

ME

NT

AT

TR

IBU

TE

AS

SE

SS

ME

NT

of

subje

ct of

for

conta

iner

of

for

made u

p o

f

insta

nce o

f

insta

ntiate

d a

s

defined for

valid

ate

d v

ia

defined for

assesed v

ia

for

a c

om

ponent of

for

of

for

at

for

of

for

pla

nned b

y

cre

ate

d fro

m

for

cre

ate

d d

uring

for

of

for

curr

ently a

t

for

for

com

posed o

f

govern

ed b

y

govern

or

of

of

subje

ct of

of

subje

ct of

part

of

made u

p o

f

of

for



Territory ManagementThis ERD (shown in Figure 60) illustrates that sales territories can be defined geographically, explicitly (using named accounts, contacts, or assets), or a combination of both. Flexible territory hierarchies can be defined to capture the relationship between territories. Multiple positions can be assigned to a given territory and multiple territories can be assigned to a given position. Accounts, contacts, and assets can be assigned to sales representatives within a sales force.


Table 60. Territory Management ERD Entities and Tables

Entity Tables

Account S_ORG_EXT

Account Team Member S_ACCNT_POSTN

Account/Terr Mapping S_TERR_ACCNT

Asset S_ASSET

Asset Team Member S_ASSET_POSTN

Asset/Terr Mapping S_TERR_ASSET

Business Unit S_BU

Contact S_CONTACT

Contact/Terr Mapping S_TERR_CON

Contact Team Member S_POSTN_CON

Division S_ORG_EXT

Geo/Terr Mapping S_TERR_ZIP, S_TERR_REGION

Position S_POSTN

Position Territory Assignment S_TERR_POSITION

Region S_REGION

Territory S_TERRITORY

Territory Hierarchy S_TERR_HIER

Territory Version S_TERRHIER_NODE

Zipcode (None)



136

Figure 60. Territory Management

��

��

��

�� 3

�"��

��

��

��

��O

racle

��

��

�

�

��

�9

��

'��

��

�

[��

�

!�

��

��

$

��

��

��

�+

�"�

��

�$

�

$�

�

�0�

��

��

"�

��

�$

�

�0�

��

�"

��

��$

�%

%�

�0�

��

��

"�

��

�$

�

�

&$

�0�

��

��

"�

��

�$

�

�

&$

��

��

"�"

�"

.�

�

�

$�

�

��

��

"�"

�"

.�

�

�%

%�

��

��

"�

"�

".

��

�%

%�

�

�

$�

�

�

��

%��

��$

!�>

�%��

$

��

9�

��!

�>�%

��$

%�

'�

%�*

��

�

.&

%�$

�%

%�&

$��

�

�

&$

�

��

��

��

�+

�9

��

��

9

+

��

��

��

�+

��

��

��

�+

�>

��

%��

$

��

%��

��$

��

��

��

�+

��

%%

�$

"�

$�

��

��

��

��

�

��

��

��

��

��

�

��

��

�

��

��

��

� �

�

��

��

�

�

��

�

��1

��3

� �

��

��

�@�

��1

3

��

��

13

��

��

��

��

�

��1

��

�

�

��

��

��

�

��

�

��1

��3

� �

�

��

��

��

�

��

�

��1

��3

� �

�

��

��

��

�

��

�

��1

��3

� �

��

��

��

�13

��

��

��

� �

��

��

�

�

��

��

��

�

��

��

��

��

��

��

��

��

��

��

�

2�

��

��

�

��

��

��

�

��

��

�

�

��

��

�

�

��

��

�

�

�

��

��

��

�

��

��

��

��

��

��

�

�

��

��

��



Territory Quota RollupThis ERD (shown in Figure 61) covers sales quotas setup and quota rollup in the territory management system. It illustrates assigning sales quotas to periods, contacts, accounts, regions, and ZIP codes. These assignments can be spread over different periods. As each territory consists of a set of contacts, accounts, regions, and ZIP codes assigned with quotas; the quotas can be rolled up to each territory or each territory for each period.


Table 61. Territory Quota Rollup ERD Entities and Tables

Entity Tables

Sales Quota S_SLS_QUOTA

Territory S_TERRITORY

Territory Quota S_TERR_QUOTA

Account/Quota S_QUOTA_ACCNT

Contact/Quota S_QUOTA_CON

Geo/Quota S_QUOTA_REGN, S_QUOTA_ZIP

Quota Assignment Breakdown S_QTA_ACC_PD, S_QTA_CON_PD, S_QTA_REGN_PD, S_QTA_ZIP_PD

Contact /Terr Mapping S_TERR_CON

Account / Terr Mapping S_TERR_ACCNT

Geo/Terr Mapping S_TERR_REGION, S_TERR_ZIP

Terr/Qta/Geo S_TERR_QTA_REGN, S_TERR_QTA_ZIP

Terr/Qta/Con S_TERR_QTA_CON

Terr/Qta/Accnt S_TERR_QTA_ACCT

Accnt Quota Credit S_TRQT_ACC_CRDT

Contact Quota Credit S_TRQT_CON_CRDT

Geo Quota Credit S_TRQT_REGNCRDT, S_TRQT_ZIP_CRDT

Period Quota S_QTA_PD_BRKDN

Terr Quota Breakdown S_TRQT_PD_BRKDN



138

Figure 61. Territory Quota Rollup

��

��

��

�� 3

�7� ��

��

��

��

��

��O

racle

��

��

��

��

�7&

��

��

.�

��

<!

�;

$

��

��

!�

7&

��

�

�

��7

&�

��

�

��

!��

�

$�

�

��7

&�

��

�

�!

��

�

$

��7

&�

��

�

��

!��

��

��

�7&

��

��"

��

��$

�

.�

��

<!

�;

$

��

��

��

�+

�7&

��

��"

��

��$

��

��

07�

�0

�$

��

��

07�

�0�

$�

��

��

07�

�0

��

��

��

��

�+

�7&

��

��

��

��

��

+

��

��

��

�+

�"�

��

�$

�

�

&$

��0��

��

��

"�

��

�$

�

�0�

��

��

"�

��

�$

�

$�

�

��

0��

��

�"

��

��$

7&

��

��

%%

�$

"�

$�

�.

��

�<

!�

;$

7&

��

��

%%

�$

"�

$�

�

�

&$

�07

&�

��

�

�07

&�

��

�

$�

�

�07

&�

��

��

��

!

�

$�

�

��

�&

$�

�

�

��

�9

��

'��

��

�

[��

�

!�

��

��

$

%�

'�

%�7

&�

��

� �

� 2��

��1

3

1��

��

� 2��

�

��

1��

��

� 2��

��

��

��

��

��

��

��

��

��

��

��

��

�

��

� �

�

��

� �

�

��

� ��

��

��

��

��

��

��

��

��

��

��

��

��

1��

�5� 6

��

�

��14�

��

��

��

2��

� �

� ��

��

��

� �

� ��

1��

�5� 6

��

��14�

��

��

��

2��

� �

� �

��

��

� �

��

��

� �

��

��

�

��

��

� �

��

��

��

��

��

�

��14�

��

� � �

� ��

�

�3��

�

6

��

� �



Textile, Apparel, and FootwearThis ERD (shown in Figure 62) illustrates how Siebel Business Applications support the assortment planning process in the textile, apparel, and footwear industries. A retailer can define the products that are sold in each season, then associate each product with one or more market segments to define recommended product assortments. Rather than complicating the assortment by specifying product entries for each combination of one or two attributes in which a style is manufactured (such as size or color), the attributes can be specified through a seasonal or nonseasonal product option range (for example, a shirt size range of S, M, L, and XL). The retailer can then further specify recommended product option mixes that indicate the proportion of each product option attribute value to deliver when ordering a style (for example, a mix preference of 20% S, 30% M, 30% L, and 20% XL), or each retail customer can create its own mix preferences. When creating an assortment plan for a season, the retail customer chooses the styles from the recommended product assortment for the season, modifies the assortment to fit its customers, and chooses the desired product option mix for each product option. The total ordered quantity of each style is then further broken down into the quantity to be delivered in each subperiod within the season (for example, each week in the season). This assortment plan can then serve as a guideline for ordering throughout the season or even facilitate the generation of orders in each delivery period in the season.

The shaded subtypes in this diagram indicate examples of the types of data that may be found within a supertype. They are not intended to indicate strict subtypes.


Table 62. Textile, Apparel, and Footwear ERD Entities and Tables

Entity Tables

Marketing Segment S_MKT_SEG

Order S_ORDER


Organization External S_ORG_EXT

Period S_PERIOD

Period Relationship S_PERIOD_REL

Product Attribute Type S_LST_OF_VAL

Product Attribute Value S_LST_OF_VAL

Product Option Mix Preference S_PROD_OPT_MIX

Product Option Mix Proportion S_PROD_OPT_PCT

Product Option Range S_PROD_OPTION

Product Option Range Member S_PROD_OPT_VAL

Quote S_DOC_QUOTE




140

Figure 62. Textile, Apparel, and Footwear

Title

: T

extile

, A

ppare

l and F

ootw

ear

Auth

or

: O

racle

, C

onfidential

QU

OT

E IT

EM A

SS

OR

TM

EN

T P

LA

N IT

EM

S

CH

ED

ULE

D D

ELIV

ER

Y

AS

SO

RT

ME

NT

P

LA

N IT

EM

OR

GA

NIZ

AT

ION

E

XT

ER

NA

L

OT

HE

R

OR

GA

NIZ

AT

ION

AC

CO

UN

T

ST

OR

E

PR

OD

UC

T IN

TE

RN

AL

LIN

E O

F B

US

INE

SS

CA

TE

GO

RY

ST

YLE

/CO

LO

R/D

IME

NS

ION

QU

OT

E

AS

SO

RT

ME

NT

P

LA

N

OR

DE

R

OR

DE

R IT

EM

OR

DE

RE

D

AS

SO

RT

ME

NT

P

LA

N IT

EM

P

RO

PO

RT

ION

OR

DE

RE

D

AS

SO

RT

ME

NT

P

LA

N IT

EM

MA

RK

ET

ING

S

EG

ME

NT

PE

RIO

DS

EA

SO

N

OT

HE

R P

ER

IOD

TY

PE

SW

EE

K

PR

OD

UC

T O

PT

ION

R

AN

GE

ME

MB

ER

PR

OD

UC

T

AT

TR

IBU

TE

T

YP

E

PE

RIO

D R

ELA

TIO

NS

HIP

PR

OD

UC

T O

PT

ION

RA

NG

E

NO

N-S

EA

SO

NA

L

SIZ

E R

UN

SE

AS

ON

AL

CO

LO

R P

ALE

TT

E

PR

OD

UC

T A

TT

RIB

UT

E V

ALU

E

SH

OE

SIZ

E

CO

LO

R

FA

MIL

YO

TH

ER

AT

TR

IBU

TE

VA

LU

E

CO

LO

R

PR

OD

UC

T O

PT

ION

MIX

PR

EF

ER

EN

CE

(SP

RE

AD

)

AC

CO

UN

T

SP

EC

IFIC

M

IX

RE

CO

MM

EN

DE

D

MIX

PR

OD

UC

T O

PT

ION

M

IX P

RO

PO

RT

ION

for

belo

ngin

g to

recom

mended to b

e o

rdere

d in

the

defa

ult

mix

for

launched

in

debut season for

bill

ed to

for

defined for

subje

ct of

rele

vant to

inclu

der

of

of

split

into

of

schedule

d

by

applic

able

to a c

olle

ction o

f

defined for

pare

nt to

defined

for

deliv

ery

period for

for

com

posed

of

cre

ate

d fro

m

lead to

for

com

posed

of

of

ord

ere

d o

n

for

of

secondarily

m

anufa

ctu

red in

in

prim

arily

m

anufa

ctu

red in

in

prim

ary

defined b

ycolle

ction o

f

secondary

defined b

ycolle

ction o

f

specific

to

definer

of

the targ

et of

targ

etted a

t

for

subje

ct of

secondarily

specify

specifie

d

on

prim

arily

specify

specifie

d

on

prim

arily

com

posed o

fsubje

ct of

secondarily

com

posed o

fsubje

ct of

for

subje

ct of

defined

for

deliv

ery

period for

specific

to

item

s w

ithin

scope o

f

defined for

com

posed o

f

defined for

com

posed

of

for

colle

ction

of

secondarily

of

subje

ct of

prim

arilly

of

subje

ct

of

secondarily

of

subje

ct of

secondarily

defined b

y

secondary

dom

ain

for

topart

of

of

made u

p

of

defined for

subje

ct of

prim

arily

defined b

y

prim

ary

dom

ain

fo

r

a v

alu

e

of

the d

om

ain

fo

r

applic

able

to

subje

ct of

prim

arily

of

subje

ct of



Time SheetThis ERD (shown in Figure 63) illustrates how Siebel Business Applications track employee time sheets. Employees can track time spent for client billing or for other purposes. Time can be entered for projects, activities, service requests, and so on. These time units can then be aggregated into time sheets through time sheet lines. A time sheet is reported for a specified reporting period and lists time spent on specific project or nonproject work such as vacation, sick leave, training, and so on. Each time sheet line is specific to a given day within the reporting period.


Table 63. Time Sheet ERD Entities and Tables

Entity Tables

Activity S_EVT_ACT


Period S_PERIOD


Project S_PROJ



Time Unit S_TMSHT_ITEM

Timesheet S_TMSHT

Timesheet Approval S_TMSHT_APPR

Timesheet Line S_TMSHT_LN

Work Type S_PROJ



142

Figure 63. Time Sheet

Title

: T

ime

Sh

ee

tA

uth

or

: O

racle

, C

on

fid

en

tia

l

PR

OJE

CT

TA

SK

OP

PO

RT

UN

ITY

SE

RV

ICE

R

EQ

UE

ST

PR

OJE

CT

TE

AM

RO

LE

TIM

E U

NIT

TIM

E A

DJU

ST

ME

NT

WO

RK

TIM

E U

NIT

AC

TIV

ITY

TIM

E S

HE

ET

TIM

E S

HE

ET

LIN

E

PE

RIO

D

PE

RS

ON

EM

PL

OY

EE

/AG

EN

T

OT

HE

R P

ER

SO

N

OR

GA

NIZ

AT

ION

UN

IT

INT

ER

NA

L

OR

GA

NIZ

AT

ION

UN

IT O

TH

ER

O

RG

AN

IZA

TIO

N

UN

IT

WO

RK

TY

PE

NO

N-P

RO

JE

CT

W

OR

K T

YP

EP

RO

JE

CT

ap

pro

ve

d

ap

pro

ve

r

cla

ssifie

d a

s

cla

ssific

atio

n f

or

be

lon

gs t

o

ma

de

up

ba

se

d

ba

sis

fo

r

su

bje

ct

of

rep

ort

of

tim

e

wo

rke

d o

n

for

su

bje

ct

of

ad

justm

en

t

ad

juste

d

rep

ort

ed

via

ma

de

up

of

asso

cia

ted

with

co

nta

ct

for

ow

ne

d b

y

ow

ne

r o

f

rep

ort

ed

by

rep

ort

er

of

su

bm

itte

d f

or

refe

ren

ce

d b

y

ow

ne

d b

y

ha

ve

ow

ne

rsh

ip o

f

targ

ete

d a

t

su

bje

ct

of

rep

ort

ed

by

rep

ort

er

of

aff

ilia

ted

with

co

mp

ose

d o

f

de

fin

ed

fo

r

req

uire

for

su

bje

ct

of

for

su

bje

ct

of

rep

ort

ed

fo

r for

pa

rt o

f

ma

de

up

of



Trade PromotionsThis ERD (shown in Figure 64) illustrates the planning and execution of a consumer goods promotion, including definition of promotion-products, promotion-accounts, and promotion-account-products. Also supported are promotion payments, promotion agreements, and observations of store conditions.


Table 64. Trade Promotions ERD Entities and Tables

Entity Tables


Contract S_D0C_AGREE, S_DOC_QUOTE, S_ORDER

Contract Item S_AGREE_ITEM, S_QUOTE_ITEM, S_ORDER_ITEM


Internal Product Presence S_ORG_PROD


Marketing Event or Activity S_SRC, S_SRC_CHNL

Note S_NOTE_SRC

Order S_ORDER

Other Contract S_DOC_AGREE, S_DOC_QUOTE


Product S_PROD_INT, S_PROD_EXT



144

Figure 64. Trade Promotions

��

��

��

� �

��

��

��

��O

racle

��

��

��

�%

�$

��

!�

��

�"

"�

�<

��

�$

�!�

>�

'�

�"

�$

��*

&$

!

*&

$!

��

''�

�

��

$

�

$�

��

�

��

!�

�

��

9�

��

�

$�

��

�

�

�

&$

�

"�

�<

��

�$

��>

�$

��

��

�

�>��

+

��

�"

��

��$

��

�

&$

�

��

9�

��"

��

<�

��$

�

�>

�$

��

��

�

�>��

+

��

�"

��

��$

��

�&

$�

��

�!

&

�

��

�"

��

��$

��

�"

��

��$

��

��

!&

�

��

�"

��

��$

��'�

$

$�

��

��

�!

&

��

��

!&

�

��8

��

�$

�'

��

�!

&

��$

��

�$

�'

��

��

��14�

��

��

��

��6

��

� �

� ��

�

��?��

��1

3

��?��

��

��

��1

3

��

��

��2��

�

��2��

��

� �

��

��

�

��1

3

��

��

��

��

�

��

�

� �

��

��

� �

��

�

��

��14�

��

��

��

��

��

��

� �

�14�

��

� ��

��

��

��

��

� 2��

��1

3

��

��

��

3��

��

��14�

��

� �

��14�

��

��

� �

��

��

�



Training Curriculum CourseThis ERD (shown in Figure 65) illustrates the entities and relationships relevant to the training business function. A training curriculum is made up of one or more training courses, which are offered through one or more course offerings. Both courses and curriculums target one or more audience types and have literature associated with them. A person can be registered for one or more course offerings. Tests that may be defined for one or more course offerings, including test questions and possible answers. Tests taken by an Individual contain the answer given by that person to each question and the score achieved by that person for each question.


Table 65. Training Curriculum Course ERD Entities and Tables

Entity Tables



Employee Course S_EMP_CRSE

Employee Course Status S_EMP_CRSE_STAT



146

Figure 65. Training Curriculum Course

Title

: T

rain

ing

Cu

rric

ulu

m C

ou

rse

Au

tho

r :

Ora

cle

, C

on

fid

en

tia

l

CA

TA

LO

G C

AT

EG

OR

Y

EM

PL

OY

EE

CO

UR

SE

ST

AT

US

EM

PL

OY

EE

CO

UR

SE

AC

CE

SS

GR

OU

P

MA

RK

ET

ING

EV

EN

T O

R A

CT

IVIT

Y

OT

HE

R M

AR

KE

TIN

G E

VE

NT

OR

A

CT

IVIT

Y

TR

AIN

ING

CO

UR

SE

OF

FE

RIN

G

LIT

ER

AT

UR

E

PE

RS

ON

PR

OD

UC

T O

R S

ER

VIC

E

TR

AIN

ING

CO

UR

SE

OT

HE

R P

RO

DU

CT

OR

SE

RV

ICE

CO

UR

SE

A

VA

ILA

BL

E

LA

NG

UA

GE

JO

B P

RO

FIL

EC

UR

RIC

UL

UM

P

ER

SO

N

TR

AIN

ING

C

UR

RIC

UL

UM

S

TE

P C

OU

RS

E

TR

AIN

ING

C

UR

RIC

UL

UM

ST

EP

TR

AIN

ING

CU

RR

ICU

LU

M

CU

RR

ICU

LU

M

TA

RG

ET

AU

DIE

NC

EC

UR

RIC

UL

UM

C

AT

EG

OR

Y

ce

rtifie

d f

or

su

bje

ct

of

su

bje

ct

of

for

sa

tisfie

d b

y

pro

vid

e t

rain

ing

fo

r

acce

sse

d b

y

gra

nte

d a

cce

ss t

ofo

r

be

lon

gs t

o

targ

et

of

targ

ete

d a

t

pa

rt o

f

co

mp

ose

d o

f

pa

th

ca

teg

orize

d in

to

for

ca

teg

orize

d in

to

of

tra

cke

d b

y

for

in n

ee

d o

f

ne

ed

ed

by

for

instr

ucte

d b

y

instr

ucto

r o

f

pro

vid

e t

rain

ing

fo

r

sa

tisfie

d b

y

ava

ilab

le f

or

off

ere

d in

reg

iste

red

by

en

rolle

d in

ba

se

d o

n

ba

sis

of

of

su

bje

ct

of

pa

rt o

f

co

mp

ose

d o

f

pa

rt o

f

co

mp

ose

d o

f

for

su

bje

ct

of

ce

rtific

atio

n o

f

su

bje

ct

of



Training Test EngineThis ERD (shown in Figure 66) illustrates the entities and relationships relevant to the training test engine business function. Tests may be defined for one or more course offerings, or for one or more courses, including test questions and possible answers, and may be available in one or more languages. Each test question can be either determined in advance or pulled from a question pool at run time. Tests taken by an Individual contain the exact question presented to the individual, the individual's answer to each question, and the score achieved by that person for each question. It also keeps track whether the question has been attempted.


Table 66. Training Test Engine ERD Entities and Tables

Entity Tables

Course/Course Offering Test S_CRSE_OFFR_TST


Individual’s Test S_CRSE_TSTRUN

Individual’s Test Answer S_CRSE_TSTRUN_A

Individual’s Test Category S_TSTRUN_CATSTS

Individual’s Test Question S_CRSE_TSTRUN_Q


Pool Question S_POOL_QUES


Question/Possible Answer S_CRSE_TST_ANSR

Question/Question Pool, Question Pool, Question S_TST_QUES

Question Category LOV

Test Available Language S_CRSE_TST_LANG

Test Question S_CRSE_TST_QUES

Topic/Objective S_CRSE_TOPIC

Training Course S_PROD_INT_CRSE, S_PROD_INT

Training Course Offering S_SRC_EVT, S_SRC

Training Test S_CRSE_TST



148

Figure 66. Training Test Engine

��

��

��

��

��

��

��

��

��

�� O

racle

��

��

�>

�$

��'

�

��

��$

7&

�%

��

$�

�

��

�

�+

7&

�%

��

$�0�7

&�

%�

��$

��

�'

7&

�%

��

$�

��

�'

7&

�%

��

$

��

%�

�7&

�%

��

$

�$!

�>�!

&�

'�%

��

%�

�7

&�

%�

��$

�$!

�>�!

&�

'�%

��

�%

��

$%

;�

�

�$!

�>�!

&�

'�%

��

%�

"�

�<

��

�$

��>

�$

��

��

�

�>��

+

��

9�

��"

��

<�

��$

��

>�

$�

��

��

��>

��+

��

��$

�$

��

&�

%�

��*

*�

��$

��

�!

&

��

��%

��

>�

�

��

��$

�$

��

&�

%�

��

9�

��

��

!&

�

��

�%�

�>

��

��

%�

��>

��'

�.

'�

'�

$

&�

�

�

&�

%�

0�

&�

%�

��*

*�

��$

��

�%

�

�$!

�>�!

&�

'�%

��

%�

�

��

�

��

+

��

�'�7

&�

%�

��$

��

��

0��

.=�

�

�>�

��

��$

�$

��

%�

7&

�%

��

$�0��

�%

%�.

'�

��$

%;

��

��

� �

��

��

��1

3

� ��

�

��

��

�

� �

� ��

�

��14�

��

��

� �

��14�

��

� ��

��

1 ��

��

��

�

��

� ��@��

��

��

��

�

��

� �

��

��

��1

3

� �

��

��

�

��

�

� �

� �

��14�

��

�2��

��

��1

3

�2��

��

��

��

��

� �

��14�

��

��

��

��

��

�

��

� �3

� �

��

��1

3

�2��

1��

��

��

��

� �

��

��

�

� �

��14�

��

��

��

�

��

��

��

1��

�

1��

� �

��

��6

��

��14�

��

��

��6

��

��14�

��

��

��6

��

��14�

��



Versioned Object DefinitionVersioned Object Definition (shown in Figure 67) provides a system for managing the versioned objects in the system including Products, Product Templates (Classes), Attributes, Context Variables, and so on. Versioned Object Definition replaces the Product Configurator infrastructure tables in all previous releases.


Table 67. Versioned Object Definition ERD Entities and Tables

Entity Tables

Attribute Definition S_ISS_ATTR_DEF

Attribute Value S_ISS_ATTR_VAL

Joint Workspace S_ISS_JWS

Joint Workspace Item S_ISS_JWS_ITEM

Object Attribute S_ISS_OBJ_ATTR

Object Attribute Value S_ISS_OBATR_VAL

Object Definition S_ISS_OBJ_DEF

Object Definition S_VOD

Versioned Object Definition Version S_VOD_VER



150

Figure 67. Versioned Object Definition

Title

: V

ers

ion

ed

Ob

ject

De

fin

itio

n

Au

tho

r :

Ora

cle

, C

on

fid

en

tia

l

JO

INT

WO

RK

SP

AC

E

ITE

M

JO

INT

WO

RK

SP

AC

EO

BJE

CT

AT

TR

IBU

TE

VA

LU

E

PR

OD

UC

T T

EM

PL

AT

E

AT

TR

IBU

TE

VA

LU

EP

RO

DU

CT

AT

TR

IBU

TE

VA

LU

E

OB

JE

CT

AT

TR

IBU

TE

PR

OD

UC

T

AT

TR

IBU

TE

PR

OD

UC

T T

EM

PL

AT

EA

TT

RIB

UT

E

AT

TR

IBU

TE

VA

LU

EA

TT

RIB

UT

E D

EF

INIT

ION

OB

JE

CT

DE

FIN

ITIO

N

PR

OD

UC

T T

EM

PL

AT

E

DE

FIN

ITIO

N

PR

OD

UC

T D

EF

INIT

ION

VE

RS

ION

ED

OB

JE

CT

D

EF

INIT

ION

VE

RS

ION

VE

RS

ION

ED

OB

JE

CT

DE

FIN

ITIO

N

AT

TR

IBU

TE

HE

AD

ER

DE

FIN

ITIO

NO

TH

ER

VE

RS

ION

ED

OB

JE

CT

HE

AD

ER

D

EF

INIT

ION

PR

OD

UC

T H

EA

DE

R

DE

FIN

ITIO

N

PR

OD

UC

T T

EM

PL

AT

E H

EA

DE

R

DE

FIN

ITIO

N

for

gro

up

ed

in

for

ha

ve

for

ha

ve

for

ha

ve

for

ha

ve

for

ha

ve

glo

ba

lly d

efin

ed

via

for

loca

lly

de

fin

ed

fo

r

ha

ve

loca

lly

de

fin

ed

fo

r

ha

ve

for

ha

ve

ha

ve

for

ch

ild f

or

pa

ren

t o

f

for

ha

ve

for

ha

ve

for

ha

ve



WarrantyThis ERD (shown in Figure 68) illustrates how Siebel Business Applications tracks product warranty coverages. Warranty coverage is provided by an organization (often the vendor of the product) and covers one or more products that are part of a covered product line. The products covered under the warranty coverage may be specified directly through product warranty coverage entries or indirectly through product line warranty coverages (which specifies coverage for the products that compose the product line). Warranty service may be provided by one or more authorized service providers. The various warranty coverages applicable to an asset throughout its life are tracked, and may be applied to fully or partially compensate the service provider for service requested in a service order.


Table 68. Warranty ERD Entities and Tables

Entity Tables

Asset S_ASSET

Asset Warranty Coverage S_ASSET_WRNTY

Order S_ORDER



Product S_PROD_INT


Product Line Warranty Coverage S_PRDLN_WRNTY

Product Warranty Coverage S_PROD_WRNTY

Warranty Coverage S_WRNTY_CVRG

Warranty Service Provider S_WRNTY_SRV_ORG



152

Figure 68. Warranty

Title

: W

arr

anty

Auth

or

: O

racle

, C

onfidential

OR

GA

NIZ

AT

ION

UN

IT

WA

RR

AN

TY

SE

RV

ICE

P

RO

VID

ER

OR

DE

R

OT

HE

R O

RD

ER

SE

RV

ICE

OR

DE

R

OR

DE

R I

TE

M

PR

OD

UC

T

LIN

E

PR

OD

UC

TA

SS

ET

PR

OD

UC

T L

INE

W

AR

RA

NT

Y

CO

VE

RA

GE

PR

OD

UC

T

WA

RR

AN

TY

C

OV

ER

AG

E

WA

RR

AN

TY

CO

VE

RA

GE

AS

SE

T

WA

RR

AN

TY

C

OV

ER

AG

E

cla

ime

d a

ga

inst

ap

plie

d t

o

ve

nd

ed

by

ve

nd

or

of

role

pla

ye

d b

y

su

bje

ct

of

of

pro

vid

ed

by

a p

art

of

ma

de

up

of

pa

rt o

f

co

mp

ose

d o

f

pro

vid

ed

by

wa

rra

nto

r o

f

pa

rt o

f

co

mp

ose

d o

f

an

in

sta

nce

of m

ad

e in

to

of

su

bje

ct

of

by

ma

de

up

of

of

su

bje

ct

of

by

ma

de

up

of

of

su

bje

ct

of

by

ma

de

up

of


4 Physical Model

The Siebel physical model encompasses the tables, their columns, and their indexes. This chapter covers the following topics.

■ “Data Model Naming Conventions” on page 153

■ “Data Model Type Definitions” on page 156

■ “Siebel System Fields” on page 160

■ “INTEGRATION_ID Columns” on page 161

■ “Include Only Field” on page 161

■ “Siebel Repository” on page 161

■ “Database Schema Version” on page 161

■ “Limit Checking for Data Types” on page 162

■ “Party Model Unifies Access to Data” on page 162

Data Model Naming ConventionsThis topic describes:

■ Table Naming Conventions

■ Index Naming Conventions on page 155

■ Column Naming Conventions on page 155

■ Abbreviations Used in the Physical Model Listings on page 156

Table Naming ConventionsTables in the Siebel database use a three-part naming convention. The syntax is: PREFIX_NAME_SUFFIX.

PREFIX Table names in Siebel Business Applications have a one- to three-letter prefix (EIM_, S_, W_, and so on) to distinguish them from other tables in your application.

NAME A unique table name that is generally an abbreviation of the entity supertype name.

SUFFIX A supertype name may be followed by the entity subtype. For example, the supertype EVT (event) has ACT (activity) as one of its subtypes. Thus, the name becomes S_EVT_ACT.


Physical Model ■ Data Model Naming Conventions

154

The prefix indicates the part of the Siebel schema to which a table belongs. Table 69 provides some of the prefixes and their descriptions.

The suffix indicates a table type. Table 70 provides some of the suffixes and their descriptions.

Table 69. Table Prefixes

Prefix Meaning

EIM_ Interface tables for Siebel Enterprise Integration Manager.

S_ Siebel base table. (Exception: Tables with names of the form S_<name>_IF are obsolete interface tables.)

W_ Oracle Business Analytics Warehouse table, described in Oracle Business Analytics Warehouse Data Model Reference.

Table 70. Base Table Suffixes

Suffix Meaning

_ATT File attachment table.

_REL A table that supports a many-to-many relationship from an entity back to itself.

_SS A table that stores Siebel-to-Siebel integration information.

_V A table that represents a database view.

_X One-to-one extension table, available for customers to add attributes to the Siebel database.

_XA A table that stores extended attributes associated with an object class.

_XM One-to-many extension table, available for customers to add attributes to the Siebel database.

Physical Model ■ Data Model Naming Conventions


Index Naming ConventionsIndexes are named the same as the table on which they are created plus a one- to four-character suffix as shown in Table 71.

CAUTION: Before modifying or deleting indexes, create a service request (SR) on OracleMetaLink 3. Modifying or deleting indexes can negatively affect the performance of Siebel Business Applications and may render it unusable. Alternatively, you can phone Global Customer Support directly to create a service request or get a status update on your current SR. Support phone numbers remain the same and are listed on OracleMetaLink 3.

Column Naming ConventionsSuffixes are used to indicate columns that must contain specific values. Table 72 shows the standard suffixes for column names and their possible values.

Table 71. Standard Index Suffixes

Suffix ValueUnique or Not Unique

_F# Foreign key index. Not unique

_P# Primary key index. Unique

_U# Primary key index of the user. Unique

_V# Special routing visibility rule index; usually on primary child foreign key and system foreign key columns not ordinarily indexed (for example, primary address, primary contact, creator, and so on).

Not unique

_M# Miscellaneous index. Any index that does not fit into one of the above categories.

Not unique

Table 72. Standard Column Suffixes

Suffix Value

_AMT This column contains a currency amount.

_CD The column value is based on the contents of the List of Values (LOV).

_DT This column contains a date or datetime value.

_FLG This column contains a Boolean value where Y indicates Yes or True; N indicates No or False.

_ID This column contains ROW_ID values.

_NUM This column contains a number or an identifying alphanumeric value.


Physical Model ■ Data Model Type Definitions

156

Abbreviations Used in the Physical Model ListingsDescriptions that appear in the physical model listings may use the abbreviations shown in Table 73.

Data Model Type DefinitionsThis topic contains the following type definitions:

■ Table Type Definitions on page 157

■ Table Status Definitions on page 158

■ Column Type Definitions on page 159

■ Domain Type Definitions on page 159

_TEXT This column contains text data.

_TM This column contains a time value.

_TS This column contains a timestamp value.

Table 73. Physical Model Listing Abbreviations

Abbreviation or Phrase Meaning

fk Foreign key; a column that references a primary key of another table.

pk Primary key; the unique row identifier of a table.

SEA Siebel Enterprise Applications.

Siebel System Field One of the Siebel Enterprise Applications system fields described in Table 78 on page 160.

Table 72. Standard Column Suffixes

Suffix Value



Table Type DefinitionsTable 74 provides descriptions of the types of tables in the Siebel database.

Table 74. Table Types in the Siebel Database

Table Type Description

Data (Intersection)

Data (Intersection) tables contain application or end-user data. An intersection table implements a many-to-many relationship between two data tables. The name of an intersection table is usually composed by concatenating the two table names, abbreviated if needed. For example S_OPTY_POSTN is the intersection table between tables S_OPTY and S_POSTN. Intersection tables cannot be extended using extension tables, but can be extended using extension columns, subject to database restrictions.

Data (Private) Data (Private) tables contain application administration or system data. Private tables cannot be extended using extension tables or extension columns.

Data (Public) Data (Public) tables contain application or end-user data. Public data tables can be extended using extension tables and, subject to database restrictions, extension columns.

Database View Database View objects appear as tables with regular columns. These tables represent database views. Objects of this table type are not created by the ddlimp Siebel database utility. Underlying views are created by SQL scripts during install and upgrade.

Dictionary S_APP_VER is the only table in this category. This table has only one row and contains information about the application such as major and minor version, application name, unicode flag, and so on. This table contains information about the data dictionary.

Extension Extension tables implement a one-to-one relationship with a data table to provide additional columns to the data table. These tables are named with an _X suffix and contain generic columns with the ATTRIB_ prefix, which are useful to define customized fields in a business component. These tables can be further extended using extension columns, subject to database restrictions.

Note that there are also tables that implement a many-to-one relationship to a data table. Those tables have an _XM suffix and their columns have generic names with the ATTRIB_ prefix. However, they are not considered extension tables. Their type is Data (Public).

Extension (Siebel) Extension (Siebel) tables also implement a one-to-one relationship with a data table to provide additional columns to the data table. However, these columns are configured in advance in Siebel Business Applications. Do not use extension tables for any other purpose. These tables can be extended using extension columns, subject to database restrictions, but cannot be extended through extension tables.



158

NOTE: Tables of the following types: Data(Public), Data(Intersection), Extension(Siebel), and Extension are designed to hold user data. These tables, as well as some of their columns, are occasionally marked as obsolete in the comments whenever they are no longer used by the current version of Siebel Business Applications. The status of the table or column indicates the support that will be provided for it in future versions of the Siebel database schema, as shown in Table 75.

Table Status DefinitionsTable 75 provides descriptions of the types of table status in the Siebel database.

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_'.

Table 75. Table Status Definitions

Table Status Description

Active Actively used and supported in Siebel Business Applications.

Inactive Dropped or removed from Siebel Data Model and no longer supported. Customers must remove every reference to these tables or columns in their configurations.

EOL End of Life. Supported as is in this release but will be dropped in a future release of Siebel Business Applications. Use alternate active tables or columns.

Not Used Not currently used by Siebel Business Applications, but may be used by customers.

Table 74. Table Types in the Siebel Database

Table Type Description



Column Type DefinitionsTable 76 provides descriptions for the types of columns in the Siebel database.

Domain Type DefinitionsTable 77 provides descriptions for the domain types of certain columns in the Siebel database.

Table 76. Column Types in the Siebel Database

Column Type Description

Data (Public) This is the general type for most columns.

Denormalized This is the type for a column that holds a value denormalized from another column. Denormalized columns are only supported in special situations and cannot be added as part of customization.

Extension These are columns that belong to an extension table or extension columns in a base table. Those columns are used to define customized fields in a business component.

System This is the type for System Fields, which are described in Table 78 on page 160.

Table 77. Domain Types

Domain Type Meaning Domain Contains

FK Foreign Key column The name of the table referenced by this Foreign Key column.

PC Primary Child The name of the table in which the Primary Child is found. For example, an account (S_ORG_EXT) may be associated to multiple industries (S_INDUST) through the intersection table S_ORG_INDUST. One of these industries is the primary industry of the account: column S_ORG_EXT.PR_INDUST_ID points to the foreign key column INDUST_ID of the primary child table S_ORG_INDUST (the column S_ORG_INDUST.INDUST_ID is a foreign key to the base table S_INDUST and so it points to S_INDUST.ROW_ID).

LOV List of Values The intended List of Values type for this column. List of values types are defined in the table S_LST_OF_VAL accessible through Siebel Tools: Screens>System Administration>List of Values.

LOVB List of Values Bounded

The List of Values type against which this column is validated. In the LOVB case, end users must specify a value from the list, whereas in the LOV case, the user can enter a value not contained in the list.


Physical Model ■ Columns of Numeric Physical Type

160

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

Siebel System FieldsEvery Siebel table contains the system fields described in Table 78. Do not alter the contents of these fields.

MLOV Multilingual List of Values

The List of Values type against which this column is validated, in multiple languages. End users must specify a value from the list, but see the values in their preferred language.

MLS Multiple Language Support

The name of the table in which the translation in an alternate language can be found.

DNRM Denormalized The path to the original column, used by the Object Manager to synchronize the values, in the form of [foreign key column].[original column]. For example, the ACCNT_NAME column of table S_ACCNT_POSTN is denormalized; its domain is [OU_EXT_ID].[NAME]. In other words, the contents of column NAME of the table referenced by OU_EXT_ID (S_ORG_EXT) are replicated into column ACCNT_NAME of table S_ACCNT_POSTN. Denormalization is used to improve query performance.

(blank) There is no domain specified for this column.

Table 78. Siebel System Fields

Column Name Description

CONFLICT_ID Unique value used to resolve Siebel remote routing conflicts if necessary; otherwise, value is zero.

CREATED Date the record was entered.

CREATED_BY User who entered the record (foreign key to S_USER).

DCKING_NUM No longer used.

Table 77. Domain Types

Domain Type Meaning Domain Contains

Physical Model ■ INTEGRATION_ID Columns


INTEGRATION_ID ColumnsMany tables contain a column called INTEGRATION_ID for back office integration. Normally, customers use this column to store the unique reference identifiers for corresponding records in the back office application. These columns are currently used by the Siebel SAP R/3 Connector.

The S_ADDR_ORG.INTEGRATION2_ID and INTEGRATION3_ID columns have been created for integration with Oracle back office applications. The INTEGRATION2_ID column is used to store the Oracle BILL TO SITE ID, and the INTEGRATION3_ID column is used to store the Oracle SHIP TO SITE ID.

Include Only FieldInclude Only is an index column field, and is either blank or checked. It applies only to DB2. When checked, it adds the column into the leaf pages of the unique index. This avoids access to table pages when the column is the only other piece of data retrieved from the table other than the indexed columns. Included columns do not contribute to the unique constraint.

Siebel RepositorySiebel Business Applications includes a set of tables referred to as the Siebel repository tables. These tables store the full definition of a given configuration of Siebel Business Applications, including the database schema and the client configuration. As with other Siebel tables, do not manipulate information in the Siebel repository tables directly. Instead, use Siebel Tools. For more information on how to use Siebel Tools, see Using Siebel Tools. To learn more about the information stored in the repository, see Siebel Object Types Reference.

Database Schema VersionEach Siebel Business Applications database installation is stamped with a database schema version. You can learn the schema version of a Siebel installation by choosing Help > Technical Support from your Siebel client. The schema version is listed in the format X.X.X.X where each instance of X represents an integer with one, two, or more digits.

LAST_UPD Date and time the record was last changed.

LAST_UPD_BY User who last changed record (foreign key to S_USER).

MODIFICATION_NUM Internally incremented number used for locking and to identify records for incremental updates of the Siebel Business Data Warehouse.

ROW_ID Unique row identifier.

Table 78. Siebel System Fields

Column Name Description


Physical Model ■ Limit Checking for Data Types

162

Limit Checking for Data TypesThe Object Manager imposes limit checking on data of specific types to make sure that every input, regardless of its source, is within specified limits (shown in Table 79). Sources of inputs include Oracle’s Siebel application, EIM, and connectors. For example, if you do a bulk import using EIM, you must make sure the dates are within the specified range, otherwise the Object Manager returns an SQL error for each out-of-range date.

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

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

Table 79. Input Limits on Data Types

Data Type Limit Checking

Dates Dates must be in the range of January 1, 1753 to December 31, 4712.

Long Maximum size of 16K

Text Maximum size of 16K

CLOB Maximum size of 128K

Table 80. S_PARTY Extension Tables and Corresponding EIM Interface Tables

Data Type Extension Table to S_PARTY EIM Interface Table

Accounts S_ORG_EXT EIM_ACCOUNT

Business Units S_BU EIM_BU

Contacts S_CONTACT EIM_CONTACT

Employees S_CONTACT EIM_EMPLOYEE

Groups S_ORG_GROUP EIM_GROUP

Physical Model ■ Party Model Unifies Access to Data


Because the extension tables are implicitly joined to S_PARTY, you do not need to configure anything to access them through S_PARTY. Some data types have a many-to-many relationship. For example, any contact can be associated with multiple accounts or partners. To model these relationships there are preconfigured intersection tables: S_PARTY_PER and S_PARTY_REL. Use S_PARTY_REL to implement relationships between parties in the S_PARTY table. In this case, records in S_PARTY are both parent (PARTY_ID) and child (PERSON_ID).

Use S_PARTY_PER to implement relationships between members:

■ Access groups and members

■ Accounts and contacts

■ Employees and positions

■ User lists and users

Organizations S_ORG_BU EIM_ORG_BU

Positions S_POSTN EIM_POSITION

Users S_USER EIM_USER

Table 80. S_PARTY Extension Tables and Corresponding EIM Interface Tables

Data Type Extension Table to S_PARTY EIM Interface Table


Physical Model ■ Party Model Unifies Access to Data

164


5 Schema Changes

This chapter lists the table, table column and table index changes in this schema:

■ “Table Changes in This Version” on page 165

■ “Table Column Changes in This Version” on page 171

■ “Table Index Changes in This Version” on page 185

Table Changes in This VersionThis topic lists the following changes to tables that have been implemented in this version of the schema:

■ “New Tables in this Version” on page 165

■ “Modified Tables in This Version” on page 171

New Tables in This VersionTable 81 lists tables that are new in this version.

Table 81. New Tables in This Version

Table Type Active

S_AGREE_BNFT Data (Public) Yes

S_AGREE_COND Data (Public) Yes

S_AGR_COND_CMPL Data (Public) Yes

S_ALGN_IND_TMP Data (Private) Yes

S_ALGN_POSTN Data (Intersection) Yes

S_ALGN_POS_OPTY Data (Intersection) Yes

S_ALGN_PROD_TMP Data (Private) Yes

S_ALGN_QTA_ACCT Data (Intersection) Yes

S_ALGN_QTA_AFFL Data (Intersection) Yes

S_ALGN_QTA_CON Data (Intersection) Yes

S_ALGN_QTA_REGN Data (Intersection) Yes

S_ALGN_QTA_TERR Data (Intersection) Yes


Schema Changes ■ Table Changes in This Version

166

S_ALGN_QTA_ZIP Data (Intersection) Yes

S_ALGN_QT_BRKDN Data (Intersection) Yes

S_ALGN_TERR_POS Data (Intersection) Yes

S_APP_VER_ATT Data (Private) Yes

S_AUDIT_JOIN Data (Private) Yes

S_AUDIT_LINK Data (Private) Yes

S_AUDIT_READ Data (Private) Yes

S_AUDIT_VERSION Data (Private) Yes

S_BDGTREQ_ORDER Data (Intersection) Yes

S_BR_CONCEPT Data (Private) Yes

S_BR_GBL_BINARY Data (Private) Yes

S_BR_GBL_PARM Data (Private) Yes

S_BR_KNWLDGBASE Data (Private) Yes

S_BR_MDL_BC_FLD Data (Private) Yes

S_BR_MDL_BC_REL Data (Private) Yes

S_BR_MODULE Data (Private) Yes

S_BR_MODULE_BIN Data (Private) Yes

S_BR_MOD_BC_REL Data (Private) Yes

S_DCP_CALL_LST Data (Intersection) Yes

S_DOCK_DL_MGR Data (Private) Yes

S_DOCK_TXN_SKIP Data (Private) Yes

S_DQ_BC_FLD_MAP Data (Private) Yes

S_DQ_BUSCOMP Data (Private) Yes

S_DQ_CON_KEY Data (Public) Yes

S_DQ_ORG_KEY Data (Public) Yes

S_DQ_PRSP_KEY Data (Public) Yes

S_DQ_RULE Data (Private) Yes

S_DQ_RULE_PARAM Data (Public) Yes

S_DQ_SYST Data (Private) Yes

S_DQ_SYST_PARM Data (Private) Yes

S_EMT_DPLYPKG Data (Public) Yes


Table Type Active



S_EMT_DPLYUNIT Data (Public) Yes

S_ENTL_BNFTTMPL Data (Public) Yes

S_ENTL_CONDTMPL Data (Public) Yes

S_ENT_SOLN Data (Public) Yes

S_FCSTSER_AGFLD Data (Public) Yes

S_FR_BID_LITM Data (Public) Yes

S_FUL_REQ_BID Data (Intersection) Yes

S_INST_UPG_HIST Data (Private) Yes

S_MKTGOFFR_BU Data (Intersection) Yes

S_MKTGOFFR_PROD Data (Intersection) Yes

S_MKTG_DOC_INVT Data (Intersection) Yes

S_MKTG_OFFR Data (Public) Yes

S_NODE_PREF Data (Private) Yes

S_NOTE_FUL_REQ Data (Public) Yes

S_NOTE_MDF Data (Public) Yes

S_OFFR_CBAST Data (Intersection) Yes

S_PROD_ACCNT Data (Public) Yes

S_PROD_CON Data (Intersection) Yes

S_PROJ_CBAST Data (Intersection) Yes

S_PRTFL_ACCNT Data (Intersection) Yes

S_PRTFL_ACCSOLN Data (Intersection) Yes

S_PRTFL_ACC_ATT Data (Public) Yes

S_PRTFL_ATT Data (Public) Yes

S_PRTFL_BU_DRVR Data (Public) Yes

S_PRTFL_BU_INTV Data (Public) Yes

S_PRTFL_CAMP Data (Intersection) Yes

S_PRTFL_CMPTR Data (Intersection) Yes

S_PRTFL_CTGRY Data (Public) Yes

S_PRTFL_ENTSOLN Data (Intersection) Yes

S_PRTFL_POSTN Data (Intersection) Yes

S_PRTFL_PRTNR Data (Intersection) Yes


Table Type Active



168

S_PRTFL_SUBACC Data (Intersection) Yes

S_QTA_ACC_PD Data (Intersection) Yes

S_QTA_CON_PD Data (Intersection) Yes

S_QTA_PARTYAFFL Data (Public) Yes

S_QTA_PD_BRKDN Data (Intersection) Yes

S_QTA_REGN_PD Data (Intersection) Yes

S_QTA_ZIP_PD Data (Intersection) Yes

S_QUOTA_ACCNT Data (Intersection) Yes

S_QUOTA_CON Data (Intersection) Yes

S_QUOTA_REGN Data (Intersection) Yes

S_QUOTA_ZIP Data (Intersection) Yes

S_RTS_BIG_ATT Data (Public) Yes

S_RTS_CFG Data (Public) Yes

S_RTS_LOG Data (Public) Yes

S_RTS_MSG_HSTRY Data (Public) Yes

S_RTS_STATE Data (Public) Yes

S_RTS_SUBSCRN Data (Public) Yes

S_RTS_TIMEOUT Data (Public) Yes

S_RTS_TMOUT_VAL Data (Public) Yes

S_RTS_WQ Data (Public) Yes

S_RTS_WQ_USER Data (Public) Yes

S_SD_ATTENDEE Data (Private) Yes

S_SLS_PORTFOLIO Data (Public) Yes

S_SLS_QUOTA Data (Public) Yes

S_SRCH_CHG_TXN Data (Private) Yes

S_SRCH_CTGRY Data (Private) Yes

S_SRCH_CTG_FLD Data (Private) Yes

S_SRCH_CTG_REL Data (Private) Yes

S_SRCH_OPERATOR Data (Private) Yes

S_SRCH_SAVED Data (Private) Yes

S_SRCH_USR_PREF Data (Private) Yes


Table Type Active



S_SRC_BDGT_REQ Data (Intersection) Yes

S_SRC_CBAST Data (Intersection) Yes

S_SRC_OFFR Data (Intersection) Yes

S_SRC_ORDER Data (Intersection) Yes

S_SRM_TASK_HIST Data (Public) Yes

S_TASK_DEFN_REL Data (Public) Yes

S_TEAMSPACEARCH Data (Public) Yes

S_TERRALGN_BU Data (Intersection) Yes

S_TERRALGN_IND Data (Intersection) Yes

S_TERRALGN_PROD Data (Intersection) Yes

S_TERRALGN_QTA Data (Intersection) Yes

S_TERRITORY_BU Data (Intersection) Yes

S_TERR_IND Data (Intersection) Yes

S_TERR_PROD Data (Intersection) Yes

S_TERR_QTA_ACCT Data (Intersection) Yes

S_TERR_QTA_AFFL Data (Intersection) Yes

S_TERR_QTA_CON Data (Intersection) Yes

S_TERR_QTA_REGN Data (Intersection) Yes

S_TERR_QTA_ZIP Data (Intersection) Yes

S_TERR_QUOTA Data (Intersection) Yes

S_TQ_AFFL_CRDT Data (Intersection) Yes

S_TRQT_ACCT_PD Data (Intersection) Yes

S_TRQT_ACC_CRDT Data (Intersection) Yes

S_TRQT_AFFL_PD Data (Intersection) Yes

S_TRQT_CON_CRDT Data (Intersection) Yes

S_TRQT_CON_PD Data (Intersection) Yes

S_TRQT_PD_BRKDN Data (Intersection) Yes

S_TRQT_REGNCRDT Data (Intersection) Yes

S_TRQT_REGN_PD Data (Intersection) Yes

S_TRQT_ZIP_CRDT Data (Intersection) Yes

S_TRQT_ZIP_PD Data (Intersection) Yes


Table Type Active



170

S_TU_INST Data (Public) Yes

S_TU_LOG Data (Private) Yes

S_TU_LOG_MAP Data (Private) Yes

S_TU_LOG_X_01 Extension Yes










S_UIC_APLT_GRP Data (Public) Yes

S_UIC_APLT_LANG Data (Public) Yes

S_UIC_APPLET Data (Public) Yes

S_UIC_ATAB_GRP Data (Public) Yes

S_UIC_ATAB_ITEM Data (Public) Yes

S_UIC_VIEW Data (Public) Yes

S_UIF_WEB_FILE Data (Private) Yes

S_USR_PREF_UOM Data (Public) Yes

S_WEBCHNL_SES Data (Public) Yes

S_WEBCHNL_SNSVC Data (Public) Yes

S_WEBCHNL_USR Data (Public) Yes

S_WFA_ANLY_INFO Data (Public) Yes

S_WFA_ANLY_PROP Data (Public) Yes

S_WFA_ANLY_TS Data (Public) Yes

S_WFA_INST_PRM Data (Public) Yes

S_WFA_INTL Data (Private) Yes


Table Type Active

Schema Changes ■ Table Column Changes in This Version


Modified Tables in This VersionTable 82 lists tables whose type has changed in this version.

Table Column Changes in This VersionThis topic lists the following changes to columns that have been implemented in this version of the schema:

■ “New Table Columns in This Version” on page 171

■ “New System Columns in This Version” on page 184

■ “Modified Table Columns in This Version” on page 184

New Table Columns in This VersionTable 83 lists table columns that are new in this version. Some column headings are abbreviated as follows.

■ Optional = Opt

■ Length = Len

■ Precision = Prec

■ LOV Bound = LOV Bnd

Table 82. Tables with Changed Type

Table Previous Type New Type

S_AUDIT_CHILDBC Data (Public) Data (Private)

T_MASTER_DTL2_X Extension (Siebel) Extension

Sie

be

l Da

ta M

od

el R

efe

ren

ce

Versio

n 8

.0, R

ev. A

17

2

Sch

em

a C

ha

ng

es ■

Table

Colu

mn C

hanges in

This V

ersio

n

Table 83. New Table Columns in This Version

Table Name Column OptData Type Len Prec

Scale Default LOV Type

LOV Bnd

S_AC_RSRC_RESP PERM_FLAG_VAL N Number 22 10 0 0

S_ADDR_ORG ALIGNMENT_FLG N Char 1 N

S_ADDR_PER ALIGNMENT_FLG N Char 1 N

S_ADJ_GROUP INTEGRATION_ID Y Varchar 30

S_ALGN_ACCT_TMP AFFL_OBJECT_CD Y Varchar 30

S_ALGN_CON_TMP AFFL_OBJECT_CD Y Varchar 30

S_ALGN_REGN_TMP AFFL_OBJECT_CD Y Varchar 30

S_ALGN_REGN_TMP ASGN_OBJECT_CD Y Varchar 30

S_ALGN_ZIP_TMP AFFL_OBJECT_CD Y Varchar 30

S_ALGN_ZIP_TMP ASGN_OBJECT_CD Y Varchar 30

S_ALGN_ZIP_TMP GEO_TYPE_CD Y Varchar 30

S_APP_QUERY OWNER_ID Y Varchar 15

S_APP_VER AUDIT_ADMIN_VER Y Varchar 30

S_AUDIT_BUSCOMP BASE_TBL_NAME N Varchar 30 x

S_AUDIT_BUSCOMP DESC_TEXT Y Varchar 250

S_AUDIT_BUSCOMP EXPORT_FLG N Char 1 N

S_AUDIT_BUSCOMP SYS_AUDIT_FLG N Char 1 N

S_AUDIT_FIELD COL_NAME Y Varchar 30

S_AUDIT_FIELD JOIN_NAME Y Varchar 75

S_AUDIT_FIELD READ_FLG N Char 1 N

S_AUDIT_FIELD READ_FV_FLG N Char 1 N

S_AUDIT_FIELD SPECIAL_JOINED_FLG N Char 1 N

S_AUDIT_FIELD TBL_NAME Y Varchar 30

S_AUDIT_ITEM AUDIT_LOG Y CLOB 1376256

S_AUDIT_ITEM AUDIT_SOURCE_CD Y Varchar 50

Sie

be

l Da

ta M

od

el R

efe

ren

ce

Versio

n 8

.0, R

ev. A

17

3

Sch

em

a C

ha

ng

es ■

Table

Colu

mn C

hanges in

This V

ersio

n

S_AUDIT_ITEM BC_BASE_TBL Y Varchar 30

S_AUDIT_ITEM CHILD_BC_BASE_TBL Y Varchar 30

S_AUDIT_ITEM CHILD_RECORD_ID Y Varchar 15

S_AUDIT_ITEM GROUP_NUM Y Varchar 15

S_AUDIT_ITEM ITEM_IDEN_NUM Y Number 22 15 0

S_AUDIT_ITEM LINK_NAME Y Varchar 175

S_AUDIT_ITEM NODE_NAME Y Varchar 50

S_AUDIT_ITEM SRC_DEST_ID Y Varchar 15

S_AUDIT_ITEM SYNC_DT Y UTC DateTime

7

S_AUDIT_ITEM TBL_NAME Y Varchar 30

S_AUDIT_ITEM TBL_RECORD_ID Y Varchar 15

S_CAMP_CALL_LST FLOWCHART_CNCTR Y Varchar 1999

S_CAMP_CON DCP_ID Y Varchar 15

S_CB_ASSET MKTG_ASSET_FLG N Char 1 N

S_CM_CNCTR SRCH_ENGINE_ID Y Varchar 15

S_COMMUNICATION DCP_ID Y Varchar 15

S_CONTACT PRESENCE_URI Y Varchar 100

S_CON_ADDR ALIGNMENT_FLG Y Char 1 N

S_CON_SYNC_SCHD CALL_LST_ID Y Varchar 15

S_CS_PATH DEPLOY_READY_FLG N Char 1 N

S_DMND_CRTN_PRG DPLY_INSTRT_TEXT Y Varchar 250

S_DMND_CRTN_PRG LAST_SYNC_DT Y UTC DateTime

7

S_DMND_CRTN_PRG MKTG_OFFR_ID Y Varchar 15

S_DMND_CRTN_PRG NEED_TO_SYNC_FLG N Char 1 N

S_DMND_CRTN_PRG OFFR_GROUP_CD Y Varchar 30 RTD_OFFER_GROUP Yes




LOV Bnd

Sie

be

l Da

ta M

od

el R

efe

ren

ce

Versio

n 8

.0, R

ev. A

17

4

Sch

em

a C

ha

ng

es ■

Table

Colu

mn C

hanges in

This V

ersio

n

S_DMND_CRTN_PRG PR_CAMPAIGN_ID Y Varchar 15

S_DMND_CRTN_PRG RTD_STATUS_CD Y Varchar 30 RTD_OFFER_STATUS Yes

S_DMND_CRTN_PRG VERSION_NUM Y Number 22 10 0 1

S_DOCK_TXN_LOG LOG_DATA_CLOB Y CLOB 1310720

S_DOCK_TXN_LOG LOG_DATA_CLOB_LEN Y Number 22 10 0

S_DYN_HRCHY HIER_LAST_UPD Y UTC DateTime

7

S_EMT_DSET_ITEM DEPLOY_MODE_CD N Varchar 30 Upsert EMT_OPERATION Yes

S_EMT_DSET_ITEM PDQ_ID Y Varchar 15

S_EMT_OBJECT EXPORT_BS_NAME Y Varchar 75

S_EMT_OBJECT EXPORT_MTHD_NAME Y Varchar 75

S_EMT_OBJECT IMPORT_BS_NAME Y Varchar 75

S_EMT_OBJECT IMPORT_MTHD_NAME Y Varchar 75

S_EMT_OBJECT PRVW_SP_BS_NAME Y Varchar 75

S_EMT_OBJECT PRVW_SP_MTHD_NAME Y Varchar 75

S_EMT_OBJECT XPT_VLD_BS_NAME Y Varchar 75

S_EMT_OBJECT XPT_VLD_MTHD_NAME Y Varchar 75

S_EMT_SESSN_ITM DEPLOY_MODE_CD N Varchar 30 Upsert EMT_OPERATION Yes

S_EMT_SESSN_ITM PDQ_ID Y Varchar 15

S_ENTL_PRDPRI AGREE_BNFT_ID Y Varchar 15

S_ENTL_PRDPRI CTLG_CAT_ID Y Varchar 15

S_ENTL_PRDPRI XA_CLASS_ID Y Varchar 15

S_ENTMPL_PRDPRI BNFT_TMPL_ID Y Varchar 15

S_ENTMPL_PRDPRI CTLG_CAT_ID Y Varchar 15

S_ENTMPL_PRDPRI XA_CLASS_ID Y Varchar 15

S_EVT_FUL_REQ COMMENTS Y Varchar 30




LOV Bnd

Sie

be

l Da

ta M

od

el R

efe

ren

ce

Versio

n 8

.0, R

ev. A

17

5

Sch

em

a C

ha

ng

es ■

Table

Colu

mn C

hanges in

This V

ersio

n

S_EVT_FUL_REQ EVTLOC_ID Y Varchar 15

S_EVT_FUL_REQ MKTG_ASSET_STAT_CD Y Varchar 30

S_EVT_MKTG CALL_REASON_CD Y Varchar 30 TODO_TYPE Yes

S_EVT_MKTG EVT_FUL_REQ_ID Y Varchar 15

S_EVT_MKTG PORTFOLIO_ID Y Varchar 15

S_EVT_MKTG PRTFL_ACCNT_ID Y Varchar 15

S_EVT_MKTG PRTFL_CTGRY_ID Y Varchar 15

S_EVT_MKTG STRTGY_CMPNT_CD Y Varchar 30 PMP_STATEGY_COMP Yes

S_FCST MGR_UPD_FLG N Char 1 N

S_FCSTSER QTY_AGFLD_ID Y Varchar 15

S_FCSTSER_POSTN AGGR_LVL_NUM Y Number 22 10 0

S_FCSTSER_POSTN FCSTSER_AGFLD_ID Y Varchar 15

S_FCST_ITEM_DTL ADJ_AMT Y Number 22 22 7

S_FCST_ITEM_DTL AGGR_DIM_NAME_1 Y Varchar 50






S_FCST_ITEM_DTL AGGR_FIELD_CD Y Varchar 30

S_FCST_ITEM_DTL CONV_QTY Y Number 22 22 7

S_FCST_ITEM_DTL CONV_UOM_CD Y Varchar 30

S_FCST_ITEM_DTL EXPECT_AMT Y Number 22 22 7

S_FCST_ITEM_DTL PAR_FCST_ITMDTL_ID Y Varchar 15

S_FCST_ITEM_DTL PERIOD_NAME Y Varchar 50

S_FCST_ITEM_DTL SEQ_NUM N Number 22 10 0 1




LOV Bnd

Sie

be

l Da

ta M

od

el R

efe

ren

ce

Versio

n 8

.0, R

ev. A

17

6

Sch

em

a C

ha

ng

es ■

Table

Colu

mn C

hanges in

This V

ersio

n

S_FCST_ITEM_DTL UOM_CONV_FCTR Y Number 22 22 7

S_FUL_REQ_ITEM CB_ASSET_ID Y Varchar 15

S_FUL_REQ_ITEM COLOR_SPEC Y Varchar 50

S_FUL_REQ_ITEM NUM_SAMPLES Y Number 22 10 0

S_FUL_REQ_ITEM PAPER_TYPE Y Varchar 50

S_FUL_REQ_ITEM RQMNT_DESC_TEXT Y Varchar 250

S_HH_SYNC_SESSN BATCH_SESSION_FLG N Char 1 N

S_HH_SYNC_SESSN DBXTRACT_CMPLT_TS Y UTC DateTime

7

S_HH_SYNC_SESSN DBXTRACT_SCHLD_TS Y UTC DateTime

7

S_HH_SYNC_SESSN DBXTRACT_STAT_CD Y Varchar 30 BATCHSYNC_EXTRACT_STATUS Yes

S_HH_SYNC_SESSN TXN_PROC_CMPLT_TS Y UTC DateTime

7

S_HH_SYNC_SESSN TXN_PROC_STAT_CD Y Varchar 30 BATCHSYNC_TXN_STATUS Yes

S_HH_SYNC_SESSN TXN_RECEIVED_TS Y UTC DateTime

7

S_HH_SYNC_SUM BATCH_SESSION_FLG N Char 1 N

S_HH_SYNC_SUM BO_FILTER_STRING_1 Y Varchar 1999



S_HH_SYNC_SUM DBXTRACT_CMPLT_TS Y UTC DateTime

7

S_HH_SYNC_SUM DBXTRACT_SCHLD_TS Y UTC DateTime

7

S_HH_SYNC_SUM DBXTRACT_STAT_CD Y Varchar 30 BATCHSYNC_EXTRACT_STATUS Yes

S_HH_SYNC_SUM TARGET_CLIENT_TYPE Y Varchar 30

S_HH_SYNC_SUM TXN_PROC_CMPLT_TS Y UTC DateTime

7

S_HH_SYNC_SUM TXN_PROC_STAT_CD Y Varchar 30 BATCHSYNC_TXN_STATUS Yes




LOV Bnd

Sie

be

l Da

ta M

od

el R

efe

ren

ce

Versio

n 8

.0, R

ev. A

17

7

Sch

em

a C

ha

ng

es ■

Table

Colu

mn C

hanges in

This V

ersio

n

S_HH_SYNC_SUM TXN_RECEIVED_TS Y UTC DateTime

7

S_INVOICE AGREE_BNFT_ID Y Varchar 15

S_MDF APPR_STATUS_CD Y Varchar 30 MKTG_PLAN_APPR_TYPE Yes

S_MDF INIT_FUND_AMT Y Number 22 22 7

S_MDF OWNER_ID Y Varchar 15

S_MDF REGION_ID Y Varchar 15

S_MKTG_BDGT_REQ MKTG_FUND_ID Y Varchar 15

S_NODE NODE_AUDIT_VER_NUM Y Varchar 30

S_NODE REAL_TM_SYNC_FLG N Char 1 N

S_OPTY_POSTN ASGN_RULE_GRP_ID Y Varchar 15

S_OPTY_POSTN ASGN_TERR_ID Y Varchar 15

S_OPTY_SRC DCP_ID Y Varchar 15

S_ORDER AGREE_BNFT_ID Y Varchar 15

S_ORDER DCP_ID Y Varchar 15

S_ORDER INIT_APRV_AMT Y Number 22 22 7

S_ORDER PURCH_ORD_EXP_TS Y TimeStamp 7

S_ORDER TOTAL_AMT Y Number 22 22 7

S_PRTNRPRG_APPL AGREE_ITEM_ID Y Varchar 15

S_PRTNRPRG_APPL AGR_IT_DT_USED_FLG N Char 1 N

S_PRTNRPRG_APPL PRTNRPRG_MBR_ID Y Varchar 15

S_PRTNRPRG_MBR AGREE_ITEM_ID Y Varchar 15

S_PRTNRPRG_MBR MEMBERSHIP_NUM N Varchar 30 x

S_PRTNR_PROG PROD_INT_ID Y Varchar 15

S_REVN ENT_SOLN_ID Y Varchar 15

S_REVN EXPECT_AMT Y Number 22 22 7

S_REVN REVN_TYPE_CD Y Varchar 30 PMP_REVENUE_TYPE Yes




LOV Bnd

Sie

be

l Da

ta M

od

el R

efe

ren

ce

Versio

n 8

.0, R

ev. A

17

8

Sch

em

a C

ha

ng

es ■

Table

Colu

mn C

hanges in

This V

ersio

n

S_RT_SVC STATE_MGMT_TYPE_CD Y Varchar 30 STATEFUL REPOSITORY_SVC_STATEMGMT_CD

Yes

S_SD_PIM_ROW OWNER_APPT_ID Y Varchar 15

S_SMQ_ADDR SECTKN_ENCRPKY_REF Y Number 22 10 0

S_SMQ_HISTORY MSG_ID_IDEN Y Varchar 50

S_SMQ_HISTORY SOURCE_OBJ_TYPE Y Varchar 100

S_SMQ_HISTORY SOURCE_OID Y Varchar 50

S_SMQ_HISTORY TYPE_CD Y Varchar 30 SMQ_MSG_TYPE Yes

S_SRC BDGT_ALLOC_PCT Y Number 22 22 7

S_SRC FLOWCHART_CNCTR Y Varchar 1999

S_SRC MEDIA_SUBTYPE_CD Y Varchar 30 OFFER_MEDIA

S_SRC PR_MKTG_OFFR_ID Y Varchar 15

S_SRC SPONSOR_EMP_ID Y Varchar 15

S_SRC_COST BDGT_REQ_ID Y Varchar 15

S_SRC_COST EVT_FUL_REQ_ID Y Varchar 15

S_SRC_COST PURCH_ORDER_ID Y Varchar 15

S_SRC_EVT_REG AWARE_CHNL_CD Y Varchar 30 ATTENDEE_AWARENESS Yes

S_SRC_EVT_REG MEAL_PREF_CD Y Varchar 30 ATTENDEE_MEAL_PREF Yes

S_SRC_EVT_REG NUM_GUESTS Y Number 22 10 0

S_SRC_PAYMENT AGREE_BNFT_ID Y Varchar 15

S_SRC_REL FLOWCHART_CNCTR Y Varchar 1999

S_SRM_REQUEST SRVR_FLOW_ID_VAL Y Varchar 40

S_SRV_REQ ENTLMNT_MTRC_ID Y Varchar 15

S_SRV_REQ RECOMMENDATION_CD Y Varchar 30 SR_RECOMMENDATION_TYPE Yes

S_STDENTL_PMTRX DYN_PMTRX_ID Y Varchar 15

S_STDENTL_PMTRX VOL_DISCNT_ID Y Varchar 15

S_STDTRNG_PMTRX DIST_CHANNEL_CD Y Varchar 30 SAP_DISTRIBUTION_CHANNEL Yes




LOV Bnd

Sie

be

l Da

ta M

od

el R

efe

ren

ce

Versio

n 8

.0, R

ev. A

17

9

Sch

em

a C

ha

ng

es ■

Table

Colu

mn C

hanges in

This V

ersio

n

S_STDTRNG_PMTRX DIVN_CD Y Varchar 30 SAP_DIVN_CD Yes

S_STDTRNG_PMTRX DYN_PMTRX_ID Y Varchar 15

S_STDTRNG_PMTRX SALES_ORG_CD Y Varchar 30 SAP_SALES_ORG Yes

S_STDTRNG_PMTRX VOL_DISCNT_ID Y Varchar 15

S_TASK_DEFN HELP_URL_TEXT Y Varchar 250

S_TASK_DEFN REL_TU_TASK_NAME Y Varchar 100

S_TERRALGN BU_ID N Varchar 15 0-R9NH

S_TERRALGN COMBINE_ALGN_ID Y Varchar 15

S_TERRALGN EXPIRATION_DT Y UTC DateTime

7

S_TERRALGN LOCKED_BY_USER_ID Y Varchar 15

S_TERRALGN LOCKED_DT Y UTC DateTime

7

S_TERRALGN LOCKED_FLG N Char 1 N

S_TERRALGN PR_POSTN_ID Y Varchar 15

S_TERRALGN ROLL_UP_AMT Y Number 22 22 7

S_TERRALGN_ACCT ACTIVATION_DT Y UTC DateTime

7

S_TERRALGN_ACCT AFFL_OBJECT_CD Y Varchar 30 TM_AFFL_OBJECT_TYPE Yes

S_TERRALGN_ACCT APPR_PER_ID Y Varchar 15

S_TERRALGN_ACCT APPR_STATUS_CD Y Varchar 30 ALGN_APPR_STATUS_CD Yes

S_TERRALGN_ACCT EXPIRATION_DT Y UTC DateTime

7

S_TERRALGN_ACCT FROM_TERR_ID Y Varchar 15

S_TERRALGN_ACCT REP_ACTION_CD Y Varchar 30 APPTM_REP_ACTION_TYPE Yes

S_TERRALGN_ACCT REQ_PER_ID Y Varchar 15

S_TERRALGN_AST ACTIVATION_DT Y UTC DateTime

7

S_TERRALGN_AST APPR_PER_ID Y Varchar 15




LOV Bnd

Sie

be

l Da

ta M

od

el R

efe

ren

ce

Versio

n 8

.0, R

ev. A

18

0

Sch

em

a C

ha

ng

es ■

Table

Colu

mn C

hanges in

This V

ersio

n

S_TERRALGN_AST APPR_STATUS_CD Y Varchar 30 ALGN_APPR_STATUS_CD Yes

S_TERRALGN_AST EXPIRATION_DT Y UTC DateTime

7

S_TERRALGN_AST REP_ACTION_CD Y Varchar 30 APPTM_REP_ACTION_TYPE Yes

S_TERRALGN_AST REQ_PER_ID Y Varchar 15

S_TERRALGN_CON ACTIVATION_DT Y UTC DateTime

7

S_TERRALGN_CON AFFL_OBJECT_CD Y Varchar 30 TM_AFFL_OBJECT_TYPE Yes

S_TERRALGN_CON APPR_PER_ID Y Varchar 15

S_TERRALGN_CON APPR_STATUS_CD Y Varchar 30 ALGN_APPR_STATUS_CD Yes

S_TERRALGN_CON EXPIRATION_DT Y UTC DateTime

7

S_TERRALGN_CON FROM_TERR_ID Y Varchar 15

S_TERRALGN_CON REP_ACTION_CD Y Varchar 30 APPTM_REP_ACTION_TYPE Yes

S_TERRALGN_CON REQ_PER_ID Y Varchar 15

S_TERRALGN_COND DIVISION_ID Y Varchar 15

S_TERRALGN_PSTN ACTIVATION_DT Y UTC DateTime

7

S_TERRALGN_PSTN EXPIRATION_DT Y UTC DateTime

7

S_TERRALGN_REGN ACTIVATION_DT Y UTC DateTime

7

S_TERRALGN_REGN AFFL_OBJECT_CD Y Varchar 30 TM_AFFL_OBJECT_TYPE Yes

S_TERRALGN_REGN APPR_PER_ID Y Varchar 15

S_TERRALGN_REGN APPR_STATUS_CD Y Varchar 30 ALGN_APPR_STATUS_CD Yes

S_TERRALGN_REGN ASGN_OBJECT_CD Y Varchar 30 TM_ASSIGN_OBJECT_TYPE Yes

S_TERRALGN_REGN EXPIRATION_DT Y UTC DateTime

7

S_TERRALGN_REGN FROM_TERR_ID Y Varchar 15

S_TERRALGN_REGN REP_ACTION_CD Y Varchar 30 APPTM_REP_ACTION_TYPE Yes




LOV Bnd

Sie

be

l Da

ta M

od

el R

efe

ren

ce

Versio

n 8

.0, R

ev. A

18

1

Sch

em

a C

ha

ng

es ■

Table

Colu

mn C

hanges in

This V

ersio

n

S_TERRALGN_REGN REQ_PER_ID Y Varchar 15

S_TERRALGN_ZIP ACTIVATION_DT Y UTC DateTime

7

S_TERRALGN_ZIP AFFL_OBJECT_CD Y Varchar 30 TM_AFFL_OBJECT_TYPE Yes

S_TERRALGN_ZIP APPR_PER_ID Y Varchar 15

S_TERRALGN_ZIP APPR_STATUS_CD Y Varchar 30 ALGN_APPR_STATUS_CD Yes

S_TERRALGN_ZIP ASGN_OBJECT_CD Y Varchar 30 TM_ASSIGN_OBJECT_TYPE Yes

S_TERRALGN_ZIP EXPIRATION_DT Y UTC DateTime

7

S_TERRALGN_ZIP FROM_TERR_ID Y Varchar 15

S_TERRALGN_ZIP GEO_TYPE_CD Y Varchar 30 TM_GEO_TYPE Yes

S_TERRALGN_ZIP REP_ACTION_CD Y Varchar 30 APPTM_REP_ACTION_TYPE Yes

S_TERRALGN_ZIP REQ_PER_ID Y Varchar 15

S_TERRITORY BU_ID N Varchar 15 0-R9NH

S_TERRITORY ROLL_UP_AMT Y Number 22 22 7

S_TERR_ACCNT AFFL_OBJECT_CD Y Varchar 30 TM_AFFL_OBJECT_TYPE Yes

S_TERR_ACCNT CREATED_BY_ALGN_ID Y Varchar 15

S_TERR_ACCNT EXPIRED_BY_ALGN_ID Y Varchar 15

S_TERR_ACCNT FROM_TERR_ID Y Varchar 15

S_TERR_ASSET CREATED_BY_ALGN_ID Y Varchar 15

S_TERR_ASSET EXPIRED_BY_ALGN_ID Y Varchar 15

S_TERR_CON AFFL_OBJECT_CD Y Varchar 30 TM_AFFL_OBJECT_TYPE Yes

S_TERR_CON CREATED_BY_ALGN_ID Y Varchar 15

S_TERR_CON EXPIRED_BY_ALGN_ID Y Varchar 15

S_TERR_CON FROM_TERR_ID Y Varchar 15

S_TERR_HIER ORIG_HIER_ID Y Varchar 15

S_TERR_POSITION CREATED_BY_ALGN_ID Y Varchar 15




LOV Bnd

Sie

be

l Da

ta M

od

el R

efe

ren

ce

Versio

n 8

.0, R

ev. A

18

2

Sch

em

a C

ha

ng

es ■

Table

Colu

mn C

hanges in

This V

ersio

n

S_TERR_POSITION EXPIRED_BY_ALGN_ID Y Varchar 15

S_TERR_REGION AFFL_OBJECT_CD Y Varchar 30 TM_AFFL_OBJECT_TYPE Yes

S_TERR_REGION ASGN_OBJECT_CD Y Varchar 30 TM_ASSIGN_OBJECT_TYPE Yes

S_TERR_REGION CREATED_BY_ALGN_ID Y Varchar 15

S_TERR_REGION EXPIRED_BY_ALGN_ID Y Varchar 15

S_TERR_REGION FROM_TERR_ID Y Varchar 15

S_TERR_ZIP AFFL_OBJECT_CD Y Varchar 30 TM_AFFL_OBJECT_TYPE Yes

S_TERR_ZIP ASGN_OBJECT_CD Y Varchar 30 TM_ASSIGN_OBJECT_TYPE Yes

S_TERR_ZIP CREATED_BY_ALGN_ID Y Varchar 15

S_TERR_ZIP EXPIRED_BY_ALGN_ID Y Varchar 15

S_TERR_ZIP FROM_TERR_ID Y Varchar 15

S_TERR_ZIP GEO_TYPE_CD Y Varchar 30 TM_GEO_TYPE Yes

S_UNVBX_ITEM CONTEXT Y Varchar 250

S_UNVBX_ITMTASK REMOTE_EXEC_CD Y Varchar 200

S_UNVBX_ITMTASK TERR_ID Y Varchar 15

S_UNVBX_ITMTYPE TRNSFR_APPLET_NAME Y Varchar 75

S_UOM_CONV_FCTR CONV_TYPE_CD Y Varchar 30

S_WFA_DATA STRING_DATA_VAL Y Varchar 1999

S_WFA_DPLOY_DEF ANALY_LVL_CD Y Varchar 30 NONE WF_ANLY_LVL_CD Yes

S_WFA_DPLOY_DEF DEL_EVT_HANDLE_FLG N Char 1 N

S_WFA_DPLOY_DEF DESCRIPTION Y Varchar 250

S_WFA_DPLOY_DEF DISPNAME_OVERRIDE Y Varchar 250

S_WFA_DPLOY_DEF DISPNAME_REF Y Varchar 75

S_WFA_DPLOY_DEF REPOSITORY_VERSION Y Number 22 10 0

S_WFA_DPLOY_DEF SUB_TASK_FLG N Char 1 N

S_WFA_DPLOY_DEF TYPE_CD N Varchar 30 PROCESS WF_TYPE_CD Yes




LOV Bnd

Sie

be

l Da

ta M

od

el R

efe

ren

ce

Versio

n 8

.0, R

ev. A

18

3

Sch

em

a C

ha

ng

es ■

Table

Colu

mn C

hanges in

This V

ersio

n

S_WFA_INSTANCE ANALY_DEF_FLG N Char 1 N

S_WFA_INSTANCE ANALY_LVL_CD N Varchar 30 NONE WF_ANLY_LVL_CD Yes

S_WFA_INSTANCE DISPNAME_OVERRIDE Y Varchar 100

S_WFA_INSTANCE INTERNAL_STAT_VAL Y Number 22 10 0

S_WFA_INSTANCE LAST_SVPT_VAL Y Varchar 15

S_WFA_INSTANCE ROOT_DEF_ID_VAL Y Varchar 15

S_WFA_INST_PROP LONG_VAL Y Text 0

S_WS_PORT ATT_PROTOCOL_CD Y Varchar 30 WS_ATT_PROTOCOL_CD Yes

T_DETAIL ENCRPTD_COL Y Varchar 50

T_DETAIL ENCRPTD_HASH_VAL Y Varchar 30

T_DETAIL ENCRPTN_KEY_INDEX Y Varchar 10

T_DETAIL NAME_CI Y Varchar 75

T_MASTER_POSTN MASTER_NAME_CI Y Varchar 75

T_MASTER_X ATTRIB_08 Y CLOB 131072

V_SA_SBLSRVR GROUP_NAME Y Varchar 45




LOV Bnd


Schema Changes ■ Table Column Changes in This Version

184

New System Columns in This VersionTwo new system columns, shown in Table 84, have been added to almost all of the Siebel tables. These columns may not be present in some tables that are used by Siebel server applications as temporary tables or log tables. These columns are maintained by the ObjectManager and Oracle’s Siebel server applications.

Modified Table Columns in This VersionTable 85 lists table columns that have changed in this version.

Table 84. New System Columns in This Version

Column Name Description Data Type

DB_LAST_UPD Last Updated - This Database UTC Datetime

DB_LAST_UPD_SRC Source of Last Update - This Database varchar (50)

Table 85. Modified Table Columns in This Version

Table Column Type of Change

Previous Value New Value

S_AUDIT_ITEM FIELD_NAME Optional No Yes

S_CON_PRDINT_M CON_CD LOV Type CONTACT_TYPE

None

S_DISCNT DISCNT_CD LOV Type DISCOUNT_TYPE

None

S_EMT_DSET_ITEM POST_PROC_WF_NAME Optional No Yes

S_ESCL_REQ REQ_ID Prec 9 15

S_LST_OF_VAL ACTIVE_FLG Optional Yes No

S_LST_OF_VAL MULTI_LINGUAL_FLG Optional Yes No

S_MDF_TXN TYPE_CD LOV Bnd Yes No

S_MERGE_LOG_ATTR NEW_STD_VALUE Length 128 500

S_MERGE_LOG_ATTR OLD_CUST_VALUE Length 128 500

S_MERGE_LOG_ATTR OLD_STD_VALUE Length 128 500

S_ORDER CCNUM_ENCRPKEY_REF Length 30 150

S_PRI_LST_ITEM PRI_CD LOV Type Price Type None

S_PTY_PAY_PRFL CCNUM_ENCRPKEY_REF Length 30 150

S_PTY_PAY_PRFL CCVNUM_ENCRPKY_REF Length 30 60

S_SMQ_ADDR SECURITY_TOKEN Length 100 210

Schema Changes ■ Table Index Changes in This Version


Table Index Changes in This VersionThis topic lists the following changes to table indexes that have been implemented in this version of the schema:

■ “New Table Indexes in This Version” on page 185

■ “Modified Table Indexes in This Version” on page 187

■ “Table Indexes Deleted from This Version” on page 190

New Table Indexes in This VersionTable 86 lists table indexes that are new in this version.

S_SRC LOAD_BEHAVIOR_CD LOV Type None CAMPAIGN_LOAD_ BEHAVIOR

S_SRC_PAYMENT CCNUM_ENCRPKEY_REF Length 30 150

S_SSO_SYS_USER PWD_ENCRPKEY_REF Length 30 150

S_TERRASGN_INFO ASGN_OBJECT_CD LOV Type None TM_ASSIGN_OBJECT_ TYPE

S_TERRASGN_INFO SEARCH_SPEC Length 250 1999

S_TERRITORY TERR_HIER_ID Optional No Yes

S_VOD LOCKED_BY Length 15 50

Table 86. New Table Indexes in This Version

Table Name Index A U Columns

S_AUDIT_ITEM S_AUDIT_ITEM_M4 Y N (OPERATION_DT)

S_BRDCST_MSG S_BRDCST_MSG_M5 Y N (UNIVERSAL_MSG_FLG)

S_CAMP_CON S_CAMP_CON_F19 Y N (DCP_ID)

S_CM_CNCTR S_CM_CNCTR_F1 Y N (SRCH_ENGINE_ID)

S_COMMUNICATION S_COMMUNICATN_F18 Y N (DCP_ID)

S_CON_SYNC_SCHD S_CON_SYNC_SCHD_F3 Y N (CALL_LST_ID)

S_DMND_CRTN_PRG S_DMND_CRTNPRG_F17 Y N (MKTG_OFFR_ID)

S_EMT_DSET_ITEM S_EMT_DSET_ITEM_F3 Y N (PDQ_ID)

S_EMT_SESSN_ITM S_EMT_SESSN_ITM_F3 Y N (PDQ_ID)

Table 85. Modified Table Columns in This Version

Table Column Type of Change

Previous Value New Value



186

S_ENTL_PRDPRI S_ENTL_PRDPRI_F50 Y N (AGREE_BNFT_ID)

S_ENTL_PRDPRI S_ENTL_PRDPRI_F51 Y N (CTLG_CAT_ID)

S_ENTL_PRDPRI S_ENTL_PRDPRI_F52 Y N (XA_CLASS_ID)

S_ENTMPL_PRDPRI S_ENTMPLPRDPRI_F50 Y N (BNFT_TMPL_ID)

S_ENTMPL_PRDPRI S_ENTMPLPRDPRI_F51 Y N (CTLG_CAT_ID)

S_ENTMPL_PRDPRI S_ENTMPLPRDPRI_F52 Y N (XA_CLASS_ID)

S_EVT_MKTG S_EVT_MKTG_F4 Y N (EVT_FUL_REQ_ID)

S_EVT_MKTG S_EVT_MKTG_F5 Y N (PORTFOLIO_ID)

S_EVT_MKTG S_EVT_MKTG_F6 Y N (PRTFL_ACCNT_ID)

S_EVT_MKTG S_EVT_MKTG_F7 Y N (PRTFL_CTGRY_ID)

S_FCSTSER S_FCSTSER_F2 Y N (QTY_AGFLD_ID)

S_FCSTSER_POSTN S_FCSTSER_POSTN_F2 Y N (FCSTSER_AGFLD_ID)

S_INVOICE S_INVOICE_F52 Y N (AGREE_BNFT_ID)

S_NODE S_NODE_F4 Y N (ROUTE_ID)

S_OPTY_POSTN S_OPTY_POSTN_F2 N N (ASGN_TERR_ID)

S_OPTY_SRC S_OPTY_SRC_F4 Y N (DCP_ID)

S_ORDER S_ORDER_F43 Y N (DCP_ID)

S_ORDER S_ORDER_F57 Y N (AGREE_BNFT_ID)

S_PRTNRPRG_APPL S_PRTNRPRG_APPL_F5 Y N (AGREE_ITEM_ID)

S_PRTNRPRG_APPL S_PRTNRPRG_APPL_F6 Y N (PRTNRPRG_MBR_ID)

S_PRTNRPRG_MBR S_PRTNRPRG_MBR_F1 Y N (AGREE_ITEM_ID)

S_PRTNRPRG_MBR S_PRTNRPRG_MBR_U2 Y Y (MEMBERSHIP_NUM,CONFLICT_ID)

S_PRTNR_PROG S_PRTNR_PROG_F7 Y N (PROD_INT_ID)

S_REVN S_REVN_F19 Y N (ENT_SOLN_ID)

S_SMQ_HISTORY S_SMQ_HISTORY_M1 Y N (TRANSPORT_IDEN)

S_SMQ_HISTORY S_SMQ_HISTORY_M2 Y N (OID_IDEN)

S_SORT_CHAR S_SORT_CHAR_U1 Y Y (CHAR_VAL)

S_SRC_PAYMENT S_SRC_PAYMENT_F65 Y N (AGREE_BNFT_ID)

S_TERR_ASSET S_TERR_ASSET_F2 Y N (CREATED_BY_ALGN_ID)

S_TERR_ASSET S_TERR_ASSET_F3 Y N (EXPIRED_BY_ALGN_ID)

S_TERR_CON S_TERR_CON_F2 Y N (CREATED_BY_ALGN_ID)





Modified Table Indexes in This VersionTable 87 lists table indexes that are now active in this version.

S_TERR_CON S_TERR_CON_F3 Y N (EXPIRED_BY_ALGN_ID)

S_TERR_CON S_TERR_CON_F4 Y N (FROM_TERR_ID)

S_TERR_POSITION S_TERR_POSITION_F3 Y N (CREATED_BY_ALGN_ID)

S_TERR_POSITION S_TERR_POSITION_F4 Y N (EXPIRED_BY_ALGN_ID)

S_TERR_REGION S_TERR_REGION_F2 Y N (CREATED_BY_ALGN_ID)

S_TERR_REGION S_TERR_REGION_F3 Y N (EXPIRED_BY_ALGN_ID)

S_TERR_REGION S_TERR_REGION_F4 Y N (FROM_TERR_ID)

S_TERR_ZIP S_TERR_ZIP_F1 Y N (CREATED_BY_ALGN_ID)

S_TERR_ZIP S_TERR_ZIP_F2 Y N (EXPIRED_BY_ALGN_ID)

S_TERR_ZIP S_TERR_ZIP_F3 Y N (FROM_TERR_ID)

S_TMSHT_ITEM S_TMSHT_ITEM_V1 Y N (CREATED_BY)

S_UNVBX_ITEM S_UNVBX_ITEM_M2 Y N (REQUESTOR_ID,RQSTD_TS)

S_UNVBX_ITMTASK S_UNVBX_ITMTASK_F2 Y N (TERR_ID)

S_UNVBX_ITMTASK S_UNVBX_ITMTASK_M1 Y N (APPROVER_ID,ACTIVE_FLG,START_TS)

T_DETAIL T_DETAIL_U1_C1 Y N (RUN_NUM,NAME_CI,CONFLICT_ID)

T_MASTER_POSTN T_MASTER_POSTN_C1 Y N (MASTER_NAME_CI)

Table 87. Table Indexes That Are Now Active in This Version


S_ADDR_ORG S_ADDR_ORG_M7 Y N (DB_LAST_UPD,ROW_ID)

S_ADDR_PER S_ADDR_PER_M6 Y N (DB_LAST_UPD,ROW_ID)





188

Table 88 lists table indexes that have changed definition in this version.

Table 88. Table Indexes That Have Changed Definition in This Version

Table Name Index Previous Columns New Columns

S_APP_QUERY S_APP_QUERY_U1 NAMEDESC_TEXTCREATED_BYLANG_IDCONFLICT_IDPRIV_FLG

NAMEDESC_TEXTOWNER_IDLANG_IDCONFLICT_IDPRIV_FLG

S_APP_QUERY S_APP_QUERY_V1 CREATED_BY OWNER_ID

S_FCST_ITEM_DTL S_FCST_ITEM_DTL_U1 FCST_ITEM_IDDETAIL_DTORIG_FCST_IDCONFLICT_ID

FCST_ITEM_IDDETAIL_DTORIG_FCST_IDSEQ_NUMCONFLICT_ID

S_POSTN S_POSTN_M4 DB_LAST_UPDPAR_ROW_ID

DB_LAST_UPDROW_IDPAR_ROW_ID

S_QUOTE_POSTN S_QUOTE_POSTN_M1 POSTN_IDQUOTE_NUMREV_NUM

POSTN_IDQUOTE_NUMREV_NUMQUOTE_ID

S_REVN S_REVN_M3 EFFECTIVE_DTPROD_ID

PROD_IDEFFECTIVE_DT

S_SRM_REQUEST S_SRM_REQUEST_M6 STATUSTGT_DELETE_TS

SRVR_FLOW_ID_VALROW_IDSTATUSTGT_DELETE_TS

S_TERRALGN S_TERRALGN_U1 TERR_HIER_IDNAMECONFLICT_ID

TERR_HIER_IDBU_IDNAMECONFLICT_ID

S_TERRALGN_ACCT S_TERRALGN_ACCT_U1 TERR_ALGN_IDTERR_IDACCNT_IDCONFLICT_ID

TERR_ALGN_IDTERR_IDACCNT_IDAFFL_OBJECT_CDCONFLICT_ID



S_TERRALGN_CON S_TERRALGN_CON_U1 TERR_ALGN_IDTERR_IDCON_IDCONFLICT_ID

TERR_ALGN_IDTERR_IDCON_IDAFFL_OBJECT_CDCONFLICT_ID

S_TERRALGN_REGN S_TERRALGN_REGN_U1 TERR_ALGN_IDTERR_IDREGION_IDCONFLICT_ID

TERR_ALGN_IDTERR_IDREGION_IDASGN_OBJECT_CDAFFL_OBJECT_CDCONFLICT_ID

S_TERRALGN_ZIP S_TERRALGN_ZIP_U1 TERR_ALGN_IDTERR_IDZIPCODECONFLICT_ID

TERR_ALGN_IDTERR_IDZIPCODEASGN_OBJECT_CDAFFL_OBJECT_CDGEO_TYPE_CDCONFLICT_ID

S_TERRITORY S_TERRITORY_U1 TERR_HIER_IDNAMECONFLICT_ID

NAMEBU_IDCONFLICT_ID

S_TERR_ACCNT S_TERR_ACCNT_U1 TERR_IDACCNT_IDEFF_START_DTCONFLICT_ID

TERR_IDACCNT_IDEFF_START_DTAFFL_OBJECT_CDCONFLICT_ID

S_TERR_CON S_TERR_CON_U1 TERR_IDCON_IDEFF_START_DTCONFLICT_ID

TERR_IDCON_IDEFF_START_DTAFFL_OBJECT_CDCONFLICT_ID

S_TERR_REGION S_TERR_REGION_U1 TERR_IDREGION_IDEFF_START_DTCONFLICT_ID

TERR_IDREGION_IDEFF_START_DTASGN_OBJECT_CDAFFL_OBJECT_CDCONFLICT_ID





190

Table Indexes Deleted from This VersionTable 89 lists table indexes that have been deleted from this version.

S_TERR_ZIP S_TERR_ZIP_U1 TERR_IDZIPCODEEFF_START_DTCONFLICT_ID

TERR_IDZIPCODEEFF_START_DTASGN_OBJECT_CDAFFL_OBJECT_CDGEO_TYPE_CDCONFLICT_ID

S_UNVBX_ITEM S_UNVBX_ITEM_F1 REQUESTOR_ID OBJECT_VAL

S_WFA_DPLOY_DEF S_WFA_DPLOY_DEF_U1 NAMEVERSIONCONFLICT_ID

TYPE_CDNAME VERSIONCONFLICT_ID

Table 89. Deleted Table Indexes


S_UNVBX_ITEM_F1 S_UNVBX_ITEM_F1 Y N REQUESTOR_ID

S_VOD S_VOD_F1 Y N LOCKED_BY




Index

Aaccount ERD

about 17diagram 19support for Dynamic Hierarchy 18support for Global Account Views 18tables 18

adjustment group ERDabout 20diagram 21tables 20

apparelSee textile, apparel, and footwear ERD

asset management ERDabout 22diagram 23tables 22tracking asset instances 22

auction ERDabout 24diagram 25tables 24

auto email response generator ERDabout 26diagram 27tables 26

Bbanking

See commercial banking ERD

Ccampaign management

See marketing campaign ERDCG promotion planning ERD

about 28diagram 30tables 28

columnsdomain type definitions 159INTEGRATION_ID columns, about 161naming conventions 155numeric physical type 160type definitions 159

commercial banking ERDabout 31

compensation planning administration ERDabout 31diagram 32tables 31

compensation planning execution ERDabout 33diagram 34tables 33

competency management system ERDabout 35diagram 36tables 35

Consumer GoodsCG promotion planning ERD 28

content management ERDabout 37diagram 38tables 37

content objectSee content management ERD

content processSee content management ERD

contract conditions ERDabout 39diagram 40tables 39

contracts ERDabout 41diagram 42tables 41

Customer Data Item, about 43

Ddata (intersection) table type

about 157obsolete, table marked as 157

data (private) table type, about 157data (public) table type

about 157obsolete, table marked as 157

data typeslimit checking 162

data visibility ERDabout 43diagram 45tables 43

Database Marketing, marketing program


Index ■ E

192

ERD 79database schema version number, finding

and format 161defect tracking

See product quality tracking ERDdesign

See schemadomain type definitions 159Dun & Bradstreet integration ERD


Dynamic Hierarchy, support by account entity 18

Eemployee KPI ERD


employeesfield service scheduler ERD 54time sheet ERD 141

entitlement items, service agreement ERD 125

ERDsaccount, diagram 19account, tables 18adjustment group, diagram 21adjustment group, tables 20asset management, diagram 23asset management, tables 22auction, diagram 25auction, tables 24auto email response generator,

diagram 27auto email response generator, tables 26CG promotion planning, diagram 30CG promotion planning, tables 28compensation planning administration,

diagram 32compensation planning administration,

tables 31compensation planning execution,

diagram 34compensation planning execution,

tables 33competency management system,

diagram 36competency management system,

tables 35content management, diagram 38content management, tables 37

contract conditions, diagram 40contract conditions, tables 39contracts, diagram 42contracts, tables 41data visibility, diagram 45data visibility, tables 43Dun & Bradstreet integration, diagram 47Dun & Bradstreet integration, tables 46employee KPI, diagram 49employee KPI, tables 48exclusive arc relationship, diagram

conventions 12expense reports, diagram 51expense reports, tables 50field service inventory, diagram 53field service inventory, tables 52field service scheduler, diagram 55field service scheduler, tables 54forecasts, diagram 57forecasts, tables 56general diagram conventions 12high tech marketing development fund,

diagram 59high tech marketing development fund,

tables 58high tech special pricing authorization,

diagram 61high tech special pricing authorization,

tables 60invoicable charges, diagram 63invoicable charges, tables 62invoices, diagram 65invoices, tables 64marketing campaign, diagram 67, 69marketing campaign, tables 68marketing collaboration, diagram 71marketing collaboration, tables 70marketing encyclopedia, diagram 73marketing encyclopedia, tables 72marketing events, diagram 76marketing events, tables 74marketing plans, diagram 78marketing plans, tables 77marketing program, diagram 81marketing program, tables 79marketing resource management: document,

diagram 83marketing resource management: document,

tables 82opportunity management, diagram 85opportunity management, tables 84order life cycle, diagram 87order life cycle, tables 86orders, diagram 89

Index ■ F


orders, tables 88partner collaboration, diagram 91partner collaboration, tables 90partner program registration, diagram 93partner program registration, tables 92party model, diagram 95party model, tables 94payments, diagram 97payments, tables 96performance review, diagram 100performance review, tables 98personal account, diagram 102personal account, tables 101personal financial review, diagram 104personal financial review, tables 103pricing comparison, diagram 106pricing comparison, tables 105pricing, diagram 108pricing, tables 107product promotion, diagram 110product promotion, tables 109product quality tracking, diagram 112product quality tracking, tables 111product recommendation, diagram 114product recommendation, tables 113products or services, diagram 116products or services, tables 115professional services, diagram 118professional services, tables 117recursive relationship, diagram

conventions 13revenue, diagram 120revenue, tables 119revision table 14sales hierarchy and credit assignment,

diagram 122sales hierarchy and credit assignment,

tables 121sales portfolio management, diagram 124sales portfolio management, tables 123,

137service agreement, diagram 126service agreement, tables 125service calendars and work shifts,

diagram 128service calendars and work shifts,

tables 127service request, diagram 130service request, tables 129shipment, diagram 132shipment, tables 131Siebel Assistant, diagram 134Siebel Assistant, tables 133territory management - LS, diagram 138

territory management, diagram 136territory management, tables 135textile, apparel, and footwear,

diagram 140textile, apparel, and footwear, tables 139time sheet, diagram 142time sheet, tables 141trade promotions, diagram 144trade promotions, tables 143training curriculum course, diagram 146training curriculum course, tables 145training test engine, diagram 148training test engine, tables 147versioned object definition, diagram 150versioned object definition, tables 149warranty, diagram 152warranty, tables 151

exclusive arc relationshipabout 12diagram conventions 12

expense reports ERDabout 50diagram 51tables 50

extension (Siebel) table typeabout 157obsolete table marked as 157

extension table type, about 157

Ffield service inventory ERD


field service scheduler ERDabout 54diagram 55tables 54

financial accountspersonal account ERD 101

financial review, personal financial review ERD 103

Financial Servicescommercial banking ERD 31

footwearSee textile, apparel, and footwear ERD

forecasts ERDabout 56diagram 57tables 56

GGlobal Account Views, support by account


Index ■ H

194

entity 18

Hhigh tech marketing development fund ERD


high tech special pricing authorization ERDabout 60diagram 61tables 60

IInclude Only field 161index column fields 161index naming conventions 155insurance

personal account ERD 101INTEGRATION_ID columns, about 161invoicable charges ERD


invoices ERDabout 64diagram 65tables 64

Llimit checking for data types 162

Mmarketing campaign ERD

about 68diagram 67, 69tables 68

marketing collaboration ERDabout 70diagram 71tables 70

marketing development fundsSee CG promotion planning ERD

marketing encyclopedia ERDabout 72diagram 73tables 72

marketing events ERDabout 74diagram 76tables 74

marketing plans ERDabout 77

diagram 78tables 77

marketing program ERDabout 79diagram 81tables 79

marketing resource management: document ERD


Master Data Item, about 43MDFs

See CG promotion planning ERD

Nnaming conventions

columns 155indexes 155physical model listings, abbreviations

used 156table names 153table prefixes 154table suffixes 154

non-Siebel application products, caution about inserting or updating data 9

normalized, defined 9

Oopportunity management ERD


Oracle Applications, about use of INTEGRATION_ID columns 161

order life cycle ERDabout 86diagram 87tables 86

orders ERDabout 88diagram 89tables 88

Ppartner collaboration ERD


partner program registration ERDabout 92diagram 93tables 92

Index ■ R


party model ERDabout 94diagram 95tables 94

party, defined 94payments ERD


performance review ERDabout 98diagram 100tables 98

personal account ERDabout 101diagram 102tables 101

personal financial review ERDabout 103diagram 104tables 103

physical modelcolumn naming conventions 155column type definitions 159columns of numeric physical type 160database schema version number, finding and

format 161domain type definitions 159Include Only field 161index naming conventions 155INTEGRATION_ID columns, about 161limit checking for data types 162party model, aboutparty model, about 162physical model listings, abbreviations

used 156Siebel repository tables, about 161Siebel system fields 160table naming conventions 153table status definitions 158table type definitions 157validating Siebel Schema 162

pricing comparison ERDabout 105diagram 106tables 105

pricing ERDabout 107diagram 108tables 107

product promotion ERDabout 109diagram 110tables 109

product quality tracking ERD


product recommendation ERDabout 113diagram 114tables 113

products or services ERDabout 115diagram 116tables 115

professional services ERDabout 117diagram 118tables 117

projects, professional services ERD 117

Rrecursive relationship

about 13diagram conventions 13

repository, about Siebel repository 161revenue ERD

diagram 120tables 119

Ssales hierarchy and credit assignment ERD


Sales Hierarchy ModuleSee sales hierarchy and credit assignment

ERDsales portfolio management ERD

about 123diagram 124tables 123, 137

schemadatabase schema version number, finding and

format 161defined 9validating Siebel Schema 162

service activities, field service scheduler ERD 54

service agreement ERDabout 125diagram 126tables 125

service calendars and work shifts ERDabout 127diagram 128tables 127


Index ■ T

196

service region, field service scheduler ERD 54

service request ERDabout 129diagram 130tables 129

shipment ERDabout 131diagram 132tables 131

Siebel Assistant ERDabout 133diagram 134tables 133

Siebel Financial Servicescommercial banking ERD 31

Siebel repository, about 161Siebel SAP R/3 Connector, about use of

INTEGRATION_ID columns 161Siebel system fields 160special ERD conventions

exclusive arc relationship 12recursive relationship 13

system fields 160

Ttables

naming conventions 153prefix naming conventions 154suffix naming conventions 154table status definitions 158types of 157

territory management - LS ERDdiagram 138

territory management ERDabout 135diagram 136tables 135

territory quota rollup ERDabout 137

tests, training test engine ERD 147textile, apparel, and footwear ERD


time sheet ERDabout 141diagram 142tables 141

trade promotions ERDabout 143diagram 144tables 143

training curriculum course ERDabout 145diagram 146tables 145

training test engine ERDabout 147diagram 148tables 147

Vvalidating Siebel Schema 162versioned object definition ERD


Wwarranty ERD


work shiftsSee service calendars and work shifts ERD

workflow processSee content management ERD

Documents

DMR