DMR

Siebel Data M odel Reference Version 8.0, Rev. A May 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, 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 errorfree. Except as may be expressly permitted in your license agreement for t hese 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 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 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, 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 Corporation and/or its af filiates. 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, 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. 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 t he 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 f rom dealing with any third party.

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, 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 errorfree. Except as may be expressly permitted in your license agreement for t hese 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 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 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, 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 Corporation and/or its af filiates. 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, 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. 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 t he 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 f rom dealing with any third party.

Contents

Siebel Data Model Reference 1

Chapter Chapter 1: What’s New in This Release Chapter 2: Data Model Overview Chapter Chapter 3: 3: Logical Model Entity Relationship Diagram Conventions

11

General Entities 12 Exclusive Arc Relationship 12 Recursive Relationship 13

Entity Relationship Diagrams and Descriptions

14

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

S i e b e l D a t a M o d e l R e f e r e n c e Version 8.0, Rev. Rev. A

3

Contents

■

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

4

82

S i e b e l D a t a M o d e l R e f e r e n c e Version 8.0, Rev. A

Contents

■

Chapter 4: Physical Model Data Model Naming Conventions

153

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

Data Model Type Definitions

156

156

Table Type Definitions 157 Table Status Definitions 158 Column Type Definitions 159 Domain Type Definitions 159

Columns of Numeric Physical Type Siebel System Fields

160

INTEGRATION_ID Columns Include Only Field Siebel Repository

160

161

161 161

Database Schema Version

161

Limit Checking for Data Types Validating the Siebel Schema

162 162

Party Model Unifies Access to Data

162

Chapter 5: Schema Changes Table Changes in This Version

165

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

Table Column Changes in This Version

171

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

Table Index Changes in This Version

185

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

Index


5

Contents

6

■


1

W h a t ’s N e w i n T h i s R e le a s e

What’s N ew in Siebel Data Model R eference, Version 8.0, Rev. A Table 1 lists changes described in this version of the documentation to support release 8.0 of the software.

Table 1.

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

Topi c

Description

High Tech Special Pricing Authorization Entity Relationship Diagram (ERD)

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

Marketing Program ERD, see Table 33 on page 79

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

Party model, see Table 80 on page 162

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

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

Table 2.

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

Topi c

Description

Marketing Budget Request ERD

A new entity-relationship diagram.

See “Marketing Budget Request” on page 66.

This ERD illustrates the Marketing Resource Management budget request process.

Marketing Program ERD

This entity-relationship diagram has been modified.

See “Marketing Program” on page 79.

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

Marketing Resource Management: Document ERD


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

This ERD illustrates the Marketing Resource Management marketing content process.


7

W h a t ’ s N e w i n T h i s R e l e as e

Table 2.

■

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

Topi c

Description

Sales Portfolio Management ERD


See “Sales Portfolio Management” on page 123.

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

Table changes See “Table Changes in This Version” on page 165. Table column changes See “Table Column Changes in This Version” on page 171. Table index changes See “Table Index Changes in This Version” on page 185. Territory Management ERD See “Territory Management” on page 135.

■

Assessing the potential of their assigned accounts

■

Engaging the high-potential accounts within their portfolio

■

Directing and managing the resources at their disposal

■

Managing ongoing relationships with customers and partners

A listing of the table changes in this schema including the new tables, deprecated tables, and changes to the existing table definitions. A listing of the column changes in this schema including the new columns, deprecated columns, and changes to the existing column definitions. A listing of the index changes in this schema including the new indexes, deprecated indexes, and changes to the existing index definitions. The relationship from Territory to Territory Hierarchy has been changed from mandatory to optional and moved out of the Territory user key. Territory is now multi-org enabled.

Territory Quota Rollup


See “Territory Quota Rollup” on page 137.

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

8


2

Data Mode l Overview

Oracle’s Siebel Data Model defines how the data used by Siebel Business Applications is stored i n a standard relational DBMS su ch as Oracle, DB2, or Microsoft SQL Server. The Siebel Dat a 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 consi dered transactions, and the database used is called an online transaction processing (OLTP) database. Optimizing a database used for t hese 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. M ost 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, an d delete data in large quantit ies, see Siebel Enterprise Integration Manager Administration Guide.


9

Data Model Overview

10

■


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 relea se 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 Di agram Conventions

■

Entity Relationship Diagrams and Descriptions on page 14

Entity Relationship Diagram Conventions This topic describes entity relationship diagram conventions, as follows: ■

General Entities on page 12

■

Exclusive Arc Relationship on page 12

■

Recursive Relationship on page 13


11

Logical Model

■

Entity Relationship Diagram Conventions

General Entities Figure 1 shows the diagram conventions for general entities used in this publication.

Figure 1.

General Entity Relationship Diagram Conventions

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

12


Logical Model

■

Entity Relationship Diagram Conventions

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

Figure 2.

Exclusive Arc Relationship Diagram Convention Example

