siebel data model reference for industry applications v8.1.1

Siebel Data Model Reference for Industry Applications

Version 8.1November 2008

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

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

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

PRODUCT MODULES AND OPTIONS. This guide contains descriptions of modules that are optional and for which you may not have purchased a license. 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 for Industry Applications Version 8.1 3

Contents

Siebel Data Model Reference for Industry Applications 1

Chapter 1: What’s New in This Release

Chapter 2: Data Model Overview

Chapter 3: Logical ModelEntity Relationship Diagram Conventions 13

General Entities 14Exclusive Arc Relationship 14Recursive Relationship 15

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

Siebel Data Model Reference for Industry Applications Version 8.1

Contents ■

4

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

Contents ■


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


Contents ■

6

Vehicle Collection 254Vehicle Financing 256Vehicle Sales 258Versioned Object Definition 260Warranty 262

Chapter 4: Physical ModelData Model Naming Conventions 265

Table Naming Conventions 265Index Naming Conventions 267Column Naming Conventions 267Abbreviations Used in the Physical Model Listings 268

Data Model Type Definitions 268Table Type Definitions 269Table Status Definitions 270Column Type Definitions 271Domain Type Definitions 271

Columns of Numeric Physical Type 272

Siebel System Fields 272

INTEGRATION_ID Columns 273

Include Only Field 273

Siebel Repository 273

Database Schema Version 274

Limit Checking for Data Types 274

Validating the Siebel Schema 274

Party Model Unifies Access to Data 275

Generating a Report about Tables 275

Chapter 5: Schema ChangesTable Changes in This Version 277

New Tables in This Version 277Changed Tables in This Version 281

Table Column Changes in This Version 281New Table Columns in This Version 282Changed Table Columns in This Version 311

Table Index Changes in This Version 311New Table Indexes in This Version 312

Contents ■


Changed Table Index in This Version 317Table Index That Was Deleted from This Version 318

Index


Contents ■

8


1 What’s New in This Release

What’s New in Siebel Data Model Reference for Industry Applications, Version 8.1Table 1 lists changes described in this version of the documentation to support release 8.1 of the software.

Table 1. What’s New in Siebel Data Model Reference for Industry Applications, Version 8.1

Topic Description

“Benefit Case Management” on page 44 This new feature supports benefits determination and case-information verification.

“Loyalty” on page 141 The Loyalty Member and Loyalty Program ERDs of previous releases have been consolidated into a single ERD. Features that are designed to extend accrual, redemption, promotion, enrollment, member administration, partner administration, and other functions have been added.

“Personalized Content Delivery” on page 183

This new feature allows sales representatives for pharmaceutical companies to deliver a sales communication using multimedia visualizations.

“Public Sector Case Lead Management” on page 199

The functionality of this ERD has been extended to enable data from application forms to be uploaded into Siebel objects.

“Sample Management” on page 216 This ERD has been modified to improve a pharmaceutical company’s ability to monitor and use its auditing and compliance processes.

“Table Changes in This Version” on page 277

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

“Table Column Changes in This Version” on page 281

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

“Table Index Changes in This Version” on page 311

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


What’s New in This Release ■

10


2 Data Model Overview

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

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

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

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

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

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

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

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

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


Data Model Overview ■

12


3 Logical Model

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

■ Entities

■ Relationships between entities

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

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

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

The information on ERDs is organized as follows:

■ Entity Relationship Diagram Conventions

■ Entity Relationship Diagrams and Descriptions on page 16

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

■ General Entities on page 14

■ Exclusive Arc Relationship on page 14

■ Recursive Relationship on page 15


Logical Model ■ Entity Relationship Diagram Conventions

14

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

16

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

Table 2. Entity Relationship Diagrams

ERD NameFigure Num. and Page Functional Area

Revised in 8.1

Newin 8.1

Account Figure 4 on page 25

General No No

Account Targeting Figure 5 on page 27

Consumer Sector No No

Activity Figure 6 on page 29

Life Sciences No No

Adjustment Group Figure 7 on page 31

General No No

Affiliations and Best Times Figure 8 on page 33

Life Sciences No No

Agencies/Agent Figure 9 on page 35

Financial Services No No

Asset Management Figure 10 on page 37

General No No

Auction Figure 11 on page 39

General No No

Auto Email Response Generator Figure 12 on page 41

General No No

Automotive Retail Figure 13 on page 43

Automotive No No

Benefit Case Management Figure 14 on page 46

Public Sector No Yes

Brick Figure 15 on page 48

Life Sciences No No

CG Promotion Planning Figure 16 on page 51

Marketing No No

Clinical Study Management Figure 17 on page 54

Life Sciences No No



Communications, Media, and Energy Account

Figure 18 on page 56

CME No No

CME Agreement Figure 19 on page 58

CME No No

CME Alert Figure 20 on page 60

CME No No

CME Energy Products, Service, and Usage


CME No No

CME Order Management Figure 22 on page 64

CME No No

Commercial Banking Figure 23 on page 67


Commercial Insurance Figure 24 on page 69


Community/Chat Discussion Figure 25 on page 71

Life Sciences No No

Compensation Planning Administration Figure 26 on page 73

ERM No No

Compensation Planning Execution Figure 27 on page 75

ERM No No

Competency Management System Figure 28 on page 77

ERM No No

Content Management Figure 29 on page 79

General No No

Contract Conditions Figure 30 on page 81

General No No

Contracts Figure 31 on page 83

General No No

Data Visibility Figure 32 on page 86

General No No

Dealer Sales and Service Promotion Figure 33 on page 88

Automotive No No

Document ID and Tax ID Figure 34 on page 90

Handheld No No

Dun & Bradstreet Integration Figure 35 on page 92

Sales/Marketing No No



Revised in 8.1

Newin 8.1



18

Employee KPI Figure 36 on page 94

ERM No No

Event Tax Administration Figure 37 on page 96

Hospitality No No

Expense Reports Figure 38 on page 98

General No No

Field Service Inventory Figure 39 on page 100

Service No No

Field Service Scheduler Figure 40 on page 102

Service No No

Financial Account Figure 41 on page 104


Financial Account Application Figure 42 on page 106


Financial Investments Figure 43 on page 108


Financial Products Figure 44 on page 110


Financial Services Events Figure 45 on page 113


Forecasts Figure 46 on page 115


Group Insurance Policies Figure 47 on page 117


Group Pensions Figure 48 on page 119


Health Provider and Provider Group Figure 49 on page 121


High Tech Marketing Development Fund Figure 50 on page 123

Marketing No No

High Tech Special Pricing Authorization Figure 51 on page 125

Sales No No

Hospitality Category Figure 52 on page 127

General No No

Institutional Sales Figure 53 on page 129




Revised in 8.1

Newin 8.1



Insurance Claims Figure 54 on page 132


Insurance Policies Figure 55 on page 134


Invoicable Charges Figure 56 on page 136

Service No No

Invoices Figure 57 on page 138

Service No No

Life Insurance Policy Figure 58 on page 140


Loyalty Figure 59 on page 144

General Yes No

Managed Care Figure 60 on page 146

Life Sciences No No

Marketing Campaign Figure 61 on page 148

Marketing No No

Marketing Collaboration Figure 62 on page 150

Marketing No No

Marketing Encyclopedia Figure 63 on page 152


Marketing Events Figure 64 on page 155

General No No

Marketing Plans Figure 65 on page 157

Marketing No No

Medical Education Event Management Figure 66 on page 159

Life Sciences No No

Objectives Figure 67 on page 161


Opportunity Management Figure 68 on page 163

Sales No No

Order Life Cycle Figure 69 on page 165

General No No

Orders Figure 70 on page 167

General No No

Partner Collaboration Figure 71 on page 169

General No No



Revised in 8.1

Newin 8.1



20

Partner Program Registration Figure 72 on page 171

General No No

Party Model Figure 73 on page 173

General No No

Payments Figure 74 on page 175

General No No

Performance Review Figure 75 on page 178

ERM No No

Personal Account Figure 76 on page 180

Industry-Specific No No

Personal Financial Review Figure 77 on page 182

Industry-Specific No No

Personalized Content Delivery Figure 78 on page 184

Life Sciences No Yes

Pricing Comparison Figure 79 on page 186

Energy No No

Pricing Figure 80 on page 188

General No No

Product Promotion Figure 81 on page 190

General No No

Product Quality Tracking Figure 82 on page 192

General No No

Product Recommendation Figure 83 on page 194

General No No

Products or Services Figure 84 on page 196

Service No No

Professional Services Figure 85 on page 198

General No No

Public Sector Case Lead Management Figure 86 on page 201

Public Sector Yes No

Public Sector Contact Identity Figure 87 on page 203

Public Sector No No

Public Sector Evidence Management Figure 88 on page 205

Public Sector No No

Public Sector Incident Management Figure 89 on page 207

Public Sector No No



Revised in 8.1

Newin 8.1



Revenue Figure 90 on page 209

General No No

Routes and Best Call Hours Figure 91 on page 211

Sales No No

Sales Hierarchy and Credit Assignment Figure 92 on page 213

Sales No No

Sales Volume Planning Figure 93 on page 215


Sample Management Figure 94 on page 217

Life Sciences Yes No

Service Agreement Figure 95 on page 219

Service No No

Service Calendars and Work Shifts Figure 96 on page 221

Service No No

Service Request Figure 97 on page 223

Service No No

Shipment Figure 98 on page 225

General No No

Siebel Assistant Figure 99 on page 227

General No No

Syndicated Data Figure 100 on page 229

Life Sciences No No

Teller Administration Figure 101 on page 231


Territory Alignment–Quota Assignment Figure 102 on page 233

Sales No No

Territory Management Figure 103 on page 235

Sales No No

Territory Management - Consumer Sector


Service No No

Territory Management - Life Sciences Figure 105 on page 239

Sales No No

Textile, Apparel, and Footwear Figure 106 on page 241


Time Sheet Figure 107 on page 243

General No No



Revised in 8.1

Newin 8.1



22

Trade Promotions Figure 108 on page 245

General No No

Training Curriculum Course Figure 109 on page 247

General No No

Training Test Engine Figure 110 on page 249

General No No

Universal Customer Master Figure 111 on page 251

General No No

Vehicle Figure 112 on page 253

Automotive No No

Vehicle Collection Figure 113 on page 255

Automotive No No

Vehicle Financing Figure 114 on page 257

Automotive No No

Vehicle Sales Figure 115 on page 259

Automotive No No

Versioned Object Definition Figure 116 on page 261

General No No

Warranty Figure 117 on page 263

Service No No



Revised in 8.1

Newin 8.1



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.

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

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

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

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

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

Table 3. Account ERD Entities and Tables

Entity Table

Account S_ORG_EXT, S_PARTY

Account Synonym S_ORG_SYN

Activity S_EVT_ACT

Address S_ADDR_PER

Assignment Group (Territory) S_ASGN_GRP

Business Unit S_BU, S_ORG_EXT, S_PARTY

Characteristics S_CHRCTR

Dynamic Account Hierarchy S_DYN_HRCHY

Dynamic Account Hierarchy Node S_DYN_HRCHY_REL

Employee/Agent S_EMP_PER, S_CONTACT, S_PARTY

Industry S_INDUST

Market Segment S_MKT_SEG

Party S_PARTY

Payment Term S_PAYMENT_TERM

Person S_CONTACT, S_PARTY

Position S_POSTN, S_PARTY



24

Price List S_PRI_LST

Sales or Service Team Member S_ACCNT_POSTN

Table 3. Account ERD Entities and Tables

Entity Table



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

LE

S O

R S

ER

VIC

E

TE

AM

ME

MB

ER

MA

RK

ET

SE

GM

EN

T

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

LO

YE

E / 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

co

nstr

ain

ed to

use

ace

ssib

le to

of

ma

de

vis

ible

thro

ugh

for m

ade

up o

f

a r

epo

rt to

a p

are

nt o

f

actio

n f

or

targ

et o

f

cla

ssific

atio

n f

or

type

of

for

pa

rt o

f

pa

rtic

ipa

nt in

targ

et o

f

respo

nsib

le f

or

respo

nsib

ility

of

use

r cha

racte

ristics f

or

de

scri

be

d in

a r

epo

rt to

a p

are

nt o

f

ano

the

r na

me

fo

r

kno

wn a

suse

r o

f

curr

ent pri

ce

lis

t fo

ra

pplic

able

to

acce

ss to

for

be

long to

addre

sse

d to

pa

rtic

ipa

te in

for

loca

ted a

t

ho

lde

rs

of

he

ld b

ypa

y o

r pa

ye

d b

y

de

fault

pa

ym

ent te

rm f

or

co

mpo

se

d o

f

co

nta

ct o

f

respo

nsib

ility

of

respo

nsib

le f

or



26

Account TargetingFigure 5 shows the Account Targeting ERD. This ERD illustrates how Siebel Enterprise applications

(Consumer Goods) support account targeting as an extension of basic querying. Account targeting provides the capability to save the results of account queries and apply those account lists when you schedule routes. The results that you save are called target lists. Target lists consist of sets of accounts that meet the conditions defined by the query. Typically, the target lists you create in account targeting are for a specific purpose and period of time. For example, the target lists might be used to support a promotion, a campaign, or an objective.


Table 4. Account Targeting ERD Entities and Tables

Entity Table


Criteria S_CG_QUERY_ITEM

Employee S_CONTACT, S_PARTY

Objective S_SRC

Query S_CG_QUERY

Route S_ACCNTRT



Figure 5. Account Targeting

CRITERIA

ACCOUNT

QUERY RESULT SET

EMPLOYEE

QUERY

ROUTEOBJECTIVE

submitted by

submit

created from

applied to

created from

applied to

returned by

return

belong to

have

combined by

combineconsist of appear on



28

ActivityFigure 6 shows the Activity ERD. This ERD illustrates how activities, contact calls, account calls, attendee calls, and meetings are managed. Every activity belongs to the employee creator and other employees assigned to the activity. Activities can be associated with one or more contacts and one account. Contact calls are associated with the employee creator and the contact, and can be associated with other employees who have been assigned, product details, samples, promotional items, and decision issues. Account calls are associated with the employee creator and an account, and can be associated with other employees who have been assigned, product details, and multiple attendee calls. Each attendee call is associated with the product details from the account call and one contact, and can be associated with samples, promotional items, and decision issues. Meetings include the employee who owns the meeting, the contacts invited to attend, the account where the meeting is taking place, and the product to be discussed at the meeting.


Table 5. Activity ERD Entities and Tables

Entity Table


Activity S_EVT_ACT

Contact S_CONTACT

Employee S_EMP_PER, S_CONTACT, S_PARTY

Indication S_PROD_APPLCTN

Issue S_PROD_ISS


Product S_PROD_INT



Figure 6. Activity

Title

: A

ctiv

ityA

utho

r : O

racle

, Con

fiden

tial

SIG

NA

TUR

E

AC

CO

UN

T

ISS

UE

IND

ICA

TIO

N

PR

OD

UC

T

DE

TAIL

PR

OM

OTI

ON

AL

ITE

M

SA

MP

LE

PE

RS

ON CO

NTA

CT

EM

PLO

YE

E

AC

TIV

ITY

ME

ETI

NG

ATT

EN

DE

E /

INV

ITE

E

CO

NTA

CT

CA

LL

ATT

EN

DE

E C

ALL

AC

CO

UN

T C

ALL

have

belo

ngs

capt

ured

for

cont

ain

com

pose

d of

affil

iate

d w

ith

subj

ect o

f

for

for

subj

ect o

f

cons

ider

atio

n on

subj

ect t

o

resp

onsi

ble

for

resp

onsi

bilit

y of

subj

ect t

o

cons

ider

atio

n on

disc

usse

d at

disc

ussi

on o

ffo

r

cont

ains

invi

ted

to/a

ttend

invi

te/a

ttend

pers

onal

list

of

belo

ng to

subj

ect o

f

for

sam

pled

at

sam

plin

g of

drop

ped

at

for



30

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


Table 6. Adjustment Group ERD Entities and Table

Entity Table

Adjustment Group S_ADJ_GROUP

Adjustment Group Dimension S_ADJ_GROUP_DIM

Product Compatibility Matrix Rule S_PRODCOMP_MTRX

Product Eligibility Matrix Rule S_PRODELIG_MTRX

Product Promotion Pricing Matrix Rule S_PROM_PMTRX

Standard Entitlement Pricing Matrix Rule S_STDENTL_PMTRX

Standard Product Pricing Matrix Rule S_STDPROD_PMTRX

Standard Training Pricing Matrix Rule S_STDTRNG_PMTRX



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



32

Affiliations and Best TimesFigure 8 shows the Affiliations and Best Times ERD. This ERD illustrates how contacts and accounts can be affiliated with one another, and how best times can be stored. Contacts can have multiple account affiliations, and can store multiple types or roles and best times for each account affiliation. Contacts can have multiple addresses and can share address records with other contacts. Contacts can also have a primary address for each position that is on the team. Accounts can also have multiple addresses and can share address records with other accounts. Contacts and accounts can share address records. Best times are stored for each address for each contact. Best times are also stored for each account.


Table 7. Affiliations and Best Times ERD Entities and Tables

Entity Table

Account Affiliation S_PARTY_PER

Address S_ADDR_PER

Address Usage S_CON_ADDR

Best Times (Account) S_BEST_CALL_HRS

Best Times (Account Affiliation) S_PARTY_PER_HRS

Best Times (Contact Address) S_CON_ADDR_HRS

Organization S_ORG_EXT, S_PARTY


Person Position S_POSTN_CON


Type S_PARTY_PER_DTL



Figure 8. Affiliations and Best Times

CONTACT

TYPE

ACCOUNT AFFILIATION

PERSON POSITION

BEST TIMES (ACCOUNT AFFILIATION)

BEST TIMES (ACCOUNT)

BEST TIMES (CONTACT ADDRESS)

POSITION

ORGANIZATION

ADDRESS USAGE

ADDRESS

composed offor

composed of

for

for

located at

for

located at

located at

for

of

defined by

composed of

for

belong to

having

located at

for

composed of

for

belong to

having

belong to

having



34

Agencies/AgentFigure 9 shows the Agencies/Agent ERD. This ERD illustrates how Siebel Financial Services supports generation of internal organization units (such as insurance agencies) that can use external organization units or agencies (such as insurance brokers) as well as individual agents to distribute their products. Each external organization unit agency or agent can be associated with details (such as licensing, appointments, commission contracts, and NASD registrations, and other selling agreements).


Table 8. Agencies/Agent ERD Entities and Tables

Entity Table

Agency Line of Business S_AGNC_LCNSLOB

Agent Line of Business S_AGENT_LCNSLOB

Agent Detail S_AGENT_DETAIL

Agency Detail S_AGENCY_DETAIL

Contact S_CONTACT, S_PARTY

Organization Unit S_ORG_EXT, S_PARTY

Product Line S_PROD_LN



Figure 9. Agencies/Agent

PRODUCT LINE

AGENT DETAIL

CONTACT

AGENT

AGENT LINE OF BUSINESS

ORGANIZATION UNIT

INTERNAL

ORGANIZATION UNIT

EXTERNAL ORGANIZATION UNIT

AGENCY

AGENCY DETAIL

AGENCY LINE OF

BUSINESS

works for

employsfor

has

based on

for based on

for

for

has

contracted by

deals with

for

subject of

contracted by

deals with

for

subject of



36

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


Table 9. Asset Management ERD Entities and Tables

Entity Table

Activity S_EVT_ACT

Activity Part Movement S_ACTPART_MVMT

Asset Contact Relationship S_ASSET_CON

Asset Employee Relationship S_ASSET_EMP

Asset External Organization S_ASSET_ACCNT

Asset Feature S_ASSET_FEA

Asset Modification S_ASSET_TXN

Asset Relationship S_ASSET_REL

Business Address S_ADDR_PER

Competitive Metric S_CMPT_MTRC

Competitive Product Feature S_CMPT_PROD_FEA



External Product S_PROD_EXT

Internal Product S_PROD_INT

Opportunity S_OPTY

Opportunity Asset S_OPTY_ASSET


Personal Address S_ADDR_PER

Product Instance (Asset) S_ASSET

Service Request S_SRV_REQ



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



38

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


Table 10. Auction ERD Entities and Tables

Entity Table

Asset S_ASSET

Auction Alert Definition S_AUC_ALRT_DEF

Auction Item S_AUC_ITEM

Auction Item Bid S_AUC_BID

Auction Item Promotion S_AUC_ITM_PROMO

Auction Item Watch S_AUC_WATCH

Auction Lister/Bidder Rating S_AUC_RATING

Catalog S_CTLG

Catalog Category S_CTLG_CAT

Catalog Category Item S_CTLG_CAT_PROD, S_CTLGCAT_ASSET, S_CTLG_CAT_AUC

Order S_ORDER

Order Item S_ORDER_ITEM

Party S_PARTY

Person S_CONTACT

Product S_PROD_INT

Triggered Auction Alert Item S_AUC_ALRT

User S_USER, S_CONTACT, S_PARTY



Figure 11. Auction

OR

DE

R

AU

CT

ION

LIS

TE

R/B

IDD

ER

R

AT

ING

TR

IGG

ER

ED

AU

CT

ION

ITE

M A

LER

T

OR

DE

R IT

EM

PA

RT

Y OT

HE

R P

AR

TY

PE

RS

ON

OT

HE

R P

ER

SO

NU

SE

R

CA

TA

LOG

PR

OD

UC

T

AS

SE

T

CA

TA

LOG

CA

TE

GO

RY

ITE

MC

AT

ALO

G C

AT

EG

OR

Y

AU

CT

ION

ITE

M W

AT

CH

AU

CT

ION

ITE

M

PR

OM

OT

ION

AU

CT

ION

ALE

RT

D

EF

INIT

ION

AU

CT

ION

ITE

M B

ID

AU

CT

ION

ITE

M

crea

ted

by

crea

tor

of

part

of

com

pose

d of

appl

icab

le to

subj

ect o

f

part

of

mad

e up

of

ratin

g of

subj

ect o

f

mad

e by

crea

tor

of

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

of

for

aler

ted

by

crea

ted

from

gene

sis

of

for

feat

ured

in

repr

esen

ted

by

disp

laye

d as

repr

esen

ted

by

disp

laye

d as

crea

ted

from

repr

esen

ted

as

acce

ssed

vi

a

owne

r of

for

owne

r of

pric

ing

mec

hani

sm

for

pric

ed b

y

pric

ing

mec

hani

smfo

r

pric

ed b

y

fulfi

llmen

t of fu

lfille

d as

for

subj

ect o

f



40

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


Table 11. Auto Email Response Generator ERD Entities and Tables

Entity Table

Activity S_EVT_ACT

Catalog S_CTLG


Category Usage Notification S_COMM_CTG_NTFY

Communication Template Usage Notification S_COMMTMPL_NTFY


Problem Resolution Document S_RESITEM

Template Communication Response S_DMND_CRTN_PRG



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



42

Automotive RetailFigure 13 shows the Automotive Retail ERD. This ERD illustrates the Automotive retail process at dealerships. Sales goals are defined for every sales representative as well as the dealership for a period (month, quarter, and so on.). These goals are for new and used vehicles or a fleet of vehicles. The sales process could comprise several steps and an opportunity to sell a vehicle may involve some of these sales steps. The sales steps taken by every sales representative are aggregated for the period to determine the effectiveness of each sales step.


Table 12. Automotive Retail ERD Entities and Tables

Entity Table

Activity S_EVT_ACT

Asset S_ASSET

Employee S_EMP_PER, S_CONTACT, S_USER

Employee Budget/Forecast S_AT_PER_FCST

Opportunity S_OPTY, S_OPTY_ATX

Opportunity Sales Step S_OPTY_SLS_STEP

Organization S_ORG_EXT, S_BU

Period S_PERIOD

Person S_CONTACT, S_CONTACT_ATX, S_CONTACT_BU

Sales Step S_SALES_STEP

Sales Step Goal S_FCST_SLS_STEP

Showroom Log Entry S_COMM_LOG

Store Budget/Forecast S_AT_ORG_FCST

Vehicle S_ASSET, S_ASSET_ATX



Figure 13. Automotive Retail

SA

LE

S S

TE

P

GO

AL

PO

SIT

ION

PE

RS

ON

OT

HE

R

PE

RS

ON

EM

PL

OY

EE

OP

PO

RT

UN

ITY

SA

LE

S S

TE

P

AS

SE

T

OT

HE

R A

SS

ET

VE

HIC

LE

AC

TIV

ITY

ST

OR

E B

UD

GE

T/F

OR

EC

AS

T

SH

OW

RO

OM

LO

G

EN

TR

Y

SA

LE

S S

TE

P

PE

RIO

D

OR

GA

NIZ

AT

ION

OT

HE

R

OR

GA

NIZ

AT

ION

DE

AL

ER

/PA

RT

NE

R

OP

PO

RT

UN

ITY

EM

PL

OY

EE

BU

DG

ET

/FO

RE

CA

ST

in c

ont

ext

of

subj

ect

of

inst

anc

e o

f

use

d by

of

has

ow

ner

of

ow

ned

by

resp

ons

ible

for

hand

led

by

on

invo

lve

r o

fha

s tr

ade

-in

of

tra

ded

in

for

sour

ce o

fof

for

for

subj

ect

of

of

use

d in

ow

ner

of

ass

igne

d to

pre

sent

ed

in

pre

sent

ed

visi

ble

to

visi

bilit

y o

f

of

has

for

in

set

by

set

defin

ed

for

subj

ect

of

defin

ed

for

subj

ect

of

ass

igne

d to

ow

ner

of

subm

itte

d by

subm

itte

r o

f

resp

ons

ible

fo

r

resp

ons

ibili

ty o

f

for

set

up



44

Benefit Case ManagementThis ERD (shown in Figure 14) illustrates how Benefit Case Management supports benefits determination and case-information verification, specifically:

■ Eligibility Determination. Provides the capability to develop benefits plans that allow caseworkers to make eligibility changes in program rules that impact benefit disbursement while reducing the number of overpayments. The feature provides the ability to submit individual or household profiles to a rules engine for eligibility determination.

The ERD shows that a Benefit Plan consists of Benefit Plan Items associated to Recipient and provided by a Provider. A Benefit Plan belongs to a Case and a Case may have a Change of Circumstance which may or may not be associated to a Benefit Plan.

■ Supporting Tasks. Helps a caseworker verify information during the intake process, where the caseworker uses the Public Sector application to document that the information was verified, how verification was accomplished and who verified the information. The caseworker performing quality assurance is presented with cases based upon random selection, queued, or high-risk profiles. The feature is also useful when a quality assurance worker reviews selected cases by following a template which provides a list of items that must be checked off to ensure uniformity in the review process.

As the ERD shows, a Case Verification Template is associated to a Case and may consist of one or more Case Verification Items. The Case Verification Template Items may be associated to a submitter and a verifier. This feature can also help a quality-assurance worker review cases following a checklist for adherence to standards and ensuring that each case in reviewed in the same way.

Table 13 lists the entities in this ERD and their corresponding tables

Table 13. Benefit Case Management ERD Entities and Tables

Entity Table

Account S_PARTY, S_ORG_EXT

Activity S_EVT_ACT

Admin Verification Template S_TMPL_PLANITEM

Admin Verification Template Item S_ASSESS_ATTRIB

Benefit Plan S_CASE_BNFTPLAN

Benefit Plan Item S_BNFT_PLAN_ITM

Benefit Plan Item Payment S_BNFPLNITM_PAY

Case S_CASE

Case Verification Item S_ASSESS_ATTRIB

Case Verification Template S_TMPL_PLANITEM

Change of Circumstance S_CASE_CHGOFCCM

Contact S_PARTY, S_CONTACT

Quality Assurance Items S_ASSESS_ATTRIB



Quality Assurance Template S_TMPL_PLANITEM

User S_PARTY, S_CONTACT, S_USER

Table 13. Benefit Case Management ERD Entities and Tables

Entity Table



46

Figure 14. Benefit Case Management

Title

: P

S B

enefit C

ase M

anagem

ent

Auth

or

: O

racle

, C

onfidential

QU

AL

ITY

A

SS

UR

AN

CE

IT

EM

S

QU

AL

ITY

A

SS

UR

AN

CE

T

EM

PL

AT

E

US

ER

CA

SE

V

ER

IFIC

AT

ION

IT

EM

CA

SE

V

ER

IFIC

AT

ION

T

EM

PL

AT

E

AC

TIV

ITY

PA

RT

Y

CO

NT

AC

T

AC

CO

UN

T

BE

NE

FIT

PL

AN

ITE

M

PA

YM

EN

T

BE

NE

FIT

PL

AN

IT

EM

CH

AN

GE

OF

C

IRC

UM

ST

AN

CE

BE

NE

FIT

PL

AN

CA

SE

su

bm

itte

d b

y

su

bm

itte

r o

f

co

mp

lete

d b

y

co

mp

lete

r o

f

su

bm

itte

d b

y

su

bm

itte

r o

f

for

ha

s

for

ha

s

for

ha

s

be

lon

gs t

o

ha

s

for

ha

s

ve

rifie

d b

y

ve

rifie

r o

f

for

ha

s

for

ha

s

for

ha

s

rece

ive

d b

y

recip

ien

t o

f

pro

vid

ed

by

pro

vid

er

of

pa

ym

en

t fo

r

ha

s

for

ha

s



BrickFigure 15 shows the Brick ERD. This ERD illustrates how region (brick and mini brick) is used in Siebel Life Sciences. Area can be associated with multiple positions. Area is defined at the address level for organizations and at the contact level. Area is tracked for activities. Syndicated data is also available at the area level.


Table 14. Brick ERD Entities and Tables

Entity Table

Activity S_EVT_ACT

Account Address S_CON_ADDR

Address S_ADDR_PER



Position S_POSTN

Region S_REGION

Syndicated Data S_SYND_DATA



48

Figure 15. Brick

PO

SIT

ION

AC

CO

UN

T A

DD

RE

SS

CO

NT

AC

TA

CT

IVIT

Y

OR

GA

NIZ

AT

ION

AD

DR

ES

S

SY

ND

ICA

TE

D D

AT

A

RE

GIO

N

BR

ICK

OT

HE

R R

EG

ION

hold

ers

of

held

by

ass

igne

d to

loca

ted

atfo

r

assi

gned

to

defin

ed b

y

for

pare

nt o

f

child

of

pare

nt o

f

child

of

for

loca

ted

at

for

subj

ect o

f

for

sour

ce o

f



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

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


Table 15. CG Promotion Planning ERD Entities and Tables

Entity Table


Authorized Product S_ORG_PROD

Fund Allocation S_MDF_ALLOC

Marketing Development Fund S_MDF

Marketing Event or Activity S_SRC

MDF Accrual S_MDF_ACCRUAL

Payment S_SRC_PAYMENT

Period S_PERIOD




Price List Item S_PRI_LST_ITEM

Product Internal S_PROD_INT


Product Structure S_PROD_REL or S_PROD_ITEM

Promotion Plan S_SRC

Promotion S_SRC

Promotion Account S_SRC



50

Promotion Product S_SRC

Promotion Category S_SRC

Promotion Account Product S_SRC

Table 15. CG Promotion Planning ERD Entities and Tables

Entity Table



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

��

�

��

��

�



52

Clinical Study ManagementFigure 17 shows the Clinical Study Management ERD. This ERD illustrates how clinical trials are managed. Each clinical trial starts with a protocol for a specific compound (product). Each protocol is conducted by sites and managed by site personnel. A protocol can have many versions and multiple protocols can roll up to a single program. Protocols can also roll up to regions. Subjects are screened and enrolled at protocol sites for specific protocol versions. Protocol sites are paid, based on the activities they complete. Visits and activities are generated for subjects based on templates defined for the protocol. The Clinical Research Associates perform site initiation activities for protocol sites and submit periodic trip reports. A protocol can also be associated with one or more projects. For a complete layout of projects, refer to “Professional Services” on page 197.


Table 16. Clinical Study Management ERD Entities and Tables

Entity Table


Activity S_EVT_ACT

Address S_ADDR_PER

Affiliation S_PTCL_ST_CON_LS

Application S_CL_PGM_APP_LS

Clinical Payment S_SRC_PAYMENT


Design S_CL_DSGN_LS

Position S_POSTN

Product S_PROD_INT

Program S_CL_PGM_LS

Project S_PROJ

Project Subcontractor S_PROG_ORG

Project Subcontractor Contact S_PROJ_ORG_CON

Protocol S_CL_PTCL_LS

Protocol Site S_PTCL_SITE_LS

Subject S_CL_SUBJ_LS

Subject Status S_CL_SUBJ_ST_LS

Subject Template S_SUBJ_TMPL_LS

Template Version S_SBJTMP_VER_LS

Template Visit S_TMPL_PLANITEM



Trip Report S_EVT_ACT

Visit S_EVT_ACT

Table 16. Clinical Study Management ERD Entities and Tables

Entity Table



54

Figure 17. Clinical Study Management

Title

: C

linic

al S

tud

y M

an

ag

em

en

tA

uth

or

: O

racle

, C

on

fid

en

tia

l PR

OJE

CT

S

UB

CO

NT

RA

CT

OR

PR

OJE

CT

S

UB

CO

NT

AC

TO

RC

ON

TA

CT

PR

OJE

CT

AC

CO

UN

T

CO

NT

AC

T

AP

PL

ICA

TIO

N

AF

FIL

IAT

ION

AD

DR

ES

S

SU

BJE

CT

S

TA

TU

S

TE

MP

LA

TE

VE

RS

ION

PR

OD

UC

T

DE

SIG

N

SU

BJE

CT

T

EM

PL

AT

E

TE

MP

LA

TE

V

ISIT

SU

BJE

CTC

LIN

ICA

L

PA

YM

EN

T

AC

TIV

ITY

TR

IP

RE

PO

RT

VIS

IT

PO

SIT

ION

PR

OG

RA

M

PR

OT

OC

OL

RE

GIO

N

PR

OT

OC

OL

SIT

E

de

fin

ed

su

bje

ct

of

use

d b

y

usin

g

ap

plie

dto

ha

vin

g

be

lon

g t

o

a p

art

ne

r fo

r

su

bco

ntr

acto

r fo

r

su

bco

ntr

acte

d t

o

co

mp

ose

d o

f

for

co

nta

ct

for

ha

vin

g

be

lon

gs t

o

co

nsis

ts o

f

for

ha

vin

g

ha

vin

g

asso

cia

ted

to

ha

vin

gstu

dy c

on

du

cte

d b

y

for

aff

ilia

ted

to

for

loca

ted

at

for

prim

ary

in

ve

stig

ato

rh

avin

g

for

ha

vin

g

ha

vin

g

co

mp

ose

d o

f

for

asso

cia

ted

with

ma

de

fo

r

su

bje

ct

of

ma

de

by

invo

lve

d in

so

urc

e o

f

co

mp

ose

d o

f

for

so

urc

e o

f

pa

rtic

ipa

nt

at

for

recip

ien

t o

f

pa

id t

o

co

mp

ose

d o

ffo

r

tea

m c

om

po

se

d o

f

tea

m m

em

be

rs o

f

tea

m m

em

be

rs o

f

ha

vin

g t

ea

m o

f

for p

art

icip

atin

g in

pa

rtic

ipa

nt

of

co

nd

ucte

d a

t

ge

ne

rato

r o

fg

en

era

ted

by

for

asso

cia

ted

with

ha

vin

g

use

d b

y

for

co

nsis

tin

g o

f



Communications, Media, and Energy AccountFigure 18 shows the Communications, Media, and Energy (CME) Account ERD. This ERD illustrates how complex hierarchies of accounts are maintained in Siebel Communications and Siebel Energy. Profiles are the way an account is further described. Addresses are associated with contacts and accounts. Addresses are unique in the database. Trouble tickets (service requests) and activities can be associated at the accounts level.


Table 17. CME Account ERD Entities and Tables

Entity Table

Account S_ORG_EXT

Activity S_EVT_ACT

Address S_ADDR_PER

Billing Profile S_INV_PROF


Exemption Profile S_SUBSIDY

Financial Profile S_FINAN_PROF

Trouble Ticket S_SRV_REQ



56

Figure 18. Communications, Media, and Energy Account

BILLING PROFILE

STATEMENT

INVOICE

EXEMPTION PROFILE

FINANCIAL PROFILE

ACCOUNT

CUSTOMER ACCT

PREMISE ACCT

BILLING ACCT

SERVICE ACCT

ACTIVITY

TROUBLE TICKET

CONTACT

ADDRESSPREMISE

SERVICE ADDR

located at

for

child of

parent of

for associated with

located at

for

fordescribed by

mailed to

for for

associated with

associated with

for

has

associated with

associated with

tracked by

for problems with

tracked by

for

described by

described byfor

part of

made up of



CME AgreementFigure 19 shows the CME Agreement ERD. This ERD illustrates how an agreement is managed in Siebel Business applications. An agreement can be associated with many accounts. An agreement has terms and entitlements associated with it. An agreement covers service instances and products through the account with which it is associated.


Table 18. CME Agreement ERD Entities and Tables

Entity Table

Accounts S_ORG_EXT, S_PARTY

Agreement S_DOC_AGREE

Agreement Note S_NOTE_AGR_CUT

Agreement Terms S_AGREE_TERMS

Event Activity S_EVT_ACT

Parameter S_QUOTE_ITEM_XA

Quote S_DOC_QUOTE

Quote Item S_QUOTE_ITEM

Solution Set S_QUOTE_ITEM



58

Figure 19. CME Agreement

Title

: C

ME

AG

RE

EM

EN

TS

Auth

or

: O

racl

e.

Confidential

QU

OT

E IT

EM

QU

OT

E

EV

EN

T A

CT

IVIT

YA

GR

EE

ME

NT

N

OT

E

AG

RE

EM

EN

T

TE

RM

S

AG

RE

EM

EN

T

AC

CO

UN

TS

be

lon

gs t

o

ha

s

ch

ild o

f

pa

ren

t o

f

ha

s a

asso

cia

ted

with

co

nsis

ts o

f

pa

rt o

f

asso

cia

ted

with

tra

cke

d

by

asso

cia

ted

w

ith

for

for

su

bje

ct

of

ch

ild o

f

pa

ren

t o

f

bo

un

d b

y

go

ve

rns



CME AlertFigure 20 shows the CME Alert ERD. This ERD illustrates how the alerts (credit and fraud) are managed. A fraud alert is associated with an account. Profile attributes provide more information about the fraud threshold for an account. A credit alert is related to an account and a statement. Activities can be performed on both these alerts.


Table 19. CME Alert ERD Entities and Tables

Entity Table


Activity S_EVT_ACT

Alert Attachment S_ALERT_ATT_CUT

Alerts S_ALERT_CUT

Asset S_ASSET

Bill Transactions S_BILL_MAINT

Energy Consumption S_USAGE

Fraud Profile S_FRD_PROF_CUT



60

Figure 20. CME Alert

Title

: C

ME

Ale

rtA

uth

or

: O

racle

, C

onfidential

AC

TIV

ITY

AS

SE

T ME

TE

R

EQ

UIP

ME

NT

OT

HE

R

EN

ER

GY

CO

NS

UM

PT

ION

US

AG

E

BIL

L

AC

CO

UN

T

ALE

RT

AT

TA

CH

ME

NT

INV

OIC

E L

INE

IT

EM

S

ALE

RT

FR

AU

D P

RO

FIL

E

pa

rt o

f

ma

de

up

of

for

descri

bed b

y

subje

ct

for

for c

onsis

ts

subje

ct of

on

for

attached to

genera

tes

for

for

associa

ted w

ith

for

attached to

genera

ted b

y

has

child o

fpare

nt of

child o

f

pare

nt of



CME Energy Products, Service, and UsageFigure 21 shows the CME Energy Products, Service and Usage ERD. This ERD illustrates how products and services in use, inactive, or planned are associated with, tracked, and maintained by account. Assets are instances of internal products with the Siebel products catalog and can represent equipment, services designated by the administrator. Services are represented as assets that consist of specific commodities or energy service with corresponding rates or prices (for example, commercial electric service with rate CE5). Each of these services can be further associated with one or multiple meters. After a service has been established as an asset with corresponding rate and meter detail, the utility consumption is recorded for each period, and an invoice is generated.


Table 20. CME Energy Products, Service, and Usage ERD Entities and Tables

Entity Table


Address S_ADDR_PER

Asset S_ASSET

External Product Presence S_ORG_PRDEXT

Invoice S_INVOICE

Invoice Adjustment S_INVOICE_ADJ

Invoice Item S_INVOICE_ITEM


Period S_PERIOD

Product: External S_PROD_EXT

Product: Internal S_PROD_INT

Service Instance S_ASSET

Usage S_USAGE



62

Figure 21. CME Energy Products, Service, and Usage

Title

: C

ME

Energ

y P

roducts

, S

erv

ices,

and U

sage

Auth

or

: O

racle

, C

onfidential

US

AG

EIN

VO

ICE

AD

JU

ST

ME

NT

PA

YM

EN

T

INV

OIC

E IT

EM

INV

OIC

E

SE

RV

ICE

IN

ST

AN

CE

PR

OD

UC

T

EX

TE

RN

AL P

RO

DU

CT

INT

ER

NA

L P

RO

DU

CT

AC

CO

UN

T

BIL

LIN

GC

US

TO

ME

RS

ER

VIC

E

PE

RIO

D

AS

SE

T

ME

TE

R

OT

HE

R

EQ

UIP

ME

NT

EX

TE

RN

AL P

RO

DU

CT

P

RE

SE

NC

E

for

subje

ct

of

associa

ted

with

for

for

record

ed

in

for

record

ed

in

record

ed

for

dis

pla

yer

of

used

by

consum

er

of

for

subje

ct

of

for

subje

ct

of

line ite

m o

f

made

of

subje

ct

of

for

made b

y

responsib

le f

or

serv

ice

at

of

made u

p o

f

is a

is m

ade into

of

subje

ct

of

at

subje

ct

of



CME Order ManagementFigure 22 shows the CME Order Management ERD. This ERD illustrates order management. Companies provide products and services to their customers over an extended period of time. Quotes and orders are used to capture the changes to a customer's installed services. The cycle starts when a customer requests the initial installation of a product or service in the form of a quote. The quote is converted to an order and that order is provisioned. At that time, the products and services described in the order are converted into assets associated with the customer's account. Subsequent changes to the configuration, disconnect instructions, or additions to the installed assets are captured in further quotes and orders.


Table 21. CME Order Management ERD Entities and Tables

Entity Table


Asset S_ASSET

Asset Attribute S_ASSET_XA

Order S_ORDER


Order Item Attribute S_ORDER_ITEM_XA

Product or Service S_PROD_INT

Quote S_DOC_QUOTE


Quote Item Attribute S_QUOTE_ITEM_XA



64

Figure 22. CME Order Management

Titl

e : C

ME

Ord

er M

anag

emen

tA

utho

r : O

racl

e, C

onfid

entia

l

AC

CO

UN

T

OT

HE

R

AC

CO

UN

T

SE

RV

ICE

AC

CO

UN

T

BIL

LIN

G A

CC

OU

NT

QU

OT

EO

RD

ER

QU

OT

E IT

EM

OR

DE

R IT

EM

AS

SE

T

OR

DE

R IT

EM

AT

TR

IBU

TE

AS

SE

T A

TT

RIB

UT

EQ

UO

TE

ITE

M A

TT

RIB

UT

E

PR

OD

UC

T O

R S

ER

VIC

E

an in

stan

ce o

f

mad

e in

to

part

of

com

pose

d of

part

of

com

pose

d of

serv

iced

by

asso

ciat

ed w

ith

serv

iced

by

asso

ciat

ed w

ith

bille

d by

asso

ciat

ed w

ith

crea

ted

from

lead

s to

for

com

pose

d of

for

com

pose

d of

ofsu

bjec

t of

of

quot

ed fo

r pu

rcha

se o

n

for

subj

ect o

f

of

subj

ect o

f

subj

ect o

f

orde

red

on

for

prov

isio

n of

subj

ect o

f

ofsu

bjec

t of

inst

ance

of

subj

ect o

fin

stan

ce o

f

subj

ect o

f

bille

d by

asso

ciat

ed w

ith



Commercial Banking Figure 23 shows the Commercial Banking ERD. This ERD illustrates how Siebel Financial Services supports generation of a commercial loan (or facility) application by portfolio type. Each application is associated with many organizations as borrowers or lenders. The application tracks the collateral, policies, prices of a facility, and documents used in the application process, for example, trailing documents and attachments. An application has to undergo several stages of approvals before it is finally approved to become a financial account.


Table 22. Commercial Banking ERD Entities and Tables

Entity Table

Activity S_EVT_ACT

Approval S_FN_APPR

Attachment S_OPTY_ATT

Borrower S_OPTY_ORG

Collateral S_FN_OFFR_COLT

Correspondence S_EVT_FUL_REQ


Exception S_OPTY_ORG_FNXM

Facility S_REVN

Facility Detail S_OPTY_PROD_FNXM

Facility Organization S_OPTYPRD_ORG

Fee S_FN_OFFR_FEE

Financial Account S_ASSET

Note S_NOTE_OPTY

Opportunity S_OPTY

Opportunity Detail S_OPTY_DTL



Portfolio Type S_MKT_SEG

Product S_PROD_INT

Rating S_OPTY_ORG_FNXM

Revenue S_REVN

Revenue S_REVN



66

Trailing Document S_OPTY_DOC

Underwriting Standard S_MKT_SEG_VAL

Table 22. Commercial Banking ERD Entities and Tables

Entity Table



Figure 23. Commercial Banking

Title

: C

om

me

rcia

l B

an

kin

g

Au

tho

r :

Ora

cle

, C

on

fid

en

tia

l

AC

TIV

ITY

FA

CIL

ITY

OR

GA

NIZ

AT

ION

SY

ND

ICA

TE

GU

AR

AN

TO

R

OR

GA

NIZ

AT

ION

RA

TIN

GE

XC

EP

TIO

N

TR

AIL

ING

D

OC

UM

EN

T

CO

RR

ES

PO

ND

EN

CE

AT

TA

CH

ME

NT

NO

TE

FA

CIL

ITY

UN

DE

RW

RIT

ING

ST

AN

DA

RD

BO

RR

OW

ER

EM

PLO

YE

E

OP

PO

RT

UN

ITY

DE

TA

IL

RE

QU

ES

T P

OLIC

Y

EX

CE

PT

ION

DE

CIS

ION

KE

Y C

RE

DIT

IS

SU

ES

UN

DE

RW

RIT

ING

S

TA

ND

AR

D

AP

PR

OV

AL

AP

PR

OV

AL

LE

VE

L

AP

PR

OV

AL

ST

AG

E

OP

PO

RT

UN

ITY

PO

RT

FO

LIO

TY

PE

FE

E

CO

LL

AT

ER

AL

PR

OD

UC

T

FA

CIL

ITY

DE

TA

IL

PR

ICE

PO

LIC

Y

CO

VE

NA

NT

FIN

AN

CIA

L A

CC

OU

NT

gen

era

tes

gen

era

ted b

y

for

gen

era

tes

repre

sen

ted b

y

part

icip

ate

d a

s

part

icip

ate

d in

su

bje

ct

ofb

ased

on

associa

ted

with

repre

sen

ted b

y

applie

d a

s

a r

eport

to

a p

are

nt

to

ow

ner

of

ow

ned b

y

for

has

for

su

bje

ct

of

for

su

bje

ct

to

of

su

bje

ct

of

of

has

of

su

bje

ct

of

of

su

bje

ct

of

of

has

for s

ubje

ct

of

for

su

bje

ct

of

part

of

inclu

des

issu

ed b

y

issu

es o

f

for

has

su

bje

ct

to

need f

or

belo

ngs t

o

for

of

has

part

of

made u

p o

f

su

bje

ct

to

requ

ired b

y

has

associa

ted

with

part

of

made u

p



68

Commercial Insurance Figure 24 shows the Commercial Insurance ERD. This ERD illustrates how Siebel Financial Services supports generation of group classes of insured items covered by an insurance policy. An insured item can belong to either one or two group classes, including a region (such as a state), a location, (such as physical location), or a class (such as an employee). Insurance coverage can be associated with either one or two group classes.


Table 23. Commercial Insurance ERD Entities and Tables

Entity Table

Asset S_ASSET

Contact S_CONTACT,S_PARTY

Group Class S_FN_GRP_CLASS

Insurance Coverage S_APPLD_CVRG

Insured Item S_INS_ITEM

Policy Contact S_ASSET_CON



Figure 24. Commercial Insurance

Title : Commercial InsuranceAuthor :Oracle, Confidential

INSURANCE COVERAGE

INSURED ITEM

ASSET

INSURANCE POLICY

GROUP CLASS

REGIONCLASS LOCATION

POLICY CONTACT

CONTACT

belongs to

covers

covers

covered by

part of

madeup of

insured as

for

associated with

subject of

part of

covers

for

subject of

of

subject of

for

associatedwith



70

Community/Chat Discussion Figure 25 shows the Community/Chat Discussion ERD. This ERD illustrates how topics can be created for chat or discussion purposes for a disease state (market product). Users can register to chat for a particular topic or they can post messages to the discussion.


Table 24. Community Chat/Discussion ERD Entities and Tables

Entity Table


Discussion Post S_MESG_BRD_LS

Product S_PROD_INT

Registration S_TOPIC_CON_LS

Topic S_TOPIC_LS



Figure 25. Community/Chat Discussion

Title : Community Chat/DiscussionAuthor : Oracle, Confidential

PRODUCTDISCUSSION POST

TOPIC

REGISTRATIONCONTACT

of

registered for

for

registration of

about

subject of

involving

posted to

for

subject of

authored by

author of



72

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


Table 25. Compensation Planning Administration ERD Entities and Tables

Entity Table

Business Unit S_BU

Compensation Budget Definition S_CP_BDGT

Compensation Budget Item S_CP_BDGT_ITEM

Compensation Budget Item For Employee S_CP_BDGT_EMP

Compensation Cycle Planning Period S_CP_PD_BDGTITM

Compensation Guideline Definition S_CP_GDLN

Compensation Guideline Factor LOV

Compensation Guideline Set S_CP_GDLN_SET

Compensation Guideline Table S_CP_GDLN_TBL

Compensation Planning Period S_CP_PERIOD

Compensation Region S_CP_REGN

Compensation Type LOV

Compensation Valid Effectivity Date S_CP_EFF_DATE

Employee Eligibility S_APP_QUERY (PDQ)

Employee/Agent S_EMP_PER

Job Category LOV

Job Code S_JOB

Job Family S_JOB_FAMILY

Job Profile S_JOB_PRFL

Period S_PERIOD

Salary Grade S_SALARY_GRADE, S_SALPLAN_GRADE

Salary Plan S_SALARY_PLAN



Figure 26. Compensation Planning Administration

Title

: C

om

pen

sation

Pla

nn

ing

Ad

min

istr

ation

Au

thor

: O

racle

, C

on

fid

en

tial

PO

SIT

ION

SA

LA

RY

PLA

N F

OR

S

ALA

RY

GR

AD

E

JO

B

FA

MIL

Y

JO

B

CA

TE

GO

RY

CO

MP

EN

SA

TIO

N

RE

GIO

N

JO

B C

OD

E

CO

MP

EN

SA

TIO

N G

UID

ELIN

E

DE

FIN

ITIO

N

CO

MP

EN

SA

TIO

N T

YP

E

SA

LA

RY

PLA

N

BU

SIN

ES

S U

NIT

PE

RIO

DQ

UA

RT

ER

LY

PE

RIO

D

AN

NU

AL P

ER

IOD

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

PLA

NN

ING

PE

RIO

D

CO

MP

EN

SA

TIO

N P

LA

NN

ING

PE

RIO

D

EM

PLO

YE

E / A

GE

NT

CO

MP

EN

SA

TIO

N B

UD

GE

T

ITE

M F

OR

EM

PLO

YE

E

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

ELIN

E T

AB

LE

CO

MP

EN

SA

TIO

N

GU

IDE

LIN

E S

ET

SA

LA

RY

GR

AD

E

support

manage b

y

sala

ry p

lan

gra

de d

efined

in for

sala

ry p

lan f

or

defined in

sala

ry g

rades f

or

have

defined f

or

used b

yperiod f

or

have

part

of

gro

upin

g f

or

cate

gorized

in

cate

gory

for

have

defined f

or

has

job c

ode f

or

locate

d in

com

pensation location f

or

sala

ry

gra

de

defined

in

for

sala

ry

defined

in

for

defined

for

com

ponent of

type o

f

type f

or

valu

es f

or

have 2

facto

r defined

in

used in

1 f

acto

r defined

in

used in

type o

f

type f

or

constr

ain

ed b

y

defined f

or

budget fo

rhave

em

plo

yed b

y

em

plo

yer

of

sub-o

rg o

f com

posed o

f

defined f

or

used in

defined f

or

used in

valid

date

for

have

defined f

or

user

of

defined f

or

used b

ysubje

ct of

conta

iner

for

allo

cate

d f

or

has

budget allo

cation f

or

has

constr

ain

ed b

y

defined f

or

subje

ct of

conta

iner

for

defined

for

com

ponent of

subje

ct of

conta

iner

for



74

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


Table 26. Compensation Planning Execution ERD Entities and Tables

Entity Table

Business Unit S_BU

Compensation Budget Definition S_CP_BDGT

Compensation Budget Item S_CP_BDGT_ITEM

Compensation Budget Item For Employee S_CP_BDGT_EMP

Compensation Cycle Planning Period S_CP_PD_BDGTITM

Compensation Guideline Definition S_CP_GDLN

Compensation Guideline Set S_CP_GDLN_SET

Compensation Guideline Table S_CP_GDLN_TBL

Compensation Plan S_CP_PLAN

Compensation Plan Comments S_NOTE_CP_PLAN

Compensation Plan For Employee S_CP_PLAN_EMP

Compensation Plan Item Detail S_CP_PLNITM_DTL

Compensation Plan Item For Employee S_CP_PLAN_ITEM

Compensation Plan Total S_CP_PLNITM_TOT

Compensation Planning Period S_CP_PERIOD

Compensation Type LOV

Compensation Valid Effectivity Date S_CP_EFF_DATE

Plan Approval S_CP_APPROVAL

Proxy Access To Plan S_USER_PROXY



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

��

� ��

��

� �

��

��

��

��



76

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


Table 27. Competency Management System ERD Entities and Tables

Entity Table

Career Path S_JOB_PRFL_TRNS

Competency, Competency Category, Root Competency 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



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

��

��

�



78

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


Table 28. Content Management ERD Entities and Tables

Entity Table

Content Item Type S_CONTENT_TYPE

Content Object S_CONTENT_OBJ

Content Project S_CONTENT_PROJ

Content Project Item S_CONTENT_ITEM

Literature S_LIT



Product S_PROD_INT



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



80

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


Table 29. Contract Conditions ERD Entities and Tables

Entity Table


Benefit S_AGREE_BNFT

Category S_CTLG_CAT

Condition S_AGREE_COND

Condition Compliance S_AGR_COND_CMPL

Contract S_DOC_AGREE

Entitlement S_ENTLMNT

Entitlement Template S_ENTL_TMPL

Object Class S_VOD, S_VOD_VER

Product S_PROD_INT


Template Benefit S_ENTL_BNFTTMPL

Template Condition S_ENTL_CONDTMPL

Template Term S_AGR_TERM_TMPL

Term S_AGR_TERM_DESC



Figure 30. Contract Conditions

Title

: C

ontr

act

Lifecycle

Managem

ent

Auth

or

: O

racl

e,

Confidential

CO

NT

RA

CT

CO

ND

ITIO

N

OB

JE

CT

CA

TE

GO

RY

OB

JE

CT

CLA

SS

PR

OD

UC

T

PR

OD

UC

T L

INE

CO

NT

RA

CT

AG

RE

EM

EN

TO

TH

ER

CO

NT

RA

CT

TE

RM

TE

MP

LA

TE

TE

RM

#

TE

RM

_N

UM

TE

MP

LA

TE

CO

ND

ITIO

N#

SE

Q_N

UM

TE

MP

LA

TE

BE

NE

FIT

#

SE

Q_N

UM

CO

ND

ITIO

N C

OM

PLIA

NC

E#

CO

MP

L_N

UM

CO

ND

ITIO

N

#

SE

Q_N

UM

BE

NE

FIT

#

SE

Q_N

UM

EN

TIT

LE

ME

NT

TE

MP

LA

TE

#

NA

ME

EN

TIT

LE

ME

NT

#

NA

ME

in r

efe

ren

ce t

osu

bje

ct

of

in r

efe

ren

ce t

o

su

bje

ct

of

in r

efe

ren

ce t

o

su

bje

ct

of

in r

efe

ren

ce t

o

su

bje

ct

of

in c

on

text

of

com

posed o

f

based o

n

used b

y

based o

n

used b

y

belo

ng t

o

com

posed o

f

corr

espon

d t

o

used b

y

applic

able

to

com

pri

se

applic

able

to

com

pri

se

in r

efe

ren

ce t

o

su

bje

ct

of

applic

able

to

govern

ed b

y

applic

able

to

govern

ed b

y

applic

able

to

su

bje

ct

of

applic

able

to

su

bje

ct

of

based o

n

used in

depen

den

t u

pon

com

pri

se

in r

efe

ren

ce t

o su

bje

ct

of

in r

efe

ren

ce t

o

basis

for



82

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


Table 30. Contracts ERD Entities and Tables

Entity Table


Asset S_ASSET


Contract S_DOC_AGREE, S_DOC_QUOTE, S_ORDER

Contract Line Item S_AGREE_ITEM, S_QUOTE_ITEM, S_ORDER_ITEM

Internal Product or Service S_PROD_INT







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



84

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

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


Table 31. Data Visibility ERD Entities and Tables

Entity Table

Access Group S_PARTY

Account S_ORG_EXT

Activity S_EVT_ACT



Catalog S_CTLG

Category S_CTLG_CAT

Dynamic Account Hierarchy S_DYN_HRCHY

Dynamic Account Hierarchy Node S_DYN_HRCHY_REL


Group S_PARTY

Internal/Partner Organization Unit S_ORG_EXT

Literature Item S_LIT

Opportunity S_OPTY



Order S_ORDER


Party S_PARTY



Product S_PROD_INT

Quote S_DOC_QUOTE


Table 31. Data Visibility ERD Entities and Tables

Entity Table



86

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

��

��

��

��

�� @��



Dealer Sales and Service PromotionThis ERD (shown in Figure 33) illustrates how a call list may be created by searching on specific attributes of vehicle, person, sales history, or service history. A person may qualify to be on the call list by virtue of possessing a specific vehicle, having the car serviced with the dealership in the past (the next service may be due), and so on. The dealer may launch a campaign for sales or service specials and include one or more call lists to be targeted through the campaign.


Table 32. Dealer Sales and Service Promotion ERD Entities and Tables

Entity Table

Call List S_CALL_LST

Call List Contact S_CALL_LST_CON

Call List Contact Vehicle S_C_LST_CON_AST

Campaign S_SRC

Campaign Call List S_CAMP_CALL_LST

Campaign Contact S_CAMP_CON

Campaign Contact Vehicle S_CAMP_CON_AST


Person S_CONTACT, S_CONTACT_ATX




88

Figure 33. Dealer Sales and Service Promotion

Title : eDealer Sales and Service Promotion

Author : Oracle, Confidential

CAMPIAGN CONTACT VEHICLE

CAMPAIGN CONTACT

VEHICLE

PERSON

MARKETING EVENT OR ACTIVITY

OTHER EVENT CAMPAIGN

CAMPAIGN CALL LIST

CALL LIST

CALL LIST CONTACT VEHICLE

CALL LIST CONTACT

in context of

subject of

target of

target

in context of

subject of

in context of

subject of

belong to

subject of

for

subject of

for

subject of

belong to

owner of in context of

subject ofowner of

belong to

source of

created from



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


Table 33. Document ID and Tax ID ERD Entities and Tables

Entity Table



Document Mask Component S_DOC_NUM_SEG

Document Types S_DOC_NUM

Document Values S_DOC_NUM_VAL

Invoice S_INVOICE

Order S_ORDER






90

Figure 34. Document ID and Tax ID

Title : Document ID and Tax IDAuthor : Oracle, Confidential

ORDER ITEM

AUTHORIZED PRODUCTPRICE LIST

ITEM

PRICE LIST

ACCOUNT

ORDER

INVOICE

DOCUMENT MASKCOMPONENTS

EMPLOYEE

DOCUMENT TYPES

DOCUMENT VALUES

have

exists for

have

exists for

for

composed of

belongs

have

for

composed of

have

exists for

have

exists for

contains

for

contains

for

have

exists for

exists for

have

have

exists for



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


Table 34. Dun & Bradstreet Integration ERD Entities and Tables

Entity Table


Call List D & B Organization S_DNB_ORG_LST

D & B Contact Responsibility S_DNB_CON_MRC

D & B Management Responsibility Type S_DNB_MRC

D & B Organization S_DNB_ORG

D & B Organization Industry Classification S_DNB_ORG_SIC

D & B Standard Industry Classification S_DNB_SIC

Industry S_INDUST

Organization Industry Classification S_ORG_INDUST


Prospect S_PRSP_CONTACT



92

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



Employee KPIThis ERD (shown in Figure 36) illustrates that Key Performance Indicators (KPI) can be defined and associated with the objectives of an employee so that the employee and the manager of the employee manager can measure achievement or current values against the goals set in the objectives of the employee.


Table 35. Employee KPI ERD Entities and Tables

Entity Table

BUSINESS UNIT S_BU

EMPLOYEE PERFORMANCE 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



94

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



Event Tax AdministrationThis ERD (shown in Figure 37) illustrates how the Siebel Hospitality application supports tax and service charge calculation for invoices. An event is hosted at a property such as a hotel or convention center. Event functions and associated subfunctions are conducted in rooms at the property. A team of events managers and operations staff at the property work together to plan and execute the event. The event functions use assets that are specific instances of products at each property. Each product is associated with a category and subcategory. Both categories and subcategories are associated with charge codes. Each charge code is composed of taxes and service charges, which may be taxable. The taxes and service charges linked with the charge code apply to the product.


Table 36. Event Tax Administration ERD Entities and Tables

Entity Table

Asset S_ASSET

Category S_CTLG_CAT

Charge Code S_EVT_CHRG_LST

Event/Function S_SRC

Event Location Room S_EVTLOC_ROOM

Position S_POSTN


Price List Item S_PRI_LST_ITM

Product S_PROD_INT

Property S_ORG_EXT, S_PARTY

Tax Code/Service Code S_PRI_LST

Team Member S_USER, S_PARTY



96

Figure 37. Event Tax Administration

Title : Event- Tax Administration Author : Oracle, Confidential

TAX CODE/SERVICE CODE

SERVICE CODE

TAX CODE

EVENT/FUNCTION

FUNCTION

EVENT

EVENT LOCATION ROOM

TEAM MEMBER

POSITION

ASSET

PROPERTY

PRICE LISTPRICE LIST ITEM

CHARGE CODE

CATEGORYPRODUCT

applies to

composed of

child of

parent to

child of

parent to

for

subject of

instance of

for

for

composed of

for

has

subject of

for

categorized in

for

for

composed of

user of

current price list of

belongs to

owns

holders of

held by

responsible for

responsibility of

belongs to

contains

held at

holds

held at

location of

for

composed of



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


Table 37. Expense Reports ERD Entities and Tables

Entity Table

Activity S_EVT_ACT


Expense Item S_EXP_ITEM

Expense Item Type S_EXP_ITM_TYPE

Expense Report S_EXP_RPT

Expense Report Approval S_EXP_RPT_APPR

Opportunity S_OPTY


Party S_PARTY


Project S_PROJ



98

Figure 38. Expense Reports

Title : Expense ReportsAuthor : Oracle, Confidential

PARTY

PERSON

EMPLOYEE /

AGENTOTHER 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



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


Table 38. Field Service Inventory ERD Entities and Tables

Entity Table

Address S_ADDR_PER

Asset S_ASSET


Inventory Location S_INVLOC

Inventory Transaction S_INV_TXN


Party S_PARTY



Product Inventory S_PROD_INV

Product Inventory Category S_PROD_INV_CAT

Product Inventory Location S_PROD_INVLOC




100

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



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


Table 39. Field Service Scheduler ERD Entities and Tables

Entity Table

Address S_ADDR_PER


Employee Exceptional Work Hours S_EMP_EXCPT_HRS

Scheduler Cost Function S_SCH_CSTFN

Scheduler Cost Function Variable S_SCH_CSTFN_VAR

Scheduler Parameter S_SCH_PARAM

Scheduler Parameter Set S_SCH_PARAM_SET

Scheduler Rule S_SCH_RULE

Scheduler Rule Node S_SCH_RULENODE

Scheduler Rule Set S_SCH_RLST

Scheduler Time Map S_SCH_TMMAP

Scheduler Time Map Duration S_SCH_TMMAP_DUR

Service Activity S_EVT_ACT

Service Region S_SRV_REGN


Timezone S_TIMEZONE

Work Shift S_SCHED_CAL

Work Shift Exception S_EXCPT_CAL

Work Shift Exception Hour S_EXCPT_CAL_HRS

Work Shift Hour S_SCHED_CAL_HRS

Zipcode S_ZIPCODE



102

Financial AccountThis ERD (shown in Figure 41) illustrates how Siebel Financial Services supports tracking of financial accounts (instances of products or assets). A financial account can be owned by an organization, or a number of contacts. The owners can track the activities, service requests, balance history, and transactions on their accounts, as well as the balance of their external accounts using Siebel Financial Services. The manager can track the profitability of his customers through contact and account profitability.

Figure 40. Field Service Scheduler

Title : Field Service SchedulerAuthor : Oracle, Confidential

ZIPCODE

SERVICE REQUEST

SERVICE ACTIVITY

ADDRESS

SCHEDULER RULE NODE SCHEDULER RULESCHEDULER RULE SET

EMPLOYEE EXCEPTIONAL WORK HOURS

WORK SHIFT EXCEPTION HOUR

WORK SHIFT EXCEPTION TIMEZONE

EMPLOYEE

WORK SHIFT HOUR WORK SHIFT

SCHEDULER PARAMETER SET

SCHEDULER PARAMETER

SCHEDULER TIME MAP DURATION

SCHEDULER TIME MAP

SCHEDULER COSTFUNCTION VARIABLE

SCHEDULER COST FUNCTION

SERVICE REGION

in

for

with

for

assigned to

assigned with

assigned to

owner of

in

for

for

subject of

ending at

for

starting

for

user of

used by

for

with

at

for

in

for

defined for

defined by

with

for

defined for

defined by

infor

in

for

underabove

for

subject of

within

made up of

within

made up of

defined for

subject of

defined for

subject of

in

for

user of

used by

user of

used by

user of

used by




Table 40. Financial Account ERD Entities and Tables

Entity Table

Account Aggregation Service S_FN_AAG_SVC

Account Analysis S_FN_SRVC_TXN

Account Profitability S_ORG_PRFTBLTY

Activity S_EVT_ACT

Address S_ADDR_PER

Asset Relationship S_ASSET_REL

Assignment Group S_ASGN_GRP

Attachment S_ASSET_ATT

Authorization S_ASSETCON_AUTH

Balance History S_FN_ACCNT_BAL


Contact Profitability S_CON_PRFTBLTY

Fee S_FN_ACCNT_FEE


Financial Account Contact S_ASSET_CON

Financial Transaction S_FN_ACCNT_TXN

Note S_NOTE_ASSET


Product S_PROD_INT

Schedule S_FN_ACCNT_SCHD




104

Figure 41. Financial Account

Title

: F

inancia

l A

ccount

Auth

or

: O

racl

e, C

onfidential

AS

SIG

NM

EN

T

GR

OU

P(T

ER

RIT

OR

Y)

CO

NT

AC

T

AD

DR

ES

S

PE

RS

ON

AL

AD

DR

ES

S

BU

SIN

ES

S

AD

DR

ES

S

BA

LA

NC

E

HIS

TO

RY

AT

TA

CH

ME

NT

NO

TE

AC

CO

UN

T

PR

OF

ITA

BIL

ITY

AS

SE

T

RE

LA

TIO

NS

HIP

AC

CO

UN

T

AN

AL

YS

IS

SE

RV

ICE

R

EQ

UE

ST

FIN

AN

CIA

L

TR

AN

SA

CT

ION

OR

GA

NIZ

AT

ION

UN

IT

EX

TE

RN

AL

O

RG

AN

IZA

TIO

N

UN

IT

INT

ER

NA

L

OR

GA

NIZ

AT

ION

U

NIT

PR

OD

UC

T

AC

TIV

ITY

CO

NT

AC

T

PR

OF

ITA

BIL

ITY

AU

TH

OR

IZA

TIO

N

FIN

AN

CIA

L A

CC

OU

NT

CO

NT

AC

T

AC

CO

UN

T

AG

GR

EG

AT

ION

S

ER

VIC

E

FE

E

SC

HE

DU

LE

FIN

AN

CIA

L A

CC

OU

NT

EX

TE

RN

AL A

CC

OU

NT

INT

ER

NA

L A

CC

OU

NT

for

pro

ble

ms w

ith

su

bje

ct

of

for

pro

ble

ms w

ith

su

bje

ct

of

de

fine

d fo

r

su

bje

ct

of

of

su

bje

ct

of

use

d b

y use

s

for

su

bje

ct

of

for

su

bje

ct

of

for

su

bje

ct

of

for

su

bje

ct

of

for

su

bje

ct

of

for

su

bje

ct

of

of su

bje

ct

of

for

su

bje

ct

of

pa

rtic

ipa

nt

in

targ

et

of

for

asso

cia

ted

with

su

bje

ct

of

for

of

asso

cia

ted

with

for

asso

cia

ted

with

for

su

bje

ct

of

loca

ted

at

for

cu

rre

ntly o

wn

ed

by

ow

ne

r

of

cu

rre

ntly o

wn

ed

by ow

ne

r o

f



Financial Account ApplicationThis ERD (shown in Figure 42) illustrates how Siebel Financial Services supports generation of a financial product (loan, mortgage, or similar) application by a consumer (contact) or an organization. The applicant is assessed based on incomes, expenses, assets, and liabilities. Fees and collateral are associated with the application, and when it is approved, it generates a financial account (asset).


Table 41. Financial Account Application ERD Entities and Tables

Entity Table

Activity S_EVT_ACT

Address S_ADDR_PER, S_CON_ADDR

Application S_OPTY

Application Contact S_OPTY_CON

Application Product S_REVN

Assessment S_ASSESS

Assessment Value S_ASSESS_VAL

Asset Liab Contact S_FN_ASTLB_CON

Asset Liability S_FN_ASSET_LIAB

Collateral S_FN_OFFR_COLT


Credit Report S_FN_CRDT_RPT

Credit Report Item S_CRDT_RPT_ITEM

Fee S_FN_OFFR_FEE


Inc. Exp. Contact S_FN_INCEXP_CON

Income/Expense S_FN_INCM_EXP

Note S_NOTE_OPTY


Product S_PROD_INT

Quote S_DOC_QUOTE

Sales Stage S_STG

Trailing Document S_OPTY_DOC



106

Figure 42. Financial Account Application

Titl

e : F

inan

cial

Acc

ount

App

licat

ion

Aut

hor

: O

racl

e,

Con

fiden

tial

CR

ED

IT

RE

PO

RT

ITE

M#

SE

Q_N

UM

CR

ED

IT R

EP

OR

T

PR

OD

UC

T

DIS

CLO

SU

RE

AP

PR

OV

AL

INC

.EX

P.

CO

NT

AC

TA

SS

ET

LIA

B.

CO

NT

AC

T

AD

DR

ES

S

AP

PLI

CA

TIO

N C

ON

TA

CT

LEN

DE

RA

PP

LIC

AN

T

SA

LES

S

TA

GE

AP

PLI

CA

TIO

N

OR

GA

NIZ

AT

ION

AP

PLI

CA

TIO

N P

RO

DU

CT

NO

TE

AS

SE

SS

ME

NT

V

ALU

E

FIN

AN

CIA

L A

CC

OU

NT

FE

EC

OLL

AT

ER

AL

AS

SE

T L

IAB

ILIT

Y

INC

OM

E/E

XP

EN

SE

AS

SE

SS

ME

NT

AC

TIV

ITY

OT

HE

R A

CT

IVIT

Y

ST

AT

EM

EN

T

TR

AIL

ING

D

OC

UM

EN

TQ

UO

TE

CO

NT

AC

T

PR

OD

UC

T

in r

efer

ence

tosu

bjec

t of

supp

orte

d by in

sup

port

of

belo

ng

to cont

ain

ackn

owle

dged

by

ackn

owle

dger

of

for

has

for

base

d on

with

hasof

incu

rred

by

with

asso

ciat

ed

to

of

asso

ciat

ed

with

for

loca

ted

at

for

loca

ted

at

has

for

asso

ciat

ed

with

has

for

uses

asso

ciat

ed

with

has

asso

ciat

ed

with

has

part

of

gene

rate

s

for

base

d on

for

base

d on

for

subj

ect

to

base

d on

gene

rate

s

gene

rate

s

gene

rate

d by

for

subj

ect o

f

for

subj

ect o

f

for

a co

mpo

nent

of

uses

used

by

has

a

on

for

subj

ect o

fre

port

ed in

to r

evie

w

for

has

for

has

repo

rted

in

to r

evie

w

for

subj

ect

of



Financial InvestmentsThis ERD (shown in Figure 43) illustrates how Siebel Financial Services supports generation of financial investments and other relevant associations with organizations, financial accounts, holdings, distribution, and transactions. The major entities are depicted in the lower half of the diagram (security and external organization).


Table 42. Financial Investments ERD Entities and Tables

Entity Table


Distribution S_FNSEC_DSTRBTN

External Organization S_ORG_EXT, S_PARTY

Earning S_FNSEC_ERNG


Holding S_FN_HLDNG

Industry S_INDUST

Literature S_LIT

Security S_PROD_INT

Transaction S_FN_ACCNT_TXN



108

Figure 43. Financial Investments

Title : Financial InvestmentsAuthor :Oracle, Confidential

DISTRIBUTION

LITERATURE TRANSACTIONHOLDING

CONTACT

FINANCIAL ACCOUNTEARNING

CAPITAL GAINS

DIVIDEND

SECURITY

STOCK FUND

INTERNAL EXTERNAL

BOND

INDUSTRY

EXTERNAL ORGANIZATION

PUBLIC COMPANY

INSTITUTIONALINVESTOR

FINANCIAL INSTITUTION

for

subject of

part of

made up of

for

subject of

for

made against

for subject of

for

subject of

for

subject of

for

subject of

for

subject of

for

made against

invested by investor of

for

subject of



Financial ProductsThis ERD (shown in Figure 44) illustrates how Siebel Financial Services supports generation of financial products and other relevant associations. Internal products, rates, fees, and product line information is also depicted. The major entities are depicted in the lower half of the diagram (Product Internal).


Table 43. Financial Products ERD Entities and Tables

Entity Table

Benefit S_PROD_BNFT

Condition S_PROD_COND

Feature S_PROD_SPEC

Fee S_PROD_FEE

Product S_PROD_INT


Rate S_PROD_RATE



110

Figure 44. Financial Products

Title : Financial ProductsAuthor :Oracle, Confidential

BENEFIT CONDITION

FEERATEFEATUREPRODUCT LINE

PRODUCT INTERNAL

made up of

part of

for

subject of

for

subject of

for

subject of

of

has

of

has

contain

within

composed of

part of

for

subset

of

has



Financial Services EventsThis ERD (shown in Figure 45) illustrates how Siebel Financial Services supports generation of marketing events in a three-level hierarchy (parent events, sub events, and sessions). An event can be associated with many opportunities, product lines, regions, or industries. It has a list of registrants (contacts or organizations). Vendors, venues, and suppliers are tracked for the event in the organization entity. For persons, tracks the registration procedure and travel plans they might participate in to attend the event.


Table 44. Financial Services Events ERD Entities and Tables

Entity Table

Activity S_EVT_ACT

Equipment Requirement S_ORDER_ITEM, S_QUOTE_ITEM

Event Cost S_SRC_COST

Event Location S_ORG_EXT, S_PARTY

Event Registration S_SRC_EVT_REG

Event Session S_SRC_EVT, S_SRC

Event Venue S_SRC_VENUE

Industry S_INDUST


Location Room S_EVTLOC_ROOM



Person S_EMP_PER, S_CONTACT, S_PARTY

Position S_POSTN

Product S_PROD_INT


Region S_REGION

Room Avail Equipment S_EVTLOC_RM_EQP

Travel Participant S_EVT_TRVL_PER

Travel Plan S_EVT_TRVL_PLAN

Vendor S_SRC_ORG

Vendor Offer S_EVT_VNDR_OFR

Vendor Review S_EVT_VNDR_RVW

Vendor Service S_EVT_VNDR_SVC



112

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 44. Financial Services Events ERD Entities and Tables

Entity Table



Figure 45. Financial Services Events

Titl

e : F

inan

cial

Ser

vice

s E

vent

sA

utho

r : O

racle

, Con

fiden

tial

TR

AV

EL

PA

RT

ICIP

AN

T

EV

EN

T C

OS

T

RE

VE

NU

E

CO

ST

TR

AV

EL

PLA

N

EV

EN

T

RE

GIS

TR

AT

ION

AT

TE

ND

EE

CA

NC

ELL

ED

R

EG

IST

RA

NT

WA

IT L

IST

RE

GIO

N

IND

US

TR

Y

RO

OM

AV

AIL

E

QU

IPM

EN

T

PR

OD

UC

TLI

TE

RA

TU

RE