Recursive Relationship Figure 3 illustrates an example of the recursive relationship. A recursive relationship is one in which an entity has a relationship to itself. For example, each activity might be part of one and only one activity, or each activity might be made up of one or more activities, as shown in Figure 3. Recursive relationships are almost always optional, and either one-to-many or many-to-many.

Part of

Activity Made up of

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

Figure 3.

Recursive Relationship Diagram Convention Example


13

Logical Model

■


Entity Relationship Diagrams an d Descriptions ERDs represent the significant entities and relevant relationships in a functional area. To enhance their readability, the diagrams do not include every relationship and subtype. Some many-to-many relationships have also been preserved instead of showing them as one-to-many relationships around intersection tables in the logical model. Table 3 provides a list of ERDs in alphabetic order. Ta bl e 3 .

Ent it y Rela ti onsh ip Diagrams

ERD Name

Figure Num. and P age

F u nctional A rea

Account

Figure 4 on page 19

General

Adjustment Group

Figure 5 on page 21

General

Asset Management

Figure 6 on page 23

General

Auction

Figure 7 on page 25

General

Auto Email Response Generator

Figure 8 on page 27

General

CG Promotion Planning

Figure 9 on page 30

Marketing

Compensation Planning Administration

Figure 10 on page 32

ERM

Compensation Planning Execution


ERM

Competency Management System


ERM

Content Management


General

Contract Conditions


General

Contracts


General

Data Visibility


General

Dun & Bradstreet Integration


Sales/Marketing

14


Revised in 8.0

N ew in 8.0

Logical Model

Ta bl e 3 .

■


Ent it y Rela ti onsh ip Diagrams Figure Num. and P age

ERD Name

F u nctional A rea

Employee KPI


ERM

Expense Reports


General

Field Service Inventory


Service

Field Service Scheduler


Service

Forecasts


Sales/Marketing

High Tech Marketing Development Fund


Marketing

High Tech Special Pricing Authorization


Sales

Invoicable Charges


Service

Invoices


Service

Marketing Budget Request


Marketing

Marketing Campaign


Marketing

Marketing Collaboration


Marketing

Marketing Encyclopedia


Sales/Marketing

Marketing Events


General

Marketing Plans


Marketing

Marketing Program


Marketing

Marketing Resource Management: Document


Marketing

Opportunity Management


Sales

Revised in 8.0

N ew in 8.0

Yes

Yes Yes


15

Logical Model

Ta bl e 3 .

■


Ent it y Rela ti onsh ip Diagrams

ERD Name

Figure Num. and P age

F u nctional A rea

Order Life Cycle


General

Orders


General

Partner Collaboration


General

Partner Program Registration


General

Party Model


General

Payments


General

Performance Review


ERM

Personal Account


Industry-Specific

Personal Financial Review


Industry-Specific

Pricing Comparison


Energy

Pricing


General

Product Promotion


General

Product Quality Tracking


General

Product Recommendation


General

Products or Services


Service

Professional Services


General

Revenue


General

Sales Hierarchy and Credit Assignment


Sales

16


Revised in 8.0

N ew in 8.0

Logical Model

Ta bl e 3 .

■


Ent it y Rela ti onsh ip Diagrams Figure Num. and P age

ERD Name

F u nctional A rea

Sales Portfolio Management


Sales

Service Agreement


Service

Service Calendars and Work Shifts


Service

Service Request


Service

Shipment


General

Siebel Assistant


General

Territory Management


Sales

Territory Quota Rollup


Sales

Textile, Apparel, and Footwear


Industry-Specific

Time Sheet


General

Trade Promotions


General

Training Curriculum Course


General

Training Test Engine


General

Versioned Object Definition


General

Warranty


Service

Revised in 8.0

N ew in 8.0 Yes

Yes Yes

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


17

Logical Model

■


The account entity is a su btype 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 incl uding 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 u ser. Each custom account hierarchy is represented completely in a relationsh ip table. The relationships are then denormalized into a separate table to be used for roll-up support. Table 4 lists the entities in this ERD and their corresponding tables. Table 4.

Account ERD Entities and Tables

Entity

Tables

Account

S_ORG_EXT, S_PARTY

Account Synonym

S_ORG_SYN

Activity

S_EVT_ACT

Address

S_ADDR_ORG

Assignment Group (Territory)

S_ASGN_GRP

Business Unit

S_BU, S_ORG_EXT, S_PARTY

Characteristics

S_CHRCTR

Dynamic Account Hierarchy

S_DYN_HRCHY

Dynamic Account Hierarchy Node

S_DYN_HRCHY_REL

Employee/Agent

S_EMP_PER, S_CONTACT, S_PARTY

Industry

S_INDUST

Market Segment

S_MKT_SEG

Party

S_PARTY

Payment Term

S_PAYMENT_TERM

Person

S_CONTACT, S_PARTY

Position

S_POSTN, S_PARTY

Price List

S_PRI_LST

Sales or Service Team Member

S_ACCNT_POSTN

18


DMR

Recommend Documents