IT

EM

PR

OD

UC

T L

INE

PO

SIT

ION

LOC

AT

ION

RO

OM

EQ

UIP

ME

NT

R

EQ

UIR

EM

EN

TA

CT

IVIT

Y

VE

NU

E

RE

VIE

WV

EN

UE

S

ER

VIC

EV

EN

UE

O

FF

ER

EV

EN

T V

EN

UE

VE

ND

OR

R

EV

IEW

VE

ND

OR

S

ER

VIC

EV

EN

DO

R

OF

FE

RP

ER

SO

N

OR

GA

NIZ

AT

ION

UN

IT

INV

ES

TIN

G

CO

MP

AN

YO

TH

ER

O

RG

AN

IZA

TIO

N

UN

IT

EV

EN

T L

OC

AT

ION

VE

NU

EO

TH

ER

LO

C

MA

RK

ET

ING

EV

EN

T O

R A

CT

IVIT

Y

SU

B E

VE

NT

PA

RE

NT

EV

EN

TE

VE

NT

SE

SS

ION

VE

ND

OR

part

icip

ates

has

incl

udes m

embe

r of

serv

iced

by

serv

ices

asso

ciat

ed w

ith

has

asso

ciat

ed w

ith

has

incl

udes

part

of

for

has

for

subj

ect

offo

r

subj

ect

of

invi

ter

of

invi

ted

to

staf

fed

by

on s

taff

for

subj

ect

of

deal

s w

ith

subj

ect

of

deal

s w

ith

subj

ect

of

deal

s w

ith

in

supp

lier

of

held

at

loca

tion

of

avai

labl

ein

equi

pped

w

ith

rele

vant

to

prom

oted

via

subj

ect

of

deal

s w

ith

resp

onsi

ble

for

resp

onsi

bilit

y of

requ

ired

by

in n

eed

of

for

subj

ect

of

revi

ewed

by

revi

ewer

of

for

subj

ect

of

of for

loca

tion

of

held

at

for

subj

ect

of

offe

red

at

prov

ider

of

offe

red

at

subj

ect

of

from

part

icip

ated

as

part

of

com

pose

d of

part

of

com

pose

d of

revi

ewed

by

revi

ewer

of

for

subj

ect

of

offe

red

by

prov

ider

of

offe

red

by

prov

ider

of



114

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 45. Forecasts ERD Entities and Tables

Entity Table


Forecast S_FCST

Forecast Item Detail S_FCST_ITEM_DTL

Forecast Period S_FCSTSER_DATE

Forecast Series S_FCSTSER

Forecasted Item S_FCST_ITEM

Marketing Event S_SRC

Opportunity S_OPTY






Project S_PROJ

Quote S_DOC_QUOTE

Revenue Item S_REVN




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



116

Group Insurance PoliciesThis ERD (shown in Figure 47) illustrates how Siebel Financial Services supports generation of a group policy instance, which can be either a group health or a group life policy, or other types of employee benefits. One organization can own many policy instances. Each organization's employee is a primary policy contact, and determines the type of coverage and the elements of coverage they enjoy. Each contact covered by a policy instance has an insurance coverage role, and the contact's dependents are stored as coverage elements. The coverage role provides each coverage element with multiple possible benefits.


Table 46. Group Insurance Policies ERD Entities and Tables

Entity Table

Census S_ORG_CENSUS

Census Detail S_CENSUS_DETAIL

Class S_VOD, S_VOD_VER

Class Attribute S_XA_ATTR


Coverage Role S_FN_CVRG_ROLE

Employee Class S_FN_GRP_CLASS

Instance Attribute S_ASSET_ITEM_XA


Policy Instance S_ASSET

Primary Policy Member S_ASSET_CON

Product Attribute S_PROD_INT_XA

Product Class S_FN_HLDNG

Product Class Rate S_FN_HLDNG_RATE

Product Component S_PROD_ITEM

Product Enrollment S_FNCVRG_ELMNTS

Product For Member S_APPLD_CVRG

Product Instance S_ASSET_ITEM


Rate Band S_PROD_RATE



Figure 47. Group Insurance Policies

Titl

e : G

roup

Insu

ranc

e P

olic

yA

utho

r : O

racle

, Con

fiden

tial

PR

OD

UC

T

EN

RO

LLM

EN

T

PR

IMA

RY

PO

LIC

Y M

EM

BE

R

PR

OD

UC

T F

OR

M

EM

BE

RS

EM

PLO

YE

E

CLA

SS

PR

OD

UC

T

AT

TR

IBU

TE

CLA

SS

INS

TA

NC

E A

TT

RIB

UT

E

CLA

SS

A

TT

RIB

UT

EP

RO

DU

CT

C

OM

PO

NE

NT

PR

OD

UC

T

INS

TA

NC

E

RA

TE

B

AN

D

PR

OD

UC

T C

LAS

S

PR

OD

UC

T C

LAS

S R

AT

E

PO

LIC

Y IN

ST

AN

CE

GR

OU

P L

IFE

OT

HE

R E

MP

LOY

EE

B

EN

EF

ITS

GR

OU

P H

EA

LTH

OR

GA

NIZ

AT

ION

UN

IT

EX

TE

RN

AL

OR

GA

NIZ

AT

ION

UN

IT

PR

OD

UC

T IN

TE

RN

AL

CE

NS

US

D

ET

AIL

CE

NS

US

CO

NT

AC

T

CO

VE

RA

GE

RO

LE

prim

ary

of

of

part

of

mad

e up

ofpa

rt o

f

mad

e up

of

base

d on

for

appl

ied

to

subj

ect

tofo

r

subj

ect

of

part

of

mad

e up

of

bene

ficia

ry o

fbe

nefit

sun

der

for

for

subj

ect

of

for

has

used

for

uses

for

has

belo

ngs

to has

belo

ngs

to

has

avai

labl

e fo

r

has

part

of

mad

e up

of

for

subj

ect

of

part

of

has

part

of

has

part

of

mad

e up

of

base

d on

basi

s of

of

has

has

of

asso

ciat

edw

ith

has

belo

ngs

to

has

for

has

of

has

base

d on

basi

s of

base

d on

basi

s of

of

has

base

d on

basi

s of

owne

r of

owne

d by

for

has

for

subj

ect

of

for

subj

ect

of



118

Group PensionsThis ERD (shown in Figure 48) illustrates how Siebel Financial Services supports group pension plans. The group pensions module is designed to meet the needs of sales and service professionals, managers, and pension administrators. Users can define group pension plans, plan classes, plan eligibility rules, and plan funding vehicles. When a pension plan is defined, users can track eligible and enrolled participants, participant contribution and investment allocations, and participant beneficiary information.


Table 47. Group Pensions ERD Entities and Tables

Entity Table

Allocation S_APPLD_CVRG

Beneficiary S_FN_CVRG_ROLE

Employee Class S_FN_GRP_CLASS

Funding Vehicle S_PROD_REL

Group Pension Participant S_CONTACT, S_PARTY

Group Pension Plan S_ASSET

Group Pension Plan Contact S_ASSET_CON

Organization Unit S_BU

Pension Plan Offering S_PROD_INT




Figure 48. Group Pensions

Title : Group PensionsAuthor : Oracle, Confidential

BENEFICIARY ALLOCATION

PARTICIPANT EMPLOYEE CLASS

ORGANIZATION UNIT

CONTACT

PRODUCT

PENSION PLAN

FUNDING VEHICLE

GROUP PENSION INSTANCE

part of

has

of

by

for

has

for

set up

part of

has

having

of part of

made up of

used for

uses

has

for

belongs to

has

belong to

consists of

has

for



120

Health Provider and Provider GroupThis ERD (shown in Figure 49) illustrates how Siebel Financial Services supports generation of heath-related organizations (such as hospitals) and providers (such as physicians). A provider can be affiliated with one or more organizations and can deliver a health product (a medical service) to a contact or a patient during an encounter. Siebel Financial Services also stores payments made to a provider by an organization, as well as the specialty, language, and schedule of the provider.


Table 48. Health Provider and Provider Group ERD Entities and Tables

Entity Table


Encounter S_FN_HLTH_ENCTR

Health Product S_PROD_INT

Language S_CONTACT_FNXM



Provider Group Schedule S_ORG_TIME

Provider Schedule S_CON_LOCTN

Specialty S_CONTACT_FNXM



Figure 49. Health Provider and Provider Group

Title : Health Provider/Provider GroupsAuthor :Oracle, Confidential

LANGUAGE

PROVIDER GROUPSCHEDULE

ORGANIZATION

EXTERNAL ORGANIZATION UNIT

PROVIDER GROUP

PAYMENT

HEALTHPRODUCT

SPECIALTYPROVIDERSCHEDULE

ENCOUNTER

CONTACT

PATIENT PROVIDER

made by

make

in

subject of provides

provided by

employs

part of

involves

part of

delivered by

delivers

made to

beneficiaryof

spoken by

speaks

for

specializedin

belongs to

subject of

serve

serve at

belongs to

subject of

involves

part of



122

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


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

Entity Table

Account, Partner, Other Account S_ORG_EXT

Claim Item S_SRC_PAYITM

Claim, Payment, Other Payment S_SRC_PAYMENT

Event Item S_SRC_COST


General Fund S_MDF

Internal Product or Service S_PROD_INT

Market Segment S_MKT_SEG



MDF Snapshot S_MDF_PERIOD

MDF Transaction S_MDF_TXN

Partner Event Activity S_SRC

Partner Program S_PRTNR_PROG

Partner Program Application S_PRTNRPRG_APPL

Partner Specific Fund S_MDF

Position S_POSTN



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



124

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


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

Entity Table

Account S_ORG_EXT

Address S_ADDR_PER


Claim Item S_POS_CLAIM_ITM

Design Registration S_OPTY_DSGN_REG

Entitlement S_ENTLMNT

Entitlement Product Price S_ENTL_PRDPRI

Meet Competition Quote S_DOC_QUOTE

Opportunity S_OPTY

Point of Sale Header S_POS

Point of Sale Item S_POS_ITEM

Product S_PROD_INT

Quote Line Item S_QUOTE_ITEM



Figure 51. High Tech Special Pricing Authorization

Title

: H

igh T

ech S

pecia

l P

ricin

g A

uth

orization

Auth

or

: O

racle

, C

onfidential

AD

DR

ES

S

PR

OD

UC

TP

OIN

T O

F S

ALE

IT

EM

OT

HE

R P

OS

ITE

M

CLA

IM IT

EM

PO

INT

OF

SA

LE

HE

AD

ER

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

ITE

M

AC

CO

UN

T

EN

TIT

LE

ME

NT

PR

OD

UC

T P

RIC

E

EN

TIT

LE

ME

NT

AG

RE

EM

EN

TM

EE

T

CO

MP

ET

ITIO

N

QU

OT

E

for

sub

ject of

for

locate

d

at

desig

ned

for

sub

ject of

sp

ecia

lly q

uote

d for

sub

ject of

for

sub

ject of

refe

rencin

g

sup

port

for

for

havin

g

for

com

posed

of

for

associa

ted

with

cre

ate

d for

sub

ject of

part

of

com

posed

of

initia

ted

by

sub

ject of

for

sub

ject of

for

havin

g

for

mad

e u

p

of

for

associa

ted

with



126

Hospitality CategoryThis ERD (shown in Figure 52) illustrates how Siebel Hospitality supports the categorization for revenue. There can be N levels of the revenue category in the hierarchy. One parent category can have one or more categories, and one category can have one or more subcategory. The subcategory is defined for the charge code and product, and a report is generated by category for each function and quote. Function and quote revenue by category hierarchy supports the hierarchical category. A macro estimate for the opportunity and quote is generated at the category level.


Table 51. Hospitality Category ERD Entities and Tables

Entity Table

Hospitality Category S_CTLG_CAT

Parent Category S_CTLG_CAT

Category S_CTLG_CAT

Subcategory S_CTLG_CAT

Category Revenue S_AVG_VAL_TNT, S_FN_CATRV_TNT, S_QUO_CATRV_TNT

Function Average Level S_AVG_VAL_TNT

Function Revenue by Category S_FN_CATRV_TNT

Quote Revenue by Category S_QUO_CATRV_TNT

Quote Macro Revenue Estimate S_QUO_MEST_TNT

Opportunity Macro Revenue Estimate

S_OPTY_MEST_TNT

Charge Code S_EVT_CHRG_LST

Function Business Type by Date S_BIZ_TP_DT_TNT

Function S_FUNC_TNT

Quote S_DOC_QUOTE

Opportunity S_OPTY


Tax/Service List S_PRI_LST



Figure 52. Hospitality Category

Title : Hospitality CategoryAuthor : Oracle, Confidential

OPPORTUNITYOPPORTUNITY MACRO REVENUE ESTIMATE

QUOTE

FUNCTION

FUNCTION BUSINESS TYPE BY DATE

QUOTE MACRO REVENUE ESTIMATE

CATEGORY REVENUE

QUOTE REVENUE BY CATEGORY

FUNCTION REVENUE BY CATEGORY

FUNCTION AVERAGE LEVEL

PRODUCT OR SERVICE

TAX / SERVICE LIST CHARGE CODE

HOSPITALITY CATEGORY

SUB CATEGORY

CATEGORY

PARENT CATEGORY

child of

parent of

child of

parent of

defined for

associated with

for

subject of

for

subject of

generated from

lead to

for

subject of

for

subject of

for

subject of

of

subject of

for

subject of

child ofparent of

for

subject of

associated with

for

related with

subject of

child of

parent of

child of

parent of



128

Institutional SalesThis ERD (shown in Figure 53) illustrates how Siebel Financial Services supports generation of a product or security traded in the stock market. One or more positions (such as institutional salespeople) can cover a product. A position owns and prepares a call list containing one or more contacts, who are the objects of the calls associated with any number of products. Siebel Financial Services also tracks security or product line interests of a contact, as well as the securities held by an organization unit (such as a company). Siebel Financial Services creates many-to-many relationships when storing the literature associated with employees, activities, and products. A position can send any number of pieces of literature to a contact within one activity.


Table 52. Institutional Sales ERD Entities and Tables

Entity Table

Activity S_EVT_ACT




Industry S_INDUST

Literature S_LIT



Product S_PROD_INT




Figure 53. Institutional Sales

Title

: In

stitu

tion

al S

ale

sA

uth

or

: O

racl

e, C

on

fid

en

tial

OR

GA

NIZ

AT

ION

UN

IT

EX

TE

RN

AL

O

RG

AN

IZA

TIO

N

UN

IT

CA

LL

LIS

T

IND

US

TR

Y

LIT

ER

AT

UR

E

EM

PL

OY

EE

AC

TIV

ITY

PR

OD

UC

T L

INE

CO

NT

AC

T

PO

SIT

ION

PR

OD

UC

T

SE

CU

RIT

Y

issued

by

issues

hold

s

held

by

auth

or

of auth

ore

d b

y

uses

attached to

cove

rs

subje

ct

of

about

subje

ct of

associa

ted

with

subje

ct

of

subje

ct

of

part

of

ow

ns

ow

ned b

y

cove

rs

cove

red

by

cove

rs

cove

red b

y

inte

reste

d in

obje

ct of

inte

rest of

inte

reste

d

in obje

ct of in

tere

st of



130

Insurance ClaimsThis ERD (shown in Figure 54) shows the important entities in the Insurance Claim recording and handling process. It illustrates the relationship between claims and claim elements and the various parties to the claim. It covers the association of invoices, invoice line items, payments and recoveries to claims. Also illustrated is the relationship between claim and insurance policy, activity, service request, document, appraisal, and so forth. The diagram also shows the metadata that supports claims and claim elements.


Table 53. Insurance Claims ERD Entities and Tables

Entity Table

Activity S_EVT_ACT, S_EVT_ACT_FNX

Assignment Group (Territory) S_ASGN_GRP, S_INSCLM_TERR

Claim Account S_INSCLM_ORG

Claim Appraisal S_INSCLM_APRSL

Claim Appraisal Attachment S_INSCLM_AP_ATT

Claim Contact S_INSCLM_CON, S_INSCLMCON_ORG

Claim Document S_INSCLM_DOC

Claim Element S_INSCLM_ELMNT

Claim File Attachment S_INSCLM_CL_ATT

Claim Payment S_SRCPAY_INSCLM

Claim Property S_INSCLM_PRPTY

Claim Recovery S_INSCLM_RECVRY

Contact S_CONTACT, S_PARTY, S_CONTACT_FNX

Default Coverage S_DEFAULT_ADMIN

Injury S_INSCLM_INJURY

Insurance Claim S_INS_CLAIMS_INSCLM_FRAUDS_INSCLM_SBRGTNS_INSCLM_UW

Insurance Policy S_ASSET

Insurance Policy Item S_INS_ITEM

Invoice S_INVOICE, S_INVC_PAYMENT

Invoice Line Item S_INVOICE_ITEM

Loss Code S_INS_LOSS_CODE, S_LOSSCD_PLNITM

Loss Code Coverage S_INS_LOSCD_COV



Loss Event S_INSCLM_EVT

Organization S_ORG_EXTS_PARTYS_ORG_EXT_FNX

Party S_PARTY

Payment S_SRC_PAYMENTS_SRCPAYMT_CONS_SRCPAYMT_ORGS_INVC_PAYMENT


Reserve Code S_INS_RSRV_CODE

Service Request S_SRV_REQ, S_SRV_REQ2_FNX

Table 53. Insurance Claims ERD Entities and Tables

Entity Table



132

Figure 54. Insurance Claims

��

��

��

��

��

��

��

��O

racle

��

��

'�

�"��

�+

"�

$�

��

+"

�$

�

�$>

��

��'

�$�

��

�"

!�

*�

&'�

�

�>

��

�

�

'�

%%

��

!�

�

�>

��

�

�

��

%�

�>

��

�!

�

'�

%%

�

�!

�

'

��"

��

�

&$

�

�$>

��

�

�

��>

��+

�%

%�

$"

�$

�

��

&�

^��

��

)

�$%

&�

�$

�

��

�'�

+��

�"

�$%

&�

�$

�

��

'�

+

��

��

+

��

�$

��

�

��

%��

��$

� ��

�

$�[

��

� �N

'�

�"��

��

��

��

+

'�

�"�

�

$�

�

�

�$=&

�+

'�

�"�*

�'�

��

��

�

9"

�$

�

'�

�"�

��

��

��%

�'�

��

��

9

"�

$�

'�

�"�

��

��

��%

�'

'�

�"��

'�

"�

$�

'�

�"�

!�

&

"�

$�

'�

�"�

��

�

>�

�+

'�

%%

��

>�

$�

%�

�>

��

��

7&

�%

T

�$%

&�

�$

�

�'�

�"

TT

� �

��

��

�

6

��

�

6

��

13

��

� ��3��

� �

��

��

��

��

��

��2 �2

��

��

��14�

��

�

��

��

� ��14�

��

�

� 2��

��

13

��14�

��

�

��3��

� �

��

�

� �

��14�

��

��

��

��

��

��

� ��

��

��

��

��14�

��

��

��

6��

��14�

��

�

��

��

6��

��14�

��

�

��

��

6��

��14�

��

�

��

��

6��

��14�

��

�

1��

��

� ��

��

��

�1��

�

��14�

��

�

��

��1

3

��

��

��

�� 1

��

� �

�� 1

��3

�

��

��

�

��

��

13

1��

��

�

��14�

��

�

��

��

�1��

� � 2��

��

� �

� �

��

�13

��

��

��1

3

��

��

� �

��14�

��

�

� �

��

��

�

��

2��

13

��

2��

�

��

��

6��

��14�

��

�

��

��

6��

��14�

��

�

��

��

��2 �2

��6

��

��

��

13��14�

��

�

��

��

6��

��14�

��

�

�

��14�

��

�

��

��

� ��14�

��

��

��

6��

��14�

��

�

� 2��

��1

3

� 2��

��

��

��

��

��14�

��

� �

��14�

��

�

��

��

6��

��14�

��

��14�

��

�

��

��

��

��

� �

� 2��

��

��

��

��14�

��

�



Insurance PoliciesThis ERD (shown in Figure 55) illustrates how Siebel Financial Services supports generation of insurance policies and related insurance policy items. The major entities are depicted in the bottom half of the diagram (insurance policy and insurance policy items). Insurance policies relate to households as well as contacts. Policy coverages, discounts, payment plans, and claim summaries are also supported.


Table 54. Insurance Policies ERD Entities and Tables

Entity Table


Claim Summary S_INS_CLAIM

Condition S_INSITEM_CNDTN


Discount S_APPLD_DISCNT

Drivers License S_DRVR_LICENSE

Household S_ORG_GROUP, S_PARTY

Household Contact S_GROUP_CONTACT

Insurance Coverages S_APPLD_CVRG

Insurance Document Item S_INS_DOC

Insurance Policy S_ASSET

Insurance Policy Item S_INS_ITEM

Insurance Policy Item Account S_INSITEM_ACCNT

License Restriction S_DL_RSTRCT

Payment Plan S_PAY_PLAN

Policy Contact S_ASSET_CON



134

Figure 55. Insurance Policies

Titl

e:I

nsur

ance

Pol

icie

sA

utho

r:O

racl

e,C

onfid

entia

l

CO

ND

ITIO

N

AC

CO

UN

T

INS

UR

AN

CE

PO

LIC

YIT

EM

AC

CO

UN

T

CLA

IMS

UM

MA

RY

PA

YM

EN

TP

LAN

HO

US

EH

OLD

INS

UR

AN

CE

PO

LIC

YIT

EM

SC

HE

DU

LED

PE

RS

ON

AL

PR

OP

ER

TY

OT

HE

RIN

SU

RA

NC

EP

OLI

CY

ITE

M

WA

TE

RC

RA

FT

DW

ELL

ING

VE

HIC

LE

INS

UR

AN

CE

PO

LIC

Y

PE

RS

ON

AL

UM

BR

ELL

ALI

NE

S

PO

LIC

YIN

ST

AN

CE

OT

HE

RP

RO

PE

RT

Y

AU

TO

LIC

EN

SE

RE

ST

RIC

TIO

N

HO

US

EH

OLD

CO

NT

AC

T

CO

NT

AC

T

PO

LIC

YC

ON

TA

CT

INS

UR

AN

CE

DO

CU

ME

NT

AT

ION

ITE

M

DR

IVE

RS

LIC

EN

SE

INS

UR

AN

CE

CO

VE

RA

GE

DIS

CO

UN

T

part

of

com

pose

dof

char

acte

ristic

of

char

acte

rized

by

on subj

ecto

f

on

subj

ecto

f

asso

ciat

edw

ith

subj

ectt

o

asso

ciat

edw

ith

subj

ectt

o

appl

ied

to

subj

ecto

f

part

of

com

pose

dof

mem

bers

hip

of

subj

ecto

f

appl

ied

to

subj

ecto

f

mad

eag

ains

t

subj

ecto

f

appl

icab

leto

subj

ectt

o

appl

ied

to subj

ecto

f

subj

ectt

o pare

ntof

owne

rof

owne

dby

mem

bers

hip

in

mad

eup

of

on

subj

ecto

f

cove

red

by

cove

rer

of

appl

icab

leto

subj

ectt

o

for

nam

edas

issu

edto

hold

erof



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


Table 55. Invoicable Charges ERD Entities and Tables

Entity Table

Activity S_EVT_ACT

Address S_ADDR_PER


Agreement Entitlement S_ENTLMNT

Agreement Line Item S_AGREE_ITEM

Asset S_ASSET

Auction Item S_AUC_ITEM

Expense Item S_EXP_ITEM

Invoicable Charge S_INVOICE_CHRG

Invoice S_INVOICE


Invoice Item Reconciliation Entry S_INVC_ITM_DTL

Order S_ORDER

Order Line Item S_ORDER_ITEM

Part Movement S_ACTPART_MVMT, S_ORDPART_MVMT

Part Repair S_PART_RPR

Party S_PARTY, S_ORG_EXT, S_CONTACT, S_USER, S_BU




Project Item S_PROJITEM

Project Team Role S_PROJ_RSRC


Shipment S_SHIPMENT

Time Sheet Item S_TMSHT_ITEM



136

Figure 56. Invoicable Charges

Title

: In

voic

able

Ch

arg

es

Au

thor

: O

racle

, C

on

fiden

tial

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

INV

OIC

AB

LE

C

HA

RG

E

AD

DR

ES

S

EX

PE

NS

E IT

EM

TIM

E S

HE

ET

IT

EM

PR

OJE

CT

TE

AM

RO

LE

PR

OJE

CT

IT

EM

AU

CT

ION

IT

EM

PA

RT

Y

OR

GA

NIZ

AT

ION

UN

IT

OT

HE

R

OR

GA

NIZ

AT

ION

UN

IT

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

RE

QU

ES

T

SH

IPM

EN

T

PR

OD

UC

T O

R

SE

RV

ICE

PA

RT

RE

PA

IR

OR

DE

R L

INE

ITE

M

OR

DE

R

AG

RE

EM

EN

T

EN

TIT

LE

ME

NT

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

MO

VE

ME

NT

INV

OIC

AB

LE

CH

AR

GE

for

su

bje

ct of

bill

ed to

con

tact of

bill

ed to

prim

ary

bill

ing c

on

tact of

made f

or

fulfill

ed b

y

part

of

made u

p o

f

for

ch

arg

ed v

ia

for

su

bje

ct of

bill

ed to

for

for

locate

d a

tbill

ed to

for

for

ch

arg

ed v

ia

for

ch

arg

ed v

ia

based o

n

for

for

ch

arg

ed v

ia

for

ch

arg

ed v

ia

for

ch

arg

ed v

ia

obje

ct fo

r

of

of ord

ere

d o

n

part

of

com

posed o

f

for

ch

arg

ed v

ia

for

ch

arg

ed v

ia

for

su

bje

ct of

invoic

ed in

to

for

for

ch

arg

ed v

ia

for

ch

arg

ed v

ia

for

ch

arg

ed v

ia

part

of

com

posed o

f

for

fulfill

ed b

y

for

ch

arg

ed v

ia

for

ch

arg

ed v

ia

based o

nbasis

of

part

of

made u

p o

f

part

of

made u

p o

f

for

ch

arg

ed v

ia

based o

n

basis

for

for

ch

arg

ed v

ia

for

ch

arg

ed v

ia

part

of

com

posed o

f



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


Table 56. Invoices ERD Entities and Tables

Entity Table

Activity S_EVT_ACT


Expense S_EXP_ITEM

Invoice S_INVOICE

Invoice Attachment S_INVOICE_ATT


Order S_ORDER


Part Movement S_ORDPART_MVMT

Part Repair S_PART_RPR


Period S_PERIOD

Product S_PROD_INT

Project S_PROJ


Shipment S_SHIPMENT



138

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



Life Insurance PolicyThis ERD (shown in Figure 58) illustrates how Siebel Financial Services supports generation of life insurance policies and annuities as assets. Each asset can be owned by an organization or a number of contacts, and the owners can specify the coverage and beneficiaries under the policy. The owner can execute a multitude of operations on the asset such as transfers, payments, withdrawals, and surrenders.


Table 57. Life Insurance Policy ERD Entities and Tables

Entity Table

Activity S_EVT_ACT

Assessment S_ASSESS


Asset Contact S_ASSET_CON

Beneficiary S_FN_CVRG_ROLE

Beneficiary Class S_FN_BENFCLASS

Bill Account S_INS_BILLACCT

Coverage Option S_CVRG_OPTION


Financial Transaction S_FN_ACCNT_TXN

Financial Transfer S_FN_ASSET_TXFR

Holding S_FN_HLDNG

Insurance Claim S_INS_CLAIM

Insurance Coverage S_APPL_CVRG


Pay Plan S_PAY_PLAN


Product S_PROD_INT


Withdrawal/Surrender S_PAYMT_REQ



140

Figure 58. Life Insurance Policy

Titl

e : L

ife In

sura

nce

Pol

icy

Aut

hor

: Ora

cle

, Con

fiden

tial

WIT

HD

RA

WA

L /S

UR

RE

ND

ER

AS

SE

SS

ME

NT

V

ALU

EB

EN

EF

ICIA

RY

CO

VE

RA

GE

O

PT

ION

AS

SE

SS

ME

NT

BIL

L A

CC

OU

NT

INS

UR

AN

CE

C

LAIM

AC

TIV

ITY

INS

UR

AN

CE

C

OV

ER

AG

E AS

SE

T

CO

NT

AC

T

PA

Y P

LAN

PE

RS

ON

SE

RV

ICE

R

EQ

UE

ST

OR

GA

NIZ

AT

ION

HO

LDIN

G

FIN

AN

CIA

L T

RA

NS

FE

R

FIN

AN

CIA

L T

RA

NS

AC

TIO

N

BE

NE

FIC

IAR

Y

CLA

SS

PR

OD

UC

TF

INA

NC

IAL

AC

CO

UN

T

PO

LIC

Y IN

ST

AN

CE

LIF

E P

OLI

CY

AN

NU

ITY

LO

AN

for

subj

ect

of

for

a co

mpo

nent

of

belo

ngs

to

subj

ect

of

requ

este

d by

initi

ate

of

incl

udes

part

of

of

subj

ect

of

cont

act

cont

act

of for

subj

ect

of

cont

act

of

cont

act

appl

icab

leto

subj

ect

of

for

subj

ect

of

for

asso

ciat

ed

with

for

has

for

set

up

for

subj

ect

of

owne

r of

owne

d by

part

of

mad

e up

of

for

subj

ect

of

for

subj

ect

of

for

subj

ect

of

unde

rtak

e

unde

rtak

en

by

in c

onte

xt o

f

resp

onsi

ble

for

for

subj

ect

of

for as

soci

ated

with

part

of

incl

udes

for

has

for

asso

ciat

ed

with

base

d on

basi

s of

owne

r of

owne

d by

base

d on

basi

s of

guar

ante

ed b

y

guar

ante

es

guar

ante

ed b

y

guar

ante

es



LoyaltyThe Loyalty Member and the Loyalty Program ERDs of previous releases have been consolidated into a single ERD in addition to the new features of 8.1.

This ERD (shown in Figure 59) illustrates how programs and promotions are created for customer loyalty. Partner companies can have association with a loyalty hosting company to create a loyalty program. A program is the highest level entity in Siebel Loyalty. Members, tiers, promotions, point values, and so on are all specific to a single program. The members of the loyalty program can be individuals, households or accounts. A loyalty member can accrue or redeem points based on their individual transactions. In Version 8.1, Pricing rule , Pricing Range, Point Subtype, Incentive Choice, and Partner Statement entities have been introduced to support enhancements to features such as Post-Paid and Pre-Paid Partnership Management, Promotion Registration Service and so on.

Siebel Loyalty 8.1 extends accrual, redemption, promotion, enrollment, member administration and other functions:

■ Accrual Processing. Allows unified partner point type for simplified billing. Accrual templates are used for configurable transaction validations. Multiple partner debits for joint promotions enable cost sharing among partners. User-defined controls and billing triggers are provided to manage partner point balance. Allows joint rewards to benefit the organization for employee’s business transactions.

■ Promotion. Supports range-based points calculation as well as issuing vouchers as an accrual reward. Promotion criteria now includes product and partner attributes and leverages target lists of members linked to marketing campaigns or generated using analytics.

■ Redemption. Supports distance-based zones to support air redemption pricing used by some airlines and carriers. Multiple currency and multiple modes of payment are allowed. Automated point loans can be assigned to members with an insufficient balance for redemption, based on their tier status. Variable redemption pricing enables member differentiation. OOTB business services support end-to-end redemptions from third-party interfaces. A voucher-based redemption model supports service awards.

■ Member Administration. Automated tier upgrades recognize member relationships. Tier assessment enhancements support additional models like anniversary-based, fixed-date and rolling-period models. Tier change approvals prevent key members from automatic downgrade of their membership status. Bulk member administration facilitates effective service recovery through dynamic targeted rewards. User-defined membership statuses manage the membership life cycle.

■ Enrollment. The member data model has been enhanced for enriched analytics and segmentation. Batch enrollment processing has been enabled for bulk member creation and pre- created memberships enable instant member acquisition.

■ Outbound Communication. Outbound communication will be triggered when certain events occur. Content is now generated in XML format for compatibility with third-party fulfillment applications.

Partner Administration functionality has also been extended:



142

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

■ Point sub-type related data-model enhancements. Point subtype information is captured to aid points administration.

■ Points Reactivation: Enables reactivation of points. Loyalty members’ point balances expire if not used for a given expiration period,. Upon request by a loyalty member, these points can be reactivated with some charges applied to the member’s account.

■ Gift Miles Service. Loyalty members are allowed to gift accrued points to other members.

■ Promotion Registration Service. Incentive choices are available at the promotion level.

■ Airport-Zone Map for Co-terminal Identification. Tracks zone details of airports .Loyalty programs can use use zone details to allow members to accrue points based on zone travel.


Table 58. Loyalty ERD Entities and Tables

Entity Table

Account S_ORG_EXT

Accrual Item S_LOY_ACRL_ITM

Accrual Template S_LOY_ACRL_RULE,S_ACRL_RULE_ITM

Activity S_EVT_ACT_LOYX

Attribute Definition S_LOY_ATTRDEFN

Bucket S_LOY_BUCKET

Hosting Company S_ORG_EXT

Household S_ORG_GROUP

Incentive Choice S_LOYPR_ICHOICE

Individual S_CONTACT

Loan S_LOY_LOAN

Loyalty Program S_LOY_PROGRAM

Loyalty Program Member S_LOY_MEMBER

Loyalty Promotion S_LOY_PROMO

Loyalty Transaction S_LOY_TXN

Membership Card S_LOY_CARD

Package Product S_LOY_TXN_ITEM

Partner Product Offering S_PGM_ORG_PROD



Partner Statement S_PROGORG_STMT

Partner Transaction S_LOY_PRT_TXN

Point Type S_LOY_ATTRDEFN

Point Subtype S_LOY_PTSUBTYP

Pricing Options S_LOY_PROD_PT

Pricing Rule S_LOY_PRI_RULE

Pricing Range S_LOY_PRI_RANGE

Product S_PROD_INT

Program Partner S_ORG_EXT, S_LOY_PROG_ORG

Purchase Transfer Limits S_LOY_PURTRN_LM

Redemption Activity S_LOY_RDM_ACT

Redemption Item S_LOY_RDM_ITM

Service Product Association S_LOY_SRV_PROD

Statement S_LOY_STMT

Status Restriction S_LOY_MSTAT_PRF

Tier S_LOY_TIER

Tier Class S_LOY_TIER_CLS

Tier Reward S_LOY_REWARD

Travel Information S_LOY_TRVL_INFO

Voucher S_LOY_MEM_VCHR

Table 58. Loyalty ERD Entities and Tables

Entity Table



144

Figure 59. Loyalty

Title

: L

oyalty

Auth

or

: O

racle

,C

onfidential

PA

RT

NE

R

ST

AT

EM

EN

T

INC

EN

TIV

E

CH

OIC

E

PO

INT

S

UB

TY

PE

PR

ICIN

G

RA

NG

E

PR

ICIN

G

RU

LE

ST

AT

EM

EN

T

PO

INT

T

YP

E

BU

CK

ET

VO

UC

HE

R

ME

MB

ER

SH

IP

CA

RD

ST

AT

US

R

ES

TR

ICT

ION

SE

RV

ICE

P

RO

DU

CT

A

SS

OC

IAT

ION

PU

RC

HA

SE

T

RA

NS

FE

R

LIM

ITS

PR

ICIN

G

OP

TIO

NS

PR

OD

UC

T

...

HO

ST

ING

C

OM

PA

NY

TIE

R

RE

WA

RD

A

TT

RIB

UT

E

DE

FIN

ITIO

N

LO

AN

AC

CR

UA

L

TE

MP

LA

TE

PO

INT

BLO

CK

PR

OG

RA

M P

AR

TN

ER

PA

RT

NE

R

PR

OD

UC

T

OF

FE

RIN

G

PA

RT

NE

R

TR

AN

SA

CT

ION

RE

DE

MP

TIO

N

ITE

M

AC

CR

UA

L IT

EM

IN

DIV

IDU

AL

HO

US

EH

OLD

AC

CO

UN

T

LO

YA

LT

Y T

RA

NS

AC

TIO

N

PA

CK

AG

E

PR

OD

UC

TR

ED

EM

PT

ION

A

CT

IVIT

YT

RA

VE

L

INF

OR

MA

TIO

N

A

CT

IVIT

Y

LO

YA

LT

Y P

RO

GR

AM

ME

MB

ER

TIE

R C

LA

SS

TIE

R

LO

YA

LT

Y

PR

OM

OT

ION

LO

YA

LT

Y P

RO

GR

AM

genera

ted for

uses

defined for

uses

part

of

consis

ts o

f

for

giv

es

defined for

uses

of

type

for

associa

ted

with

uses

for

allo

cate

d to

part

of

consis

ts o

f

for

subje

ct of

based o

n

basis

for

for

subje

ct of

in

made o

f

ow

ned b

y ow

ner

of

defined for

uses

uses

for

defined for

subje

ct of

defined for

uses

belo

ngs to

for

used b

y

uses

ow

ned b

y ow

ns

uses

used b

y

part

of

made o

f

part

of

made o

f

used b

y

uses

defined for

uses

run b

yhost fo

r

for

qualif

ied for

availa

ble

for

qualif

ies for

for

of

defined for

subje

ct of

for

subje

ct of

in

for

part

nere

dw

ith

involv

ed in

ow

ned b

y

ow

ner

of

subje

ct of

defined

for

for

subje

ct of

defined for

uses

part

nere

dw

ith

involv

ed in

used b

y

uses

enro

lled b

y

in

enro

lled b

y

in

enro

lled b

y

in

for

subje

ct of

for

subje

ct of

child

of

pare

nt of

for

subje

ct of

done b

y

execute

r of

part

of

made u

p o

f

refe

rred b

y

refe

rence for

qualif

ied for

opte

d in b

y

part

of

made u

p o

f



Managed CareThis ERD (shown in Figure 60) illustrates how plan design, formulary, and formulary product are used in Siebel Life Sciences. An account contains plan designs, which have relationships to contacts. Each plan design contains formularies, which are associated with markets that are essentially products. Each formulary contains formulary products, which are children products for the market the formulary is associated with.


Table 59. Managed Care ERD Entities and Tables

Entity Table


Formulary S_INSPLN_FRMLY

Formulary Product S_PLNFRMLY_PROD

Health Care Professional S_CONTACT, S_PARTY

Managed Care Plan S_INS_PLAN

Plan Design Contact S_INSPLAN_CON

Product, Market S_PROD_INT



146

Figure 60. Managed Care

Title : Managed Care Author : Oracle, Confidential

HEALTH CARE PROFESSIONAL

PRODUCTFORMULARY PRODUCT

FORMULARY

MANAGED CARE PLAN

ACCOUNT

MARKET

has

associated with

hasof

accepted by

acceptor of

child of

parent to

defined for

for

is

for

for

contains

for

composed of

provided by

provider of



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


Table 60. Marketing Campaign ERD Entities and Tables

Entity Table

Activity S_EVT_ACT


Call List Member S_CALL_LST_CON

Campaign Call List S_CAMP_CALL_LST

Campaign Contact S_CAMP_CON

Fulfillment Recipient S_FUL_RECIP

Fulfillment Request S_EVT_FUL_REQ

Fulfillment Request Item S_FUL_REQ_ITEM



Opportunity S_OPTY

Opportunity Contact S_OPTY_CON

Order S_ORDER




Prospective Contact S_PRSP_CONTACT

Response S_COMMUNICATION

Territory S_ASGN_GRP



148

Figure 61. Marketing Campaign

Title

: M

ark

eting C

am

paig

nA

uth

or

: Ora

cle

, C

onfidential

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

LF

ILLM

EN

T

RE

QU

ES

T IT

EM

LIT

ER

AT

UR

E

ITE

M

FU

LF

ILLM

EN

T

RE

QU

ES

T

CA

LL L

IST

ME

MB

ER

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 L

IST

gen

era

ted b

y

ori

gin

ato

r of

gen

era

ted b

yori

gin

ato

r of

gen

era

ted b

yori

gin

ato

r of

part

of

made

for

user

of

respon

sib

ility

of

respon

sib

le f

or

associa

ted w

ith

intr

odu

ction

to

for

targ

ete

d a

t

rele

van

t to

pro

mote

d v

ia

part

of

su

bje

ct

of

part

of

con

du

cte

d a

s

initia

tor

of

initia

ted b

y

for

su

bje

ct

of

addre

ssed t

o

recip

ient

of

of

subje

ct

of

part

of

made u

p

of

of

for

of

subje

ct

of

of

subje

ct

of

of

subje

ct

of

for

targ

ete

d a

t

assig

ned t

o

role

pla

yed b

ym

anaged w

ithin

focus o

f

assig

ned t

o

assig

ned t

o s

ell

in

assig

ned t

o

assig

ned t

o

for

com

posed o

f

part

of

made u

p o

fa r

eport

to

a p

are

nt

to

of

subje

ct

of

of

used in

inm

ade u

p o

f

prim

arily

fro

m

sourc

e o

f

of

subje

ct

of



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


Table 61. Marketing Collaboration ERD Entities and Tables

Entity Table

Internal Partner/Organization S_ORG_EXT, S_PARTY


Opportunity S_OPTY

Order S_ORDER

Organization Unit, Other Organization Unit S_ORG_EXT, S_PARTY

Partner Organization S_BU, S_PARTY

Party, Other Party S_PARTY

Quote S_DOC_QUOTE

Response S_COMMUNICATION



150

Figure 62. Marketing Collaboration

Title : Marketing Collaboration

Author : 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



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


Table 62. Marketing Encyclopedia ERD Entities and Tables

Entity Table

Company Literature S_CO_LIT

Competitive Company Feature S_CMPT_CO_FEA

Competitive Metric S_CMPT_MTRC

Competitive Product Feature S_CMPT_PROD_FEA

Issue S_ISS



Product Comparison S_PROD_CMP

Product Detail S_PROD_SPEC

Product External S_PROD_EXT


Product Literature S_PROD_LIT



152

Figure 63. Marketing Encyclopedia

Titl

e : M

arke

ting

Enc

yclo

pedi

aA

utho

r : O

racle

, Con

fiden

tial

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



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


Table 63. Marketing Events ERD Entities and Tables

Entity Table

Activity S_EVT_ACT

Contract Line Item S_ORDER_ITEM, S_QUOTE_ITEM

Equipment Requirement S_SRC_REQ_EQUIP

Event S_SRC_EVT, S_SRC

Event Cost S_SRC_COST

Event Location S_EVTLOC

Event Registration S_SRC_EVT_REG

Event Session S_SRC_EVT, S_SRC

Event Vendor S_SRC_ORG

Event Venue S_SRC_VENUE


Location Room S_EVTLOC_ROOM


Order S_ORDER


Parent Event S_SRC_EVT, S_SRC



Quote S_DOC_QUOTE

Room Avail Equipment S_EVTLOC_RM_EQP

Travel Participant S_EVT_TRVL_PER

Travel Plan S_EVT_TRVL_PLAN



154

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 63. Marketing Events ERD Entities and Tables

Entity Table



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

��

�



156

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


Table 64. Marketing Plans ERD Entities and Tables

Entity Table



Marketing Event Cost S_SRC_COST

Marketing Event or Activity, Marketing Plan, Other Marketing Plan 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



Figure 65. Marketing Plans

Titl

e : M

arke

ting

Pla

nsA

utho

r : O

racle

, Con

fiden

tial

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



158

Medical Education Event Management This ERD (shown in Figure 66) illustrates the significant entities related to medical education events including plans, subplans, funds, events, sessions, products, and team members (employees). Medical education event planning also supports the allocation and aggregation of medical education budgets and expenditures for individual team members.


Table 65. Medical Education Event Management ERD Entities and Tables

Entity Table

Activity S_EVT_ACT

Event S_ME_EVT_LS

Event Invitee S_ME_EVT_INV_LS

Event Position S_ME_EVT_POS_LS

Fund S_MDF, S_ME_PLN_MDF_LS

Literature S_ME_SES_LIT_LS

Material S_ME_SES_MAT_LS

Period S_PERIOD


Plan S_ME_PLN_LS


Product S_ME_SES_PRD_LS, S_ME_EVT_PRD_LS, S_ME_PLN_PRD_LS, S_PROD_INT

Session S_ME_SES_LS

Session Invitee S_ME_SES_INV_LS



Figure 66. Medical Education Event Management

Title

: M

edic

al E

duca

tion

Eve

nt M

anag

emen

tA

utho

r :

Ora

cle

, Con

fiden

tial

AC

TIV

ITY

LITE

RA

TUR

E

MA

TER

IAL

SE

SS

ION

IN

VIT

EE

EV

EN

T IN

VIT

EE

PE

RS

ON

EM

PLO

YE

E

CO

NTA

CT

EV

EN

T P

OS

ITIO

N

PO

SIT

ION

PR

OD

UC

T

PE

RIO

D

FU

ND

SE

SS

ION

EV

EN

T

PLA

N

in

for

of

team

mem

ber

for

owne

r of

owne

d by

top

plan

for

child

pla

n of

for

sour

ce o

f

for

team

co

mpo

sed

ofsubj

ect

to

for

rele

vant

to

usag

e of

for

havi

ng

com

pose

d of

part

of

havi

ng

spea

ker

at

to invi

ter

of

of

for

to invi

ter

ofof

invi

tee

for

prom

otio

n of

prom

oted

at

prom

otio

n of

prom

oted

at

allo

cate

d fu

nds

by allo

catin

g fu

nds

for

prom

otio

n of

pare

nt o

fch

ild o

f

allo

cate

d to

usin

g



160

ObjectivesThis ERD (shown in Figure 67) illustrates how the Siebel Consumer Goods application supports the objective process as part of retail execution. The retail execution process begins with the creation of an objective. Objectives are generated to help facilitate the process of accomplishing certain goals. This model shows that an objective can be applied to many accounts, including accounts with multiple contacts. There are generally multiple activities that belong to an objective, activities which require follow-through to help bring the objective to fruition. The objective must be executed by personnel who are assigned to the objective, its accounts, and activities.


Table 66. Objectives ERD Entities and Tables

Entity Table


Activity Details S_EVT_ACT


Objective S_SRC

Position S_POSTN



Figure 67. Objectives

Title : OBJECTIVESAuthor : Oracle, Confidential

ACTIVITY DETAILS

POSITION

CONTACTACCOUNT

OBJECTIVE

assigned to

responsible for

has

subject to

target of

for

target of

for



162

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


Table 67. Opportunity Management ERD Entities and Tables

Entity Table

Address S_ADDR_PER




Event S_EVT_ACT

External Organization Unit S_ORG_EXT, S_PARTY

Issue S_ISS

Opportunity S_OPTY

Opportunity Relationship S_OPTY_REL



Product S_PROD_INT

Quote S_DOC_QUOTE

Sales Stage S_STG

Source S_SRC




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



164

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


Table 68. Order Life Cycle ERD Entities and Tables

Entity Table


Invoice S_INVOICE


Opportunity S_OPTY

Opportunity Product S_REVN

Order S_ORDER


Order Part Movement S_ORDPART_MVMT


Quote S_DOC_QUOTE


Shipment S_SHIPMENT



Figure 69. Order Life Cycle

Title

: O

rder

Life

Cyc

leA

utho

r : O

racle

, Con

fiden

tial

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



166

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


Table 69. Orders ERD Entities and Tables

Entity Table

Activity S_EVT_ACT

Asset S_ASSET


Inventory Transaction S_INV_TXN

Inventory Transaction Type S_INV_TXN_TYPE

Order S_ORDER


Order Type S_ORDER_TYPE

Part Movement S_ACTPART_MVMT, S_ORDPART_MVMT

Part Movement Type S_PARTMVMT_TYPE

Party S_PARTY, S_ORG_EXT, S_POSTN, S_CONTACT

Product S_PROD_INT



Figure 70. Orders

Titl

e : O

rder

sA

utho

r : O

racle

, Con

fiden

tial

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



168

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


Table 70. Partner Collaboration ERD Entities and Tables

Entity Table

Business Unit S_BU

Collaboration S_PARTY_GROUP

Collaboration Resource S_PARTY_PER

Collaboration Invitation S_BRDCST_MSG

Party S_PARTY

Position S_POSTN



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

��

�

� �

��

��

�

� �

��

��

�

� �

� ��

��

�



170

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


Table 71. Partner Program Registration ERD Entities and Tables

Entity Table

Application Approval Team S_PRG_APPL_PSTN

Application Attachment S_PRG_APPL_ATT

Application Question Answer S_PRG_APPL_QA

Approval List S_PRTNRPRG_PRTN

Eligibility List S_PRTNRPRG_PRTN

Partner S_ORG_EXT

Partner Program S_PRTNR_PROG

Partner Program Application S_PRTNRPRG_APPL

Partner Program Group S_PRTNRPRG_GRP

Partner Program Membership S_PRTNRPRG_MBR

Program Team S_PRTNRPRG_PSTN

Renew List S_PRTNRPRG_PRTN



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

�



172

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


Table 72. Party Model ERD Entities and Tables

Entity Table



Business Address S_ADDR_PER


Group S_PARTY

Household S_ORG_GROUP, S_PARTY

Organization Relationship S_PARTY_REL


Party S_PARTY

Party Relationship S_PARTY_REL


Person Relationship S_PARTY_REL or S_CONTACT_REL



User List S_PARTY

User Login S_USER



Figure 73. Party Model

��3�" �� Oracle��

�!!��%%

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

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

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

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

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

��+

��&�

9�&%�9�'!

��%��$

&%��'�%�

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

��&$�

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

��9��&�

��%%��&�

��9��+

&%��'��$

��%�$

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

��9��%�$

��

��

��1��

� ��

��

��1��

��

��

��

��

��

��

� �

� ��

� �

� ��

� �

� ��

� �

� ��

6��

��

�

��

��

��



174

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


Table 73. Payments ERD Entities and Tables

Entity Table

Address S_ADDR PER

Invoice S_INVOICE

Order S_ORDER


Party S_PARTY



Prepayment Balance S_PREPAY_BAL



Figure 74. Payments

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



176

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

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


Table 74. Performance Review ERD Entities and Tables

Entity Table

360 Evaluation S_PERF_360_EVAL

Competency S_CMPTNCY

Employee Criteria (PDQ) S_APP_VER, S_RVW_360_CS


Evaluation Script S_CS_PATH, S_CS_PATH_SCPT

Evaluation Script Answer S_CS_RUN, S_CS_RUN_ANSWR

Job Family S_JOB_FAMILY


Party S_PARTY

Performance Measurement Item S_PERF_MEAS_ITM

Performance Review S_EMP_PERF_MEAS

Period S_PERIOD



Review Component S_PERF_RVW_CMP

Review Component Language S_RVW_COMP_LANG

Review For Skill Item S_PERF_CMPTNCY



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 74. Performance Review ERD Entities and Tables

Entity Table



178

Figure 75. 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 76) illustrates how personal accounts (such as financial accounts or insurance policies) are accessible by contacts and associated with accounts, and how addresses are relevant for each of these. Also supported are associations between contacts and the membership of contacts in groups. Opportunities are associated with personal accounts to track the source of existing business.


Table 75. Personal Account ERD Entities and Tables

Entity Table


Activity S_EVT_ACT


Opportunity S_OPTY


Personal Account S_ASSET

Personal Account Contact S_ASSET_CON


Product S_PROD_INT




180

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


Table 76. Personal Financial Review ERD Entities and Tables

Entity Table

Activity S_EVT_ACT

Activity Product Instance S_ACT_ASSET

Asset (Liability) S_FN_ASSET_LIAB

Asset (Liability) Contact S_FN_ASSET_LIAB_CON


Contact Relationship S_CONTACT_REL

Financial Need S_FN_NEED

Financial Recommendation S_FN_RCMD

Household/Account S_ORG_GROUP, S_PARTY

Income (Expense) S_FN_INCM_EXP

Income (Expense) Contact S_FN_INCM_EXP_CON

Need Contact S_FN_NEED_CON

Opportunity S_OPTY


Product S_PROD_INT

Product Instance S_ASSET

Product Instance Contact S_ASSET_CON

Received Product Instance S_FN_RCMD_ASSET

Recommendation Contact S_FN_RCMD_CON



182

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



Personalized Content DeliveryThe Personalized Content Delivery feature allows pharmaceutical sales representatives to deliver a sales communication to general practitioners and medical specialists using multimedia visualizations. This ERD (shown in Figure 78) illustrates how a Message Plan is associated to Messages, Products Presentation Details and Party Entities such as Account, Contact, Position and Business Unit.


Table 77. Personalized Content Delivery ERD Entities and Tables

Entity Table


Activity S_EVT_ACT, S_EVT_ACT_LSX

Assessment Template S_TMPL_PLANITEM

Business Unit S_PARTY, S_BU


Decision Issues S_ISS

Message S_LIT, S_LIT_LSX

Message Product Application S_LIT_PROD_APPL

Messaging Plan S_MSG_PLAN

Messaging Plan Item S_MSGPLAN_ITM

Objective S_SRC

Offer S_DMND_CRTN_PRG

Period S_PERIOD

Position S_PARTY, S_POSTN

Presentation Details S_PCD_DETAIL

Product S_PROD_INT



184

Figure 78. Personalized Content Delivery

Title

: L

S P

ers

on

aliz

ed

Co

nte

nt

De

live

ryA

uth

or

: O

racle

, C

on

fid

en

tia

l

AS

SE

SS

ME

NT

TE

MP

LA

TE

ME

SS

AG

ING

PL

AN

IT

EM

DE

CIS

ION

IS

SU

ES

ME

SS

AG

E P

RO

DU

CT

A

PP

LIC

AT

ION

PR

OD

UC

T

ME

SS

AG

E

AC

TIV

ITY

PR

ES

EN

TA

TIO

N

DE

TA

ILS

PA

RT

Y

CO

NT

AC

T

AC

CO

UN

T

PO

SIT

ION

BU

SIN

ES

S

UN

IT

OF

FE

R

PE

RIO

D

OB

JE

CT

IVE

ME

SS

AG

ING

P

LA

N

for

ha

s

pe

rio

d o

f

pe

rio

d f

or

ha

s

for

ha

s

for

pa

ren

t o

f

ch

ild o

ffo

rh

as

pa

ren

t o

f

ch

ild o

fp

are

nt

of

ch

ild o

f

ha

s

for

for

asso

cia

ted

to

asso

cia

ted

to

ha

s

asso

cia

ted

to

for

ha

s

for

ha

s

for

for

ha

s

asso

cia

ted

to

for

ha

s

for

ha

s

for

cre

ato

r o

f

cre

ate

d b

y

ha

s

for

ha

s

for

asso

cia

ted

to

for

asso

cia

ted

to

for

ha

s

for



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

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


Table 78. Pricing Comparison ERD Entities and Tables

Entity Table


Object Class Extended Attribute S_XA_ATTR

Opportunity S_OPPTY



Pricing Matrix S_PRI_MTRX

Pricing Matrix Item S_PRI_MTRX_ITEM

Product Extended Attribute S_PROD_INT_XA


Product or Service Structure S_PROD_ITEM

Quote S_DOC_QUOTE


Quote Item Extended Attribute S_QUOTE_ITEM_XA

Tier Price Value S_VDISCNT_ITEM

Tier Pricing S_VOL_DISCNT



186

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


Table 79. Pricing ERD Entities and Tables

Entity Table

Component Price Adjustment S_PRI_CFG_ITEM


Object Class Extended Attribute S_XA_ATTR



Pricing Factor Item S_PRIFCTR_ITM

Pricing Factor Item Attrib S_PRIFCTITM_ATR

Pricing Matrix S_PRI_MTRX

Pricing Matrix Attribute S_PRI_ATTR

Pricing Matrix Item S_PRI_MTRX_ITEM

Pricing Matrix Value S_PRI_MTRX_VAL

Pricing Model S_PRIMDL

Pricing Model Factor S_PRIMDL_FCTR

Product Extended Attribute S_PROD_INT_XA


Product or Service Structure S_PROD_ITEM



188

Figure 80. Pricing

Titl

e : P

ricin

gA

utho

r : O

racle

, Con

fiden

tial

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 81) provides a system for managing product promotions. Production Promotion allows the user to fully define the promotion based on products, product templates, product attributes, and so on. Product Promotion also allows the user to specify other information for the promotion including the terms, charges, and pricing rules.


Table 80. Product Promotion ERD Entities and Tables

Entity Table

Conditional Charge Prorate Plan S_AGR_PR_PLAN

Product Promotion S_PROD_INT

Product Promotion Charge S_PROM_CHRG

Product Promotion Item S_PROM_ITEM

Product Promotion Item Attribute S_PROM_ITEM_XA

Product Promotion Item Attribute Value S_PROMITM_VAL

Product Promotion Pricing Matrix Rule S_PROM_PMTRX

Product Promotion Term S_PROMITM_TRMS

Product Promotion Term Description S_PROD_TRM_DESC



190

Figure 81. 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 82) illustrates the significant entities related to product defect tracking. Defects can be associated with service requests and may have associated activities defined to fix the defect. Associations may be defined with various product or product versions to record which are affected by the defect, which are planned to fix the defect, and which actually fix the defect. Additional relevant associations with external products may be recorded. Defects may be associated with other, related defects.


Table 81. Product Quality Tracking ERD Entities and Tables

Entity Table

Activity S_EVT_ACT

Defect Symptom S_PRDFCT_SYMP



Product or Service S_PROD_INT, S_PROD_EXT

Product Quality Item S_PROD_DEFECT

Project S_PROJ

Project Item S_PROJITEM

Resolution Item S_RESITEM




192

Figure 82. 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 83) provides a system for managing product recommendations for up-sell or cross-sell. Product Recommendation allows the user to clearly define the messages, the set of possible responses, and the recommendation itself.


Table 82. Product Recommendation ERD Entities and Tables

Entity Table

Communication S_COMMUNICATION

Product Message S_PROD_MSG

Product Message Response S_PROD_MSG_RESP

Product Message Variable S_PROD_MSG_VAR


Product Recommendation S_PROD_RECMNDTN



194

Figure 83. 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 84) illustrates the significant entities related to a product including product components (product structure), substitute or competitive products (product comparison), the product's vendor, the product line or lines to which the product belongs, and so on. In addition, this diagram illustrates the relationship between products and product prices, as well as the language translations for some of these entities.


Table 83. Products or Services ERD Entities and Tables

Entity Table

Catalog S_CTLG


Class Attribute S_XA_ATTR

Class of Product or Service S_VOD, S_VOD_VER

Language S_LANG



Product Assembly Port S_PROD_ITEM


Product or Service S_PROD_INT or S_PROD_EXT

Product or Service Attribute S_PROD_INT_XA

Product Structure S_PROD_ITEM

Vendor S_ORG_EXT, S_PARTY



196

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


Table 84. Professional Services ERD Entities and Tables

Entity Table

Activity S_EVT_ACT

Address S_ADDR_PER

Billing Rate List S_PRI_LST


Internal/Partner Organization S_ORG_EXT, S_PARTY

Invoice S_INVOICE

Lead Source S_SRC

Opportunity S_OPTY




Potential Project Resource S_PROJ_PTL_RSRC

Project S_PROJ

Project Contact S_PROJ_CON

Project Issue S_PROJ_ISS


Skill S_PROJRSRC_SKL



198

Figure 85. Professional Services

Titl

e : P

rofe

ssio

nal S

ervi

ces

Aut

hor

: O

racle

, Con

fiden

tial

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



Public Sector Case Lead ManagementThis ERD (shown in Figure 86) illustrates how an investigative lead is related to incident and case. It shows how a party, such as a person, organization, or group, becomes involved in the investigative lead, and the positions of team members assigned to work on it. This ERD also shows evidence/supporting documentation as the trigger of the investigative lead. The physical object used, location of the investigative lead, as well as the related activity, disease, and service request are shown. This ERD covers the features of applications received from users and their supporting documents as well as their visibility to various organizations.

New features in 8.1 include:

■ Submitted applications are reviewed on the Siebel side and information uploaded from the applications into Siebel objects such as case and contacts.

■ Applications received from users/citizens for benefits, visa, immigration, and so forth are taken into account. The supporting documents for a given application, as well as any scanned images of the application, are stored in file systems. The visibility of an application to various organizations is also managed.

■ Data from the application form, as filled out by the citizen or employee, is transferred to the Siebel application so that the agency has a historical record of the data as submitted at that point in time. Employees will then upload the application into the system. During the upload process, relevant data from the form(s) is imported into the appropriate Siebel contact, household and case records.


Table 85. Public Sector Case Lead Management ERD Entities and Tables

Entity Table

INVESTIGATIVE CASE LEAD S_CASE_LEAD

PARTY S_PARTY

PERSON S_CONTACT, S_USER, S_CONTACT_PSX

ORGANIZATION/GROUP S_ORG_EXT, S_ORG_GRP_PSX

POSITION S_POSTN

ADDRESS S_ADDR_PER

SERVICE REQUEST S_SRV_REQ

ACTIVITY S_EVT_ACT

CASE S_CASE, S_CASE_PSX

PHYSICAL OBJECT S_ASSET

DISEASE S_DISEASE

EVIDENCE/SUPPORTING DOCUMENT S_EVIDENCE

INCIDENT S_INCIDENT

PERSON DESCRIPTION S_SUBJECT



200

APPLICATION S_PS_APPL

APPLICATION ATTACHMENT S_PS_APPL_ATT

APPLICATION/BUSINESS UNIT VISIBILITY S_PS_APPL_BU

Table 85. Public Sector Case Lead Management ERD Entities and Tables

Entity Table



Figure 86. Public Sector Case Lead Management

Title

: P

ublic

Secto

r C

ase L

ead M

anagem

ent

Auth

or

: O

racle

, C

onfidential

AP

PLIC

AT

ION

AP

PLIC

AT

ION

B

US

INE

SS

UN

IT

AP

PLIC

AT

ION

A

TT

AC

HM

EN

T

INC

IDE

NT

SE

RV

ICE

R

EQ

UE

ST

PH

YS

ICA

L O

BJE

CT

PE

RS

ON

DE

SC

RIP

TIO

N

IN

VE

ST

IGA

TIV

E L

EA

D

AC

TIV

ITY

AD

DR

ES

S

PA

RT

Y

PO

SIT

ION

OR

GA

NIZ

AT

ION

/GR

OU

P

SU

SP

ICIO

US

G

RO

UP

OT

HE

R

OR

GA

NIZ

AT

ION

AG

EN

CY

PE

RS

ON

SU

SP

EC

T A

GE

NT

OT

HE

R

PE

RS

OND

ISE

AS

E

EV

IDE

NC

E / S

UP

PO

RT

ING

DO

CU

ME

NT

CA

SE

is r

ela

ted to

has

rela

ted to

has v

isib

ility

to

rela

ted to

has

is r

ela

ted to

is v

isib

le to

part

of

com

posed

of

rela

ted w

ith

involv

ed in

matc

hin

g w

ith

for

for

subje

ct

of

for

has

conducte

d for

initia

tion o

f

targ

et at

subje

ct of

appro

ved b

y

appro

ver

of

investigate

d b

y

assig

ned to

responsib

le for

responsib

ility

of

genera

ted b

y

serv

iced thro

ughs

erv

iced thro

ugh

genera

ted b

y

genera

ted b

y

serv

iced v

ia

for

support

ed b

y

for

rela

ted to

serv

iced thro

ugh

genera

ted b

y

rele

vant to

associa

ted w

ith

locate

d in

for

based o

n

subje

ct fo

r for

rela

ted to

addre

ss for

location o

f

for

support

ed b

y

basis

for

trig

gere

d b

y

rela

ted to

lead to

subje

ct of

for

associa

ted w

ith

the u

se o

f

rele

vant to



202

Public Sector Contact IdentityPublic Sector Contact Identity (shown in Figure 87) allows you to track the identity of an individual, including personal attributes, marital status changes, place of residence, and so on over time so that the responsible organization can react swiftly to the legality of the individual. Public Sector Contact Identity also tracks the entry and departure information of the individual into and out of the country. Public Sector Contact Identity is used mainly for the purposes of homeland security.


Table 86. Public Sector Contact Identity ERD Entities and Tables

Entity Table

IDENTITY S_PS_IDENTITY

CREDENTIAL S_PS_CREDENTIAL

STAY S_PS_STAY_LOG

PUBLIC SECTOR CONTACT S_PS_CONTACT

ORGANIZATION/GROUP S_ORG_EXT, S_BU

PARTY, CONTACT S_PARTY, S_CONTACT



Figure 87. Public Sector Contact Identity

��

��

�1

��%

��

��

�

��

��

��3

��

��

��

Ora

cle

��

�

��

��

��

�

��

�

$�[

��

��$

0�

�&

�

�%%

&�$

��

�

$

+�

�9

��

%�

��

��

*��

$�

�+

%�

�+

��

��

�>�

'��

%

��

!�

$�

��'

��

��

�

��

+�

!��

��

!�

$�

��'�$

&"

��%

%&

�$

�

�&

$�

�+

��

%%

��

��

>�%

�

�&

.'

��%

�

��

��

�$

��

�

��

��

+

�

$�

�

�

�!�

$�

��+

��!

�$

��

+�$

&"

��

��

��

�

� �

��

��

��

� �

��

6�1

3

��

6

��

6�1

3

��

6

��

��1

3

��

�

��

��

��

��

��

��

�

� �

��

�

� �

��

�

1

��

�13

�

��

��

�

��

��1

3

��

2�



204

Public Sector Evidence ManagementThis ERD (show in Figure 88) illustrates how evidence and supporting documents are related to the incident and case and acts as the trigger of the investigative lead. It shows how a party, such as a person, organization, or group, is included in the evidence and supporting documents. The ERD describes the positions of team members assigned to handle the incident and approve the documents. This ERD also shows how the items are supported by the documents. The location of the incident, physical object used in the incident, as well as the activity and service request related to the evidence are shown.


Table 87. Public Sector Evidence Management ERD Entities and Tables

Entity Table

EVIDENCE/SUPPORTING DOCUMENT S_EVIDENCE

PARTY S_PARTY

PERSON S_CONTACT, S_USER

ORGANIZATION/GROUP S_ORG_EXT

POSITION S_POSTN

ADDRESS S_ADDR_PER


QUOTE ITEM S_QUOTE_ITEM

ORDER ITEM S_ORDER_ITEM

QUOTE S_DOC_QUOTE

ORDER S_ORDER


ACTIVITY S_EVT_ACT

INVESTIGATIVE LEAD S_CASE_LEAD

INCIDENT S_INCIDENT

CASE S_CASE



Figure 88. Public Sector Evidence Management

��

��

�1��

�%��

��

2��

��"

��

��

��

��

��O

racle

��

��

�

��>

��+

�9

+%

��

'�

�.

=�

�

��$

>�

%�

��

��>

��

'�

�!

%�

�>

��

��

�7

&�

%�

�

%�

�$

�!�

$�

�>

�!�

$

��0�%

&�

��

��

�$

�!�

&

"�

$�

��

��

+

��

%��

��$

��

�

$�[

��

��$

0�

�&

�

9�

&%

�9

�'!

��

9�

��

��

�

$�[

��

��$

�%&

%�

��

&%

�

��

&�

��

�$

+

��

�%

�$

��

�$

��%

&%

��

�

��

9�

��

��

%�

$

��!

!�

�%

%

7&

��

��

�"

7&

��

�

��

!�

��

�"

��

!�

�

��

��6

��

��2 �2

��

� ��1

3

��1�

��

��

�

��

� �

� �

� ��

�1��

�

��14�

��

�

1��

��

�

� ��

��

�

� �

��

��

��

��

��

��

��

��

��1

3

��2

��

��

� �

� ��

��

�� 1��

��?��

��

��1

3� �

� ��

�

� �

��

��

��

��

��

��

��1

3

1��

��

1��

�

��

2��1

3

��

2��

�

��

��1

3

6

��

�

�� 1

��3

� �

�� 1

��

� �

��2�

� �

��

��

�

��

� �

��

��

�

��

��6

��

��2 �2

��

� �

��

��1

3

� ��

��

�� 1��

��

��

��

��1

3

� ��

��

�

� ��

� �

��2

��

��

1��

��

��

��

��1

3

��

��

� ��

�

� �

� �

� ��

�

� �

��2

��

��

� �

��

��1

3

��

��2��

��

��

��

��



206

Public Sector Incident ManagementThis ERD (shown in Figure 89) illustrates how an incident is related to investigative lead and case. It shows how a party, such as a person, organization, or group, becomes involved in the incident in different roles such as victim, offender, witness, suspect, or owner of the incident. It includes the offense committed and any arrest initiated by the incident or case. The physical object used in the offense, arrest, and incident, as well as the activity and the service request related with the incident, are also shown.


Table 88. Public Sector Incident Management ERD Entities and Tables

Entity Table

INCIDENT S_INCIDENT

PARTY S_PARTY

PERSON S_CONTACT, S_USER

ORGANIZATION/GROUP S_ORG_EXT

INCIDENT ACCOUNT S_INCIDNT_ACCNT

INCIDENT CONTACT S_INCIDENT_CON

INJURY S_INCTCON_INJRY

INCIDENT VICTIM TYPE S_INCDNT_VCTMTP

CIRCUMSTANCE S_CIRCUMSTANCE


ACTIVITY S_EVT_ACT

INVESTIGATIVE LEAD S_CASE_LEAD

CASE S_CASE


ARREST S_ARREST

ARREST FORCE S_ARREST_FORCE

OFFENSE S_OFFENSE

OFFENSE CRIMINAL ACTIVITY S_OFFENSE_ACT



Figure 89. Public Sector Incident Management

��

��

�1��

�%��

��

��

��"

��

��

��

��

��O

racle

��

��

�*

*�

$%

��

��"

�$�

'��

�

�>��

+

�$

�!�

$�

��

�

&$

�

;��

$�

%%

��

�&

$�

��

9�

��

�$

�!�

$�

��

�&

$�

�$

�!�

$�

�%

&%

��

��&

%�

�

�&

�

�$>

�%

��

��

�$

��

�

&$

�

�*

*�

$!

��

��

�

&$

�

>�

��"

��

�

&$

�

�$

�!�

$�

�>

��

�"��

+�

�

�9

+%

��

'��

.=�

�

��$

>�

%�

��

��>

��

'�

�!

�

%�

�$

�!�

$�

��

$�

�

��$

�!

�$

��

%&

%�

�

�

��

9�

��$

�!

�$

��

�$

��

�

�$

�!�

$�

�;��

$�

%%

�$

�!�

$�

��

**

�$

!�

��$

�!

�$

��

>�

��"

�$>

�%

��

��

�$

��

�

$�

��

&

"%

��

$

�

��

��

+��

��

%�

$

�%&

%�

�

��

�9

��

��

��

%�

$��

�

$�

��

�

$�[

��

��$

0�

�&

�

��

9�

��

��

�

$�[

��

��$

��

�$

+

�%&

%�

��

&%

�

��

&�

%�

�>

��

��

�7

&�

%�

�

��>

��+

��

��

%�

�*�

�

�

�$=&

�+

��

��

%�

�*

*�

$%

�

�$

�!�

$�

� ��

��

��

��

�

� �

��

��

�

��14�

��

� �

� �

��

��

� �

��2 �2

��

�

��

��

��14�

��

��2 �2

��

��

��

� �

��2 �2

��

�

��1

3

� �

� ��

��

��

��

�

��

��

��14�

��

� �

��

��

��

� �

��

��

�

��

��

��6

��

� �

��

��6

��

��

� �

��

��

��

� �

� ��

�

��

��

��

��

��

� �

�

��

��

��

��

��6

��

1��

��

1��

�

� �

��14�

��

� �

��2

��

��

��

��1

3�

��

��

��

2 �2

��

��14�

��

�

� �

��

��6

��

��

� �

��

��6

��

��

� �

� ��

�

� �

��

��

��



208

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


Table 89. Revenue ERD Entities and Tables

Entity Table


Agreement Item S_AGREE_ITEM

Invoice S_INVOICE

Invoice Item S_INVC_ITEM


Opportunity S_OPTY






Project S_PROJ

Revenue Item S_REVN

Revenue Template S_REVN_TMPL

Revenue Template Item S_REVN_TMPL_ITM




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



210

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


Table 90. Routes and Best Call Hours ERD Entities and Tables

Entity Table

Best Call Hour S_BEST_CALL_HRS

Organization External S_ORG_EXT, S_PARTY

Route S_ACCNTRT



Figure 91. Routes and Best Call Hours

Title : Routes and Best Call Hours Author : Oracle, Confidential


RETAILER

OTHER ORGANIZATION

SYNDICATE GROUP

STORE

BEST CALL HOUR ROUTE

defined for

appear onfor

have

part of

made up of



212

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 92) consists of sales territories, which are made up of positions and crediting rules. The sales hierarchy can be versioned to accommodate ongoing changes without losing track of its history. A position can be assigned to different territories or the same territory with different start date and end date. A crediting rule can be applied to positions with allocation percentage defined. For a given hierarchy version, the credit assignment engine is able to identify all the positions assigned to the territories and all the applicable crediting rules by effective start date and end date. The crediting rules, their criteria and values are read by Siebel Assignment Manager, which performs the assignments appropriately. The sales hierarchy needs to be approved and validated before taking effect.


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

Entity Table

Credit Allocation S_SLSCR_RL_PSTN

Credit Assignment Rule S_SLSCRDT_RULE

Credit Rule Criteria S_SLSCRDT_CRIT

Credit Rule Criteria Value S_SLSCRDT_VAL

Hierarchy Version S_SLS_HIER_VER

Hierarchy Version Territory S_SLS_HIER_TERR


Position Territory Assignment S_SLSTERR_POSTN

Sales Hierarchy S_SLS_HIER

Sales Territory S_SLS_TERR



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



214

Sales Volume PlanningThis ERD (shown in Figure 93) illustrates how Siebel Business applications (Consumer Goods) support sales volume planning (SVP). A sales volume plan is the targeted sales volume (cases or currency) for a period. This volume is calculated based on historical data within a period. Algorithms used to calculate the SVP could be a flat percentage change over a period, or it could be a trended volume. While planning, an authorized employee may allocate down an account, or an account product category tree. Prior to allocating, historical data must be aggregated up these trees. After the initial aggregation, allocation and aggregation may occur any number of times until the plan is committed or until historical data within the plan's period is entered into the application.


Table 92. Sales Volume Planning ERD Entities and Tables

Entity Table


Authorized Product Detail S_ORG_DIST_LST

Category S_CTLG_CAT

Category Baseline S_CG_CAT_BASELN

Consumption Category S_CG_CAT_CONSUM

Employee S_CONTACT, S_PARTY

External Organization S_ORG_EXT, S_PARTY



Period S_PERIOD

Planned Volume S_PROD_BASELINE, S_CG_CAT_BASELN, S_PROD_TARGET, S_CG_CAT_TARGET

Product Baseline S_PROD_BASELINE

Product Consumption S_PROD_CONSUME


Product Shipment S_PROD_SHIPMENT

Product Target S_PROD_TARGET

Sales Volume Planning Action S_CG_SVP_ACTION

Shipment Category S_CG_CAT_SHIP

Target Category S_CG_CAT_TARGET



Figure 93. Sales Volume Planning

Title : Sales Volume PlanningAuthor : Oracle, Confidential

PRODUCT MOVEMENT

CATEGORY BASELINE

PRODUCT TARGET

PRODUCT CONSUMPTION

PRODUCT SHIPMENT

PRODUCT BASELINE

CATEGORY TARGET

CATEGORY CONSUMPTION

CATEGORY SHIPMENT

AUTHORIZED PRODUCT

AUTHORIZED PRODUCT DETAIL

MARKETING EVENT

PERIOD

CATEGORY

F-GROUP

PRODUCT INTERNAL


RETAILER

SYNDICATE GROUP

SUPPLIER

STORE

OTHER ORGANIZATIONpart of

composed of

have

exist for

exist for

have

exist for

have

of

subject of

at

subject offor

has

have

for an

part of

made up of



216

Sample ManagementThis ERD (shown in Figure 94) illustrates how product samples can be tracked in inventory. Inventory is for a particular employee and for a specified period. All transactions involving samples such as disbursement, shipments, and sample orders can be tracked and each active inventory period can be reconciled after a physical inventory count.

Use of samples for product promotion by pharmaceutical companies around the world is governed by local country legislation. The Life Science Sampling, Sample Management and Compliance feature details requirements for sample management and compliance processes in a pharmaceutical company to ensure that the company’s processes comply with regulations. Sample Audit and Compliance Administration functionality enables companies to adhere to government guidelines.


Table 93. Sample Management ERD Entities and Tables

Entity Table

Audit Report Attachment S_INVADTRPT_ATT

Call S_EVT_ACT




Inventory Audit Report S_INV_AUDIT_RPT

Order Item S_SMPL_TXN_ITEM

Person S_CONTACT, S_PARTY, S_USER

Product Inventory S_STOCK_EMP

Sample Order S_SAMPLE_TXN

Sample Transaction S_SAMPLE_TXN

Sample Transfer S_SAMPLE_TXN

Signature Audit S_EMP_AUDITSIGN

Stock Period S_STK_PERD_EMP

Transaction Attachment S_SMPL_TXN_ATT

Transaction Item S_SMPL_TXN_ITEM

Transfer Item S_SMPL_TXN_ITEM

Validation Result S_VALDN_RESULT



Figure 94. Sample Management

Title

: S

am

ple

Ma

na

ge

me

nt

Au

tho

r :

Ora

cle

, C

on

fid

en

tia

l

SIG

NA

TU

RE

A

UD

IT

TR

AN

SA

CT

ION

A

TT

AC

HM

EN

T VA

LID

AT

ION

R

ES

UL

T

AU

DIT

RE

PO

RT

A

TT

AC

HM

EN

T

INV

EN

TO

RY

AU

DIT

RE

PO

RT

PE

RS

ON

EM

PL

OY

EE

CO

NT

AC

T

TR

AN

SF

ER

IT

EM

INT

ER

NA

L P

RO

DU

CT

ST

OC

K P

ER

IOD

PR

OD

UC

T I

NV

EN

TO

RY

TR

AN

SA

CT

ION

IT

EM

SA

MP

LE

TR

AN

SA

CT

ION

SA

MP

LE

TR

AN

SF

ER

SA

MP

LE

OR

DE

RO

RD

ER

IT

EM

CA

LL

for a

sso

cia

ted

with

for

asso

cia

ted

w

ith

asso

cia

ted

w

ith co

nsis

ts o

f

for

su

bje

ct

of

asso

cia

ted

with

co

nsis

ts o

f

ow

ne

d b

y

ow

n

be

lon

gs t

oP

ers

on

lis

t fa

cto

r

tra

nsfe

rre

d b

y

tra

nsfe

r

be

lon

gin

g t

o

of

be

lon

gin

g t

o

of

ow

ne

d b

y

ow

ntr

an

sfe

rre

d b

y

tra

nsfe

r

ow

ne

d b

y

ow

n

tra

nsfe

rre

d b

y

tra

nsfe

r

ow

ne

d b

y

ow

n

tra

nsfe

rre

d b

y

tra

nsfe

r

ow

ne

d b

y

ow

n

for

inve

nto

rie

d in

for

co

mp

ose

d o

f

for

co

mp

ose

d o

f

be

lon

gin

g t

o

for

ad

justm

en

t o

fa

dju

ste

d f

rom

be

lon

gin

g t

oo

fite

ms o

f

co

mp

ose

d o

f

dro

pp

ed

at

dro

p o

f



218

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


Table 94. Service Agreement ERD Entities and Tables

Entity Table



Agreement Entitlement S_ENTLMNT

Agreement Item S_AGREE_ITEM

Asset S_ASSET


Entitled Product or Asset S_ENTLMNT_ITEM

Entitled Service S_ENTL_ACT_TYPE

Expense Type S_EXP_ITEM_TYPE

Material S_PROD_INT

Order S_ORDER

Preventive Maintenance S_PM_PLNITM

Price Adjustment S_ENTL_PRDPRI

Product S_PROD_INT

Service Calendar S_SCHED_CAL

Service Metric S_SVC_METRIC


Work Type S_PROJ



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



220

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


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

Entity Table

Employee S_CONTACT, S_EMP_PER, S_PARTY

Employee Exception Hours S_EXCPT_CAL_HRS

Exception Calendar S_EXCPT_CAL

Exception Calendar Hours S_EXCPT_CAL_HRS


Schedule Calendar S_SCHED_CAL

Schedule Calendar Hours S_SCHED_CAL_HRS

Service Calendar S_SCHED_CAL

Work Shift S_SCHED_CAL



Figure 96. Service Calendars and Work Shifts

Title : Service Calendars and Work 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



222

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


Table 96. Service Request ERD Entities and Tables

Entity Table

Activity S_EVT_ACT

Asset (Product Instance) S_ASSET

External Product Instance S_ORG_PRDEXT

Party S_PARTY, S_ORG_EXT, S_CONTACT, S_USER

Product or Service S_PROD_INT, S_PROD_EXT

Service Region S_SRV_REGN



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



224

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


Table 97. Shipment ERD Entities and Tables

Entity Table


Order S_ORDER, S_ORDER_SHIP

Order Item Delivery Request S_ORDPART_REQ

Order Line Item S_ORDER_ITEM

Order Part Movement S_ORDPART_MVMT, S_SHIPMENT_MVMT

Part Movement Type S_PARTMVMT_TYPE


Quote S_DOC_QUOTE, S_DOC_ORDER

Quote Item Delivery Promise S_QTE_ITM_DLVRQ

Quote Item Delivery Request S_QTE_ITM_DLVRQ

Quote Line Item S_QUOTE_ITEM

Shipment S_SHIPMENT



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

�

��

� �

� �

� ��

�

�

��

�

� ��

��

�

� ��

��

�

��

��

��

��

��

� �

��

��

��

��

��

��

��

��

��

��

��



226

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


Table 98. Siebel Assistant ERD Entities and Tables

Entity Table


Activity S_EVT_ACT

Activity Plan S_EVT_ACT

Activity Plan Template S_TMPL_PLANITEM

Assessment Template S_TMPL_PLANITEM

Assessment S_ASSESS

Assessment Attribute S_ASSESS_ATTRIB

Assessment Attribute Valid Value S_ASSESS_ATTVAL



Opportunity S_OPTY

Opportunity Stage S_OPTY_STG


Sales Methodology S_SALES_METHOD

Sales Stage S_STG

Stage Plan Item S_STG_PLANITEM

Stage Recommendation S_STG_RECOMMEND

Template Activity S_EVT_ACT



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



228

Syndicated DataThis ERD (shown in Figure 100) illustrates how the syndicated data (sales and prescription information) is associated with a period, plan, account, contact, postal code, territory, and area.


Table 99. Syndicated Data ERD Entities and Tables

Entity Table



Period S_PERIOD

Plan S_INS_PLAN


Postal Code S_ZIPCODE

Product S_PROD_INT

Region S_REGION

Syndicated Data S_SYND_DATA




Figure 100.Syndicated Data

Title

: S

yndi

cate

d D

ata

Aut

hor

: Ora

cle,

Con

fiden

tial

AR

EA

PR

OD

UC

T

TER

RIT

OR

Y

PO

STA

L C

OD

E

SY

ND

ICA

TED

DA

TA

SA

LES

PR

ES

CR

IPTI

ON

PO

SIT

ION

PLA

N

CO

NTA

CT

PE

RIO

D

AC

CO

UN

T

in

for

for

subj

ect o

f

of

for

in

for

for

subj

ect o

f

for

reci

pien

t of

for

subj

ect o

f

for

subj

ect o

f

for

subj

ect o

f



230

Teller AdministrationThis ERD (shown in Figure 101) illustrates how Siebel Financial Services supports the administration of a tellers activities at a financial institution branch. A set of employee, transaction, and container limits are defined for each branch, as well as a multiple containers. Each teller is associated with a set of containers, where they execute different activities and service requests for the customer.


Table 100. Teller Administration ERD Entities and Tables

Entity Table

Activity S_EVT_ACT

Activity Batch S_FN_ACT_BATCH

Activity Settle S_FN_ACT_SETTL

Bait S_FN_BAIT


Container S_FN_CONTAINER

Container Limits S_FNCONTNR_LMTS


Employee Teller Limits S_EMP_TLR_LMTS

Holdover S_FN_TXN_HLDVR, S_FN_HLDVR_CTF




Transaction Limits S_FN_TXN_LMTS



Figure 101.Teller Administration

Titl

e : T

elle

r A

dmin

istr

atio

nA

utho

r :

Ora

cle,

Con

fiden

tial

PA

RT

Y P

ER

SO

N

C

ON

TA

CT

EM

PLO

YE

E

OR

GA

NIZ

AT

ION

UN

IT

BR

AN

CH

SE

RV

ICE

R

EQ

UE

ST

LIN

EIT

EM

BA

IT/T

RA

P

SE

TT

LEM

EN

TB

AT

CH

A

CT

IVIT

Y

HO

LDO

VE

R

CA

LEN

DA

R

TR

AN

SA

CT

ION

LIM

ITS E

MP

LOY

EE

T

ELL

ER

LIM

ITS

TR

AN

SA

CT

ION

LI

MIT

SC

ON

TA

INE

R

LIM

ITS

SE

RV

ICE

R

EQ

UE

ST

AC

TIV

ITY

CO

NT

AIN

ER

DR

AW

ER

BA

TC

HV

AU

LTB

IN

asso

ciat

ed w

ith

from

part

of

incl

udes

asso

ciat

edw

ith

has

has

for

used

by

has

to

from

gene

rate

dbyge

nera

tes

from

to

asso

ciat

ed

with

has

asso

ciat

ed

with

has

for

has

for

has

asso

ciat

ed

with

has

asso

icat

ed

with

has

asso

icat

ed

with

has

mad

e up

of

part

of

incl

udes

subj

ect

of



232

Territory Alignment–Quota AssignmentThis ERD (shown in Figure 102) shows how to set up territory alignment to determine if the end results of quota assignments are expected. It covers assigning quotas to alignments, breaking these assignments down by contacts, accounts, regions, or ZIP codes and changes included in a given alignment.


Table 101. Territory Alignment–Quota Assignment ERD Entities and Tables

Entity Table

Sales Quota S_SLS_QUOTA

Territory S_TERRITORY

Alignment Terr Quota S_ALGN_QTA_TERR

Alignment Terr/Qta Breakdown S_ALGN_QT_BRKDN

Period S_PERIOD

Alignment Quota S_TERRALGN_QTA

Territory Alignment S_TERRALGN

Contact/Terr Mapping Change S_TERRALGN_CON

Con/Quota Change S_ALGN_QTA_CON

Account/Terr Mapping Change S_TERRALGN_ACCT

Accnt/Quota Change S_ALGN_QTA_ACCT

Geo/Terr Mapping Change S_TERRALGN_REGN, S_TERRALGN_ZIP



Figure 102.Territory Alignment–Quota Assignment

��

��

��

��

�3��

��

��

��

�7�

��

��

��

��

��

��

��

��O

racle

��

�

��

��

��

�

�

$07

&�

��

�

9�

$

�

�

�07

&�

��

�

9�

$

�

�

$

�07

&�

��

�

9�

$

�

�'

�$

"�

$�

��

��

07�

��.

��

�<

!�

;$

�

�0�

��

��"

��

��$

�

9�

$

�

�

$�

�

�0�

��

��

"�

��

�$

�9

�$

�

�

�

&$

�0�

��

��

"�

��

�$

�9

�$

�

�'

�$

"�

$�

��

��

�7&

��

��

�'

�$

"�

$�

�7&

��

�

��

��

!

��

��

��

�+

�9

��

��

9

+�

��

��

��

+�

�'

�$

"�

$�

%�

'�

%�7

&�

��

��

��

��

�+

��

��

�

��

��

��

� �

� �

�

��

��

��

�

��

��

��

��

��

� �

�

��

��

��

�

��

��

��

��

��

� �

�

��

��

��

�

� �

�

��

��

��

�

� �

�

��

��

��

�

��

��

��

��

��

� �

�

��

��

��

�

��

��

��

2�

�

� �

� �

1��

�5�

6

��

�

��

��

��

��

�2�

��

��

��

��

�

� �

��

��

��

��

�

��

14�

��

�

� �

�

��

��

��

�

��

��

��

��

�

��

��

�2��



234

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


Table 102. Territory Management ERD Entities and Tables

Entity Table

Account S_ORG_EXT

Account Team Member S_ACCNT_POSTN

Account/Terr Mapping S_TERR_ACCNT

Asset S_ASSET

Asset Team Member S_ASSET_POSTN

Asset/Terr Mapping S_TERR_ASSET

Business Unit S_BU

Contact S_CONTACT

Contact/Terr Mapping S_TERR_CON

Contact Team Member S_POSTN_CON

Division S_ORG_EXT

Geo/Terr Mapping S_TERR_ZIP, S_TERR_REGION

Position S_POSTN

Position Territory Assignment S_TERR_POSITION

Region S_REGION


Territory Hierarchy S_TERR_HIER

Territory Version S_TERRHIER_NODE

Zipcode (None)



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

��

��

�

��

��

��

�

��

��

�

�

��

��

�

�

��

��

�

�

�

��

��

��

�

��

��

��

��

��

��

�

�

��

��

��



236

Territory Management - Consumer SectorTerritory Management - Consumer Sector (CS), shown in Figure 104, allows multiple representatives to call on the same account to carry out different roles on a regular basis. The Territory Management module within Siebel Consumer Goods supports a system for creating territories and modifying them to meet the needs of the consumer goods industry.


Table 103. Territory Management - CS ERD Entities and Tables

Entity Table

Account S_ORG_EXT

Account Team Member S_ACCNT_POSTN

Account Team Role S_ACCNT_POSROLE

Account/Terr Mapping S_TERR_ACCNT

Activity S_EVT_ACT

Business Unit S_BU


Contact S_CONTACT

Contact Team Member S_POSTN_CON

Contact/Terr Mapping S_TERR_CON

Division S_ORG_EXT

Position S_POSTN

Position Territory Assignment S_TERR_POSITION

Position Role (LOV type TERR_POSITION_ROLE)



Territory Position Role S_TERR_POS_ROLE




Figure 104.Territory Management - Consumer Sector

��

��

��

��

�3�"

��

��

��

��

��^%

��

%{

��

��

��

Ora

cle

��

�

��

��

��

�

��

��

��

�+

��

�%

��

$�

��

'�

�

�

&$

��

��

"��

�'�

��

%��

��$

��

'�

�

��

'�

�

��

�

��

+

�

��>

��+

��

��

��

�+

�"�

��

�$

�

�

&$

��0��

��

��

"�

��

�$

�

$�

�

�0�

��

��

"�

��

�$

�

�

&$

��

��

"�

"�

".

��

�

$�

�

��

��

"�"

�"

.�

�

�

$�

�

�

��

%��

��$

!�>

�%��

$%

�'�

%�*

��

�

��

9�

��!

�>�%

��$.

&%

�$�

%%

�&$

��

�

�

&$

�

��

��

��

�+

�9

��

��

9

+

��

��

��

�+

��

��

��

�+

�>�

�%

��$

��

%��

��$

��

��

��

�+

��%

%�

$"

�$

�

��

��

��

��

��

��

��

��14�

��

��2 �2

��

��14�

��

�

� �

��14�

��

��

��

��14�

��

� �

��14�

��

��

�

��14�

��

�

��

�

��

��

�

�� 1

��3

�

��

��@

��1

3

��1

3

��

��

�� 1

��

� �

�

��

��

�� 1

��3

�

�

��

��

�

�� 1

��3

�

��1

3 ��

��

�

��

� �

� �

� ��

��

� �

��

��

��

��

2��

� ��

�

��

��

�

��

� �

�

��

� �

�

� �

� ��

�

��

� �

� �

� ��

�

�

��

��

��

� �

��

��

�



238

Territory Management - Life SciencesFor Life Science companies, a key business process is territory alignment (sales force alignment). This ERD (shown in Figure 105) illustrates how Territory Alignments can be defined encompassing territories, sales representatives, business rules, territory roll-ups, and so on. Historical alignments can be maintained for reference and comparison. Future alignments can be staged and analyzed concurrently, thus facilitating simultaneous evaluation of multiple strategies for a sales force.


Table 104. Territory Management - LS ERD Entities and Tables

Entity Table

Account S_ORG_EXT

Account/Terr Mapping Change S_TERRALGN_ACCT

Asset S_ASSET

Asset/Terr Mapping Change S_TERRALGN_AST

Business Unit S_BU

Contact S_CONTACT

Contact/Terr Mapping Change S_TERRALGN_CON

Division S_ORG_EXT

Geo/Terr Mapping Change S_TERR_REGION, S_TERR_ZIP

Position S_POSTN

Position Territory Assignment Change S_TERRALGN_PSTN

Region S_REGION


Territory Alignment S_TERRALGN

Territory Alignment Condition S_TERRALGN_COND



Zipcode (None)



Figure 105.Territory Management - Life Sciences

��

��

��

�� 3

�"��

��^%

��

�'%

{��

��

��

��O

racle

��

��

��

%��

��$

0��

��

��

%%

�$

"�

$�

�

9�

$

�

��

0��

��

�"�

��

�$

�

9�

$

�

�%

%�

�0�

��

��

"�

��

�$

�9

�$

�

�

$�

�

�0�

��

��

"�

��

�$

�9

�$

�

�

�

&$

�0�

��

��

"�

��

�$

�9

�$

�

��

��

��

�+

��

'�

$"

�$

��

�

$!

��

$

��

��

��

�+

��'�

$"

�$

�

�

�

��

�9

��

'��

��

� ��

��

$[

��

�!

� �%

%�

�

�

$�

�

�

��

%��

��$

!�>

�%��

$%

�'�

%�*

��

�

��

9�

��!

�>�%

��$

.&

%�$

�%

%�&

$��

�

�

&$

�

��

��

��

�+

�9��

��

�

9+�

��

��

��

+

��

��

��

�+

�>�

�%

��$

��

��

�

��

��

��

��

�

� ��

��0�

� �

��

��1

3 �

��

��

� �

� �

� ��

�

� ��

��0�

� �

��

��1

3 �

��

��

� �

� �

� ��

�

� ��

��0�

� �

��

��1

3 �

��

��

� ��

��0�

� �

��

��1

3

�

��

��

� �

� �

� ��

�

� �

� �

� ��

�

� ��

��0�

� �

��

��1

3

�

��

��

� �

� �

� ��

�

��

��

��2

��

� �

� 2��

��1

3

��

��@

��1

3

��1

3

��

��

��14�

��

��

�

�� 1

��

��1

3

��

��

�

��

� �

� �

� ��

�

��

� �

��

��

��

��

�

2��

� ��

�

��

��

��

� �

� �

� ��

�

��

� �

��

��

�



240

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

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


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

Entity Table

Marketing Segment S_MKT_SEG

Order S_ORDER


Organization External S_ORG_EXT

Period S_PERIOD

Period Relationship S_PERIOD_REL

Product Attribute Type S_LST_OF_VAL

Product Attribute Value S_LST_OF_VAL

Product Option Mix Preference S_PROD_OPT_MIX

Product Option Mix Proportion S_PROD_OPT_PCT

Product Option Range S_PROD_OPTION

Product Option Range Member S_PROD_OPT_VAL

Quote S_DOC_QUOTE




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



242

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


Table 106. Time Sheet ERD Entities and Tables

Entity Table

Activity S_EVT_ACT


Period S_PERIOD


Project S_PROJ



Time Unit S_TMSHT_ITEM

Timesheet S_TMSHT

Timesheet Approval S_TMSHT_APPR

Timesheet Line S_TMSHT_LN

Work Type S_PROJ



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



244

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


Table 107. Trade Promotions ERD Entities and Tables

Entity Table


Contract S_D0C_AGREE, S_DOC_QUOTE, S_ORDER

Contract Item S_AGREE_ITEM, S_QUOTE_ITEM, S_ORDER_ITEM


Internal Product Presence S_ORG_PROD


Marketing Event or Activity S_SRC, S_SRC_CHNL

Note S_NOTE_SRC

Order S_ORDER

Other Contract S_DOC_AGREE, S_DOC_QUOTE


Product S_PROD_INT, S_PROD_EXT



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

��

��

� �

��

��

�



246

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


Table 108. Training Curriculum Course ERD Entities and Tables

Entity Table



Employee Course S_EMP_CRSE

Employee Course Status S_EMP_CRSE_STAT



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



248

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


Table 109. Training Test Engine ERD Entities and Tables

Entity Table

Course/Course Offering Test S_CRSE_OFFR_TST

Event Location S_EVTLOC

Individual’s Test S_CRSE_TSTRUN

Individual’s Test Answer S_CRSE_TSTRUN_A

Individual’s Test Category S_TSTRUN_CATSTS

Individual’s Test Question S_CRSE_TSTRUN_Q


Pool Question S_POOL_QUES


Question/Possible Answer S_CRSE_TST_ANSR

Question/Question Pool, Question Pool, Question S_TST_QUES

Question Category LOV

Test Available Language S_CRSE_TST_LANG

Test Question S_CRSE_TST_QUES

Topic/Objective S_CRSE_TOPIC

Training Course S_PROD_INT_CRSE, S_PROD_INT

Training Course Offering S_SRC_EVT, S_SRC

Training Test S_CRSE_TST



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

��



250

Universal Customer MasterThis ERD (shown in Figure 111) illustrates how Universal Customer Master works with external systems and the Siebel application. This ERD also shows the UCM engine schematics including the survivorship rule set and its relationship with repository-based information, UCM objects, and operations such as deduplication, merge, and the keeping of history.


Table 110. Universal Customer Master ERD Entities and Tables

Entity Table

Attribute Group S_UCM_ATGP

Attribute Group Field Mapping S_UCM_ATGP_FLD

Attribute Group Rule S_UCM_ATGP_RULE

Attribute Group Update History S_UCM_CON_ATGP, S_UCM_ORG_ATGPS_UCM_OGP_ATGP

Confidence Level S_UCM_CONF_LVL

External Information System S_CIF_EXT_SYST

External Information System Mapping S_CIF_CON_MAP, S_CIF_ORGRP_MAP, S_CIF_ORG_MAP

External System Privilege S_CIF_SYS_DTL

Rule Set S_UCM_RULE_SET

UCM Address S_UCM_ADDR_PER

UCM Asset S_UCM_ASSET

UCM Child Object S_UCM_CON_CHILDS_UCM_OGP_CHILDS_UCM_ORG_CHILD

UCM Deduplication S_UCM_DEDUP

UCM Merge History S_UCM_CON_MERGE, S_UCM_ORG_MERGE

UCM Object S_UCM_CONTACTS_UCM_ORG_EXTS_UCM_ORGGRP

UCM Privacy S_UCM_PRIVACY



Figure 111.Universal Customer Master

��

��&

��2

��

��

��

��

��"

��

��

��

��

��O

racle

��

�

��

��

��

�

&

"��

��>

�

+

&

"��

%%

��

&

"��

!!

��

%%

&

"�"

��

�

�9

�%�

��

+

�&

'�

��%

��

��

��

%��

��

+�.

&%

�$�

%%

�

�"

��

$�

$�

��

��

%��

��

+�*

��'

!��

.=�

�

��

��

�.&

��

��

�&

��

*��

'!

�"�

��

�$

��

��

�.&

��

��

�&

��&

�!

��

��9

�%�

��

+

�8

��

�$

�'

�%

+%

��

"�

��

�>�'

�

�

�8

��

�$

�'

��$

*�

�"

��

��$

�%+

%�

�"

&

"��

��

�+

��

8�

&

"��

.=�

�

&

"�

9�

&%

�9

�'

!&

"

��

�

�$

�[�

��

$

&

"��

��

%�

$

�8

��

�$

�'

��$

*�

�"

��

��$

�%+

%�

�"

�"

��

��$

&

"�!

�!

&�

�

$*

�!�

$

��'

�>

�'

��

��

�.&

��

�

��

&�

��&

'�

��

��

�.&

��

��

�&

�

��

��

+

��

�%

�$

��

�

$�[

��

��$

9�

&%

�9

�'

!

��

�

��

��

1�

� �

��

��

�

� �

��

�

��

��

��

�

��

��

��

�6��

��

�

1�

� �

��

�

��

��

��

�

��

��

��

�

��

��

��

�

��

��

��

��

��

��

1�

� �

��

��

�

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

1�

� �

��

��

�

�

��

��

��

��

��

1�

� �

��

��

�

��

��

��

�

��

��

��

��

�

��

��

��

�3�

�

�

��

��

��

� �

� �

��

��

� �

��

�



252

VehicleThis ERD (shown in Figure 112) illustrates how Siebel Automotive tracks the configuration and relationships associated with a vehicle. Vehicles represent a physical asset based on a product that may be related to one or more contacts, organizations, accounts, and positions. In addition to the attributes inherited from the product upon which it is based, a vehicle may also have one or more options (also products) associated with it. A vehicle's sales history, financial detail, service history and service requests can be tracked through its life cycle.


Table 111. Vehicle ERD Entities and Tables

Entity Table

Asset S_ASSET


Dealer S_ORG_EXT, S_PARTY

Features S_PROD_SPEC

Financial Detail S_VHCL_FIN_DTL

Installed Option S_ASSET_REL

Option S_PROD_REL

Position S_POSITION, S_PARTY

Product S_PROD_INT

Product Features S_PROD_SPEC

Sales History S_VHCL_SALES

Service History S_VHCL_SRV


Specifications S_PROD_SPEC


Vehicle Product S_PROD_INT



Figure 112.Vehicle

Title

: V

ehic

leA

utho

r :

Ora

cle

, Con

fiden

tial

FIN

AN

CIA

L D

ETA

IL

SA

LES

HIS

TOR

Y

PO

SIT

ION

SE

RV

ICE

HIS

TOR

Y

PE

RS

ON

EM

PLO

YE

E

OTH

ER

P

ER

SO

N

AS

SE

T

INS

TALL

ED

O

PTI

ON

VE

HIC

LE

PR

OD

UC

T D

ETA

ILS

SP

EC

IFIC

ATI

ON

S

FE

ATU

RE

S

OR

GA

NIZ

ATI

ON OTH

ER

OR

GA

NIZ

ATI

ON

DE

ALE

R /

PA

RTN

ER

SE

RV

ICE

RE

QU

ES

T

PR

OD

UC

T

VE

HIC

LE

PR

OD

UC

TO

PTI

ON

have

vis

ibili

ty to

visi

ble

to

pref

er

serv

ice

prov

ider

of

belo

ng to

owne

r of

for

ofof

invo

lved

in

of

for

of

for

sold

by

selle

r of

perf

orm

ed b

y

perf

orm

rout

ed to

assi

gned

to

of invo

lved

in

of

invo

lved

in

for

subj

ect o

f

for

of

for

Sub

ject

of

repo

rted

by

repo

rter

of

com

pose

d of

mad

e in

to

for

subj

ect o

f

assi

gned

to for

mad

e in

to

an in

stan

ce o

f

Cur

rent

ly o

wne

d by

/rel

ated

to

for

belo

ngs

to

cont

ains

an in

stan

ce o

f

mad

e in

to

prim

arily

co

mpo

sed

of

for

seco

ndar

ily c

ompo

sed

of for

a re

port

to

a pa

rent

to



254

Vehicle CollectionThis ERD (shown in Figure 113) illustrates how the Siebel application helps an automotive captive finance company deploy collections processes. Relevant information includes that a customer's car can be impounded by a government agency, or a customer might abandon the car during the life cycle of vehicle ownership. Captive Finance allows the capture of multiple promises to pay (PTPs) for a given account. When the customer breaks a promise to pay, a Service Request is created for an impound, a repossession, or a cure process.


Table 112. Vehicle Collection ERD Entities and Tables

Entity Table

Bankruptcy S_BANKRUPTCY, S_BK_PARTY

Service Request S_SRV_REQ, S_SRV_REQ1_FNX

Promise to Pay S_CF_PTP

Party S_PARTY, S_ORG_EXT, S_CONTACT, S_USER

Asset, Financial Account S_ASSET

Vehicle Insurance S_CF_INSURANCE



Figure 113.Vehicle Collection

A

SS

ET

VE

HIC

LE

OT

HE

R

AS

SE

T

FIN

AN

CIA

L A

CC

OU

NT

VE

HIC

LE

LE

AS

E

OT

HE

R F

INA

NC

IAL

AC

CO

UN

T

P

AR

TY

OR

GA

NIZ

AT

ION

VE

HIC

LE

LE

AS

E

HO

LD

ING

C

OM

PA

NY

OT

HE

R O

RG

AN

IZA

TIO

N

INS

UR

AN

CE

CO

MP

AN

YIM

PO

UN

D A

GE

NC

YR

EP

OS

ES

SIO

N

AG

EN

CY

PE

RS

ON

CO

NT

AC

TC

OLLE

CT

ION

A

GE

NT

OT

HE

R

PE

RS

ON

SE

RV

ICE

RE

QU

ES

T

IMP

OU

ND

NO

TIF

ICA

TIO

N

RE

PO

SE

SS

ION

R

EQ

UE

ST

BA

NK

RU

PT

CY

* C

AS

E_N

UM

VE

HIC

LE

IN

SU

RA

NC

E*

EF

F_S

TA

RT

_D

TP

RO

MIS

E T

O P

AY

* S

EQ

_N

UM

asso

cia

ted

to

su

bje

ct

of

insu

red

fo

r

insu

red

by

insu

red

fo

r

insu

red

by

file

d b

y

file

r of

insu

red

by

insu

re f

or

reco

rde

d f

or

ha

s b

ee

n f

iled

fo

r

issu

ed

by

wo

rk o

n

assig

ne

d t

o

wo

rk o

n



256

Vehicle FinancingAsset financing (shown in Figure 114) refers to the niche area of capital financing where an asset is converted into a working cash flow in exchange for a security interest in the asset. For example, an auto dealer might offer a customer a lease option, where the customer pays a fixed monthly charge in exchange for using the vehicle for a predetermined period of time. In this form of leasing, the lessee has the right to use the vehicle, but does not own the vehicle. The lessee pays an up-front cost and pays monthly payments to get the right to use the vehicle. At the end of the lease, the lessee usually has several options: to buy the vehicle or pay the end-of-lease cost and walk away. The lessor must now deal with remarketing the vehicle. The lessor can lease it to another lessee or auction the vehicle to dealers or consumers.


Table 113. Vehicle Financing ERD Entities and Tables

Entity Table

Asset S_ASSET

Contract S_DOC_AGREE


Financial Account State S_FN_ACCNT_STAT

Historical Auction Price S_VHCL_AUC_REF

Historical FMV Price S_VHCL_FMV_REF

Historical Residual Value S_VHCL_RSDL_REF

Product S_PROD_INT


Vehicle Consignment S_VHCL_CNSGNMNT

Vehicle Consignment Details S_VHCL_CNSGNDTL

Vehicle Consignment Fees S_VHCL_CNSGNFEE

Vehicle FMV S_VHCL_FMV

Vehicle Inspection S_VHCL_INSPCTN

Vehicle Inspection Charges S_VHCL_INSPCHRG

Vehicle Option at Lease S_FNACC_AST_OPT

Vehicle Title Log S_VHCL_TITLELOG

Vehicle Turn In S_VHCL_TURN_IN



Figure 114.Vehicle Financing

Titl

e : V

ehic

le F

inan

cing

Aut

hor

: Ora

cle

, Con

fiden

tial

AS

SE

T

VE

HIC

LE

VE

HIC

LE

OP

TIO

N

HIS

TO

RIC

AL

RE

SID

UA

L V

ALU

E

HIS

TO

RIC

AL

FM

V P

RIC

EH

IST

OR

ICA

L A

UC

TIO

N P

RIC

E

PR

OD

UC

T

VE

HIC

LE T

UR

N IN

INS

PE

CT

ION

CH

AR

GE

# S

EQ

_NU

M

SE

RV

ICE

R

EQ

UE

ST

VE

HIC

LE IN

SP

EC

TIO

N#

SE

Q_N

UM

VE

HIC

LE F

MV

# C

ALC

ULA

TIO

N T

YP

E#

EV

ALU

AT

ION

DA

TE

CO

NT

RA

CT

OT

HE

R

CO

NT

RA

CT

LEA

SE

A

GR

EE

ME

NT

VE

HIC

LE T

ITLE

LO

G#

SE

Q_N

UM

CO

NS

IGN

ME

NT

F

EE

CO

NS

IGN

ME

NT

D

ET

AIL

VE

HIC

LE C

ON

SIG

NM

EN

T

FIN

AN

CIA

L A

CC

OU

NT

S

TA

TE

VE

HIC

LE O

PT

ION

A

T L

EA

SE

VE

HIC

LE F

INA

NC

IAL

AC

CO

UN

T#

SE

Q_N

UM

FIN

AN

CIA

L A

CC

OU

NT

OT

HE

R

FIN

AN

CIA

L A

CC

OU

NT

VE

HIC

LE L

EA

SE

VE

HIC

LE

LOA

N

for

cons

ists

of

base

d on

subj

ect o

f

in c

onte

xt

subj

ect

of

perfo

rmed

for

subj

ect

of

for

has

for

subj

ect

offo

r

subj

ect

of

for

subj

ect o

f

subj

ect o

f

for

subj

ect o

f

for

in r

efer

ence

to

subj

ect o

f

in r

efer

ence

tosu

bjec

t of

in r

efer

ence

tosu

bjec

t of

for

subj

ect

of

asso

ciat

ed

to

subj

ect

of

in c

onte

xt o

f

subj

ect

of

for

subj

ect o

f

asso

ciat

ed to

subj

ect

of

asso

ciat

ed to

subj

ect

of

for

subj

ect o

f

for

subj

ect o

f

asso

ciat

ed to

subj

ect

of

asso

ciat

ed

to

subj

ect

of

for

subj

ect o

f

for

has



258

Vehicle SalesThis ERD (shown in Figure 115) illustrates the vehicle sales process at automotive dealerships. A prospective buyer could come into a dealership as a result of a marketing activity by the dealership such as an advertisement campaign, direct mailer, and so on. This could result in an opportunity to sell a vehicle to the prospective buyer. A showroom log entry is created by a sales representative to record the visit of the prospective buyer. The sales representative could call and pursue the opportunity with the prospect. If the vehicle is sold, the sale is recorded with the team of sales representatives involved in the sale. The sale data could be made visible to affiliated dealerships.


Table 114. Vehicle Sales ERD Entities and Tables

Entity Table

Contact Access Log S_CON_ACCSS_LOG

Employee S_EMP_PER, S_CONTACT, S_USER


Opportunity S_OPTY, S_OPTY_ATX

Organization S_ORG_EXT, S_BU

Person S_CONTACT, S_CONTACT_ATX, S_CONTACT_BU

Showroom Log Entry S_COMM_LOG


Vehicle Sale S_VHCL_SALES, S_VHCL_SALES_BU, S_VHCL_SALE_EMP



Figure 115.Vehicle Sales

Titl

e : V

ehic

le S

ales

Aut

hor

: Ora

cle

, Con

fiden

tial

VE

HIC

LE S

ALE

SH

OW

RO

OM

LO

GE

NT

RY

OP

PO

RT

UN

ITY

MA

RK

ET

ING

EV

EN

T O

R

AC

TIV

ITY

OR

GA

NIZ

AT

ION

OT

HE

R

OR

GA

NIZ

AT

ION

DE

ALE

R /

PA

RT

NE

R

CO

NT

AC

T

AC

CE

SS

LO

G#

AC

CE

SS

DA

TE

VE

HIC

LE

PE

RS

ON

OT

HE

R

PE

RS

ON

EM

PLO

YE

E

mad

e by

invo

lved

in

for

subj

ect

of

part

icip

ate

in

hand

led

by

subj

ect

of

in c

onte

xt o

f

have

vis

ibili

ty to

visi

ble

to

in c

onte

xt o

f

subj

ect

of

for

subj

ect

of

sold

by

selle

r of

subj

ect

of

in c

onte

xt o

f

subj

ect

of

targ

et

resu

lt of

resu

lt in

resu

lt of

resu

lt in

crea

ted

by

reco

rd

targ

et

targ

eted

in

in c

onte

xt o

f initi

ator

of

owne

r of

belo

ng t

o



260

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


Table 115. Versioned Object Definition ERD Entities and Tables

Entity Table

Attribute Definition S_ISS_ATTR_DEF

Attribute Value S_ISS_ATTR_VAL

Joint Workspace S_ISS_JWS

Joint Workspace Item S_ISS_JWS_ITEM

Object Attribute S_ISS_OBJ_ATTR

Object Attribute Value S_ISS_OBATR_VAL

Object Definition S_ISS_OBJ_DEF

Object Definition S_VOD

Versioned Object Definition Version S_VOD_VER



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



262

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


Table 116. Warranty ERD Entities and Tables

Entity Table

Asset S_ASSET

Asset Warranty Coverage S_ASSET_WRNTY

Order S_ORDER



Product S_PROD_INT


Product Line Warranty Coverage S_PRDLN_WRNTY

Product Warranty Coverage S_PROD_WRNTY

Warranty Coverage S_WRNTY_CVRG

Warranty Service Provider S_WRNTY_SRV_ORG



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



264


4 Physical Model

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

■ “Data Model Naming Conventions” on page 265

■ “Data Model Type Definitions” on page 268

■ “Columns of Numeric Physical Type” on page 272

■ “Siebel System Fields” on page 272

■ “INTEGRATION_ID Columns” on page 273

■ “Include Only Field” on page 273

■ “Siebel Repository” on page 273

■ “Database Schema Version” on page 274

■ “Limit Checking for Data Types” on page 274

■ “Validating the Siebel Schema” on page 274

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

■ “Generating a Report about Tables” on page 275

Data Model Naming ConventionsThis topic describes:

■ Table Naming Conventions

■ Index Naming Conventions on page 267

■ Column Naming Conventions on page 267

■ Abbreviations Used in the Physical Model Listings on page 268

Table Naming 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.


Physical Model ■ Data Model Naming Conventions

266

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

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

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.

Table 117. Table Prefixes

Prefix Meaning

EIM_ Interface tables for Siebel Enterprise Integration Manager.

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

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

Table 118. Base Table Suffixes

Suffix Meaning

_ATT File attachment table.

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

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

_V A table that represents a database view.

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

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

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

Physical Model ■ Data Model Naming Conventions


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

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 120 shows the standard suffixes for column names and their possible values.

Table 119. 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 120. Standard Column Suffixes

Suffix Value

_AMT This column contains a currency amount.

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

_DT This column contains a date or datetime value.

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

_ID This column contains ROW_ID values.

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


Physical Model ■ Data Model Type Definitions

268

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

Data Model Type DefinitionsThis topic contains the following type definitions:

■ Table Type Definitions on page 269

■ Table Status Definitions on page 270

■ Column Type Definitions on page 271

■ Domain Type Definitions on page 271

_TEXT This column contains text data.

_TM This column contains a time value.

_TS This column contains a timestamp value.

Table 121. Physical Model Listing Abbreviations

Abbreviation or Phrase Meaning

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

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

SEA Siebel Enterprise Applications.

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

Table 120. Standard Column Suffixes

Suffix Value



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

Table 122. 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.



270

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

Table Status DefinitionsTable 123 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 123. Table Status Definitions

Table Status Description

Active Actively used and supported in Siebel Business Applications.

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

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

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

Table 122. Table Types in the Siebel Database

Table Type Description



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

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

Table 124. Column Types in the Siebel Database

Column Type Description

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

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

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

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

Table 125. Domain Types

Domain Type Meaning Domain Contains

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

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

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

LOVB List of Values 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

272

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 126. 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 126. Siebel System Fields

Column Name Description

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

CREATED Date the record was entered.

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

DCKING_NUM No longer used.

Table 125. 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.

DB_LAST_UPD Date and time the record was last changed in the database.

DB_LAST_UPD_SRC Source of the instance or operation that changed the record in the database.

LAST_UPD Date and time the record was last changed.

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

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

ROW_ID Unique row identifier.

Table 126. Siebel System Fields

Column Name Description


Physical Model ■ Database Schema Version

274

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 41.XX.YY.ZZ, where XX, YY, and ZZ are one or two digit integers.

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 127). Sources of inputs include Oracle’s Siebel application, EIM, and connectors. For example, if you do a bulk import using EIM, you must make sure the dates are within the specified range, otherwise the Object Manager returns an SQL error for each out-of-range date.

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.

Table 127. Input Limits on Data Types

Data Type Limit Checking

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

Long Maximum size of 16K

Text Maximum size of 16K

CLOB Maximum size of 128K

Physical Model ■ Party Model Unifies Access to Data


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 128 lists the extension tables and their corresponding EIM interface tables.

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

Use S_PARTY_PER to implement relationships between members:

■ Access groups and members

■ Accounts and contacts

■ Employees and positions

■ User lists and users

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

Table 128. S_PARTY Extension Tables and Corresponding EIM Interface Tables

Data Type Extension Table to S_PARTY EIM Interface Table

Accounts S_ORG_EXT EIM_ACCOUNT

Business Units S_BU EIM_BU

Contacts S_CONTACT EIM_CONTACT

Employees S_CONTACT EIM_EMPLOYEE

Groups S_ORG_GROUP EIM_GROUP

Organizations S_ORG_BU EIM_ORG_BU

Positions S_POSTN EIM_POSITION

Users S_USER EIM_USER


Physical Model ■ Generating a Report about Tables

276

To generate a table report

1 Log in to the Siebel application, and navigate to the Administration - Application screen, then Tables view.

2 From the Menu menu, choose New Query.

3 In the Name column, enter the name of the table for which the report is to be generated, and press Enter.

4 Click the Reports icon in the icon bar.

5 Select Tables Report from the drop-down list.

The Output Type dialog box appears.

6 Select the output format for the report from the drop-down list.

7 Click Submit to generate the report.

The File Download dialog box appears.

8 Choose to open, save or cancel the report.

NOTE: For more information about generating reports, see Siebel Reports Administration Guide.


5 Schema Changes

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

■ “Table Changes in This Version” on page 277

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

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

Table Changes in This 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 277

■ “Changed Tables in This Version” on page 281

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

Table 129. New Tables in This Version

Table Type Active

S_ACC_VIEW_APPL Data(Private) Yes

S_ACRL_RULE_ITM Data (Public) Yes

S_ACT_PGROUP Data (Intersection) Yes

S_BNFPLNITM_PAY Data(Public) Yes

S_BNFT_PLAN_ITM Data(Public) Yes

S_BR_ACTION Data (Public) Yes

S_BR_ACTN_SET Data (Public) Yes

S_BR_EXCPTN Data (Public) Yes

S_BR_INST Data (Public) Yes

S_BULK_REQ Data (Public) Yes

S_CASE_BNFTPLAN Data(Public) Yes

S_CASE_CHGOFCCM Data(Public) Yes

S_CASE_PSX Extension Yes


Schema Changes ■ Table Changes in This Version

278

S_CASE_TMPL Data(Intersection) Yes

S_CASE_TMPLITM Data(Intersection) Yes

S_CHAT_KB_VSTD Data (Public) Yes

S_CHAT_LANG_MAP Data (Public) Yes

S_CHAT_PARAM Data (Public) Yes

S_CHAT_ROUTE Data (Public) Yes

S_CHRCTR_IMPT Data (Public) Yes

S_COMM_IMPT Data (Public) Yes

S_COMM_PGROUP Data (Intersection) Yes

S_COMM_SVY_LOG Data (Public) Yes

S_CON_PGROUP Data (Intersection) Yes

S_CONTACT_IMPT Data (Public) Yes

S_CONTACT_PSX Extension Yes

S_CTLGCAT_MSGPL Data(Intersection) Yes

S_DCP_MSGPLAN Data(Intersection) Yes

S_EMP_AUDITSIGN Data(Intersection) Yes

S_INT_OBJ_DATA Data (Private) Yes

S_INT_OBJ_DPLOY Data (Private) Yes

S_INV_AUDIT_RPT Data(Public) Yes

S_INVADTRPT_ATT Data(Public) Yes

S_LEAD Data (Public) Yes

S_LEAD_BU Data (Intersection) Yes

S_LEAD_IMPT Data (Public) Yes

S_LEAD_OPTY Data (Intersection) Yes

S_LEAD_POSTN Data (Intersection) Yes

S_LEAD_PROD Data (Intersection) Yes

S_LEADPROD_IMPT Data (Public) Yes

S_LEADRESP_IMPT Data (Public) Yes

S_LIT_LSX Extension(Siebel) Yes

S_LIT_PROD_APPL Data(Intersection) Yes

S_LITERATUR_REL Data(Intersection) Yes


Table Type Active



S_LOY_ACRL_RULE Data (Public) Yes

S_LOY_ACTRANGE Data (Public) Yes

S_LOY_DISTANCE Data (Public) Yes

S_LOY_LOAN Data (Public) Yes

S_LOY_MEM_BLKAD Data (Public) Yes

S_LOY_MSTAT_PRF Data (Public) Yes

S_LOY_OLAPSTG Data (Public) Yes

S_LOY_PG_PR_ITM Data (Public) Yes

S_LOY_PRI_RANGE Data(Public) Yes

S_LOY_PRI_RULE Data(Public) Yes

S_LOY_PRT_TXN Data (Public) Yes

S_LOY_PTSUBTYPE Data(Public) Yes

S_LOY_PURTRN_LM Data (Public) Yes

S_LOY_RDM_ACT Data (Public) Yes

S_LOY_SOM_HIST Data (Public) Yes

S_LOY_SRC_PROMO Data (Intersection) Yes

S_LOY_SRV_PROD Data (Public) Yes

S_LOY_TRVL_INFO Data (Public) Yes

S_LOY_TXN_ITEM Data (Public) Yes

S_LOY_TXN_STG Data (Public) Yes

S_LOYPR_ICHOICE Data(Public) Yes

S_MKT_EVT_TRG Data(Public) Yes

S_MKT_IMPRT_TSK Data (Public) Yes

S_MKT_IMPT_MAP Data (Public) Yes

S_MKT_SRVY Data (Public) Yes

S_MKT_STGWAIT Data(Public) Yes

S_MKT_STGWT_REL Data(Public) Yes

S_MKTEVTRG_HST Data(Public) Yes

S_MKTEVTRG_MAP Data(Intersection) Yes

S_MKTIMP_CHRCTR Data (Intersection) Yes

S_MKTIMPMAP_ITM Data (Public) Yes


Table Type Active



280

S_MKTIMPTSK_ARG Data (Public) Yes

S_MKTIMPTSK_LOG Data (Public) Yes

S_MKTPRG_ACTN Data(Public) Yes

S_MKTPRGACT_LST Data(Intersection) Yes

S_MKTSVY_A_LANG Data (Intersection) Yes

S_MKTSVY_ANSW Data (Public) Yes

S_MKTSVY_Q_LANG Data (Intersection) Yes

S_MKTSVY_QUES Data (Public) Yes

S_MKTSVY_SCTN Data (Public) Yes

S_MKTSVYST_QUES Data (Public) Yes

S_MSG_PLAN Data(Public) Yes

S_MSGPL_ITM_REL Data(Intersection) Yes

S_MSGPLAN_BU Data(Intersection) Yes

S_MSGPLAN_ITM Data(Intersection) Yes

S_NOTE_LEAD Data (Public) Yes

S_NOTEOPTY_PGRP Data (Intersection) Yes

S_OPTY_ORG_ATTR Data(Public) Yes

S_OPTY_PGROUP Data (Intersection) Yes

S_ORDER_ACTNSET Data (Intersection) Yes

S_ORG_EXT_IMPT Data (Public) Yes

S_ORG_GRP_PSX Extension Yes

S_ORG_PGROUP Data (Intersection) Yes

S_ORG_RL_PROF Extension (Siebel) Yes

S_PCD_DETAIL Data(Public) Yes

S_PGM_ORG_PROD Data (Public) Yes

S_PGMORG_PNTTYP Data (Public) Yes

S_PGROUP_LANG Data (Intersection) Yes

S_PGROUP_REL Data (Public) Yes

S_PRO_CFG_ITEM Data (Intersection) Yes

S_PROGORG_STMT Data(Public) Yes

S_PROMO_PRTNR Data (Public) Yes


Table Type Active

Schema Changes ■ Table Column Changes in This Version


Changed Tables in This VersionTable 130 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 282

S_PRSPCON_IMPT Data (Public) Yes

S_PS_APPL Data (Public) Yes

S_PS_APPL_ATT Data (Public) Yes

S_PS_APPL_BU Data (Intersection) Yes

S_SMPL_TXN_ATT Data(Public) Yes

S_SRC_MSGPLAN Data(Intersection) Yes

S_STKPEREMP_EMP Data(Intersection) Yes

S_TIMEZONE_DTL Data (Private) Yes

S_VALDN_RESULT Data(Public) Yes

S_WEB_SITE Data (Public) Yes

S_WEB_SITE_LANG Data (Public) Yes

S_WEBSITE_CNTNT Data (Public) Yes

S_WEBST_TMPL_RL Data (Public) Yes

S_XMLP_REP_IOBJ Data(Public) Yes

S_XMLP_REP_TMPL Data (Public) Yes

S_XMLP_REPOUTPT Data (Public) Yes

S_XMLP_RPT_LANG Data (Intersection) Yes

S_XMLP_RPT_VIEW Data (Intersection) Yes

Table 130. Table with Changed Type

Table Previous Type New Type

S_TIMEZONE Data (Public) Data (Private)


Table Type Active



282

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

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

■ Opt indicates optional.

■ Len indicates length.

■ Prec indicates precision.

■ Def indicates default.

■ LOV Bnd indicates LOV bound.



Table

131.

New

Table

Colu

mns

in T

his

Vers

ion

Ta

ble

C

olu

mn

O

pt

Da

ta

Typ

eLen

Pre

cS

ca

leD

ef

LO

V T

yp

eLO

V

Bn

d

S_AC

CN

T_PO

STN

NEXT_C

ALL

_D

TY

UTC

D

ate

Tim

e7

S_AC

CN

T_PO

STN

NEXT_C

ALL

_O

BJE

CTIV

YVarc

har

1500

S_AC

T_PR

DIN

TIN

TEG

RATIO

N_ID

YVarc

har

30

S_AC

T_PR

DIN

TM

AX_ALL

OC

_Q

TY

YN

um

ber

22

22

7

S_AC

T_PR

DIN

TM

AX_C

ALL

_Q

TY

YN

um

ber

22

22

7

S_AC

T_PR

DIN

TM

AX_PR

OD

UC

T_Q

TY

YN

um

ber

22

22

7

S_AC

T_PR

DIN

TPR

OD

_ALL

OC

_ID

YVarc

har

15

S_AC

T_PR

DIN

TSU

M_SAM

PLE

_ALL

OC

YN

um

ber

22

22

7

S_AC

T_PR

DIN

TSU

M_SAM

PLE

_PR

OD

YN

um

ber

22

22

7

S_AC

T_PR

OD

_A

PPL

PR

OD

_ALL

OC

_ID

YVarc

har

15

S_AC

T_S

IGN

CO

N_FS

T_N

AM

EY

Varc

har

50

S_AC

T_S

IGN

CO

N_LS

T_N

AM

EY

Varc

har

50

S_AC

T_S

IGN

DIS

CLA

IMER

_TEXT

YVarc

har

2000

S_AC

T_S

IGN

INV

_AU

DIT

_R

PT_ID

YVarc

har

15

S_AC

T_S

IGN

REP_C

OM

P_N

AM

EY

Varc

har

50

S_AC

T_S

IGN

REP_FS

T_N

AM

EY

Varc

har

50

S_AC

T_S

IGN

REP_LS

T_N

AM

EY

Varc

har

50

S_AC

T_S

IGN

REP_PO

STN

YVarc

har

50

S_AC

T_S

IGN

REP_S

UB

_C

ON

TR

AC

TO

RY

Varc

har

50

S_AC

T_S

IGN

SAM

PLE

_TXN

_ID

YVarc

har

15

S_AD

DR

_O

RG

AD

DR

ESSEE

YVarc

har

100

S_AD

DR

_PER

AD

DR

ESSEE

YVarc

har

100



S_AD

DR

_PER

AIA

_IN

TEG

_ID

YVarc

har

150

S_ASS

ESS

INV

_AU

DIT

_R

PT_ID

YVarc

har

15

S_ASS

ESS

LIT_ID

YVarc

har

15

S_ASS

ET

AIA

_IN

TEG

_ID

YVarc

har

150

S_ASS

ET

BIL

L_PR

OFI

LE_ID

YVarc

har

15

S_C

AM

P_C

ON

CTR

L_G

RP_FL

GN

Char

1N

S_C

AM

P_C

ON

SEG

MEN

T_C

OD

E_1

YVarc

har

30

S_C

AM

P_C

ON

SEG

MEN

T_C

OD

E_2

YVarc

har

30

S_C

ASE

APPLI

CA

NT_ID

YVarc

har

15

S_C

ASE

AU

DIT

_EM

P_ID

YVarc

har

15

S_C

ASE

CH

GO

FCC

M_R

EQ

_FL

GN

Char

1N

S_C

ASE

MS

TR

_C

ASE_ID

YVarc

har

15

S_C

ASE

PS

_APPL_

IDY

Varc

har

15

S_C

IF_EX

T_S

YS

TM

IDD

LEW

AR

E_FL

GN

Char

1N

S_C

IF_EX

T_S

YS

TM

SG

_TYPE_C

DY

Varc

har

30

S_C

IF_SYS

_D

TL

PR

OXY_BS

YVarc

har

100

S_C

IF_SYS

_D

TL

PR

OXY_M

TD

_N

AM

EY

Varc

har

150

S_C

OM

M_D

TL

BAN

NER

_AD

_STR

NG

YVarc

har

100

S_C

OM

M_D

TL

CLI

EN

T_IP

_AD

DR

YVarc

har

100

S_C

OM

M_D

TL

CU

RR

EN

T_U

RL

YVarc

har

200

S_C

OM

M_D

TL

KEYW

OR

D_STR

NG

YVarc

har

100

S_C

OM

M_D

TL

MK

T_SR

VY_LA

NG

_ID

YVarc

har

5

S_C

OM

M_D

TL

REFE

RR

ER

_U

RL

YVarc

har

200

Table

131.

New

Table

Colu

mns

in T

his

Vers

ion

Ta

ble

C

olu

mn

O

pt

Da

ta

Typ

eLen

Pre

cS

ca

leD

ef

LO

V T

yp

eLO

V

Bn

d



S_C

OM

M_D

TL

REFE

RR

ER

_U

SER

NAM

EY

Varc

har

100

S_C

OM

M_IM

PT

AC

CN

T_PO

STN

_ID

YVarc

har

15

S_C

OM

M_IM

PT

AC

CN

T_R

EVN

_AM

TY

Num

ber

22

22

7

S_C

OM

MU

NIC

ATIO

NC

OS

T_A

MT

YN

um

ber

22

22

7

S_C

OM

MU

NIC

ATIO

NC

OS

T_C

UR

CY_C

DY

Varc

har

20

S_C

OM

MU

NIC

ATIO

NLE

AD

_ID

YVarc

har

15

S_C

OM

MU

NIC

ATIO

NM

KT_SR

VY_ID

YVarc

har

15

S_C

OM

MU

NIC

ATIO

NPG

RO

UP_PU

BLI

C_FL

GY

Char

1N

S_C

OM

MU

NIC

ATIO

NR

ESP_VALU

E_C

DY

Varc

har

30

S_C

ON

_A

DD

RAD

DR

ESSEE

YVarc

har

100

S_C

ON

TAC

TAIA

_IN

TEG

_ID

YVarc

har

150

S_C

ON

TAC

TAPPR

OVA

L_S

TATU

S_C

DY

Varc

har

30

APPR

OVAL_

STA

TU

SY

S_C

ON

TAC

TEM

AIL

_STA

TU

S_C

DY

Varc

har

30

EM

AIL

_STA

TU

S

S_C

ON

TAC

TLS

T_EM

LAD

R_U

PD

_TS

YU

TC

D

ate

Tim

e7

S_C

ON

TAC

TM

STR

_C

ASE_ID

YVarc

har

15

S_C

ON

TAC

TN

UM

_H

AR

D_B

NC

EY

Num

ber

22

10

0

S_C

ON

TAC

TN

UM

_SO

FT_B

NC

EY

Num

ber

22

10

0

S_C

ON

TAC

T_LO

YX

HO

ME_AIR

PO

RT

YVarc

har

30

S_C

ON

TAC

T_LS

XC

ERT_EX

PIR

E_D

TY

UTC

D

ate

Tim

e7

S_C

ON

TAC

T_LS

XLA

ST_S

MPL_

AU

DIT

_D

TY

UTC

D

ate

Tim

e7

S_C

ON

TAC

T_LS

XM

ASTER

_SIG

N_ID

YVarc

har

15

Table

131.

New

Table

Colu

mns

in T

his

Vers

ion

Ta

ble

C

olu

mn

O

pt

Da

ta

Typ

eLen

Pre

cS

ca

leD

ef

LO

V T

yp

eLO

V

Bn

d



S_C

T_APLT

_R

LST

LOC

K_FL

GY

Char

1N

S_C

T_R

ULE

_SET

LOC

K_FL

GY

Char

1N

S_C

T_R

ULE

_SET

RU

LE_S

ET_TYPE_C

DY

Varc

har

30

S_D

CP_C

ALL

_LS

TALL

OC

ATED

_C

NT

YN

um

ber

22

10

0

S_D

CP_C

ALL

_LS

TALL

OC

ATED

_PC

TY

Num

ber

22

22

7

S_D

CP_C

ALL

_LS

TC

TR

L_G

RP_PC

TY

Num

ber

22

22

7

S_D

CP_C

ALL

_LS

TPC

T_A

LLO

C_FL

GN

Char

1Y

S_D

CP_U

RL

LAN

D_SIT

E_ID

YVarc

har

15

S_D

CP_U

RL

RELA

Y_EM

BED

_ID

_FL

GN

Char

1N

S_D

MN

D_C

RTN

_PR

GAC

T_A

PPT_D

URTN

_M

INY

Num

ber

22

22

7

S_D

MN

D_C

RTN

_PR

GAC

T_C

AL_

TYPE_C

DY

Varc

har

30

S_D

MN

D_C

RTN

_PR

GAC

T_C

OM

MEN

TS

YVarc

har

100

S_D

MN

D_C

RTN

_PR

GAC

T_C

OM

MEN

TS_LO

NG

YVarc

har

1500

S_D

MN

D_C

RTN

_PR

GAC

T_D

ON

E_FL

GN

Char

1N

S_D

MN

D_C

RTN

_PR

GAC

T_O

WN

ER

_PER

_ID

YVarc

har

15

S_D

MN

D_C

RTN

_PR

GAC

T_PLA

N_EN

D_D

TY

UTC

D

ate

Tim

e7

S_D

MN

D_C

RTN

_PR

GAC

T_PLA

N_STA

RT_D

TY

UTC

D

ate

Tim

e7

S_D

MN

D_C

RTN

_PR

GAC

T_PR

IOR

ITY_C

DY

Varc

har

30

S_D

MN

D_C

RTN

_PR

GAC

T_PR

IV_FL

GN

Char

1N

S_D

MN

D_C

RTN

_PR

GAC

T_S

TAT_C

DY

Varc

har

30

S_D

MN

D_C

RTN

_PR

GAC

T_TO

DO

_C

DY

Varc

har

30

Table

131.

New

Table

Colu

mns

in T

his

Vers

ion

Ta

ble

C

olu

mn

O

pt

Da

ta

Typ

eLen

Pre

cS

ca

leD

ef

LO

V T

yp

eLO

V

Bn

d



S_D

MN

D_C

RTN

_PR

GAC

T_TO

DO

_D

UE_D

TY

UTC

D

ate

Tim

e7

S_D

MN

D_C

RTN

_PR

GC

REATED

_TS

YU

TC

D

ate

Tim

e7

S_D

MN

D_C

RTN

_PR

GD

EPLO

Y_TS

YU

TC

D

ate

Tim

e7

S_D

MN

D_C

RTN

_PR

GK

IOS

K_M

OD

E_FL

GN

Char

1N

S_D

MN

D_C

RTN

_PR

GLA

ND

GS

ITE_S

TAT_C

DY

Varc

har

30

LAN

DIN

G_S

ITE_

STA

TU

S_TYPE

S_D

MN

D_C

RTN

_PR

GM

KT_SR

VY_ID

YVarc

har

15

S_D

MN

D_C

RTN

_PR

GN

EXT_BTT

N_TEXT

YVarc

har

50

S_D

MN

D_C

RTN

_PR

GO

RIG

_C

REATO

R_ID

YVarc

har

15

S_D

MN

D_C

RTN

_PR

GO

WN

ER

_PO

STN

_ID

YVarc

har

15

S_D

MN

D_C

RTN

_PR

GPU

BLI

SH

_TS

YU

TC

D

ate

Tim

e7

S_D

MN

D_C

RTN

_PR

GR

ED

IREC

T_U

RL

YVarc

har

250

S_D

MN

D_C

RTN

_PR

GR

ED

IREC

T_U

RL_

FLG

NC

har

1N

S_D

MN

D_C

RTN

_PR

GR

ESU

ME_FL

GY

Char

1

S_D

MN

D_C

RTN

_PR

GSTRT_O

N_LN

DPG

_FL

GN

Char

1N

S_D

MN

D_C

RTN

_PR

GSTRT_SV

Y_BTT

N_TEXT

YVarc

har

50

S_D

MN

D_C

RTN

_PR

GSU

BM

IT_BTT

N_TEXT

YVarc

har

50

S_D

MN

D_C

RTN

_PR

GTEST_U

RL_

TEXT

YVarc

har

250

S_D

MN

D_C

RTN

_PR

GTIN

Y_U

RL_

TEXT

YVarc

har

250

S_D

MN

D_C

RTN

_PR

GTIT

LE_N

AM

EY

Varc

har

100

S_D

MN

D_C

RTN

_PR

GTM

PL_

STA

TU

S_C

DY

Varc

har

30

Table

131.

New

Table

Colu

mns

in T

his

Vers

ion

Ta

ble

C

olu

mn

O

pt

Da

ta

Typ

eLen

Pre

cS

ca

leD

ef

LO

V T

yp

eLO

V

Bn

d



S_D

OC

_Q

UO

TE

ATT

R_ID

YVarc

har

15

S_D

OC

_Q

UO

TE

BIL

L_PR

OFI

LE_ID

YVarc

har

15

S_D

OC

_Q

UO

TE_SPA

APPR

_S

EQ

_N

UM

YN

um

ber

22

10

0

S_D

OC

_Q

UO

TE_SPA

SPA

_SU

B_TYPE_C

DY

Varc

har

30

S_EM

P_PER

LS_A

PPR

OV

ER

_ID

YVarc

har

15

S_EM

P_PER

PC

D_TBAR

_A

LIG

N_C

DY

Varc

har

30

S_EM

P_PR

DIN

TALL

OC

_TYPE_C

DN

Varc

har

30

Pro

d-

uct

Al

loca

-ti

on

S_EM

P_PR

DIN

TEN

D_D

TY

UTC

D

ate

Tim

e7

S_EM

P_PR

DIN

TM

AX_ALL

OC

_Q

TY

YN

um

ber

22

22

7

S_EM

P_PR

DIN

TM

AX_C

ALL

_Q

TY

YN

um

ber

22

22

7

S_EM

P_PR

DIN

TM

AX_O

RD

ER

_Q

TY

YN

um

ber

22

22

7

S_EM

P_PR

DIN

TM

IN_O

RD

ER

_Q

TY

YN

um

ber

22

22

7

S_EM

P_PR

DIN

TSTA

RT_D

TY

UTC

D

ate

Tim

e7

S_EM

P_PR

DIN

TSTO

P_SAM

PLE

_FL

GN

Char

1N

S_EV

T_A

CT

BN

FT_PLA

N_IT

M_ID

YVarc

har

15

S_EV

T_A

CT

LEAD

_ID

YVarc

har

15

S_EV

T_A

CT

SK

IN_C

DY

Varc

har

30

S_EVT_AC

T_FN

XPG

RO

UP_PU

BLI

C_FL

GY

Char

1N

S_EV

T_A

CT_LS

XC

ALL

_VA

LDN

_R

ESU

LTY

Varc

har

50

Table

131.

New

Table

Colu

mns

in T

his

Vers

ion

Ta

ble

C

olu

mn

O

pt

Da

ta

Typ

eLen

Pre

cS

ca

leD

ef

LO

V T

yp

eLO

V

Bn

d



S_EV

T_A

CT_LS

XN

EXT_C

ALL

_D

TY

UTC

D

ate

Tim

e7

S_EV

T_A

CT_LS

XSU

PER

VIS

OR

_ID

YVarc

har

15

S_EV

T_C

OM

MAR

EA

_C

DY

Varc

har

30

S_EV

T_C

OM

MC

HAT_TR

AN

SC

RIP

TY

Undefine

d1310

72

S_EV

T_C

OM

MEM

AIL

_AD

DR

_PR

VD

YVarc

har

100

S_EV

T_C

OM

MFS

T_N

AM

E_PR

VD

YVarc

har

50

S_EV

T_C

OM

MLA

ST_N

AM

E_PR

VD

YVarc

har

50

S_EV

T_C

OM

MN

EW

_EM

AIL

_PR

VD

_FL

GN

Char

1N

S_EV

T_C

OM

MN

EW

_PH

_PR

VD

_FL

GN

Char

1N

S_EV

T_C

OM

MPR

OB

LEM

_D

ESC

_TEXT

YVarc

har

250

S_EV

T_C

OM

MSU

B_A

REA

_C

DY

Varc

har

30

S_EV

T_C

OM

MW

RA

PU

P_EN

D_TS

YU

TC

D

ate

Tim

e7

S_EV

T_C

OM

MW

RA

PU

P_FE

ED

BAC

K_C

DY

Varc

har

30

WR

APU

P_

FEED

BA

CK

Y

S_EV

T_C

OM

MW

RA

PU

P_O

UTC

OM

E_C

DY

Varc

har

30

WR

APU

P_

OU

TC

OM

EY

S_EV

T_C

OM

MW

RA

PU

P_R

EASO

N_C

DY

Varc

har

30

WR

APU

P_R

EAS

ON

Y

S_EV

T_C

OM

MW

RA

PU

P_S

TART_TS

YU

TC

D

ate

Tim

e7

S_FC

ST

SELF

_AD

J_A

MT

YN

um

ber

22

22

7

S_FC

ST

TO

T_A

DJ_

BY_SU

B_A

MT

YN

um

ber

22

22

7

S_FC

STS

ER

_PO

STN

SU

BM

IT_TO

_PSTN

_ID

YVarc

har

15

Table

131.

New

Table

Colu

mns

in T

his

Vers

ion

Ta

ble

C

olu

mn

O

pt

Da

ta

Typ

eLen

Pre

cS

ca

leD

ef

LO

V T

yp

eLO

V

Bn

d



S_FO

RM

_M

AP

CATEG

OR

Y_C

DY

Varc

har

30

PU

B_FO

RM

_

CATEG

OR

YY

S_FO

RM

_M

AP

DO

C_N

UM

BER

YVarc

har

30

S_IN

CID

EN

TSIG

N_EVT_ID

YVarc

har

15

S_IN

CID

EN

T_C

ON

RO

W_S

TATU

SN

Varc

har

10

Y

S_IN

V_PR

OF

AU

TO

_TO

P_U

P_FL

GY

Char

1N

S_IN

V_PR

OF

BIL

L_PR

FL_C

OM

MEN

TS

YVarc

har

255

S_IN

V_PR

OF

CC

_S

EC

_C

OD

EY

Varc

har

10

S_IN

V_PR

OF

CC

NU

M_EN

CR

PK

EY_R

EF

YVarc

har

30

S_IN

V_PR

OF

CC

V_N

UM

BER

YVarc

har

20

S_IN

V_PR

OF

CC

VN

UM

_EN

CR

PK

Y_R

EF

YVarc

har

30

S_IN

V_PR

OF

CR

DT_C

RD

_EXP_M

O_C

DY

Varc

har

30

TELC

O_M

ON

TH

_

TYPE

Y

S_IN

V_PR

OF

CR

DT_C

RD

_EXP_YR

_C

DY

Varc

har

30

YEA

R

S_IN

V_PR

OF

PAYM

EN

T_TYPE_C

DY

Varc

har

30

BIL

L_PA

YM

EN

T_

TYPE

Y

S_IN

V_PR

OF

RO

UTIN

G_N

UM

YVarc

har

50

S_IN

V_PR

OF

RO

UTIN

G_N

UM

BER

YVarc

har

30

S_IN

V_PR

OF

SM

S_N

OTIF

Y_FL

GY

Char

1N

S_IN

V_PR

OF

TH

RES

HO

LD_U

OM

_C

DY

Varc

har

30

BIL

L_PR

EPA

ID_

UO

MY

S_IN

V_PR

OF

TH

RES

HO

LD_VALU

EY

Num

ber

22

22

7

S_IN

V_PR

OF

TO

P_U

P_U

OM

_C

DY

Varc

har

30

BIL

L_PR

EPA

ID_

UO

MY

S_IN

V_PR

OF

TO

P_U

P_VALU

EY

Num

ber

22

22

7

Table

131.

New

Table

Colu

mns

in T

his

Vers

ion

Ta

ble

C

olu

mn

O

pt

Da

ta

Typ

eLen

Pre

cS

ca

leD

ef

LO

V T

yp

eLO

V

Bn

d



S_IN

V_PR

OF

TO

PU

P_FR

EQ

_C

DY

Varc

har

30

BIL

L_ F

REQ

UEN

CY

Y

S_IN

VC

_AD

J_IT

EM

AD

J_EFF

EC

TIV

E_D

TY

Date

7

S_IN

VC

_AD

J_IT

EM

AD

J_PER

CEN

TAG

EY

Num

ber

322

7

S_IN

VC

_AD

J_IT

EM

AD

J_TYPE_C

DY

Varc

har

30

S_IN

VC

_AD

J_IT

EM

AD

JUSTM

EN

T_VA

LUE

YN

um

ber

22

22

7

S_IN

VC

_AD

J_IT

EM

APPR

_PER

CEN

TAG

EY

Num

ber

22

22

7

S_IN

VC

_AD

J_IT

EM

APPR

_VALU

EY

Num

ber

22

22

7

S_IN

VC

_AD

J_IT

EM

APPR

OV

_AD

J_PER

CEN

TY

Num

ber

322

7

S_IN

VC

_AD

J_IT

EM

INV_IT

EM

_D

ETA

IL_ID

YVarc

har

15

S_IN

VC

_AD

J_IT

EM

NO

TES

YVarc

har

30

S_IN

VC

_AD

J_IT

EM

OR

IGIN

AL_

VALU

EY

Num

ber

22

22

7

S_IN

VC

_AD

J_IT

EM

REAS

ON

_C

DY

Varc

har

30

S_IN

VC

_AD

J_IT

EM

REQ

_PER

CEN

TAG

EY

Num

ber

22

22

7

S_IN

VC

_AD

J_IT

EM

REQ

_VALU

EY

Num

ber

22

22

7

S_IN

VC

_AD

J_IT

EM

RESO

UR

CE_TO

_A

DJ_

CD

YVarc

har

30

S_IN

VC

_AD

J_IT

EM

TAX_TR

EATM

EN

T_C

DY

Varc

har

30

S_IN

VC

_AD

J_IT

EM

TAX_VALU

EY

Num

ber

22

22

7

S_IN

VC

_IT

M_D

TL

DIS

CO

UN

T_AM

TY

Num

ber

22

10

0

S_IN

VC

_IT

M_D

TL

IS_C

UR

REN

CY_FL

GY

Char

1N

S_IN

VC

_IT

M_D

TL

ITEM

_D

TY

Date

7

S_IN

VC

_IT

M_D

TL

PH

_EXT_N

UM

YVarc

har

100

S_IN

VC

_IT

M_D

TL

TO

TAL_

US

GY

Num

ber

22

10

0

S_IN

VO

ICE

BIL

L_PR

OF_

IDY

Varc

har

15

Table

131.

New

Table

Colu

mns

in T

his

Vers

ion

Ta

ble

C

olu

mn

O

pt

Da

ta

Typ

eLen

Pre

cS

ca

leD

ef

LO

V T

yp

eLO

V

Bn

d



S_IN

VO

ICE_AD

JAD

J_EFF

_D

TY

Date

7

S_IN

VO

ICE_AD

JAD

J_LE

VEL_

CD

YVarc

har

30

S_IN

VO

ICE_AD

JAPPR

_PER

CEN

TAG

EY

Num

ber

22

22

7

S_IN

VO

ICE_AD

JB

ILL_

PR

OF_

IDY

Varc

har

15

S_IN

VO

ICE_AD

JR

EQ

_PER

CEN

TAG

EY

Num

ber

22

22

7

S_IN

VO

ICE_AD

JTA

X_TR

EATM

EN

T_C

DY

Varc

har

30

S_IN

VO

ICE_AD

JTA

X_VALU

EY

Num

ber

22

22

7

S_LE

AD

_IM

PT

AC

CN

T_PO

STN

_ID

YVarc

har

15

S_LE

AD

_IM

PT

AC

CN

T_R

EVN

_AM

TY

Num

ber

22

22

7

S_LE

AD

RES

P_IM

PT

QU

ESTIO

N_N

AM

EY

Varc

har

100

S_LO

Y_A

CR

L_IT

MPRTN

R_PT_D

EBT_Q

TY

YN

um

ber

22

10

0

S_LO

Y_A

CR

L_IT

MPT_SU

B_TYPE_ID

YVarc

har

15

S_LO

Y_A

CR

L_IT

MR

ET_EFF

_D

TY

UTC

D

ate

Tim

e7

S_LO

Y_A

CTC

RTR

BU

S_S

ER

VIC

E_N

AM

EY

Varc

har

75

S_LO

Y_A

CTC

RTR

METH

OD

_N

AM

EY

Varc

har

75

S_LO

Y_A

CTC

RTR

PR

OD

_ID

YVarc

har

15

S_LO

Y_A

CTC

RTR

PT_SU

B_TYPE_ID

YVarc

har

15

S_LO

Y_A

CTC

RTR

REL_

TYPE_C

DY

Varc

har

30

PARTY_R

ELA

TIO

NS

HIP

_TYPE

Y

S_LO

Y_A

CTC

RTR

VO

UC

HER

_Q

TY

YN

um

ber

22

10

0

S_LO

Y_ATT

RD

EFN

AC

CN

T_A

CT_C

DY

Varc

har

30

LOY_PT_EXP_

AC

C_A

CTVIT

Y_C

DY

S_LO

Y_ATT

RD

EFN

EXP_PD

_U

OM

_C

DY

Varc

har

30

LOY_PT_EXP_ U

OM

Y

Table

131.

New

Table

Colu

mns

in T

his

Vers

ion

Ta

ble

C

olu

mn

O

pt

Da

ta

Typ

eLen

Pre

cS

ca

leD

ef

LO

V T

yp

eLO

V

Bn

d



S_LO

Y_ATT

RD

EFN

EXP_PER

IOD

_LE

NY

Num

ber

22

22

7

S_LO

Y_ATT

RD

EFN

EXPIR

Y_A

LIG

N_C

DY

Varc

har

30

LOY_PT_EXP_

SN

AP_TO

Y

S_LO

Y_ATT

RD

EFN

EXPIR

Y_BA

SIS

_C

DY

Varc

har

30

LOY_PT_EXPIR

Y_

BASIS

_C

DY

S_LO

Y_ATT

RD

EFN

EXPIR

Y_D

AY_C

DY

Varc

har

30

FIN

S_C

F_

AG

REEM

NT_

PAYM

T_D

UE_D

AY

Y

S_LO

Y_ATT

RD

EFN

EXPIR

Y_M

ON

TH

_C

DY

Varc

har

30

LOY_M

ON

TH

_ T

YPE

Y

S_LO

Y_ATT

RD

EFN

METH

OD

_N

AM

EY

Varc

har

75

S_LO

Y_ATT

RD

EFN

MIN

_R

EA

CTIV

ATN

_Q

TY

YN

um

ber

22

10

0

S_LO

Y_ATT

RD

EFN

QU

AL_

PO

INT_FL

GN

Char

1N

S_LO

Y_ATT

RD

EFN

REAC

TIV

ATE_FL

GN

Char

1N

S_LO

Y_ATT

RD

EFN

RET_EFF

_FL

GN

Char

1N

S_LO

Y_ATT

RD

EFN

RPT_EXP_PD

_U

OM

_C

DY

Varc

har

30

S_LO

Y_ATT

RD

EFN

RPT_EXP_PER

IOD

_LE

NY

Num

ber

22

10

0

S_LO

Y_B

UC

KET

OR

DER

_N

UM

YN

um

ber

22

10

0

S_LO

Y_M

EM

_TIE

RAPPLD

_PR

OM

O_R

L_ID

YVarc

har

15

S_LO

Y_M

EM

_TIE

RAPPLI

ED

_PR

OM

O_ID

YVarc

har

15

S_LO

Y_M

EM

_TIE

RB

ULK

_R

EF_

IDY

Varc

har

15

S_LO

Y_M

EM

_TIE

RFU

TR

_TIE

R_ID

YVarc

har

15

S_LO

Y_M

EM

_TIE

RFU

TR

_TIE

R_STA

MP_D

TY

UTC

D

ate

Tim

e7

S_LO

Y_M

EM

_TIE

RN

EXT_ASS

ESS_D

TY

UTC

D

ate

Tim

e7

Table

131.

New

Table

Colu

mns

in T

his

Vers

ion

Ta

ble

C

olu

mn

O

pt

Da

ta

Typ

eLen

Pre

cS

ca

leD

ef

LO

V T

yp

eLO

V

Bn

d



S_LO

Y_M

EM

_TIE

RPO

INT_TYPE_E_VAL

YN

um

ber

22

22

7

S_LO

Y_M

EM

_TIE

RPO

INT_TYPE_F_

VAL

YN

um

ber

22

22

7

S_LO

Y_M

EM

_TIE

RPO

INT_TYPE_G

_VAL

YN

um

ber

22

22

7

S_LO

Y_M

EM

_TIE

RPO

INT_TYPE_H

_VA

LY

Num

ber

22

22

7

S_LO

Y_M

EM

_TIE

RQ

UAL_

EN

D_D

TY

UTC

D

ate

Tim

e7

S_LO

Y_M

EM

_VC

HR

BAS

IS_C

DY

Varc

har

30

Tie

r Rew

ar

LOY_V

CH

R_B

AS

IS_

CD

Y

S_LO

Y_M

EM

_VC

HR

CO

NS

UM

ED

_TXN

_ID

YVarc

har

15

S_LO

Y_M

EM

_VC

HR

MER

GE_M

EM

_ID

YVarc

har

15

S_LO

Y_M

EM

_VC

HR

OR

IG_VC

HR

_ID

YVarc

har

15

S_LO

Y_M

EM

_VC

HR

TXN

_IT

EM

_ID

YVarc

har

15

S_LO

Y_M

EM

BER

AC

CR

UAL_

TYPE_C

DY

Varc

har

30

LOY_C

OR

P_A

CC

R_

TYPE

Y

S_LO

Y_M

EM

BER

CO

RP_M

EM

_N

UM

YVarc

har

15

S_LO

Y_M

EM

BER

HO

ME_AIR

PO

RT

YVarc

har

30

S_LO

Y_M

EM

BER

LAS

T_A

CC

R_TXN

_D

TY

UTC

D

ate

Tim

e7

S_LO

Y_M

EM

BER

LAS

T_R

DM

_TXN

_D

TY

UTC

D

ate

Tim

e7

S_LO

Y_M

EM

BER

LFTM

_PT_TYPE_E_VA

LY

Num

ber

22

22

7

S_LO

Y_M

EM

BER

LFTM

_PT_TYPE_F_

VAL

YN

um

ber

22

22

7

S_LO

Y_M

EM

BER

LFTM

_PT_TYPE_G

_VAL

YN

um

ber

22

22

7

S_LO

Y_M

EM

BER

LFTM

_PT_TYPE_H

_VAL

YN

um

ber

22

22

7

Table

131.

New

Table

Colu

mns

in T

his

Vers

ion

Ta

ble

C

olu

mn

O

pt

Da

ta

Typ

eLen

Pre

cS

ca

leD

ef

LO

V T

yp

eLO

V

Bn

d



S_LO

Y_M

EM

BER

MEM

SH

IP_SC

HEM

E_ID

YVarc

har

15

S_LO

Y_M

EM

BER

PO

INT_TYPE_E_VAL

YN

um

ber

22

22

7

S_LO

Y_M

EM

BER

PO

INT_TYPE_F_

VAL

YN

um

ber

22

22

7

S_LO

Y_M

EM

BER

PO

INT_TYPE_G

_VAL

YN

um

ber

22

22

7

S_LO

Y_M

EM

BER

PO

INT_TYPE_H

_VA

LY

Num

ber

22

22

7

S_LO

Y_M

EM

BER

STM

T_TYPE_C

DY

Varc

har

30

LOY_STM

T_TYPE_

CD

S_LO

Y_M

EM

BER

SU

RV

_M

EM

_ID

YVarc

har

15

S_LO

Y_PR

OD

_PT

DIS

TAN

CE_U

OM

_C

DY

Varc

har

30

LOY_U

OM

_C

DY

S_LO

Y_PR

OD

_PT

MA

X_D

ISTA

NC

EY

Num

ber

22

22

7

S_LO

Y_PR

OD

_PT

MIN

_D

ISTA

NC

EY

Num

ber

22

22

7

S_LO

Y_PR

OD

_PT

PR

_AM

T_C

RC

Y_EXC

_D

TY

Date

7

S_LO

Y_PR

OD

_PT

PR

ICE_AM

TY

Num

ber

22

22

7

S_LO

Y_PR

OD

_PT

PR

ICE_AM

T_C

UR

CY_C

DY

Varc

har

20

S_LO

Y_PR

OD

_PT

PR

OD

_PT_U

IDN

Varc

har

15

S_LO

Y_PR

OD

_PT

PRTN

R_PR

I_TYPE_C

DY

Varc

har

30

LOY_PRTN

R_

PR

ICE_TYPE_C

DY

S_LO

Y_PR

OD

_PT

PRTN

R_PR

ICE_AM

TY

Num

ber

22

22

7

S_LO

Y_PR

OD

_PT

PYM

T_TYPE_C

DY

Varc

har

30

Poin

ts

LOY_PA

YM

EN

T_ C

DY

S_LO

Y_PR

OG

_O

RG

AC

RL_

VALI

D_PD

_LE

NY

Num

ber

22

22

7

S_LO

Y_PR

OG

_O

RG

AC

RL_

VALI

D_U

OM

_C

DY

Varc

har

30

LOY_PT_EXP_ U

OM

Y

S_LO

Y_PR

OG

_O

RG

ALL

W_N

EG

ATIV

E_FL

GN

Char

1N

S_LO

Y_PR

OG

_O

RG

BIL

LIN

G_TYPE_C

DY

Varc

har

30

Table

131.

New

Table

Colu

mns

in T

his

Vers

ion

Ta

ble

C

olu

mn

O

pt

Da

ta

Typ

eLen

Pre

cS

ca

leD

ef

LO

V T

yp

eLO

V

Bn

d



S_LO

Y_PR

OG

_O

RG

CR

ED

IT_LI

MIT

YN

um

ber

22

10

0

S_LO

Y_PR

OG

_O

RG

MIN

_O

RD

ER

_Q

TY

YN

um

ber

22

10

0

S_LO

Y_PR

OG

_O

RG

PR

EC

ALC

_AC

RL_

FLG

NC

har

1N

S_LO

Y_PR

OG

_O

RG

PR

ICIN

G_R

ULE

_ID

YVarc

har

15

S_LO

Y_PR

OG

_O

RG

REO

RD

ER

_LI

MIT

YN

um

ber

22

10

0

S_LO

Y_PR

OG

_O

RG

RET_B

EFO

RE_D

AYS

YN

um

ber

22

10

0

S_LO

Y_PR

OG

_O

RG

SK

IP_AC

RL_

VAL_

FLG

NC

har

1N

S_LO

Y_PR

OG

_O

RG

VA

LDT_D

ISPU

TE_U

SR

YVarc

har

30

S_LO

Y_PR

OG

_O

RG

VA

LID

_D

ISPU

TE_FL

GN

Char

1N

S_LO

Y_PR

OG

RAM

PN

T_TO

_PA

Y_FL

GN

Char

1N

S_LO

Y_PR

OG

RAM

PO

INT_EXP_LE

VEL_

CD

YVarc

har

30

Tie

r Le

vel

LOY_PT_EXP_LV

L_C

DY

S_LO

Y_PR

OG

RAM

PU

R_S

TRT_D

AY_C

DY

Varc

har

30

1FI

NS_C

F_

AG

REEM

NT_

PAYM

T_D

UE_ D

AY

Y

S_LO

Y_PR

OG

RAM

PU

R_S

TRT_M

TH

_C

DY

Varc

har

30

Janu

ary

MO

NTH

_N

AM

EY

S_LO

Y_PR

OG

RAM

REVR

EC

G_PER

IOD

_D

UR

YN

um

ber

22

22

7

S_LO

Y_PR

OG

RAM

REVR

EC

G_PR

D_TYP_C

DY

Varc

har

30

LOY_R

EVR

EC

G_

PER

IOD

Y

S_LO

Y_PR

OG

RAM

TXFR

_S

TRT_D

AY_C

DY

Varc

har

30

1FI

NS_C

F_

AG

REEM

NT_

PAYM

T_D

UE_ D

AY

Y

S_LO

Y_PR

OG

RAM

TXFR

_S

TRT_M

TH

_C

DY

Varc

har

30

Janu

ary

MO

NTH

_N

AM

EY

S_LO

Y_PR

OM

OB

ASE_PR

OM

O_FL

GN

Char

1N

Table

131.

New

Table

Colu

mns

in T

his

Vers

ion

Ta

ble

C

olu

mn

O

pt

Da

ta

Typ

eLen

Pre

cS

ca

leD

ef

LO

V T

yp

eLO

V

Bn

d



S_LO

Y_PR

OM

OEXPO

RT_FL

GN

Char

1N

S_LO

Y_PR

OM

OO

RD

ER

_FL

GN

Char

1N

S_LO

Y_PR

OM

OPK

G_A

CR

L_FL

GN

Char

1N

S_LO

Y_PR

OM

OM

EM

ELI

G_FL

GN

Char

1N

S_LO

Y_PTR

_ATM

PC

ITY_C

DY

Varc

har

30

S_LO

Y_R

DM

_IT

MPR

_D

EBT_PT

YN

um

ber

22

10

0

S_LO

Y_S

TM

TM

EM

_TIE

R_ID

YVarc

har

15

S_LO

Y_S

TM

TPA

RTN

ER

_ID

YVarc

har

15

S_LO

Y_S

TM

TR

EP_FI

LE_N

AM

EY

Varc

har

500

S_LO

Y_S

TM

TR

EP_S

TATU

S_C

DY

Varc

har

30

LOY_S

TM

T_C

RTN

_S

TATU

S_C

D

S_LO

Y_S

TM

TSTM

T_TYPE_C

DY

Varc

har

30

LOY_STM

T_TYPE_

CD

S_LO

Y_S

TM

TTR

X_ID

YVarc

har

15

S_LO

Y_S

TM

TVO

UC

HER

_ID

YVarc

har

15

S_LO

Y_S

TM

T_C

RTN

PR

OG

_ID

YVarc

har

15

S_LO

Y_S

TM

T_C

RTN

STM

T_TYPE_C

DY

Varc

har

30

LOY_STM

T_TYPE_

CD

S_LO

Y_S

TM

T_IT

MB

ILL_

AM

OU

NT

YN

um

ber

22

10

0

S_LO

Y_S

TM

T_IT

MC

UR

CY_C

DY

Varc

har

20

S_LO

Y_S

TM

T_IT

MN

ON

_B

ILL_

AM

OU

NT

YN

um

ber

22

10

0

S_LO

Y_S

TM

T_IT

MPA

RTN

ER

_PR

ICE

YN

um

ber

22

10

0

S_LO

Y_S

TM

T_IT

MPT_SU

B_TYPE_ID

YVarc

har

15

S_LO

Y_S

TM

T_LO

GPA

RTN

ER

_ID

YVarc

har

15

Table

131.

New

Table

Colu

mns

in T

his

Vers

ion

Ta

ble

C

olu

mn

O

pt

Da

ta

Typ

eLen

Pre

cS

ca

leD

ef

LO

V T

yp

eLO

V

Bn

d



S_LO

Y_S

TM

T_TX

NPA

RTN

ER

_PR

ICE

YN

um

ber

22

10

0

S_LO

Y_TIE

RD

WN

GR

D_APPR

V_FL

GN

Char

1N

S_LO

Y_TIE

R_C

LSAPPLY

_FL

GN

Char

1N

S_LO

Y_TIE

R_C

LSAPPR

OV

ER

_ID

YVarc

har

15

S_LO

Y_TIE

R_C

LSASS

ESS

_D

AY_C

DY

Varc

har

30

FIN

S_C

F_

AG

REEM

NT_

PAYM

T_D

UE_ D

AY

Y

S_LO

Y_TIE

R_C

LSASS

ESS

_M

ON

TH

_C

DY

Varc

har

30

MO

NTH

_N

AM

EY

S_LO

Y_TIE

R_C

LSASS

ESS

_R

EC

UR

_C

DY

Varc

har

30

LOY_TA

_R

EC

UR

_

TYPE

Y

S_LO

Y_TIE

R_C

LSEN

D_TIE

R_PD

_D

AY_C

DY

Varc

har

30

FIN

S_C

F_

AG

REEM

NT_

PAYM

T_D

UE_ D

AY

Y

S_LO

Y_TIE

R_C

LSEN

D_TIE

R_PD

_M

TH

_C

DY

Varc

har

30

MO

NTH

_N

AM

EY

S_LO

Y_TIE

R_C

LSM

IN_TIE

R_LE

NY

Num

ber

22

22

7

S_LO

Y_TIE

R_C

LSM

IN_TIE

RLE

N_U

OM

_C

DY

Varc

har

30

LOY_LE

AD

_TIM

E_

CD

Y

S_LO

Y_TIE

R_C

LSQ

UAL_

PD

_U

OM

_C

DY

Varc

har

30

LOY_LE

AD

_TIM

E_

CD

Y

S_LO

Y_TIE

R_C

LSQ

UAL_

PER

IOD

_LE

NY

Num

ber

22

22

7

S_LO

Y_TIE

R_C

LSR

EQ

UAL_

PD

_U

OM

_C

DY

Varc

har

30

REQ

UAL_

PD

_U

OM

_C

DY

S_LO

Y_TIE

R_C

LSR

EQ

UAL_

PER

IOD

_LE

NY

Num

ber

22

22

7

S_LO

Y_TIE

R_C

LSST_Q

UAL_

PD

_D

AY_C

DY

Varc

har

30

FIN

S_C

F_

AG

REEM

NT_PA

YM

T_D

UE_ D

AY

Table

131.

New

Table

Colu

mns

in T

his

Vers

ion

Ta

ble

C

olu

mn

O

pt

Da

ta

Typ

eLen

Pre

cS

ca

leD

ef

LO

V T

yp

eLO

V

Bn

d



S_LO

Y_TIE

R_C

LSST_Q

UAL_

PD

_M

TH

_C

DY

Varc

har

30

MO

NTH

_N

AM

E

S_LO

Y_TIE

R_C

LSST_TIE

R_PD

_D

AY_C

DY

Varc

har

30

FIN

S_C

F_

AG

REEM

NT_

PAYM

T_D

UE_ D

AY

Y

S_LO

Y_TIE

R_C

LSST_TIE

R_PD

_M

TH

_C

DY

Varc

har

30

MO

NTH

_N

AM

EY

S_LO

Y_TXN

AC

CR

_R

ULE

_ID

YVarc

har

15

S_LO

Y_TXN

AC

TIV

ITY_D

AY

YN

um

ber

22

10

0

S_LO

Y_TXN

AC

TIV

ITY_H

OU

RY

Num

ber

22

10

0

S_LO

Y_TXN

AM

T_VA

LY

Num

ber

22

22

7

S_LO

Y_TXN

BID

_FL

GN

Char

1N

S_LO

Y_TXN

BO

OK

ING

_D

TY

UTC

D

ate

Tim

e7

S_LO

Y_TXN

BU

LK_R

EF_

IDY

Varc

har

15

S_LO

Y_TXN

CAN

C_R

EASO

N_C

DY

Varc

har

30

LOY_C

AN

C_

REASO

N_C

DY

S_LO

Y_TXN

CH

ILD

_TXN

_ID

YVarc

har

15

S_LO

Y_TXN

CO

RP_R

EF_

NU

MY

Varc

har

15

S_LO

Y_TXN

DES

T_C

ITY_C

DY

Varc

har

30

S_LO

Y_TXN

EN

RO

L_PR

OM

O_ID

YVarc

har

15

S_LO

Y_TXN

INC

EN

TIV

_C

HO

ICE

YVarc

har

30

S_LO

Y_TXN

LOC

ATIO

N_C

DY

Varc

har

30

S_LO

Y_TXN

MK

TG

_FL

T_N

UM

YVarc

har

30

S_LO

Y_TXN

OPER

_C

AR

RIE

R_ID

YVarc

har

15

S_LO

Y_TXN

OPER

_FL

T_N

UM

YVarc

har

30

Table

131.

New

Table

Colu

mns

in T

his

Vers

ion

Ta

ble

C

olu

mn

O

pt

Da

ta

Typ

eLen

Pre

cS

ca

leD

ef

LO

V T

yp

eLO

V

Bn

d



S_LO

Y_TXN

OR

DER

_N

UM

YN

um

ber

22

10

0

S_LO

Y_TXN

OR

DER

_Q

TY

YN

um

ber

22

22

7

S_LO

Y_TXN

OR

IG_AC

RL_

REF_

IDY

Varc

har

15

S_LO

Y_TXN

OR

IG_AM

OU

NT

YN

um

ber

22

22

7

S_LO

Y_TXN

OR

IG_O

RD

_IT

M_ID

YVarc

har

15

S_LO

Y_TXN

OR

IG_PO

INTS

YN

um

ber

22

10

0

S_LO

Y_TXN

OR

IGIN

_C

ITY_C

DY

Varc

har

30

S_LO

Y_TXN

OVR

_D

UP_C

HEC

K_FL

GN

Char

1N

S_LO

Y_TXN

OVR

_PR

I_FL

AG

NC

har

1N

S_LO

Y_TXN

PAC

KA

GE_C

DY

Varc

har

30

LOY_PA

CK

AG

E

S_LO

Y_TXN

PER

IOD

_D

UR

_C

DY

Varc

har

30

LOY_M

EM

_PER

_

TYPE

Y

S_LO

Y_TXN

PER

IOD

_TYPE_C

DY

Varc

har

30

LOY_M

EM

_PER

_

TYPE

Y

S_LO

Y_TXN

PYM

T_TYPE_C

DY

Varc

har

30

LOY_PA

YM

EN

T_ C

D

S_LO

Y_TXN

RD

M_IT

M_ID

YVarc

har

15

S_LO

Y_TXN

RD

M_Q

TY

YN

um

ber

22

22

7

S_LO

Y_TXN

RD

M_Q

TY_U

OM

_C

DY

Varc

har

30

LOY_U

OM

_C

DY

S_LO

Y_TXN

REAS

ON

_C

DY

Varc

har

30

S_LO

Y_TXN

REFU

ND

_B

ASIS

_C

DY

Varc

har

30

LOY_R

EFU

ND

_

BASIS

Y

S_LO

Y_TXN

REFU

ND

_PC

TY

Num

ber

22

22

7

S_LO

Y_TXN

RFN

D_O

VR

D_C

MN

TS

YVarc

har

250

Table

131.

New

Table

Colu

mns

in T

his

Vers

ion

Ta

ble

C

olu

mn

O

pt

Da

ta

Typ

eLen

Pre

cS

ca

leD

ef

LO

V T

yp

eLO

V

Bn

d



S_LO

Y_TXN

RFN

D_O

VR

D_R

SN

_C

DY

Varc

har

30

LOY_O

VR

_

REASO

N_C

DY

S_LO

Y_TXN

SO

UR

CE_C

DY

Varc

har

30

LOY_TX

N_

SO

UR

CE_C

D

S_LO

Y_TXN

TAX_AM

TY

Num

ber

22

22

7

S_LO

Y_TXN

TO

_M

EM

_N

UM

YVarc

har

30

S_LO

Y_TXN

TO

TAL_

LIN

ES

YN

um

ber

22

10

0

S_LO

Y_TXN

TR

VL_

DIS

TAN

CE

YN

um

ber

22

22

7

S_LO

Y_TXN

TXN

_S

OU

RC

E_C

DY

Varc

har

30

LOY_TX

N_

SO

UR

CE_C

D

S_LO

Y_TXN

VA

L_S

TATU

S_C

DY

Varc

har

30

LOY_TX

N_VA

L_

STA

TU

S

S_M

KTG

_S

RVR

_TS

KIM

PRT_TS

K_ID

YVarc

har

15

S_N

OTE_O

PTY

PG

RO

UP_PU

BLI

C_FL

GY

Char

1N

S_O

PTY

PG

RO

UP_PU

BLI

C_FL

GY

Char

1N

S_O

PTY_D

SG

N_R

EG

CU

ST_A

CC

NT_ID

YVarc

har

15

S_O

PTY_D

SG

N_R

EG

DS

GN

_C

OM

PLE

TE_D

TY

UTC

D

ate

Tim

e7

S_O

PTY_D

SG

N_R

EG

EN

D_EQ

UIP

_C

DY

Varc

har

30

HTIM

_EN

D_

EQ

UIP

_C

DY

S_O

PTY_D

SG

N_R

EG

ESTIM

ATE_U

NIT

SY

Num

ber

22

10

0

S_O

PTY_D

SG

N_R

EG

PR

OD

_PR

OB

_C

DY

Varc

har

30

PR

OJ_

PR

IOR

ITY_

CO

DE

Y

S_O

PTY_D

SG

N_R

EG

PR

OD

_PR

OB

_R

EASO

NY

Varc

har

50

S_O

PTY_D

SG

N_R

EG

PR

OG

_LI

FE_TIM

EY

Num

ber

22

10

0

Table

131.

New

Table

Colu

mns

in T

his

Vers

ion

Ta

ble

C

olu

mn

O

pt

Da

ta

Typ

eLen

Pre

cS

ca

leD

ef

LO

V T

yp

eLO

V

Bn

d



S_O

PTY_D

SG

N_R

EG

PR

OG

_TYPE_C

DY

Varc

har

30

HTIM

_PR

OG

_

TYPE_C

DY

S_O

PTY_D

SG

N_R

EG

REG

_S

TAT_C

DY

Varc

har

30

HTIM

_STA

TU

S_ C

D

S_O

PTY_D

SG

N_R

EG

TIM

E_U

NIT

_C

DY

Varc

har

30

Mont

hs

UN

IT_VA

LUES

Y

S_O

PTY_D

SG

N_R

EG

USAG

EY

Num

ber

22

10

0

S_O

RD

_IT

M_LO

YX

BID

_FL

AG

NC

har

1N

S_O

RD

_IT

M_LO

YX

BO

OK

ING

_D

TY

UTC

D

ate

Tim

e7

S_O

RD

_IT

M_LO

YX

DIS

TAN

CE

YN

um

ber

22

22

7

S_O

RD

_IT

M_LO

YX

EN

D_D

TY

UTC

D

ate

Tim

e7

S_O

RD

_IT

M_LO

YX

OVER

RID

E_PR

I_FL

GN

Char

1N

S_O

RD

_IT

M_LO

YX

OVER

RID

E_R

EAS

ON

YVarc

har

250

S_O

RD

_IT

M_LO

YX

OVER

RID

E_R

EAS

ON

_C

DY

Varc

har

30

LOY_O

VR

_

REASO

N_C

DY

S_O

RD

_IT

M_LO

YX

PO

INTS_LO

AN

YN

um

ber

22

22

7

S_O

RD

_IT

M_LO

YX

PO

INTS_U

SED

YN

um

ber

22

22

7

S_O

RD

_IT

M_LO

YX

STA

RT_D

TY

UTC

D

ate

Tim

e7

S_O

RD

_IT

M_LO

YX

TR

VL_

DIS

TAN

CE

YN

um

ber

22

22

7

S_O

RD

_IT

M_LO

YX

TXN

_AM

OU

NT

YN

um

ber

22

22

7

S_O

RD

_IT

M_LO

YX

TXN

_PO

INTS

YN

um

ber

22

22

7

S_O

RD

_IT

M_LO

YX

VO

UC

HER

_ID

YVarc

har

15

S_O

RD

_IT

M_LO

YX

VO

UC

HER

_Q

TY

YN

um

ber

10

10

0

Table

131.

New

Table

Colu

mns

in T

his

Vers

ion

Ta

ble

C

olu

mn

O

pt

Da

ta

Typ

eLen

Pre

cS

ca

leD

ef

LO

V T

yp

eLO

V

Bn

d



S_O

RD

ER

BIL

L_PR

OFI

LE_ID

YVarc

har

15

S_O

RD

ER

_IT

EM

AG

EN

CY_N

AM

EY

Varc

har

100

S_O

RD

ER

_IT

EM

BIL

L_PR

OFI

LE_ID

YVarc

har

15

S_O

RD

ER

_IT

EM

EN

D_PH

ON

E_N

UM

YVarc

har

20

S_O

RD

ER

_IT

EM

OR

IG_AC

CN

T_N

UM

YVarc

har

50

S_O

RD

ER

_IT

EM

OR

IG_PIN

YVarc

har

50

S_O

RD

ER

_IT

EM

PO

RT_N

UM

YVarc

har

20

S_O

RD

ER

_IT

EM

RLT

D_S

RVC

_PR

OD

_ID

YVarc

har

15

S_O

RD

ER

_IT

EM

RLT

DSR

VC

AS

T_IN

T_ID

YVarc

har

15

S_O

RD

ER

_IT

EM

RQ

ST_PO

RT_D

ATE

YU

TC

D

ate

Tim

e7

S_O

RD

ER

_IT

EM

STA

RT_PH

ON

E_N

UM

YVarc

har

20

S_O

RD

ER

_IT

EM

SV

C_PR

OVID

ER

YVarc

har

100

S_O

RD

ER

_IT

EM

SV

C_ZIP

_C

OD

EY

Varc

har

30

S_O

RD

ER

_IT

EM

_O

MPR

EV_B

ILL_

PR

OF_

IDY

Varc

har

15

S_O

RD

ER

_IT

EM

_O

MPR

EV_N

ET_PR

IY

Num

ber

25

10

0

S_O

RD

ER

_IT

EM

_O

MSU

B_A

CTIO

N_C

DY

Varc

har

30

S_O

RG

_EXT

AIA

_IN

TEG

_ID

YVarc

har

150

S_O

RG

_EXT

APPR

OVA

L_S

TATU

S_C

DY

Varc

har

30

APPR

OVAL_

S

TATU

SY

S_O

RG

_EXT

PR

_BIL

L_PR

FL_ID

YVarc

har

15

S_O

RG

_G

RO

UP

AIA

_IN

TEG

_ID

YVarc

har

150

S_O

RG

_G

RO

UP

MN

TH

LY_H

S_C

OST_AM

TY

Num

ber

22

10

0

Table

131.

New

Table

Colu

mns

in T

his

Vers

ion

Ta

ble

C

olu

mn

O

pt

Da

ta

Typ

eLen

Pre

cS

ca

leD

ef

LO

V T

yp

eLO

V

Bn

d



S_O

RG

_G

RO

UP

PR

_D

OM

ESTC

_LA

NG

_ID

YVarc

har

5

S_PA

RTY

AD

MIN

_AD

J_FL

GN

Char

1N

S_PG

RO

UP

CO

NFI

DEN

TIA

L_FL

GY

Char

1N

S_PG

RO

UP

PR

_PO

STN

_ID

YVarc

har

15

S_PG

RO

UP

SU

PPR

ESS

_FL

GY

Char

1N

S_PO

STN

PG

RO

UP_ID

YVarc

har

15

S_PO

STN

_C

ON

NEXT_C

ALL

_D

TY

UTC

D

ate

Tim

e7

S_PO

STN

_C

ON

NEXT_C

ALL

_O

BJE

CTIV

YVarc

har

1500

S_PR

D_C

MPLN

T_LS

CO

MB_PR

OD

_FL

GY

Char

1N

S_PR

D_C

MPLN

T_LS

PR

D_S

UB_TR

AC

K_N

UM

YVarc

har

30

S_PR

D_C

MPLN

T_LS

PR

E_M

KT_APPL_

NU

MY

Varc

har

30

S_PR

D_C

MPLN

T_LS

SEVEN

_D

AY_R

PT_FL

GY

Char

1N

S_PR

D_C

MPLN

T_LS

TH

IRTY_D

AY_R

PT_FL

GY

Char

1N

S_PR

OD

_IN

TB

ILLI

NG

_TYPE_C

DY

Varc

har

30

S_PR

OD

_IN

TD

PN

DN

CY_VLD

TN

_FL

GY

Char

1N

S_PR

OD

_IN

TLO

Y_EX

PR

_BAS

IS_C

DY

Varc

har

30

LOY_EXPR

_

BASIS

_C

DY

S_PR

OD

_IN

TLO

Y_N

UM

_YEAR

YN

um

ber

22

22

7

S_PR

OD

_IN

TLO

Y_PER

IOD

_D

UR

YN

um

ber

22

22

7

S_PR

OD

_IN

TLO

Y_PER

IOD

_TYPE_C

DY

Varc

har

30

LOY_M

EM

_PER

_

TYPE

Y

S_PR

OD

_IN

TLO

Y_SEQ

_TYPE_C

DY

Varc

har

30

LOY_S

EQ

_TYPE_

CD

Y

Table

131.

New

Table

Colu

mns

in T

his

Vers

ion

Ta

ble

C

olu

mn

O

pt

Da

ta

Typ

eLen

Pre

cS

ca

leD

ef

LO

V T

yp

eLO

V

Bn

d



S_PR

OD

_IN

TLO

Y_SER

IES_PR

EFI

XY

Varc

har

15

S_PR

OD

_IN

TLO

Y_VC

H_EX

P_D

AY_C

DY

Varc

har

30

FIN

S_C

F_

AG

REEM

NT_

PAYM

T_D

UE_D

AY

Y

S_PR

OD

_IN

TLO

Y_VC

H_EX

P_M

TH

_C

DY

Varc

har

30

MO

NTH

_N

AM

EY

S_PR

OD

_IN

TLO

Y_VC

HR

EXP_PR

DD

UR

YN

um

ber

22

22

7

S_PR

OD

_IN

TLO

Y_VEXP_PERTYP_C

DY

Varc

har

30

LOY_V

CH

R_

EX

PIR

Y_PER

IOD

_

TYPE

Y

S_PR

OD

_IN

TPA

YM

NT_TYPE_C

DY

Varc

har

30

BIL

L_PA

YM

EN

T_

TYPE

Y

S_PR

OD

_IN

TPER

MIT

TED

_TYPE

YVarc

har

250

S_PR

OD

_IN

TR

EQ

D_S

ER

VIC

E_FL

GY

Char

1N

S_PR

OD

_IN

T_LS

XC

OM

_D

EV

_N

AM

EY

Varc

har

50

S_PR

OD

_IN

T_LS

XC

UTO

FF_TH

RESH

OLD

YN

um

ber

22

22

7

S_PR

OD

_IN

T_LS

XM

AX_PR

OD

UC

T_Q

TY

YN

um

ber

22

22

7

S_PR

OD

_R

EL

SV

C_C

HR

G_C

DY

Varc

har

30

S_PR

OM

_PM

TR

XEFF

_EN

D_TS

YU

TC

D

ate

Tim

e7

S_PR

OM

_PM

TR

XEFF

_STA

RT_TS

YU

TC

D

ate

Tim

e7

S_PR

SP_C

ON

TAC

TEM

AIL

_STA

TU

S_C

DY

Varc

har

30

EM

AIL

_STA

TU

SY

S_PR

SP_C

ON

TAC

TLS

T_EM

AIL

AD

R_U

PD

YU

TC

D

ate

Tim

e7

S_PR

SP_C

ON

TAC

TN

UM

_H

AR

D_B

NC

EY

Num

ber

22

10

0

S_PR

SP_C

ON

TAC

TN

UM

_SO

FT_B

NC

EY

Num

ber

22

10

0

Table

131.

New

Table

Colu

mns

in T

his

Vers

ion

Ta

ble

C

olu

mn

O

pt

Da

ta

Typ

eLen

Pre

cS

ca

leD

ef

LO

V T

yp

eLO

V

Bn

d



S_PS_C

ON

TAC

TATT

AC

H_C

NTR

YN

um

ber

22

10

0

S_PS_C

ON

TAC

TSTU

DEN

T_FL

GY

Char

1N

S_PS_C

ON

TAC

TVETER

AN

_FL

GY

Char

1N

S_Q

UO

_IT

M_LO

YX

BID

_FL

AG

NC

har

1N

S_Q

UO

_IT

M_LO

YX

BO

OK

ING

_D

TY

UTC

D

ate

Tim

e7

S_Q

UO

_IT

M_LO

YX

DIS

TAN

CE

YN

um

ber

22

22

7

S_Q

UO

_IT

M_LO

YX

EN

D_D

TY

UTC

D

ate

Tim

e7

S_Q

UO

_IT

M_LO

YX

OVER

RID

E_PR

I_FL

GN

Char

1N

S_Q

UO

_IT

M_LO

YX

OVER

RID

E_R

EAS

ON

YVarc

har

250

S_Q

UO

_IT

M_LO

YX

OVER

RID

E_R

EAS

ON

_C

DY

Varc

har

30

LOY_O

VR

_

REASO

N_C

DY

S_Q

UO

_IT

M_LO

YX

PO

INTS_LO

AN

YN

um

ber

22

22

7

S_Q

UO

_IT

M_LO

YX

PO

INTS_U

SED

YN

um

ber

22

22

7

S_Q

UO

_IT

M_LO

YX

STA

RT_D

TY

UTC

D

ate

Tim

e7

S_Q

UO

_IT

M_LO

YX

TR

VL_

DIS

TAN

CE

YN

um

ber

22

22

7

S_Q

UO

_IT

M_LO

YX

TXN

_AM

OU

NT

YN

um

ber

22

22

7

S_Q

UO

_IT

M_LO

YX

TXN

_PO

INTS

YN

um

ber

22

22

7

S_Q

UO

_IT

M_LO

YX

VO

UC

HER

_ID

YVarc

har

15

S_Q

UO

_IT

M_LO

YX

VO

UC

HER

_Q

TY

YN

um

ber

10

10

0

S_Q

UO

TE_IT

EM

AG

EN

CY_N

AM

EY

Varc

har

100

S_Q

UO

TE_IT

EM

BIL

L_PR

OFI

LE_ID

YVarc

har

15

Table

131.

New

Table

Colu

mns

in T

his

Vers

ion

Ta

ble

C

olu

mn

O

pt

Da

ta

Typ

eLen

Pre

cS

ca

leD

ef

LO

V T

yp

eLO

V

Bn

d



S_Q

UO

TE_IT

EM

EN

D_PH

ON

E_N

UM

YVarc

har

20

S_Q

UO

TE_IT

EM

OR

IG_AC

CN

T_N

UM

YVarc

har

50

S_Q

UO

TE_IT

EM

OR

IG_PIN

YVarc

har

50

S_Q

UO

TE_IT

EM

PO

RT_N

UM

YVarc

har

20

S_Q

UO

TE_IT

EM

RLT

D_S

RVC

_PR

OD

_ID

YVarc

har

15

S_Q

UO

TE_IT

EM

RLT

DSR

VC

AS

T_IN

T_ID

YVarc

har

15

S_Q

UO

TE_IT

EM

RQ

ST_PO

RT_D

ATE

YTim

e

Sta

mp

7

S_Q

UO

TE_IT

EM

STA

RT_PH

ON

E_N

UM

YVarc

har

20

S_Q

UO

TE_IT

EM

SV

C_PR

OVID

ER

YVarc

har

100

S_Q

UO

TE_IT

EM

SV

C_ZIP

_C

OD

EY

Varc

har

30

S_Q

UO

TE_IT

EM

_O

MPR

EV_B

ILL_

PR

OF_

IDY

Varc

har

15

S_Q

UO

TE_IT

EM

_O

MPR

EV_N

ET_PR

IY

Num

ber

25

10

0

S_Q

UO

TE_IT

EM

_O

MSU

B_A

CTIO

N_C

DY

Varc

har

30

S_Q

UO

TE_IT

M_SPA

AU

TH

_C

OST_AM

TY

Num

ber

22

22

7

S_Q

UO

TE_IT

M_SPA

SPA

_IT

M_AC

TIO

N_C

DY

Varc

har

30

HTIM

_Q

UO

TE_

AC

TIO

N_TYPE

S_Q

UO

TE_IT

M_SPA

STA

TU

S_U

PD

_BY

YVarc

har

15

S_R

EV

NU

SAG

EY

Num

ber

22

10

0

S_SAM

PLE

_TX

NAPPR

OV

ER

_ID

YVarc

har

15

S_SAM

PLE

_TX

NN

UM

_PA

CK

AG

E_R

EC

DY

Num

ber

22

10

0

S_SAM

PLE

_TX

NN

UM

_PA

CK

AG

E_SEN

TY

Num

ber

22

10

0

S_SAM

PLE

_TX

NO

LD_TXN

_ID

YVarc

har

15

Table

131.

New

Table

Colu

mns

in T

his

Vers

ion

Ta

ble

C

olu

mn

O

pt

Da

ta

Typ

eLen

Pre

cS

ca

leD

ef

LO

V T

yp

eLO

V

Bn

d



S_SAM

PLE

_TX

NPK

G_A

RR

IVA

L_D

TY

UTC

D

ate

Tim

e7

S_SAM

PLE

_TX

NPK

G_D

LVRY_D

TY

UTC

D

ate

Tim

e7

S_SAM

PLE

_TX

NR

OO

T_TX

N_ID

YVarc

har

15

S_SAM

PLE

_TX

NSR

C_TXN

_ID

YVarc

har

15

S_SAM

PLE

_TX

NTR

AC

KIN

G_N

UM

YVarc

har

30

S_SD

_PIM

_R

OW

CA

L_R

EPEAT_PA

TTER

NY

Varc

har

500

S_SD

_U

SER

_M

AP

SEB

L_U

SER

_G

RP_C

DY

Varc

har

30

S_SD

_U

SER

_M

AP

SEB

L_U

SR

EX

TR

AC

T_D

TY

UTC

D

ate

Tim

e7

S_SIG

N_D

ISC

_LS

DIS

C_SU

B_TYPE_C

DY

Varc

har

30

S_SIG

N_D

ISC

_LS

DIS

C_TYPE_C

DY

Varc

har

30

S_SM

PL_

TXN

_IT

EM

MA

X_O

RD

ER

_Q

TY

YN

um

ber

22

22

7

S_SM

PL_

TXN

_IT

EM

MIN

_O

RD

ER

_Q

TY

YN

um

ber

22

22

7

S_SM

PL_

TXN

_IT

EM

PR

OD

_ALL

OC

_ID

YVarc

har

15

S_SM

PL_

TXN

_IT

EM

REC

EIV

ED

_D

TY

UTC

D

ate

Tim

e7

S_SM

PL_

TXN

_IT

EM

STK

_PER

D_EM

P_ID

YVarc

har

15

S_SR

CFU

NN

EL_

STA

GE_ID

YVarc

har

15

S_SR

CM

UTL_

EXC

LUSIV

E_FL

GN

Char

1Y

S_SR

CPC

T_A

LLO

C_FL

GN

Char

1Y

S_SR

CPR

E_LO

AD

_TSK

_W

F_ID

YVarc

har

15

S_SR

CPS

T_LN

CH

_TS

K_W

F_ID

YVarc

har

15

Table

131.

New

Table

Colu

mns

in T

his

Vers

ion

Ta

ble

C

olu

mn

O

pt

Da

ta

Typ

eLen

Pre

cS

ca

leD

ef

LO

V T

yp

eLO

V

Bn

d



S_SR

CPS

T_LO

AD

_TSK

_W

F_ID

YVarc

har

15

S_SR

CR

EC

UR

RIN

G_FL

GN

Char

1Y

S_SR

C_PA

YM

EN

TAPPR

V_PO

STN

_ID

YVarc

har

15

S_STA

TE_LI

C_LS

ON

E_SAM

PLE

_FL

GN

Char

1N

S_STK

_PER

D_EM

PAPPR

OV

ER

_ID

YVarc

har

15

S_STK

_PER

D_EM

PAU

DIT

_EM

P_ID

YVarc

har

15

S_STO

CK

_EM

PIN

V_AU

DIT

_R

PT_ID

YVarc

har

15

S_STO

CK

_EM

PIN

VEN

TO

RY_C

OU

NT

YN

um

ber

22

22

7

S_TM

PL_

PLA

NIT

EM

CAS

E_TYPE_C

DY

Varc

har

30

S_U

SER

DAY_O

VER

DU

E_IN

VC

HK

YN

um

ber

22

10

0

S_U

SER

DAYS

_C

OM

P_TR

NG

YN

um

ber

22

10

0

S_U

SER

DAYS

_IN

V_AU

DIT

YN

um

ber

22

10

0

S_U

SER

DAYS

_O

VER

DU

E_A

CK

YN

um

ber

22

10

0

S_U

SER

DAYS

_R

EPO

RT_LO

SS

YN

um

ber

22

10

0

S_U

SER

DAYS

_SM

PL_

WA

RN

ING

YN

um

ber

22

10

0

S_U

SER

DAYS_TR

AN

SFE

R_IN

YN

um

ber

22

10

0

S_U

SER

DAYS

_TR

SFR

_D

ISC

RY

Num

ber

22

10

0

S_U

SER

INTEG

_U

SER

_FL

GN

Char

1N

S_U

SER

LAS

T_U

NC

OM

PR

ESS

_D

TY

UTC

D

ate

Tim

e7

S_U

SER

MA

X_SAM

PLE

_C

ALL

YN

um

ber

22

10

0

S_U

SER

MIN

_IN

VEN

TO

RY

YN

um

ber

22

10

0

S_U

SER

STA

TU

S_C

DY

Varc

har

30

US

ER

_S

TATU

SY

Table

131.

New

Table

Colu

mns

in T

his

Vers

ion

Ta

ble

C

olu

mn

O

pt

Da

ta

Typ

eLen

Pre

cS

ca

leD

ef

LO

V T

yp

eLO

V

Bn

d



S_W

FA_IN

ST_LO

GW

OR

KIT

EM

_ID

_VA

LY

Varc

har

15

S_XM

LP_R

EP_TM

PL

RPT_H

AS

_PA

RA

M_FL

GN

Char

1N

S_XM

LP_R

EP_TM

PL

RPT_U

PLO

AD

_STA

T_C

DY

Varc

har

30

S_XM

LP_R

EP_TM

PL

XM

LP_R

EP_IN

TO

BJ_

IDY

Varc

har

15

Table

131.

New

Table

Colu

mns

in T

his

Vers

ion

Ta

ble

C

olu

mn

O

pt

Da

ta

Typ

eLen

Pre

cS

ca

leD

ef

LO

V T

yp

eLO

V

Bn

d

Schema Changes ■ Table Index Changes in This Version


Changed Table Columns in This VersionTable 132 lists table columns that have changed 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 312

■ “Changed Table Index in This Version” on page 317

Table 132. Table Columns That Have Changed in This Version

Table Name Column Type of Change

Previous Value New Value

S_ASSET RATE_STATE Length 10 30

S_AUDIT_ITEM ITEM_IDEN_NUM Default 0

S_INST_UPG_HIST ADDL_LANG_INSTALED Length 50 100

S_INVC_ADJ_ITEM INTEGRATION_ID Varchar 30 450

S_INVC_ITM_DTL INTEGRATION_ID Varchar 30 450

S_INVOICE INTEGRATION_ID Varchar 30 450

S_INVOICE_ADJ INTEGRATION_ID Varchar 30 450

S_INVOICE_DTL INTEGRATION_ID Varchar 30 450

S_LOY_MEMBER VAL_SCORE Length 50 30

S_LOY_PROD_PT PARTNER_ID Opt N Y

S_LOY_STMT_CRTN TIER_ID Opt N Y

S_LOY_STMT_LOG MEMBER_ID Opt N Y

S_LOY_TIER_CLS START_QUAL_PD_CD Active Enrollment/Anniversary Date

LOV Type LOY_START_ QUAL_PER_CD

LOY_START_QUAL_PER_CD

S_RT_SVC NAME Length 30 75

S_RT_SVC_METH NAME Length 30 75

S_RT_SVC_M_ARG NAME Length 30 75

S_SRV_REQ2_FNX WTR_COUNTRY Length 25 30

S_TIMEZONE UTC_OFFSET Opt N Y

S_XMLP_REP_TMPL INT_OBJ_NAME Opt N Y



312

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

New Table Indexes in This VersionTable 133 lists table indexes that are new in this version. Some column headings are abbreviated as follows:

■ A indicates active.

■ U indicates unique.

Table 133. Table Indexes That Are New in This Version

Table Index A U Columns

S_ACT_PRDINT S_ACT_PRDINT_F52 Y N (PROD_ALLOC_ID)

S_ACT_PROD_APPL S_ACT_PROD_APPL_F3 Y N (PROD_ALLOC_ID)

S_ACT_SIGN S_ACT_SIGN_F4 Y N (INV_AUDIT_RPT_ID)

S_ACT_SIGN S_ACT_SIGN_F5 Y N (SAMPLE_TXN_ID)

S_ACT_SIGN S_ACT_SIGN_U1 Y Y (ACTIVITY_ID,SIGN_NUM, INV_AUDIT_RPT_ID,SAMPLE_TXN_ID,CONFLICT_ID)

S_ASSESS S_ASSESS_F55 Y N (INV_AUDIT_RPT_ID)

S_ASSESS S_ASSESS_F56 Y N (LIT_ID)

S_ASSET S_ASSET_M7 Y N (STATUS_CD,REGISTERED_DT)

S_ASSET S_ASSET_F74 Y N (BILL_PROFILE_ID)

S_CAMP_CON S_CAMP_CON_M3 Y N (CAMP_LD_WAVE_ID,BATCH_NUM, MARK_FOR_DEL_FLG,STAT_CD)

S_CASE S_CASE_F4 Y N (AUDIT_EMP_ID)

S_CASE S_CASE_F5 Y N (MSTR_CASE_ID)

S_CASE S_CASE_F6 Y N (APPLICANT_ID)

S_CASE S_CASE_F7 Y N (PS_APPL_ID)

S_COMMUNICATION S_COMMUNICATN_F19 Y N (MKT_SRVY_ID)

S_COMMUNICATION S_COMMUNICATN_F20 Y N (LEAD_ID)

S_COMMUNICATION S_COMUNICATION_M51 Y N (PGROUP_PUBLIC_FLG)

S_CONTACT S_CONTACT_M24 Y N (PRIV_FLG,LAST_NAME,FST_NAME)

S_CONTACT S_CONTACT_F65 Y N (MSTR_CASE_ID)

S_CONTACT_LSX S_CONTACT_LSX_F2 Y N (MASTER_SIGN_ID)

S_DCP_URL S_DCP_URL_F1 Y N (LAND_SITE_ID)



S_DMND_CRTN_PRG S_DMND_CRTNPRG_F22 Y N (ACT_OWNER_PER_ID)

S_DMND_CRTN_PRG S_DMND_CRTNPRG_F18 Y N (MKT_SRVY_ID)

S_DMND_CRTN_PRG S_DMND_CRTNPRG_F19 Y N (BU_ID)

S_DMND_CRTN_PRG S_DMND_CRTNPRG_F20 Y N (OWNER_POSTN_ID)

S_DMND_CRTN_PRG S_DMND_CRTNPRG_F21 Y N (ORIG_CREATOR_ID)

S_DOC_QUOTE S_DOC_QUOTE_F65 Y N (ATTR_ID)

S_DOC_QUOTE S_DOC_QUOTE_F40 Y N (BILL_PROFILE_ID)

S_EMP_PER S_EMP_PER_F50 Y N (LS_APPROVER_ID)

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

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

S_EVT_ACT S_EVT_ACT_F82 Y N (BNFT_PLAN_ITM_ID)

S_EVT_ACT S_EVT_ACT_F42 Y N (LEAD_ID)

S_EVT_ACT S_EVT_ACT_F43 Y N (SRC_EVT_REG_ID)

S_EVT_ACT_FNX S_EVT_ACT_FNX_M1 Y N (PGROUP_PUBLIC_FLG)

S_EVT_ACT_LSX S_EVT_ACT_LSX_F5 Y N (SUPERVISOR_ID)

S_EVT_FUL_REQ S_EVT_FUL_REQ_F16 Y N (EVTLOC_ID)

S_FCSTSER_POSTN S_FCSTSER_POSTN_F3 Y N (SUBMIT_TO_PSTN_ID)

S_INCIDENT S_INCIDENT_F5 Y N (SIGN_EVT_ID)

S_INVC_ADJ_ITEM S_INVC_ADJ_ITEM_II Y N (INTEGRATION_ID)

S_INVC_ADJ_ITEM S_INVC_ADJ_ITEM_U1 Y Y (INVOICE_ADJ_ID,INVOICE_ITEM_ID,INV_ITEM_DETAIL_ID,CONFLICT_ID)

S_INVOICE S_INVOICE_M51 Y N (INVC_DT,SRC_ID)

S_INVOICE S_INVOICE_M1 Y N (INVC_DT)

S_INVOICE_ADJ S_INVOICE_ADJ_II Y N (INTEGRATION_ID)

S_LOY_ACRL_ITM S_LOY_ACRL_ITM_F8 Y N (PT_SUB_TYPE_ID)

S_LOY_ACTCRTR S_LOY_ACTCRTR_F6 Y N (PT_SUB_TYPE_ID)

S_LOY_ACTCRTR S_LOY_ACTCRTR_F4 Y N (PROD_ID)

S_LOY_ACTCRTR S_LOY_ACTCRTR_F5 Y N (PROMO_RULE_ID)





314

S_LOY_ADN_LANG S_LOY_ADN_LANG_F1 Y N (LANG_ID)

S_LOY_ATTRDEFN S_LOY_ATTRDEFN_F4 Y N (CURCY_CD)

S_LOY_ATTRDEFN S_LOY_ATTRDEFN_F5 Y N (PROGRAM_ID)

S_LOY_ATTRIB S_LOY_ATTRIB_F2 Y N (MEMBER_ID)

S_LOY_BCKT_TXN S_LOY_BCKT_TXN_F2 Y N (PROMO_BUCKET_ID)

S_LOY_CRTR_VAL S_LOY_CRTR_VAL_F1 Y N (CRITERIA_ID)

S_LOY_MEM_BU S_LOY_MEM_BU_F1 Y N (BU_ID)

S_LOY_MEM_BU S_LOY_MEM_BU_F2 Y N (MEMBER_ID)

S_LOY_MEM_CON S_LOY_MEM_CON_F2 Y N (MEMBER_ID)

S_LOY_MEM_PSTN S_LOY_MEM_PSTN_F1 Y N (MEMBER_ID)

S_LOY_MEM_PSTN S_LOY_MEM_PSTN_F2 Y N (POSTN_ID)

S_LOY_MEM_TIER S_LOY_MEM_TIER_F10 Y N (MEMBER_ID)

S_LOY_MEM_TIER S_LOY_MEM_TIER_F6 Y N (FUTR_TIER_ID)

S_LOY_MEM_TIER S_LOY_MEM_TIER_F7 Y N (APPLIED_PROMO_ID)

S_LOY_MEM_TIER S_LOY_MEM_TIER_F8 Y N (APPLD_PROMO_RL_ID)

S_LOY_MEM_TIER S_LOY_MEM_TIER_F9 Y N (BULK_REF_ID)

S_LOY_MEM_TIER S_LOY_MEM_TIER_M2 Y N (MEM_TIER_NUM)

S_LOY_MEM_VCHR S_LOY_MEM_VCHR_F4 Y N (ORIG_VCHR_ID)

S_LOY_MEM_VCHR S_LOY_MEM_VCHR_F5 Y N (TXN_ITEM_ID)

S_LOY_MEM_VCHR S_LOY_MEM_VCHR_F6 Y N (MERGE_MEM_ID)

S_LOY_MEM_VCHR S_LOY_MEM_VCHR_F7 Y N (CONSUMED_TXN_ID)

S_LOY_MEMBER S_LOY_MEMBER_F15 Y N (MEMSHIP_SCHEME_ID)

S_LOY_MEMBER S_LOY_MEMBER_F16 Y N (BU_ID)

S_LOY_MEMBER S_LOY_MEMBER_F17 Y N (CURCY_CD)

S_LOY_MEMBER S_LOY_MEMBER_F18 Y N (LANG_ID)

S_LOY_MEMBER S_LOY_MEMBER_F19 Y N (SURV_MEM_ID)

S_LOY_MEMPTRPG S_LOY_MEMPTRPG_F3 Y N (MEMBER_ID)

S_LOY_PROD_PT S_LOY_PROD_PT_F4 Y N (CURCY_CD)

S_LOY_PROD_PT S_LOY_PROD_PT_F5 Y N (PRICE_AMT_CURCY_CD)

S_LOY_PROD_PT S_LOY_PROD_PT_F6 Y N (PROGRAM_ID)

S_LOY_PROD_PT S_LOY_PROD_PT_U1 Y Y (PROD_PT_UID,CONFLICT_ID)





S_LOY_PROG_BU S_LOY_PROG_BU_F1 Y N (BU_ID)

S_LOY_PROG_BU S_LOY_PROG_BU_F2 Y N (PROG_ID)

S_LOY_PROG_ORG S_LOY_PROG_ORG_F2 Y N (PROG_ID)

S_LOY_PROG_ORG S_LOY_PROG_ORG_F3 Y N (PRICING_RULE_ID)

S_LOY_PROGRAM S_LOY_PROGRAM_F2 Y N (BU_ID)

S_LOY_PROMO S_LOY_PROMO_F8 Y N (BU_ID)

S_LOY_PROMO_ATR S_LOY_PROMO_ATR_F2 Y N (LOY_PROMO_ID)

S_LOY_PROMO_BU S_LOY_PROMO_BU_F1 Y N (BU_ID)

S_LOY_PROMO_BU S_LOY_PROMO_BU_F2 Y N (PROMO_ID)

S_LOY_PROMO_CST S_LOY_PROMO_CST_F2 Y N (COST_CURCY_CD)

S_LOY_PROMO_CST S_LOY_PROMO_CST_F3 Y N (PROMO_ID)

S_LOY_PROMO_RL S_LOY_PROMO_RL_F1 Y N (PROMO_ID)

S_LOY_PROMO_TR S_LOY_PROMO_TR_F2 Y N (PROMOTION_ID)

S_LOY_PROMOMEM S_LOY_PROMOMEM_F2 Y N (PROMO_ID)

S_LOY_PROMOPRD S_LOY_PROMOPRD_F4 Y N (PROMO_ID)

S_LOY_PT_BLCK S_LOY_PT_BLCK_F8 Y N (CURCY_CD)

S_LOY_PT_BLCK S_LOY_PT_BLCK_F9 Y N (SALE_CURCY_CD)

S_LOY_PTR_ATMP S_LOY_PTR_ATMP_F2 Y N (PARTNER_ID)

S_LOY_PTR_ZONE S_LOY_PTR_ZONE_F1 Y N (PARTNER_ID)

S_LOY_SR_TXN S_LOY_SR_TXN_F2 Y N (SRV_REQ_ID)

S_LOY_STMT S_LOY_STMT_F6 Y N (MEM_TIER_ID)

S_LOY_STMT S_LOY_STMT_F7 Y N (PARTNER_ID)

S_LOY_STMT S_LOY_STMT_F8 Y N (TRX_ID)

S_LOY_STMT S_LOY_STMT_F9 Y N (VOUCHER_ID)

S_LOY_STMT_ATTR S_LOY_STMT_ATTR_F2 Y N (STMT_ID)

S_LOY_STMT_CRTN S_LOY_STMT_CRTN_F1 Y N (PROG_ID)

S_LOY_STMT_CRTN S_LOY_STMT_CRTN_F2 Y N (TIER_ID)

S_LOY_STMT_ITM S_LOY_STMT_ITM_F4 Y N (STMT_ID)

S_LOY_STMT_ITM S_LOY_STMT_ITM_F5 Y N (PT_SUB_TYPE_ID)

S_LOY_STMT_LOG S_LOY_STMT_LOG_F3 Y N (PARTNER_ID)

S_LOY_STMT_TXN S_LOY_STMT_TXN_F7 Y N (CURCY_CD)





316

S_LOY_STMT_TXN S_LOY_STMT_TXN_F8 Y N (STMT_ID)

S_LOY_STMT_VCHR S_LOY_STMT_VCHR_F2 Y N (STMT_ID)

S_LOY_TIER S_LOY_TIER_F3 Y N (TIER_CLASS_ID)

S_LOY_TIER_CLS S_LOY_TIER_CLS_F1 Y N (APPROVER_ID)

S_LOY_TIER_CLS S_LOY_TIER_CLS_F2 Y N (PROGRAM_ID)

S_LOY_TIER_MAP S_LOY_TIER_MAP_F3 Y N (PROG_TIER_ID)

S_LOY_TXN S_LOY_TXN_F19 Y N (ACCR_RULE_ID)

S_LOY_TXN S_LOY_TXN_F20 Y N (BULK_REF_ID)

S_LOY_TXN S_LOY_TXN_F21 Y N (BU_ID)

S_LOY_TXN S_LOY_TXN_F22 Y N (CURCY_CD)

S_LOY_TXN S_LOY_TXN_F23 Y N (ORIG_ACRL_REF_ID)

S_LOY_TXN S_LOY_TXN_F24 Y N (CHILD_TXN_ID)

S_LOY_TXN S_LOY_TXN_F25 Y N (ORIG_ORD_ITM_ID)

S_LOY_TXN S_LOY_TXN_F26 Y N (RDM_ITM_ID)

S_LOY_TXN S_LOY_TXN_F27 Y N (ENROL_PROMO_ID)

S_LOY_TXN S_LOY_TXN_F28 Y N (OPER_CARRIER_ID)

S_LOY_TXN_BU S_LOY_TXN_BU_F1 Y N (BU_ID)

S_LOY_TXN_BU S_LOY_TXN_BU_F2 Y N (TXN_ID)

S_LOYAL_PROF S_LOYAL_PROF_F1 Y N (ACCNT_ID)

S_MDF S_MDF_F9 Y N (OWNER_ID)

S_MDF S_MDF_F10 Y N (REGION_ID)

S_MKTG_SRVR_TSK S_MKTG_SRVR_TSK_F8 Y N (IMPRT_TSK_ID)

S_OPTY S_OPTY_M60 Y N (PGROUP_PUBLIC_FLG)

S_OPTY_DSGN_REG S_OPTY_DSGN_REG_F8 Y N (CUST_ACCNT_ID)

S_ORD_ITM_LOYX S_ORD_ITM_LOYX_F2 Y N (VOUCHER_ID)

S_ORDER S_ORDER_F44 Y N (BILL_PROFILE_ID)

S_ORDER_ITEM S_ORDER_ITEM_F47 Y N (BILL_PROFILE_ID)

S_ORG_EXT S_ORG_EXT_F22 Y N (PR_BILL_PRFL_ID)

S_POSTN S_POSTN_F5 Y N (PGROUP_ID)

S_QUO_ITM_LOYX S_QUO_ITM_LOYX_F2 Y N (VOUCHER_ID)

S_QUOTE_ITEM S_QUOTE_ITEM_F41 Y N (BILL_PROFILE_ID)





Changed Table Index in This VersionTable 134 lists a table index that was changed in this version.

S_SAMPLE_TXN S_SAMPLE_TXN_F7 Y N (OLD_TXN_ID)

S_SAMPLE_TXN S_SAMPLE_TXN_F8 Y N (SRC_TXN_ID)

S_SAMPLE_TXN S_SAMPLE_TXN_F9 Y N (APPROVER_ID)

S_SAMPLE_TXN S_SAMPLE_TXN_F10 Y N (ROOT_TXN_ID)

S_SMPL_TXN_ITEM S_SMPL_TXN_ITEM_F6 Y N (PROD_ALLOC_ID)

S_SMPL_TXN_ITEM S_SMPL_TXN_ITEM_F7 Y N (STK_PERD_EMP_ID)

S_SRC S_SRC_F40 Y N (PST_LNCH_TSK_WF_ID)

S_SRC S_SRC_F41 Y N (PRE_LOAD_TSK_WF_ID)

S_SRC S_SRC_F42 Y N (FUNNEL_STAGE_ID)

S_SRC S_SRC_F43 Y N (PST_LOAD_TSK_WF_ID)

S_SRC_PAYMENT S_SRC_PAYMENT_F66 Y N (APPRV_POSTN_ID)

S_STK_PERD_EMP S_STK_PERD_EMP_F1 Y N (APPROVER_ID)

S_STK_PERD_EMP S_STK_PERD_EMP_F2 Y N (AUDIT_EMP_ID)

S_STOCK_EMP S_STOCK_EMP_F4 Y N (INV_AUDIT_RPT_ID)

S_STOCK_EMP S_STOCK_EMP_U1 Y Y (EMP_ID,PRDINT_ID, STK_PERD_EMP_ID,LOT_ID, INV_AUDIT_RPT_ID,CONFLICT_ID)

S_XMLP_REP_TMPL S_XMLP_REP_TMPL_F1 Y N (XMLP_REP_INTOBJ_ID)

Table 134. Table Index That Changed Definition in This Version

Table Name Index Previous Columns New Columns

S_LOY_PROD_PT S_LOY_PROD_PT_U1 (PROGRAM_ID,TXN_TYPE_CD, PROD_ID,ATTRIB_1,ATTRIB_2, ATTRIB_3,ATTRIB_4,ATTRIB_5, ATTRIB_6,CONFLICT_ID)

(PROD_PT_UID, CONFLICT_ID)





318

Table Index That Was Deleted from This VersionTable 135 lists a table index that was deleted from this version.

Table 135. Table Index

Table Name Index A U Column

S_SD_SYNC_INFO S_SD_SYNC_INFO_M4 Y N (SEQ_ID)


Index

Aaccount ERD

about 23diagram 25support for Dynamic Hierarchy 23support for Global Account Views 23tables 23

account targeting ERDabout 26diagram 27tables 26

activity ERDabout 28diagram 29tables 28

adjustment group ERDabout 30diagram 31tables 30

affiliations and best times ERDabout 32diagram 33tables 32

agencies/agent ERDabout 34diagram 35tables 34

agreementSee CME agreement ERD

alertsSee CME alert ERD

apparelSee textile, apparel, and footwear ERD

asset management ERDabout 36diagram 37tables 36tracking asset instances 36

assetsSee CME energy products, service, and usage

ERDauction ERD

about 38diagram 39tables 38

auto email response generator ERDabout 40

diagram 41tables 40

Automotiveautomotive retail ERD 42dealer sales and service promotion 87vehicle collection ERD 254vehicle ERD 252vehicle financing ERD 256vehicle sales ERD 258

automotive retail ERDabout 42diagram 43tables 42

Bbanking

See commercial banking ERDbenefit case management ERD


best call hoursSee routes and best call hours ERD

brick ERDabout 47diagram 48tables 47

Ccampaign management

See marketing campaign ERDCG promotion planning ERD


chatSee community/chat discussion ERD

clinical study management ERDabout 52diagram 54tables 52

CME account ERDabout 55diagram 56tables 55

CME agreement ERD


Index ■ D

320


CME alert ERDabout 59diagram 60tables 59

CME energy products, service, and usage ERD


CME order management ERDabout 63diagram 64tables 63

columnsdomain type definitions 271INTEGRATION_ID columns, about 273naming conventions 267numeric physical type 272type definitions 271

commercial banking ERDabout 65diagram 67tables 65

commercial insurance ERDabout 68diagram 69tables 68

Communications, Media, EnergyCME account ERD 55CME agreement ERDCME alert ERD 59CME energy products, service, and usage

ERD 61CME order management ERD 63pricing comparison ERD 185

community/chat discussion ERDabout 70diagram 71tables 70

compensation planning administration ERDabout 72diagram 73tables 72

compensation planning execution ERDabout 74diagram 75tables 74

competency management system ERDabout 76diagram 77tables 76

Consumer Sectoraccount targeting ERD 26best hours entity 210CG promotion planning ERD 49objectives ERD 160sales volume planning ERD 214territory management - CS ERD 236

content management ERDabout 78diagram 79tables 78

content objectSee content management ERD

content processSee content management ERD

contract conditions ERDabout 80diagram 81tables 80

contracts ERDabout 82diagram 83tables 82

credit alertsSee CME alert ERD

Customer Data Item, about 84

Ddata (intersection) table type

about 269obsolete, table marked as 269

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

about 269obsolete, table marked as 269

data typeslimit checking 274

data visibility ERDabout 84diagram 86tables 84

database schema version number, finding and format 274

dealer sales and service promotion ERDabout 87diagram 88tables 87

defect trackingSee product quality tracking ERD

designSee schema

discussionSee community/chat discussion ERD

Index ■ E


document ID and tax ID ERDabout 89diagram 90tables 89

domain type definitions 271Dun & Bradstreet integration ERD


Dynamic Hierarchy, support by account entity 23

Eemployee KPI ERD


Employee Relationship Managementcompensation planning administration

ERD 72compensation planning execution ERD 74competency management system ERD 76employee KPI ERD 93performance review ERD 176

employeesfield service scheduler ERD 101time sheet ERD 242

entitlement items, service agreement ERD 218

ERDsaccount targeting, diagram 27account targeting, tables 26account, diagram 25account, tables 23activity, diagram 29activity, tables 28adjustment group, diagram 31adjustment group, tables 30affiliations and best times, diagram 33affiliations and best times, tables 32agencies/agent, diagram 35agencies/agent, tables 34asset management, diagram 37asset management, tables 36auction, diagram 39auction, tables 38auto email response generator,

diagram 41auto email response generator, tables 40automotive retail, diagram 43automotive retail, tables 42benefit case management, diagram 46benefit case management, tables 44

brick, diagram 48brick, tables 47CG promotion planning, diagram 51CG promotion planning, tables 49clinical study management, diagram 54clinical study management, tables 52CME account, diagram 56CME account, tables 55CME agreement, diagram 58CME agreement, tables 57CME alert, diagram 60CME alert, tables 59CME energy products, service, and usage,

diagram 62CME energy products, service, and usage,

tables 61CME order management ERD, diagram 64CME order management ERD, tables 63commercial banking, diagram 67commercial banking, tables 65commercial insurance, diagram 69commercial insurance, tables 68community/chat discussion, diagram 71community/chat discussion, tables 70compensation planning administration,

diagram 73compensation planning administration,

tables 72compensation planning execution,

diagram 75compensation planning execution,

tables 74competency management system,

diagram 77competency management system,

tables 76content management, diagram 79content management, tables 78contract conditions, diagram 81contract conditions, tables 80contracts, diagram 83contracts, tables 82conventions, description of 13data visibility, diagram 86data visibility, tables 84dealer sales and service promotion,

diagram 88dealer sales and service promotion,

tables 87document ID and tax ID, diagram 90document ID and tax ID, tables 89Dun & Bradstreet integration, diagram 92Dun & Bradstreet integration, tables 91employee KPI, diagram 94


Index ■ E

322

employee KPI, tables 93event tax administration, diagram 96event tax administration, tables 95exclusive arc relationship, diagram

conventions 14expense reports, diagram 98expense reports, tables 97field service inventory, diagram 100,

102field service inventory, tables 99field service scheduler, tables 101financial account application, diagram 106financial account application, tables 105financial account, diagram 104financial account, tables 103financial investments, diagram 108financial investments, tables 107financial products, diagram 110financial products, tables 109financial services events, diagram 113financial services events, tables 111forecasts, diagram 115forecasts, tables 114general diagram conventions 14group insurance policies, diagram 117group insurance policies, tables 116group pensions, diagram 119group pensions, tables 118health provider/provider group,

diagram 121health provider/provider group, tables 120high tech marketing development fund,

diagram 123high tech marketing development fund,

tables 122high tech special pricing authorization,

diagram 125high tech special pricing authorization,

tables 124hospitality category, diagram 127hospitality category, tables 126institutional sales, diagram 129institutional sales, tables 128insurance claims, diagram 132insurance claims, tables 130insurance policies, diagram 134insurance policies, tables 133invoicable charges, diagram 136invoicable charges, tables 135invoices, diagram 138invoices, tables 137life insurance policy, diagram 140life insurance policy, tables 139loyalty, diagram 144

loyalty, tables 142managed care, diagram 146managed care, tables 145marketing campaign, diagram 148marketing campaign, tables 147marketing collaboration, diagram 150marketing collaboration, tables 149marketing encyclopedia, diagram 152marketing encyclopedia, tables 151marketing events, diagram 155marketing events, tables 153marketing plans, diagram 157marketing plans, tables 156medical education event management,

diagram 159medical education event management,

tables 158objectives, diagram 161objectives, tables 160opportunity management, diagram 163opportunity management, tables 162order life cycle, diagram 165order life cycle, tables 164orders, diagram 167orders, tables 166partner collaboration, diagram 169partner collaboration, tables 168partner program registration, diagram 171partner program registration, tables 170party model, diagram 173party model, tables 172payments, diagram 175payments, tables 174performance review, diagram 178performance review, tables 176personal account, diagram 180personal account, tables 179personal financial review, diagram 182personal financial review, tables 181personalized content delivery, tables 183pricing comparison, diagram 184, 186pricing comparison, tables 185pricing, diagram 188pricing, tables 187product promotion, diagram 190product promotion, tables 189product quality tracking, diagram 192product quality tracking, tables 191product recommendation, diagram 194product recommendation, tables 193products or services, diagram 196products or services, tables 195professional services, diagram 198professional services, tables 197

Index ■ F


public sector case lead management, diagram 201

public sector case lead management, tables 199

public sector contact identity, diagram 203public sector contact identity, tables 202public sector evidence management,

diagram 205public sector evidence management,

tables 204public sector incident management,

diagram 207public sector incident management,

tables 206recursive relationship, diagram

conventions 15revenue, diagram 209revenue, tables 208revision table 16routes and best call hours, diagram 211routes and best call hours, tables 210sales hierarchy and credit assignment,

diagram 213sales hierarchy and credit assignment,

tables 212sales volume planning, diagram 215sales volume planning, tables 214sample management, diagram 217sample management, tables 216service agreement, diagram 219service agreement, tables 218service calendars and work shifts,

diagram 221service calendars and work shifts,

tables 220service request, diagram 223service request, tables 222shipment, diagram 225shipment, tables 224Siebel Assistant, diagram 227Siebel Assistant, tables 226syndicated data, diagram 229syndicated data, tables 228teller administration, diagram 231teller administration, tables 230territory alignment - quota assignment

diagram 233territory alignment - quota assignment,

tables 232territory management - CS, diagram 237territory management - CS, tables 236territory management - LS, diagram 239territory management - LS, tables 238territory management, diagram 235

territory management, tables 234textile, apparel, and footwear,

diagram 241textile, apparel, and footwear, tables 240time sheet, diagram 243time sheet, tables 242trade promotions, diagram 245trade promotions, tables 244training curriculum course, diagram 247training curriculum course, tables 246training test engine, diagram 249training test engine, tables 248universal customer master, diagram 251universal customer master, tables 250vehicle collection, diagram 255vehicle collection, tables 254vehicle financing, diagram 257vehicle financing, tables 256vehicle sales, diagram 259vehicle sales, tables 258vehicle, diagram 253vehicle, tables 252versioned object definition, diagram 261versioned object definition, tables 260warranty, diagram 263warranty, tables 262

event tax administration ERDabout 95diagram 96tables 95

exclusive arc relationshipabout 14diagram conventions 14

expense reports ERDabout 97diagram 98tables 97

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

extension table type, about 269

Ffield service inventory ERD

about 99diagram 100, 102tables 99

field service scheduler ERDabout 101tables 101

financial account application ERDabout 105diagram 106


Index ■ G

324

tables 105financial account ERD


financial accountsfinancial account application ERD 105financial account ERD 102personal account ERD 179

financial investments ERDabout 107diagram 108tables 107

financial products ERDabout 109diagram 110tables 109

financial review, personal financial review ERD 181

Financial Servicesagencies/agent ERD 34commercial banking ERD 65commercial insurance ERD 68financial account application ERD 105financial account ERD 102financial investments ERD 107financial products ERD 109financial services events ERD 111group insurance policies ERD 116group pensions ERD 118health provider/provider group ERD 120institutional sales ERD 128insurance claims ERD 130insurance policies ERD 133life insurance policy ERD 139teller administration ERD 230

financial services events ERDabout 111diagram 113tables 111

footwearSee textile, apparel, and footwear ERD

forecasts ERDabout 114diagram 115tables 114

fraud alertsSee CME alert ERD

Ggenerating table report 275Global Account Views, support by account

entity 23

group insurance policies ERDabout 116diagram 117tables 116

group pensions ERDabout 118diagram 119tables 118

Hhealth provider/provider group ERD


high tech marketing development fund ERDabout 122diagram 123tables 122

high tech special pricing authorization ERDabout 124diagram 125tables 124

Hospitalityevent tax administration ERD 95

hospitality category ERDabout 126diagram 127tables 126

IInclude Only field 273index column fields 273index naming conventions 267institutional sales ERD


insurancecommercial insurance ERD 68group insurance policies ERD 116insurance claims ERD 130insurance policies ERD 133life insurance policy ERD 139personal account ERD 179

insurance claims ERDabout 130diagram 132tables 130

insurance policies ERDabout 133diagram 134tables 133

INTEGRATION_ID columns, about 273

Index ■ L


invoicable charges ERDabout 135diagram 136tables 135

invoices ERDabout 137diagram 138tables 137

Llife insurance policy ERD


Life Sciencesactivity ERD 28affiliations and best times ERD 32brick ERD 47clinical study management ERD 52community/chat discussion ERD 70managed care ERD 145medical education event management

ERD 158personalized content delivery ERD 183sample management ERD 216syndicated data ERD 228territory management - LS ERD 238

limit checking for data types 274loans, commercial banking entity 65logical model

ERD conventions 13ERD descriptions 16

loyalty ERDabout 141diagram 144tables 142

Mmanaged care ERD


MarketingCG promotion planning ERD 49Dun & Bradstreet integration ERD 91forecasts ERD 114high tech marketing development fund

ERD 122marketing campaign ERD 147marketing collaboration ERD 149marketing encyclopedia ERD 151marketing events ERD 153marketing plans ERD 156

marketing campaign ERDabout 147diagram 148tables 147

marketing collaboration ERDabout 149diagram 150tables 149

marketing development fundsSee CG promotion planning ERD

marketing encyclopedia ERDabout 151diagram 152tables 151

marketing events ERDabout 153diagram 155tables 153

marketing plans ERDabout 156diagram 157tables 156

Master Data Item, about 84MDFs

See CG promotion planning ERDMedEd event management

See medical education event management ERD

medical education event management ERDabout 158diagram 159tables 158

mini brickSee brick ERD

Nnaming conventions

columns 267indexes 267physical model listings, abbreviations

used 268table names 265table prefixes 266table suffixes 266

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

normalized, defined 11

Oobjectives ERD

about 160diagram 161


Index ■ P

326

tables 160opportunity management ERD


Oracle Applications, about use of INTEGRATION_ID columns 273

order life cycle ERDabout 164diagram 165tables 164

orders ERDabout 166diagram 167tables 166

Ppartner collaboration ERD


partner program registration ERDabout 170diagram 171tables 170

party model ERDabout 172diagram 173tables 172

party model, about 275party, defined 172payments ERD


performance review ERDabout 176diagram 178tables 176

personal account ERDabout 179diagram 180tables 179

personal financial review ERDabout 181diagram 182tables 181

personalized content delivery ERDabout 183tables 183

physical modelcolumn naming conventions 267column type definitions 271

columns of numeric physical type 272database schema version number, finding and

format 274domain type definitions 271Include Only field 273index naming conventions 267INTEGRATION_ID columns, about 273limit checking for data types 274party model, about 275physical model listings, abbreviations

used 268Siebel repository tables, about 273Siebel system fields 272table naming conventions 265table report, about 275table status definitions 270table type definitions 269validating Siebel Schema 274

physicians, health provider/provider group ERD 120

prescription information, syndicated data ERD 228

pricing comparison ERDabout 185diagram 184, 186tables 185

pricing ERDabout 187diagram 188tables 187

product promotion ERDabout 189diagram 190tables 189

product quality tracking ERDabout 191diagram 192tables 191

product recommendation ERDabout 193diagram 194tables 193

products or services ERDabout 195diagram 196tables 195

professional services ERDabout 197diagram 198tables 197

projects, professional services ERD 197protocols

See clinical study management ERDpublic sector benefit case management ERD

Index ■ R



public sector case lead management ERDabout 199diagram 201tables 199

public sector contact identity ERDabout 202diagram 203tables 202

public sector evidence management ERDabout 204diagram 205tables 204

public sector incident management ERDabout 206diagram 207tables 206

Rrecursive relationship

about 15diagram conventions 15

repository, about Siebel repository 273revenue ERD


routes and best call hours ERDabout 210diagram 211tables 210

SSales

Dun & Bradstreet integration ERD 91forecasts ERD 114high tech special pricing authorization

ERD 124marketing encyclopedia ERD 151opportunity management ERD 162routes and best call hours ERD 210sales hierarchy and credit assignment ERDterritory alignment - quota assignment

ERD 232territory management - LS ERD 238territory management ERD 234

sales hierarchy and credit assignment ERDabout 212diagram 213tables 212

Sales Hierarchy Module

See sales hierarchy and credit assignment ERD

sales volume planning ERDabout 214diagram 215tables 214

sample management ERDabout 216diagram 217tables 216

schemachanges to 277database schema version number, finding and

format 274defined 11validating Siebel Schema 274

Servicefield service inventory ERD 99field service scheduler ERD 101invoicable charges ERD 135invoices ERD 137products or services ERD 195service agreement ERD 218service calendars and work shifts ERD 220service request ERD 222territory management - CS ERD 236warranty ERD 262

service activities, field service scheduler ERD 101

service agreement ERDabout 218diagram 219tables 218

service calendars and work shifts ERDabout 220diagram 221tables 220

service region, field service scheduler ERD 101

service request ERDabout 222diagram 223tables 222

service requestsSee CME account ERD

servicesSee CME energy products, service, and usage

ERDshipment ERD


Siebel Assistant ERDabout 226


Index ■ T

328

diagram 227tables 226

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

INTEGRATION_ID columns 273Siebel system fields 272special ERD conventions

exclusive arc relationship 14recursive relationship 15

syndicated data ERDabout 228diagram 229tables 228

system fields 272

Ttable columns

changed 311new 282

table indexeschanged 317deleted 318new 312

tableschanged 281generating report 275naming conventions 265new 277prefix naming conventions 266suffix naming conventions 266table status definitions 270types of 269

tax IDSee document ID and tax ID ERD

teller administration ERDabout 230diagram 231tables 230

territory alignment - quota assignment ERDabout 232diagram 233tables 232

territory management - CS ERDabout 236diagram 237tables 236

territory management - LS ERDabout 238diagram 239tables 238

territory management ERDabout 234diagram 235

tables 234tests, training test engine ERD 248textile, apparel, and footwear ERD


time sheet ERDabout 242diagram 243tables 242

trade promotions ERDabout 244diagram 245tables 244

training curriculum course ERDabout 246diagram 247tables 246

training test engine ERDabout 248diagram 249tables 248

trouble ticketsSee CME account ERD

Uuniversal customer master ERD


Vvalidating Siebel Schema 274vehicle collection ERD


vehicle ERDabout 252diagram 253tables 252

vehicle financing ERDabout 256diagram 257tables 256

vehicle sales ERDabout 258diagram 259tables 258

versioned object definition ERDabout 260diagram 261tables 260

Index ■ W


Wwarranty ERD


work shiftsSee service calendars and work shifts ERD

workflow processSee content management ERD


Index ■ W

330

siebel data model reference for industry applications v8.1.1

Documents