Your SlideShare is downloading. ×
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Siebel Data Model Reference 82
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Siebel Data Model Reference 82

5,800

Published on

Published in: Technology, Business
1 Comment
7 Likes
Statistics
Notes
No Downloads
Views
Total Views
5,800
On Slideshare
0
From Embeds
0
Number of Embeds
17
Actions
Shares
0
Downloads
1
Comments
1
Likes
7
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Siebel Data Model Reference Version 8.2 Rev. A March 2013
  • 2. Copyright © 2005, 2013 Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error- free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are “commercial computer software” pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
  • 3. Siebel Data Model Reference Version 8.2 Rev. A 3 Contents Siebel Data Model Reference 1 Chapter 1: What’s New in This Release Chapter 2: Siebel Logical Model Overview of Siebel Data Model 13 Entity Relationship Diagram Conventions 14 General Entities 14 Exclusive Arc Relationship 15 Recursive Relationship 16 Entity Relationship Diagrams and Descriptions for Siebel Cross-Industry Applications 17 Account 20 Adjustment Group 23 Asset Management 25 Auction 27 Auto Email Response Generator 29 CG Promotion Planning 31 Compensation Planning Administration 34 Compensation Planning Execution 36 Competency Management System 38 Content Management 40 Contract Conditions 42 Contracts 44 Data Visibility 46 Dun & Bradstreet Integration 49 Employee KPI 51 Expense Reports 53 Field Service Inventory 55 Field Service Scheduler 57 Forecasts 59 High Tech Marketing Development Fund 61 Invoiceable Charges 63 Invoices 66 Lead Management 68 Marketing Budget Request 71 Marketing Campaign 73
  • 4. Siebel Data Model Reference Version 8.2 Rev. A Contents ■ 4 Marketing Collaboration 75 Marketing Encyclopedia 77 Marketing Event Driven Dialogue 79 Marketing Events 81 Marketing Plans 84 Marketing Program 86 Marketing Resource Management: Document 89 Opportunity Management 91 Order and Promotion 93 Order Life Cycle 95 Orders 97 Partner Collaboration 99 Partner Program Registration 101 Party Model 103 Payments 105 Performance Review 107 Personal Account 110 Personal Financial Review 112 Pricing Comparison 114 Pricing 116 Product Promotion 118 Product Quality Tracking 120 Product Recommendation 122 Products or Services 124 Professional Services 126 Promotion Group 128 Revenue 131 Sales Hierarchy and Credit Assignment 133 Sales Portfolio Management 135 Service Agreement 137 Service Calendars and Work Shifts 139 Service Request 141 Shipment 143 Siebel Assistant 145 Territory Management 147 Territory Quota Rollup 149 Textile, Apparel, and Footwear 151 Time Sheet 153 Trade Promotions 155 Training Curriculum Course 157 Training Test Engine 159 Versioned Object Definition 161
  • 5. Contents ■ Siebel Data Model Reference Version 8.2 Rev. A 5 Warranty 163 Warranty Claim 166 Work Order 169 Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 171 Account Targeting 174 Activity 176 Affiliations and Best Times 178 Agencies/Agent 180 Automotive Retail 182 Brick 184 Clinical Study Management 186 Communications, Media, and Energy (CME) Account 189 CME Agreement 191 CME Alert 193 CME Energy Products, Service, and Usage 195 CME Order Management 197 Commercial Banking 199 Commercial Insurance 202 Community/Chat Discussion 204 Dealer Sales and Service Promotion 206 Document ID and Tax ID 208 Event Tax Administration 210 Financial Account 212 Financial Account Application 214 Financial Investments 216 Financial Products 218 Financial Services Events 220 Fleet Management 223 Flexcube Universal Banking Integration 226 Group Insurance Policies 228 Group Pensions 230 Health Provider and Provider Group 232 High Tech Special Pricing Authorization 234 Hospitality Category 236 Institutional Sales 238 Insurance Claims 240 Insurance Policies 243 Life Insurance Policy 245 Loyalty 247 Loyalty Flowchart and Formula 251 Managed Care 253 Medical Education Event Management 255
  • 6. Siebel Data Model Reference Version 8.2 Rev. A Contents ■ 6 Objectives 257 Personalized Content Delivery 259 Public Sector Benefit Case Management 261 Public Sector Case Lead Management 264 Public Sector Child Welfare 267 Public Sector Contact Identity 269 Public Sector Evidence Management 271 Public Sector Incident Management 273 Public Sector Service Provider and Referral Management 275 Real-Time Scheduler Integration 277 Routes and Best Call Hours 279 Sales Volume Planning 281 Sample Management 283 Special Rate List 285 Syndicated Data 287 Teller Administration 289 Territory Alignment–Quota Assignment 291 Territory Management - Consumer Sector 293 Territory Management - Life Sciences 295 Universal Customer Master 297 Vehicle 299 Vehicle Collection 301 Vehicle Financing 303 Vehicle Sales 305 Chapter 3: Siebel Physical Model Data Model Naming Conventions 307 Table Naming Conventions 307 Index Naming Conventions 309 Column Naming Conventions 309 Abbreviations Used in the Physical Model Listings 310 Data Model Type Definitions 310 Table Type Definitions 311 Table Status Definitions 312 Column Type Definitions 313 Domain Type Definitions 313 Columns of Numeric Physical Type 314 Siebel System Fields 314 INTEGRATION_ID Columns 315 Include Only Field 315
  • 7. Contents ■ Siebel Data Model Reference Version 8.2 Rev. A 7 Siebel Repository 315 Database Schema Version 315 Limit Checking for Data Types 316 Validating the Siebel Schema 316 Party Model Unifies Access to Data 316 Generating a Report about Tables 317 Chapter 4: Schema Changes Siebel Repositories are Combined 319 New Tables for Siebel Business Applications 319 Table Column Changes for Siebel Business Applications 320 New Table Columns in This Version 8.2.2.3 320 Changed Table Columns in Version 8.2.2.3 323 Table Index Changes for Siebel Business Applications 323 New Table Indexes in Version 8.2.2.3 324 Changed Table Indexes in Version 8.2.2.3 325 Index
  • 8. Siebel Data Model Reference Version 8.2 Rev. A Contents ■ 8
  • 9. Siebel Data Model Reference Version 8.2 Rev. A 9 1 What’s New in This Release What’s New in Siebel Data Model Reference, Version 8.2 Rev. A Table 1 lists changes described in this version of the documentation to support this release of the software. What’s New in Siebel Data Model Reference, Version 8.2 Table 1 lists changes described in this version of the documentation to support this release of the software. Table 1. What’s New in Siebel Data Model Reference, Version 8.2 Rev. A Topic Description “New Tables for Siebel Business Applications” on page 319 Modified topic. It lists the new tables for Siebel Business Applications in this schema. “Table Column Changes for Siebel Business Applications” on page 320 Modified topic. It lists the table column changes for Siebel Business Applications in this schema, including the new columns and changes to the existing column values. “Table Index Changes for Siebel Business Applications” on page 323 Modified topic. It lists the table index changes for Siebel Business Applications in this schema, including the new indexes and changes to the existing index definitions. Table 2. What’s New in Siebel Data Model Reference, Version 8.2 Topic Description “CME Alert” on page 193 Modified topic. This feature enables the association of billing profiles with credit alerts. “CME Order Management” on page 197 Modified topic. This feature has added support for tracking order synchronization failures. “Fleet Management” on page 223 New topic. Fleet Management enables transportation management customers to perform order capture, rating, and order management of transportation orders. “Flexcube Universal Banking Integration” on page 226 This new topic describes the integration of Siebel CRM with an external banking system. It provides financial plans, goals, and limits that can be specified for a customer.
  • 10. Siebel Data Model Reference Version 8.2 Rev. A What’s New in This Release ■ 10 “Loyalty Flowchart and Formula” on page 251 New topic. Loyalty promotion flowcharts help to execute promotions in a particular sequence. Loyalty formulas are used to create and store a set of objects and operators specific to a loyalty program. “Order and Promotion” on page 93 New topic. This ERD specifies the relationship between Product Promotions and Order, Quote and Asset entities. “Products or Services” on page 124 Modified topic. This feature now includes a new entity to support user-defined attributes for a product. “Promotion Group” on page 128 New topic. Promotion groups offer advanced product and service bundling and new community offerings that tie various customer assets in a loosely-coupled network, and provide shared benefits and provisioning functions. “Public Sector Benefit Case Management” on page 261 Modified topic. The eligibility determination feature has been enhanced to include effective dating that allows the application to capture, store, and generate change history for a business component that has effective- dating enabled. “Public Sector Child Welfare” on page 267 New topic. This feature addresses the intake and case management needs of social service agencies working to provide child welfare services. “Public Sector Service Provider and Referral Management” on page 275 New topic. This feature allows social service agencies to locate service providers and manage the referral process. “Real-Time Scheduler Integration” on page 277 New topic. Real-Time Scheduler Integration is an external application that performs scheduling. Scheduling involves matching an available service technician to a job or service request. “Special Rate List” on page 285 New topic. A special rate list is a list of phone numbers, country codes, area codes, and so forth, to be used for special rates in telephone rate plans. This special rate list is subsequently used in quotes and orders for the customer in relation to the telephone owned by the customer. “Warranty” on page 163 Modified topic. A warranty service can be provided by one or more authorized service providers. Warranties can also have coverage lists, exclusions from coverage, fault codes, trouble codes, repair operation codes, and repair operation times associated with them Table 2. What’s New in Siebel Data Model Reference, Version 8.2 Topic Description
  • 11. What’s New in This Release ■ Siebel Data Model Reference Version 8.2 Rev. A 11 “Warranty Claim” on page 166 New topic. A warranty claim is the customer's claim for repair or replacement of, or compensation for, non- performance or under-performance of an item as provided in its warranty. “Work Order” on page 169 New topic. A work order is created when a dealer performs any kind of service, which can be part of a warranty claim or a paid service on the asset. Table 2. What’s New in Siebel Data Model Reference, Version 8.2 Topic Description
  • 12. Siebel Data Model Reference Version 8.2 Rev. A What’s New in This Release ■ 12
  • 13. Siebel Data Model Reference Version 8.2 Rev. A 13 2 Siebel Logical Model The entity relationship diagrams (ERDs) included in this chapter 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: ■ Overview of Siebel Data Model ■ Entity Relationship Diagram Conventions ■ Entity Relationship Diagrams and Descriptions for Siebel Cross-Industry Applications on page 17 ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications on page 171 Overview of Siebel Data Model 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 might not be implemented in the physical model at the present time. 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 CRM products you have purchased. You are not entitled to use any portion of the Siebel Data Model to support Siebel CRM 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.
  • 14. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagram Conventions 14 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 (http://www.oracle.com/ technetwork/indexes/documentation/index.html) and Oracle Software Delivery Cloud. It might also be installed locally on your intranet or on a network location. Entity Relationship Diagram Conventions The Siebel logical model represents the following in Siebel Business Applications: ■ Entities ■ Relationships between entities 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. This topic describes entity relationship diagram conventions, as follows: ■ General Entities on page 14 ■ Exclusive Arc Relationship on page 15 ■ Recursive Relationship on page 16 General Entities Figure 1 shows the diagram conventions for general entities used in this guide.
  • 15. Siebel Logical Model ■ Entity Relationship Diagram Conventions Siebel Data Model Reference Version 8.2 Rev. A 15 Exclusive Arc Relationship Figure 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: Each [entity] must be [relationship name] either to only one [entity] or [relationship name] to only one [entity]. For example, each Product Comparison must be to only one Product Internal or to only one Product External as shown in Figure 2. Figure 1. General Entity Relationship Diagram Conventions
  • 16. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagram Conventions 16 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 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
  • 17. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 17 Entity Relationship Diagrams and Descriptions for Siebel Cross-Industry Applications The ERD descriptions and diagrams in this topic apply to Siebel Cross-Industry Applications. These applications are designed for particular business activities and operate across industries. They include the Siebel Call Center, Siebel Service, Siebel Sales, Siebel Marketing, and other applications. Table 3 provides a list of ERDs in alphabetic order. Table 3. Entity Relationship Diagrams for Siebel Cross-Industry Applications ERD Name Figure Number and Page Functional Area Account Figure 4 on page 22 General Adjustment Group Figure 5 on page 24 General Asset Management Figure 6 on page 26 General Auction Figure 7 on page 28 General Auto Email Response Generator Figure 8 on page 30 General CG Promotion Planning Figure 9 on page 33 Marketing Compensation Planning Administration Figure 10 on page 35 ERM Compensation Planning Execution Figure 11 on page 37 ERM Competency Management System Figure 12 on page 39 ERM Content Management Figure 13 on page 41 General Contract Conditions Figure 14 on page 43 General Contracts Figure 15 on page 45 General Data Visibility Figure 16 on page 48 General Dun & Bradstreet Integration Figure 17 on page 50 Sales/Marketing Employee KPI Figure 18 on page 52 ERM Expense Reports Figure 19 on page 54 General Field Service Inventory Figure 20 on page 56 Service Field Service Scheduler Figure 21 on page 58 Service Forecasts Figure 22 on page 60 Sales/Marketing High Tech Marketing Development Fund Figure 23 on page 62 Marketing Invoiceable Charges Figure 24 on page 65 Service Invoices Figure 25 on page 67 Service Lead Management Figure 26 on page 70 Sales/Marketing
  • 18. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 18 Marketing Budget Request Figure 27 on page 72 Marketing Marketing Campaign Figure 28 on page 74 Marketing Marketing Collaboration Figure 29 on page 76 Marketing Marketing Encyclopedia Figure 30 on page 78 Sales/Marketing Marketing Event Driven Dialogue Figure 31 on page 80 Marketing Marketing Events Figure 32 on page 83 General Marketing Plans Figure 33 on page 85 Marketing Marketing Program Figure 34 on page 88 Marketing Marketing Resource Management: Document Figure 35 on page 90 Marketing Opportunity Management Figure 36 on page 92 Sales Order and Promotion Figure 37 on page 94 General Order Life Cycle Figure 38 on page 96 General Orders Figure 39 on page 98 General Partner Collaboration Figure 40 on page 100 General Partner Program Registration Figure 41 on page 102 General Party Model Figure 42 on page 104 General Payments Figure 43 on page 106 General Performance Review Figure 44 on page 109 ERM Personal Account Figure 45 on page 111 Industry-Specific Personal Financial Review Figure 46 on page 113 Industry-Specific Pricing Comparison Figure 47 on page 115 Energy Pricing Figure 48 on page 117 General Product Promotion Figure 49 on page 119 General Product Quality Tracking Figure 50 on page 121 General Product Recommendation Figure 51 on page 123 General Products or Services Figure 52 on page 125 General Professional Services Figure 53 on page 127 General Promotion Group Figure 54 on page 130 General Revenue Figure 55 on page 132 General Sales Hierarchy and Credit Assignment Figure 56 on page 134 Sales Sales Portfolio Management Figure 57 on page 136 Sales Table 3. Entity Relationship Diagrams for Siebel Cross-Industry Applications ERD Name Figure Number and Page Functional Area
  • 19. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 19 Service Agreement Figure 58 on page 138 Service Service Calendars and Work Shifts Figure 59 on page 140 Service Service Request Figure 60 on page 142 Service Shipment Figure 61 on page 144 General Siebel Assistant Figure 62 on page 146 General Territory Management Figure 63 on page 148 Sales Territory Quota Rollup Figure 64 on page 150 Sales Textile, Apparel, and Footwear Figure 65 on page 152 Consumer Sector Time Sheet Figure 66 on page 154 General Trade Promotions Figure 67 on page 156 General Training Curriculum Course Figure 68 on page 158 General Training Test Engine Figure 69 on page 160 General Versioned Object Definition Figure 70 on page 162 General Warranty Figure 71 on page 165 Service Warranty Claim Figure 72 on page 168 Service Work Order Figure 73 on page 170 Service Table 3. Entity Relationship Diagrams for Siebel Cross-Industry Applications ERD Name Figure Number and Page Functional Area
  • 20. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 20 Account This ERD (see Figure 4) illustrates the account entity, 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 4 lists the entities in this ERD and their corresponding tables. Table 4. Account ERD Entities and Tables Entity Table Account S_ORG_EXT, S_PARTY Account Synonym S_ORG_SYN Activity S_EVT_ACT Address S_ADDR_ORG (Siebel Cross-Industry Applications) S_ADDR_PER (Siebel Industry Applications) 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
  • 21. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 21 Position S_POSTN, S_PARTY Price List S_PRI_LST Sales or Service Team Member S_ACCNT_POSTN Table 4. Account ERD Entities and Tables Entity Table
  • 22. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 22 Figure 4. Account NAMEDHIERARCHY NAMEDHIERARCHY ACCOUNT PAYMENTTERM ACCOUNTSYNONYM INDUSTRY CORRESPONDENCE PRICELIST SALESORSERVICE TEAMMEMBER MARKET SEGMENT DECISION ISSUES PARTY POSITION ACCOUNT OTHER PARTYBUSINESSUNITPERSON OTHERPERSONEMPLOYEE/AGENT ACTIVITY ASSIGNMENT GROUP (TERRITORY) ADDRESS CHARACTERISTIC constrainedtouse acessibleto of madevisiblethrough for madeupof areportto aparentof actionfor targetof classificationfor typeof for partof participantin targetof responsiblefor responsibilityof usercharacteristicsfor describedin areporttoaparentof anothernamefor knownasuserof currentprice listfor applicableto accessto for belongto addressedto participatein for locatedat holders of heldbypayorpayedby defaultpaymenttermfor composedof contactof responsibilityof responsiblefor
  • 23. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 23 Adjustment Group This ERD (see Figure 5) illustrates the system for managing the various matrices for pricing, compatibility, eligibility, product promotions, and so on. It allows the user to define a matrix, its dimensions, and all of its rules. This new infrastructure allows the adjustment to be any value, not just a price amount. Table 5 lists the entities in this ERD and their corresponding tables. Table 5. 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
  • 24. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 24 Figure 5. Adjustment Group STANDARD TRAINING PRICING MATRIX RULE # MTRX_RULE_NUM STANDARD PRODUCT PRICING MATRIX RULE # MTRX_RULE_NUM STANDARD ENTITLEMENT PRICING MATRIX RULE # MTRX_RULE_NUM PRODUCT PROMOTION PRICING MATRIX RULE # MTRX_RULE_NUM PRODUCT ELIGIBILITY MATRIX RULE # MTRX_RULE_NUM PRODUCT COMPATABILITY MATRIX RULE # MTRX_RULE_NUM ADJUSTMENT GROUP DIMENSION # FIELD_NAME ADJUSTMENT GROUP # ADJ_GROUP_NAME for contain for contain for contain for contain for contain for contain for contain
  • 25. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 25 Asset Management This ERD (see Figure 6) illustrates how Siebel Business Applications track instances of assets. Moving counter-clockwise from the lower-right corner, the diagram shows how internal products can be made into assets and associated with an account or a contact to register ownership. Additional relationships between assets and accounts, contacts, and employees are illustrated in the upper- right corner. Additional information such as the related opportunities, the current business or personal address location of the asset, notes, and related assets are shown across the top of the diagram. The left side of the diagram shows the relationships with service requests, activities, and related part movements. Table 6 lists the entities in this ERD and their corresponding tables. Table 6. Asset Management ERD Entities and Tables Entity Table Activity S_EVT_ACT Activity Part Movement S_ACTPART_MVMT Asset Contact Relationship S_ASSET_CON Asset Employee Relationship S_ASSET_EMP Asset External Organization S_ASSET_ACCNT Asset Feature S_ASSET_FEA Asset Modification S_ASSET_TXN Asset Relationship S_ASSET_REL Business Address S_ADDR_ORG (Siebel Cross-Industry Applications) S_ADDR_PER (Siebel Industry Applications) Competitive Metric S_CMPT_MTRC Competitive Product Feature S_CMPT_PROD_FEA Contact S_CONTACT, S_PARTY Employee S_EMP_PER, S_CONTACT, S_PARTY External Product S_PROD_EXT Internal Product S_PROD_INT Opportunity S_OPTY Opportunity Asset S_OPTY_ASSET Person S_CONTACT, S_PARTY Personal Address S_ADDR_PER Product Instance (Asset) S_ASSET Service Request S_SRV_REQ
  • 26. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 26 Figure 6. Asset Management ACTIVITYPART MOVEMENT ACTIVITY SERVICE REQUEST ADDRESS PERSONAL ADDRESS BUSINESS ADDRESS NOTE COMPETITIVE PRODUCT FEATURE COMPETITIVE METRIC OPPORTUNITY PRODUCT INTERNALPRODUCT NON-SERIALIZABLE PRODUCT SERIALIZABLE PRODUCT EXTERNAL PRODUCT PRODUCTINSTANCE(ASSET) PERSON CONTACT EMPLOYEE OPPORTUNITY ASSET ASSET MODIFICATION ASSET RELATIONSHIP ASSET FEATURE ASSETEMPLOYEERELATIONSHIP ASSETCONTACTRELATIONSHIP ASSETEXTERNALORGANIZATION EXTERNAL ORGANIZATION VENDOR ACCOUNT OTHEREXTERNAL ORGANIZATION for subjectof definedfor subjectof performedon subjectof forproblemswith subjectof forproblemswith subjectof partof madeupof of movedby of movedby initiatedby initiatorof partof madeupof definedfor subjectof locatedat for for subjectof of classificationfor forsubjectof of classificationfor forinitiatedby useof involvedin for associatedwith currentlyownedby ownerof currentlyownedby ownerof currentlypossessedby possessorof acomponentof anassemblyof instanceof madeinto childofparentofproducedby vendorof to associatedwith of subjectof to associatedwith of subjectof of subjectof to associatedwith of associatedwith useof involvedin for modifiedby of initiatorof
  • 27. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 27 Auction This ERD (see Figure 7) illustrates how the Siebel Data Model represents the auctioning of goods or services to bidders. An auction item can be a stand-alone offering, or can 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 can 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 can be tracked through one or more order items. Finally, users can set up watched items, define alerts, and rate fellow listers or bidders. Table 7 lists the entities in this ERD and their corresponding tables. Table 7. 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
  • 28. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 28 Figure 7. Auction ORDER AUCTIONLISTER/BIDDER RATING TRIGGEREDAUCTIONITEMALERT ORDERITEM PARTY OTHERPARTY PERSON OTHERPERSONUSER CATALOG PRODUCT ASSET CATALOGCATEGORYITEMCATALOGCATEGORY AUCTIONITEMWATCH AUCTIONITEM PROMOTION AUCTIONALERT DEFINITION AUCTIONITEMBID AUCTIONITEM createdby creatorof partof composedof applicableto subjectof partof madeupof ratingof subjectof madeby creatorof placedby placerof listedby listerof for subjectof for subjectof for creatorof for alertedby created from genesisof for featuredin representedby displayedas representedby displayedas createdfrom representedas accessed via ownerof for ownerof pricing mechanism for pricedby pricing mechanism for pricedby fulfillmentof fulfilledas for subjectof
  • 29. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 29 Auto Email Response Generator This ERD (see Figure 8) illustrates the data model for the automatic generation of a response to an inbound communication. Incoming messages (inbound communications) are compared against a database of previously categorized messages to categorize them in one or more categories. The categories are associated with predefined template communication responses, used to generate a default response to each category of message. A notification mechanism can be defined to alert a person whenever the usage of a category or template exceeds a predefined limit. Table 8 lists the entities in this ERD and their corresponding tables. Table 8. Auto Email Response Generator ERD Entities and Tables Entity Table Activity S_EVT_ACT Catalog S_CTLG Catalog Category S_CTLG_CAT Category Usage Notification S_COMM_CTG_NTFY Communication Template Usage Notification S_COMMTMPL_NTFY Person S_CONTACT, S_PARTY Problem Resolution Document S_RESITEM Template Communication Response S_DMND_CRTN_PRG
  • 30. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 30 Figure 8. Auto Email Response Generator TEMPLATE COMMUNICATION RESPONSE PROBLEM RESOLUTION DOCUMENT ACTIVITY OUTBOUND RESPONSE INBOUND COMMUNICATION CATALOG CATEGORY CATALOG PERSON COMMUNICATION TMPL USAGE NOTIFICATION CATEGORY USAGE NOTIFICATION for usage of subject of categorized within classification for classification of default response for categorized under classification for part of made up of part of made up to notify target of to notify target of for usage of subject of
  • 31. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 31 CG Promotion Planning This ERD (see Figure 9) 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 can be covered by a single payment to the partner account. Advanced Planning is a feature designed to address the process used by CG organizations to plan sales volume and sales revenue at key accounts. Advanced Planning is part of a broader process called Trade Marketing. Trade Marketing includes planning, executing, and analyzing sales. Table 9 lists the entities in this ERD and their corresponding tables. Table 9. CG Promotion Planning ERD Entities and Tables Entity Table Account S_ORG_EXT, S_PARTY Authorized Product S_ORG_PROD Fund Allocation S_MDF_ALLOC Marketing Development Fund S_MDF Marketing Event or Activity S_SRC MDF Accrual S_MDF_ACCRUAL Payment S_SRC_PAYMENT Period S_PERIOD Person S_CONTACT, S_PARTY Position S_POSTN, S_PARTY Price List S_PRI_LST Price List Item S_PRI_LST_ITEM Product Internal S_PROD_INT Product Line S_PROD_LN Product Structure S_PROD_REL or S_PROD_ITEM Promotion Plan S_SRC Promotion S_SRC Promotion Account S_SRC Promotion Product S_SRC
  • 32. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 32 Promotion Category S_SRC Promotion Account Product S_SRC Table 9. CG Promotion Planning ERD Entities and Tables Entity Table
  • 33. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 33 Figure 9. CG Promotion Planning MARKETINGEVENTORACTIVITY PROMOTIONPLAN PROMOTIONACCOUNTPRODUCT PROMOTIONACCOUNT PROMOTION OTHERMARKETINGEVENTOR ACTIVITY PROMOTIONPRODUCT PROMOTIONCATEGORY PAYMENT OTHERPAYMENT PROMOTIONPAYMENT PERSON EMPLOYEE/AGENT OTHERPERSON POSITION ACCOUNT PRODUCTLINE AUTHORIZED PRODUCT MDFACCRUAL PRICELISTITEM FUND ALLOCATION PRICELIST PRODUCT STRUCTURE MARKETING DEVELOPMENT FUND MIXEDFUND ACCRUAL FUND FIXEDFUND INTERNALPRODUCTOR SERVICE PERIOD suballocatedto suballocationof partof madeof of promotedvia definedfor subjectof userof usedby targetof availableto definedfor subjectof to recipientof for subjectof coveredby for assignedto responsiblefor relatedto relationof approvedby approverof requestedby requestorof ofsubjectof earnedinsubjectof madeupof partof at subjectof designatedto targetof composedofpartof subjectto applicableto assignedto responsiblefor forpromotionof subjectof earnedby earnerof earnedbyearnerof for fundedthrough hierarchychildof hierarchyparentof ofsubjectof composedof for basedon basisfor of subjectof definedforsubjectof anassemblyof for acomponentof of forpromotionof subjectof 7LWOH*3URPRWLRQ3ODQQLQJ $XWKRUOracleRQILGHQWLDO
  • 34. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 34 Compensation Planning Administration This ERD (see Figure 10) illustrates the administration activities of compensation planning, which involve setting up salary structures such as salary plan, salary grades, and job codes. In addition to salary structures, an organization sets up compensation budgets, compensation types such as merit increase, bonus, promotion, and stock options, planning periods, budget calculation and eligibility rules, guidelines and calculation of budget allocations for employees. Table 10 lists the entities in this ERD and their corresponding tables. Table 10. 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
  • 35. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 35 Figure 10. Compensation Planning Administration Title:CompensationPlanningAdministration Author:Oracle,Confidential POSITION SALARYPLANFOR SALARYGRADE JOB FAMILY JOB CATEGORY COMPENSATION REGION JOBCODE COMPENSATIONGUIDELINE DEFINITION COMPENSATIONTYPE SALARYPLAN BUSINESSUNIT PERIOD QUARTERLYPERIOD ANNUALPERIOD COMPENSATION CHANGEEFFECTIVITY DATE COMPENSATIONCYCLEPLANNINGPERIOD COMPENSATIONPLANNINGPERIOD EMPLOYEE/AGENT COMPENSATIONBUDGET ITEMFOREMPLOYEE EMPLOYEEELIGIBILITY (PDQ) COMPENSATIONBUDGETITEM COMPENSATIONBUDGETDEFINITION COMPENSATION GUIDELINE FACTOR COMPENSATIONGUIDELINETABLE COMPENSATION GUIDELINESET SALARYGRADE supportmanageby salaryplan gradedefined in for salaryplanfor definedin salarygradesfor have definedfor usedbyperiodfor have partof groupingfor categorized in categoryfor have definedfor has jobcodefor locatedin compensationlocationfor salary grade defined in for salary defined in for defined for componentof typeof typefor valuesfor have 2factor defined in usedin 1factor defined in usedin typeof typefor constrainedby definedfor budgetfor have employedby employerof sub-orgof composedof definedforusedin definedfor usedin validdatefor have definedfor userof definedforusedbysubjectof containerfor allocatedfor has budgetallocationfor has constrainedby definedfor subjectof containerfor defined for componentof subjectof containerfor
  • 36. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 36 Compensation Planning Execution This ERD (see Figure 11) illustrates the execution phase of compensation planning. In this phase, 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 can grant to his employees. Authorized persons such as managers, or HR personnel approve the plans. Totals are maintained for each manager and organization. Table 11 lists the entities in this ERD and their corresponding tables. Table 11. 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
  • 37. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 37 Figure 11. Compensation Planning Execution 7LWOHRPSHQVDWLRQ3ODQQLQJ([HFXWLRQ $XWKRUOracleRQILGHQWLDO 3(5,2' 203(16$7,21 *8,'(/,1( '(),1,7,21 203(16$7,21 3/$1727$/ 203(16$7,2173( %86,1(66 81,7 203(16$7,21 3/$1200(176 203(16$7,213/$1,7(0)25(03/2(( 203(16$7,213/$1)25(03/2(( 203(16$7,21 3/$1 203(16$7,21 *8,'(/,1(6(7 203(16$7,21 *8,'(/,1(7$%/( 203(16$7,21 %8'*(7 '(),1,7,21 203(16$7,21 %8'*(7,7(0 203(16$7,21 %8'*(7,7(0)25 (03/2(( (03/2(( $*(17 203(16$7,213/$11,1* 3(5,2' 203(16$7,21 /(3/$11,1* 3(5,2' GHILQHGIRU XVHGLQ EDVHGRQ XVHGLQ YDOXHVIRU KDYH VXEPLWWHGE VXEPLWWHURI WRWDOIRU WSHIRU IRU KDYH YLVLEOHWR DFFHVVWR KDV SDUHQWPDQDJHUIRU WSHRI WSHIRU VXEMHFWRI VXEMHFWIRU GHILQHGIRUXVHURI GHILQHGIRU XVHGE GHILQHGIRU KDV VXEMHFWRI FRQWDLQHUIRU GHILQHGIRU XVHGE VXEMHFWRI FRQWDLQHUIRU WSHRI WSHIRU GHILQHGIRU KDV DSSURYHGE DSSURYHUIRU FXUUHQWOSODQQHGE SODQQHUIRUORFNHGE FXUUHQWRZQHUIRU EXGJHWIRU KDYH HPSORHGE HPSORHURI IRU KDYH GHILQHGIRU XVHGLQ LWHPVIRU KDYH FRPSRVHGRI SDUWRI SDUWRI FRPSRVHGRI RZQHGE RZQHURI VXEMHFWRI FRQWDLQHUIRU DOORFDWHGIRU KDV
  • 38. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 38 Competency Management System This ERD (see Figure 12) illustrates how 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 he or she completes those courses. Table 12 lists the entities in this ERD and their corresponding tables. Table 12. 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
  • 39. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 39 Figure 12. Competency Management System 7LWOHRPSHWHQF0DQDJHPHQW6VWHP $XWKRUOracleRQILGHQWLDO 7($0203(7(1 48$/,),$7,2125(;3(5,(1( 352)(66,21$/0(0%(56+,3 +21256$1'$:$5'6 352)(66,21$/(57,),$7,21 3$67:25.(;3(5,(1( ('8$7,21$/48$/,),$7,21 (03/2((203(7(1 +$1*( (03/2((855(17203(7(1 203(7(1$7(*25 5227203(7(1$7(*25 203(7(1 -2%2'( 5(9,(:5$7,1*6$/( 5(9,(:5$7,1* 75$,1,1*2856( $5((53$7+ -2%352),/( 3(5621 (03/2(( $*(17 27+(5 3(5621 IRU VXEMHFWRI DFTXLUHG IURP UHVXOWVLQ UHTXLUHPHQW IRU UHTXLUHURI SDUWRI FRPSRVHGRI FDWHJRUL]HGXQGHU FDWHJRUIRU IRU PDQDJHURIKDV IRU KDV IRU KDV IRU UDWHGXVLQJ UDWHGXQGHU SDUWRI FRPSRVHGRI UHYLHZHGE UHYLHZHUIRU ZRUNLQJWRZDUGV IXWXUHJRDOIRU FRGLILHGE FRGLILFDWLRQRI HPSORHGXQGHU DVVLJQHGWR SDUWRI FRPSRVHGRI VFRUHGDW VFRUHIRU WDNHQE JHWWUDLQHGLQ SURYLGHWUDLQLQJIRU VDWLVILHGE FXUUHQWOKROGLQJ FXUUHQWOKHOGE SDWKIURP FXUUHQWSURILOHIRU PRYHWR WDUJHWRI IRU VXEMHFWRI KHOGE KROGHURI
  • 40. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 40 Content Management This ERD (see Figure 13) 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 might be the responsibility of, reviewed by, or approved by one or more Positions. Table 13 lists the entities in this ERD and their corresponding tables. Table 13. 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 Person S_CONTACT, S_PARTY Position S_POSTN, S_PARTY Product S_PROD_INT
  • 41. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 41 Figure 13. Content Management Title:ContentManagement Author:Oracle,Confidential MASTERDATAITEM OTHERMASTER DATAITEMPRODUCT LITERATURE POSITION BUSINESS OBJECT PICKLIST CONTENTOBJECT CONTENT PROJECT CONTENT PROJECT ITEM PERSON VIEW PICKAPPLET WORKFLOWPROCESS EAI INTEGRATION OBJECT CONTENTITEM TYPE formanaging changesto managedby heldby holderof pickedvia usedby generally controlled by generallyfollowed by responsible for responsibility of generallyresponsiblefor generallytheresponsibilityof viewedvia usedby usedby viewedvia producedby producerofownedby ownerof basedon basisfor pickedvia usedby pickedvia usedby pickedvia usedby pickedvia usedby controlledby followedby partof made upof anexampleof typefor pickedvia usedby publishedvia usedby
  • 42. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 42 Contract Conditions This ERD (see Figure 14) illustrates the usage of templates to create agreements. An agreement could comprise one or more entitlements. A contracts administrator can define template entitlements, template benefits and template conditions in addition to template terms. Template benefits and conditions could be for a specific product or product line or product class or category. An entitlement could be created using the entitlement template and this would create the corresponding benefits and conditions based on the corresponding template benefits and conditions. The terms governing the agreement could be based on template terms. Table 14 lists the entities in this ERD and their corresponding tables. Table 14. Contract Conditions ERD Entities and Tables Entity Table Agreement S_DOC_AGREE Benefit S_AGREE_BNFT Category S_CTLG_CAT Condition S_AGREE_COND Condition Compliance S_AGR_COND_CMPL Contract S_DOC_AGREE Entitlement S_ENTLMNT Entitlement Template S_ENTL_TMPL Object Class S_VOD, S_VOD_VER Product S_PROD_INT Product Line S_PROD_LN Template Benefit S_ENTL_BNFTTMPL Template Condition S_ENTL_CONDTMPL Template Term S_AGR_TERM_TMPL Term S_AGR_TERM_DESC
  • 43. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 43 Figure 14. Contract Conditions Title:ContractLifecycleManagement Author:Oracle,Confidential CONTRACTCONDITION OBJECT CATEGORY OBJECTCLASS PRODUCT PRODUCTLINE CONTRACT AGREEMENTOTHER CONTRACT TERM TEMPLATETERM #TERM_NUM TEMPLATECONDITION #SEQ_NUM TEMPLATEBENEFIT #SEQ_NUM CONDITIONCOMPLIANCE #COMPL_NUM CONDITION #SEQ_NUM BENEFIT #SEQ_NUM ENTITLEMENTTEMPLATE #NAME ENTITLEMENT #NAME inreferencetosubjectof inreferenceto subjectof inreferenceto subjectof inreferenceto subjectof incontextof composedof basedon usedby basedon usedby belongto composedof correspondto usedby applicableto comprise applicableto comprise inreferenceto subjectof applicableto governedby applicableto governedby applicableto subjectof applicableto subjectof basedon usedin dependentupon comprise inreferenceto subjectof inreferenceto basisfor
  • 44. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 44 Contracts This ERD (see Figure 15) 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 might be a person. The party on the other side of the contract is an internal or partner organization (or business unit). A contract is composed of contract line items that specify the internal products, services, or assets to be covered under the terms of the contract. Table 15 lists the entities in this ERD and their corresponding tables. Table 15. Contracts ERD Entities and Tables Entity Table Account S_ORG_EXT, S_PARTY Asset S_ASSET Business Unit S_BU, S_ORG_EXT, S_PARTY 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 Payment Term S_PAYMENT_TERM Person S_CONTACT, S_PARTY Position S_POSTN, S_PARTY Price List S_PRI_LST
  • 45. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 45 Figure 15. Contracts Title:Contracts Author:Oracle,Confidential POSITIONPERSONBUSINESSUNIT ASSETINTERNAL PRODUCTOR SERVICE PAYMENT TERM PRICELIST ACCOUNT CONTRACTLINEITEM ORDERLINEITEM AGREEMENTLINE ITEM QUOTELINEITEM OTHERCONTRACTLINEITEM CONTRACT AGREEMENT OTHERCONTRACT QUOTEORDER for subjectof partofcomposedof partof composedof for subjectof involvedby primarycontactfor responsibilityof responsiblefor for subjectof partofcomposedof pricedby pricing methodfor pricedby defaultpricingfor aninstanceof madeinto employerof employedat responsibilityof responsiblefor subjectto for subjectto for pricedby pricingfor applicableto subjectto
  • 46. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 46 Data Visibility The main business entities represented (see Figure 16) in the Siebel Data Model fall into one of two super-types: Master Data Item or Customer Data Item. A Master Data Item represents data set up and administered by the company using Siebel Business Applications such as products, literature, and price Lists. Master Data Items are often categorized to make information more accessible. A user gains visibility to this data either through the person's association with a business unit (multiple organization visibility) or through the person's access to items in a catalog (access control). Access to items in a catalog is provided by making the category public, or by granting access to the category to one or more access groups. Each access group can be made up of smaller access groups and can 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 can be made up of smaller business units. A given type of customer data item is usually assigned to employees through position or directly to the employee, but rarely both. Managers can be granted access to customer data items assigned to their subordinates. Table 16 lists the entities in this ERD and their corresponding tables. Table 16. Data Visibility ERD Entities and Tables Entity Table Access Group S_PARTY Account S_ORG_EXT Activity S_EVT_ACT Agreement S_DOC_AGREE Business Unit S_BU, S_ORG_EXT, S_PARTY Catalog S_CTLG Category S_CTLG_CAT Dynamic Account Hierarchy S_DYN_HRCHY Dynamic Account Hierarchy Node S_DYN_HRCHY_REL Employee/Agent S_EMP_PER, S_CONTACT, S_PARTY Group S_PARTY Internal/Partner Organization Unit S_ORG_EXT Literature Item S_LIT Opportunity S_OPTY
  • 47. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 47 Order S_ORDER Organization Unit S_ORG_EXT, S_PARTY Party S_PARTY Position S_POSTN, S_PARTY Price List S_PRI_LST Product S_PROD_INT Quote S_DOC_QUOTE Service Request S_SRV_REQ Table 16. Data Visibility ERD Entities and Tables Entity Table
  • 48. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 48 Figure 16. Data Visibility 7LWOH'DWD9LVLELOLW $XWKRUOracleRQILGHQWLDO $7$/2* $7(*25 3$57 27+(53$57 *5283 27+(5*5283 326,7,21 25*$1,=$7,2181,7 ,17(51$/3$571(525*$1,=$7,2181,7 27+(5 ,17(51$/3$571(5 25*$1,=$7,2181,7 %86,1(6681,7 27+(525*$1,=$7,2181,7 $(66*5283 3(5621 (03/2(($*(1727+(53(5621 86720(5'$7$,7(0 6(59,( 5(48(67 23325781,7$*5((0(17 27+(586720(5 '$7$,7(0 25'(5 $7,9,7 4827( 0$67(5'$7$,7(0 27+(50$67(5 '$7$,7(0 35,(/,67 /,7(5$785(,7(0 352'87 RZQHGE RZQHURI PHPEHURI FRPSRVHGRI FKLOGRI SDUHQWRI FKLOGRI SDUHQWRI GHILQHGZLWKLQ FRPSRVHGRI PDGHXSRI PHPEHURI SDUWRI PDGHXSRI RUJDQL]HGZLWKLQ RUJDQL]DWLRQIRU GHILQHGIRU JUDQWHG DFFHVVWR SDUWRI PDGHXSRI UHSRUWWR PDQDJHURI GHILQHGIRU RZQHURI UHVSRQVLELOLWRI DVVLJQHG WR UHVSRQVLELOLWRI DVVLJQHGWR DFFHVVLEOHWR JUDQWHGDFFHVVWR GHILQHGLQ PDGHXSRI PDGHXS RI FDWHJRUL]HGLQ
  • 49. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 49 Dun Bradstreet Integration This ERD (see Figure 17) illustrates how Siebel Business Applications integrate with Dun Bradstreet (D B) Organization information. A D B organization can be classified as doing business in one or more industries, and can provide information about contacts at the organization and their management responsibilities. In addition, a D B organization can indicate its direct parent organization, its ultimate domestic parent, and its ultimate global parent. A Siebel organization unit (for example, an account) can be related to its equivalent D B organization and its associated parent organizations. Contact information from one or more D B organizations can be used to create one or more call lists. Table 17 lists the entities in this ERD and their corresponding tables. Table 17. Dun Bradstreet Integration ERD Entities and Tables Entity Table Call List S_CALL_LST Call List D B Organization S_DNB_ORG_LST D B Contact Responsibility S_DNB_CON_MRC D B Management Responsibility Type S_DNB_MRC D B Organization S_DNB_ORG D B Organization Industry Classification S_DNB_ORG_SIC D B Standard Industry Classification S_DNB_SIC Industry S_INDUST Organization Industry Classification S_ORG_INDUST Organization Unit S_ORG_EXT, S_PARTY Prospect S_PRSP_CONTACT
  • 50. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 50 Figure 17. Dun Bradstreet Integration Title:DunBradstreetIntegration Author:Oracle,Confidential PROSPECT DBCONTACTOTHER PROSPECT CALLLIST CALLLISTDB ORGANIZATION ORGANIZATIONUNIT INDUSTRY ORGANIZATIONINDUSTRYCLASSIFICATION DBMANAGEMENT RESPONSIBILITYTYPE DBCONTACTRESPONSIBILITY DBSTANDARDINDUSTRY CLASSIFICATION DBORGANIZATIONINDUSTRYCLASSIFICATION DBORGANIZATION affiliatedwith composedof composedof memberin for bearerof direct childof direct parentof primarilya banking customerof abankfor ofsourceof for createdfrom equivalenttoequivalentto globalparentofglobalchildof domesticparentofdomesticchildof parentofchildof specifierof classificationfor classifierof classifiedwithin of assignedto globalchild of global parentof domestic childof domestic parentof specifierof classificationfor classifierof classified within
  • 51. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 51 Employee KPI This ERD (see Figure 18) illustrates that Key Performance Indicators (KPI) can be defined and associated with the objectives of an employee so that the employee and the manager of the employee manager can measure achievement or current values against the goals set in the objectives of the employee. Table 18 lists the entities in this ERD and their corresponding tables. Table 18. 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
  • 52. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 52 Figure 18. Employee KPI Title : Employee KPI Author : Oracle, Confidential KPI VALUE HISTORY KPI VALUE FOR EMPLOYEE KPI VALUE FOR OBJECTIVE KEY PERFORMANCE INDICATOR DEFINITION PARTY GROUP ACCESS GROUP ORGANIZATION UNIT DIVISION OTHER PARTY 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 value for measurement of subject of approved by approver of child visibility node of parent visibility node of accessed by have access to
  • 53. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 53 Expense Reports This ERD (see Figure 19) illustrates how Siebel Business Applications track employee expense reports. Employees (for example, sales representatives, field service engineers, and professional services personnel) can track expense items incurred for business purposes. These expenses can be associated with an account, an opportunity, or a project, and can be related to an activity. Other employees or contacts involved in the expense can be associated with the expense. The expenses in a specified reporting period can then be reported on an expense report for reimbursement. Table 19 lists the entities in this ERD and their corresponding tables. Table 19. Expense Reports ERD Entities and Tables Entity Table Activity S_EVT_ACT Employee S_EMP_PER, S_CONTACT, S_PARTY 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 Organization Unit S_ORG_EXT, S_PARTY Party S_PARTY Person S_CONTACT, S_PARTY Project S_PROJ
  • 54. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 54 Figure 19. Expense Reports Title : Expense Reports Author : Oracle, Confidential PARTY PERSON EMPLOYEE / AGENT OTHER PERSON ORGANIZATION UNIT INTERNAL ORGANIZATION / PARTNER OTHER ORGANIZATION UNIT ACTIVITY EXPENSE REPORT APPROVAL PERIOD PROJECT OPPORTUNITY EXPENSE REPORT EXPENSE ITEM TYPE EXPENSE ITEM reported for the reporting period for reported by reporter ofaccounting approval by approver of charged to charged with by provider of involved in involver of incurred for subject of of classification for incurred during source of incurred for subject of incurred by incurrer of for source of for subject of incurred for subject of of subject of reported on composed of made up of part of
  • 55. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 55 Field Service Inventory This ERD (see Figure 20) illustrates how Siebel Business Applications track field service parts inventory. Parts can 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 can be located at a third-party provider, as well as within the internal organization. They can also be related to other inventory locations for the purposes of replenishment or fulfillment. Table 20 lists the entities in this ERD and their corresponding tables. Table 20. Field Service Inventory ERD Entities and Tables Entity Table Address S_ADDR_ORG (Siebel Cross-Industry Applications) S_ADDR_PER (Siebel Industry Applications) Asset S_ASSET Business Unit S_BU, S_ORG_EXT, S_PARTY Inventory Location S_INVLOC Inventory Transaction S_INV_TXN Organization Unit S_ORG_EXT, S_PARTY Party S_PARTY Person S_CONTACT, S_PARTY Position S_POSTN, S_PARTY Product Inventory S_PROD_INV Product Inventory Category S_PROD_INV_CAT Product Inventory Location S_PROD_INVLOC Product or Service S_PROD_INT
  • 56. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 56 Figure 20. Field Service Inventory Title:FieldServiceInventory Author:Oracle,ConfidentialINVENTORY TRANSACTIONTYPE INVENTORYTRANSACTION NON-SERIALIZED TRANSACTION SERIALIZED TRANSACTION PRODUCTINVENTORY LOCATION PRODUCT INVENTORY CATEGORY PRODUCTINVENTORY ASSET(PRODUCT INSTANCE) PERSON ADDRESS ORGANIZATIONUNIT INTERNAL/PARTNER ORGANIZATION OTHER ORGANIZATION POSITION BUSINESS UNIT INVENTORY LOCATIONTYPE PRODUCTORSERVICE PRODUCTINTERNAL SERIALIZABLE PRODUCT NON-SERIALIZABLE PRODUCT INVENTORYLOCATION VIRTUALINVENTORY LOCATION OTHERINVENTORY LOCATION WAREHOUSE PERSONAL(TRUNK) INVENTORYLOCATION replenishedfrom replenishment sourcefor isa ismadeinto of for typeof locatedat anassemblyof acomponentof partofmadeup visible to accessorof responsibility of responsible for located at for replenished from supplier of participatesin for definesmovement from isaffectedby defines movementtoisaffected by at stores of storedin countsproductfor arecountedvia currentlyin inventoryat statusof typeof for heldby holderofaffiliated with composed of for locatedat accessedby responsible for responsibilityof responsible for for composedof sub-org ofcomposedof typeof for
  • 57. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 57 Field Service Scheduler This ERD (see Figure 21) illustrates how the Siebel Data Model supports the scheduling of employees to perform service activities within configured service regions. A service region corresponds to one or more ZIP codes or other geographical representation, but can only be associated with a single time zone. The service region defines a number of parameters, time duration maps, cost functions, and rule sets that constrain the scheduling of resources within the region. A given service request or activity is assigned to a service region and then to an employee, based on the employee's working hours and current schedule. Table 21 lists the entities in this ERD and their corresponding tables. Table 21. Field Service Scheduler ERD Entities and Tables Entity Table Address S_ADDR_ORG (Siebel Cross-Industry Applications) S_ADDR_PER (Siebel Industry Applications) Employee S_EMP_PER, S_CONTACT, S_PARTY Employee Exceptional Work Hours S_EMP_EXCPT_HRS Scheduler Cost Function S_SCH_CSTFN Scheduler Cost Function Variable S_SCH_CSTFN_VAR Scheduler Parameter S_SCH_PARAM Scheduler Parameter Set S_SCH_PARAM_SET Scheduler Rule S_SCH_RULE Scheduler Rule Node S_SCH_RULENODE Scheduler Rule Set S_SCH_RLST Scheduler Time Map S_SCH_TMMAP Scheduler Time Map Duration S_SCH_TMMAP_DUR Service Activity S_EVT_ACT Service Region S_SRV_REGN Service Request S_SRV_REQ Timezone S_TIMEZONE Work Shift S_SCHED_CAL Work Shift Exception S_EXCPT_CAL Work Shift Exception Hour S_EXCPT_CAL_HRS Work Shift Hour S_SCHED_CAL_HRS Zipcode S_ZIPCODE
  • 58. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 58 Figure 21. Field Service Scheduler Title : Field Service Scheduler Author : Oracle, Confidential ZIPCODE SERVICE REQUEST SERVICE ACTIVITY ADDRESS SCHEDULER RULE NODE SCHEDULER RULE SCHEDULER 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 COST FUNCTION 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 in for 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
  • 59. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 59 Forecasts This ERD (see 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 can be attributed to different kinds of business transactions, and can be defined at any of a number of levels based on business rules. These forecast items can be generated based on known revenue items. Forecasts that managers make can contain items from the forecasts of their subordinates. Table 22 lists the entities in this ERD and their corresponding tables. Table 22. Forecasts ERD Entities and Tables Entity Table Agreement S_DOC_AGREE Forecast S_FCST Forecast Item Detail S_FCST_ITEM_DTL Forecast Period S_FCSTSER_DATE Forecast Series S_FCSTSER Forecasted Item S_FCST_ITEM Marketing Event S_SRC Opportunity S_OPTY Organization Unit S_ORG_EXT, S_PARTY Person S_CONTACT, S_PARTY Position S_POSTN, S_PARTY Product Line S_PROD_LN Product or Service S_PROD_INT Project S_PROJ Quote S_DOC_QUOTE Revenue Item S_REVN Service Request S_SRV_REQ
  • 60. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 60 Figure 22. Forecasts Title:Forecasts Author:Oracle,Confidential AGGREGATE DIMENSION FORECAST REVENUEITEM FORECASTSERIES FORECASTPERIOD FORECASTEDITEM FORECASTITEMDETAIL OPPORTUNITY POSITION PERSON EMPLOYEE/ AGENT OTHERPERSON QUOTEAGREEMENT SERVICEREQUEST ORGANIZATIONUNIT OTHER ORGANIZATION UNIT INTERNAL ORGANIZATION UNIT PRODUCTLINE PRODUCTOR SERVICE PROJECT MARKETING EVENTOR ACTIVITY definedfor aggregatedby governedby applicableto for attributedto for subjectof generatedfor forecastedvia submittedby submitterof for partnerattributedto definedby authorof for accountattributedto participantof for ownedby ownerof submittedfor periodfor for attributedto for attributedto for attributedto for attributedto for attributedto for attributedto for attributedto forsubjectof areportto managerof validperiodfor subjectof memberoforiginalforecastof memberofsummaryof subordinator'sforecastof manager'sforecastof
  • 61. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 61 High Tech Marketing Development Fund This ERD (see Figure 23) illustrates how Siebel Business Applications support the funding of trade promotions in the high technology industry. Marketing Development Fund (MDF) is a pool of money made available to partners for the organization of marketing activities (campaigns, events, and so on). An MDF can 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 (preapproval) 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 preapproved by the brand owner. Table 23 lists the entities in this ERD and their corresponding tables. Table 23. High Tech Marketing Development Fund ERD Entities and Tables Entity Table Account, Partner, Other Account S_ORG_EXT Claim Item S_SRC_PAYITM Claim, Payment, Other Payment S_SRC_PAYMENT Event Item S_SRC_COST Fund Allocation S_MDF_ALLOC General Fund S_MDF Internal Product or Service S_PROD_INT Market Segment S_MKT_SEG Marketing Development Fund S_MDF Marketing Event or Activity S_SRC MDF Snapshot S_MDF_PERIOD MDF Transaction S_MDF_TXN Partner Event Activity S_SRC Partner Program S_PRTNR_PROG Partner Program Application S_PRTNRPRG_APPL Partner Specific Fund S_MDF Position S_POSTN
  • 62. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 62 Figure 23. High Tech Marketing Development Fund Title:HighTechMarketingDevelopmentFund Author:Oracle,Confidential PARTNER PROGRAM PARTNER PROGRAM APPLICATION POSITION MARKET SEGMENT MDF SNAPSHOT EVENTITEM CLAIMITEM MDFTRANSACTION DEBITCREDIT MARKETINGEVENTOR ACTIVITY OTHERMARKETING EVENTORACTIVITY PARTNEREVENT ACTIVITY PAYMENT CLAIM OTHERPAYMENT ACCOUNT OTHER ACCOUNT PARTNER PRODUCT LINE FUNDALLOCATION MARKETING DEVELOPMENT FUND GENERAL FUND PARTNER SPECIFIC FUND INTERNALPRODUCTOR SERVICE for belongsto . for for belongsto for belongsto for has for subjectofdefinedfor subjectof partof has belongsto has for basisfor of subjectof belongs has . . definedfor subjectof targetof availableto for fundedthroughearnedby earnerofearnedby earnerof forpromotionof subjectof forpromotionof subjectof composedof partof designatedto targetof to has partof . partof madeof ofpromotedvia to recipientof hierarchychildof hierarchyparentof
  • 63. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 63 Invoiceable Charges This ERD (see Figure 24) illustrates how financial transactions, such as charges and credits, are handled. Any charge or credit that could be invoiced is added to this table. This is based on defined consolidation plan rules to consolidate charges and credits into invoice and invoice items. Table 24 lists the entities in this ERD and their corresponding tables. Table 24. Invoiceable Charges ERD Entities and Tables Entity Table Activity S_EVT_ACT Address S_ADDR_ORG (Siebel Cross-Industry Applications) S_ADDR_PER (Siebel Industry Applications) Agreement S_DOC_AGREE Agreement Entitlement S_ENTLMNT Agreement Line Item S_AGREE_ITEM Asset S_ASSET Auction Item S_AUC_ITEM Expense Item S_EXP_ITEM Financial Account S_ASSET Invoiceable Charge S_INVOICE_CHRG Invoice S_INVOICE Invoice Item S_INVOICE_ITEM Invoice Item Reconciliation Entry S_INVC_ITM_DTL Order S_ORDER Order Line Item S_ORDER_ITEM Part Movement S_ACTPART_MVMT, S_ORDPART_MVMT Part Repair S_PART_RPR Party S_PARTY, S_ORG_EXT, S_CONTACT, S_USER, S_BU Payment S_SRC_PAYMENT Payment Term S_PAYMENT_TERM Product or Service S_PROD_INT Project Item S_PROJITEM Project Team Role S_PROJ_RSRC Service Request S_SRV_REQ
  • 64. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 64 Shipment S_SHIPMENT Time Sheet Item S_TMSHT_ITEM Table 24. Invoiceable Charges ERD Entities and Tables Entity Table
  • 65. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 65 Figure 24. Invoiceable Charges Title:InvoiceableCharges Author:Oracle,Confidential FINANCIALACCOUNT PAYMENT INVOICEITEM RECONCILIATIONENTRY INVOICEITEM INVOICEABLE CHARGE INVOICEITEM DETAIL ADDRESS EXPENSEITEM TIMESHEETITEM PROJECT TEAMROLE PROJECT ITEM AUCTIONITEM PARTY OTHER PARTY PERSON ORGANIZATIONUNIT OTHER ORGANIZATION UNIT ACCOUNT INVOICEITEM INVOICE PAYMENTTERM AGREEMENT LINEITEM AGREEMENT SERVICE REQUEST SHIPMENT PRODUCTOR SERVICE PARTREPAIR ORDERLINE ITEM ORDER AGREEMENT ENTITLEMENT ASSET ACTIVITY PARTMOVEMENT ACTIVITY PART MOVEMENT ORDER PART MOVEMENT INVOICEABLECHARGE forchargedvia forsubjectof billedtocontactof billedto primarybillingcontactof madefor fulfilledby partof madeupof for chargedvia for subjectof billedto for for locatedat billedto for for chargedvia for chargedvia basedon for for chargedvia for chargedvia forchargedvia objectfor of of orderedon partof composedof for chargedvia forchargedvia for subjectof invoicedinto for for chargedvia forchargedvia for chargedvia partof composedof for fulfilledby forchargedvia for chargedvia basedonbasisof partof madeupof partof madeupof forchargedvia basedon basisfor for chargedvia forchargedvia partof composedof
  • 66. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 66 Invoices This ERD (see Figure 25) illustrates the invoicing and payment processes. An invoice can be considered a receivable or a payable for the company. It can 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 can be reconciled with one or more other entities as well. A payment can be made for one or more Invoices, and an invoice can be paid through one or more payments. Table 25 lists the entities in this ERD and their corresponding tables. Table 25. Invoices ERD Entities and Tables Entity Table Activity S_EVT_ACT Agreement S_DOC_AGREE Expense S_EXP_ITEM Invoice S_INVOICE Invoice Attachment S_INVOICE_ATT Invoice Item S_INVOICE_ITEM Order S_ORDER Order Item S_ORDER_ITEM Part Movement S_ORDPART_MVMT Part Repair S_PART_RPR Payment S_SRC_PAYMENT Period S_PERIOD Product S_PROD_INT Project S_PROJ Service Request S_SRV_REQ Shipment S_SHIPMENT
  • 67. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 67 Figure 25. Invoices Title:Invoices Author:Oracle,Confidential PROJECT INVOICEATTACHMENT SHIPMENT PERIOD ACTIVITY PARTMOVEMENT SHIPPEDPART EXPENSE UNITOF LABOR INVOICEITEM INVOICE OTHERINVOICEPAYABLEINVOICERECEIVABLEINVOICE PARTREPAIR PAYMENT TERM SERVICEREQUEST AGREEMENT PRODUCT ORDERITEM ORDER PAYMENT generatedfor reasonfor generated for reasonfor for billedvia for billedvia for sourcefor for detailfor forbilledvia partof composed of objectfor for fulfillmentfor fulfilledby generated for reasonfor generated for reasonfor forbilledvia for billedvia for billedvia forbilledvia generated for reasonfor generated for reasonfor forbilledvia forbilledvia madefor fulfilledby of orderedon partof composedof partof composed of forbilledvia for billedvia basedon for generated for reasonfor
  • 68. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 68 Lead Management This ERD (see Figure 26) illustrates how the lead management process is supported. A lead refers to a new prospect or an existing customer who is interested in certain products or services and can be converted into an Opportunity. A lead can be generated as a result of a marketing campaign, a marketing offer or other marketing activities. A lead can be referred by a partner organization. A lead can be assigned to internal team members or partners. Responses or various activities are tracked for each lead. Steps in the lead management process include: ■ Lead Entity. Views for sales users to create leads that are distinct from contacts or prospects, responses and opportunities, and manage their leads. ■ Lead Import. Import lists of customers, prospects, responses or leads from an outside party or another internal system. ■ Lead Quality Control. Rule-based user interface that enables the business user to create a formula or set of rules that compute a score for a lead ■ Lead Assignment. Lead-assignment rule system which can be fully administered by a sales operations user or sales manager. Leads can also be assigned to partner organizations or partner users. ■ Lead Conversion. End-user actions to convert a lead into an opportunity, quote or order in one step, reject the lead or retire the lead. Table 26 lists the entities in this ERD and their corresponding tables. Table 26. Lead Management ERD Entities and Tables Entity Table Lead S_LEAD Lead Note S_NOTE_LEAD Opportunity S_OPTY Product S_PROD_INT Marketing Import Task S_MKT_IMPRT_TSK Lead Source S_SRC Campaign Contact S_CAMP_CON Marketing Offer S_DMND_CRTN_PRG Response S_COMMUNICATION Activity S_EVT_ACT Prospect Contact S_PRSP_CONTACT Contact S_CONTACT Business Unit S_BU
  • 69. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 69 Position S_POSTN Account S_ORG_EXT Internal Organization S_ORG_EXT Partner Organization S_ORG_EXT Assigned External Organization S_ORG_EXT Table 26. Lead Management ERD Entities and Tables Entity Table
  • 70. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 70 Figure 26. Lead Management Title:LeadManagement Author:Oracle,Confidential OPPORTUNITY MARKETING IMPORTTASK LEADNOTE PROSPECT CONTACT LEAD SOURCE DEMAND CREATION PROGRAM RESPONSE ACTIVITY CAMPAIGN CONTACT PRODUCT PARTY ACCOUNT OTHERORGANIZATION PARTNER ASSIGNED EXTERNAL INTERNAL POSITION CONTACT BUSINESS UNIT LEAD referred by refers involved in involverof belongs to owns assigned to reponsible for belongs to owns under responsible for for creates for creates generated for subjectof generated from turns into for primaryfor for primaryfor generated by generates generated from generates discovered from source for generated for subject of imports created via consideration of considered on attached to subject of
  • 71. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 71 Marketing Budget Request This ERD (see Figure 27) covers the Marketing Resource Management: budget request process. It illustrates the relationships between budget requests and marketing tactics, marketing funds, and purchase orders. A budget request can be managed by a team and defined against a dedicated marketing fund for a period and a region. It can be associated with one or more industries, products, and product lines. Table 27 lists the entities in this ERD and their corresponding tables. Table 27. Marketing Budget Request ERD Entities and Table Entity Table Budget Request S_MKTG_BDGT_REQ Purchase Request S_ORDER Marketing Development Fund S_MDF Marketing Plan S_SRC Marketing Fund S_MDF Marketing Tactics S_SRC Tactics Expense S_SRC_COST Purchase Request Line Item S_ORDER_ITEM
  • 72. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 72 Figure 27. Marketing Budget Request 7LWOH0DUNHWLQJ%XGJHW5HTXHVW $XWKRUOracleRQILGHQWLDO 3(5,2' 5(*,21 7$7,6(;3(16( 385+$6( 5(48(67/,1( ,7(0 ,1'8675 352'87/,1(352'87326,7,21 0$5.(7,1*7$7,6 385+$6(5(48(67 0$5.(7,1*3/$1 ,192,( %86,1(6681,7 0$5.(7,1* )81' 0$5.(7,1*'(9(/230(17)81' %8'*(75(48(67 EHORQJWR JRYHUQ EHORQJWR JRYHUQ EHORQJWR JRYHUQ EHORQJWR JUDQWHGDFFHVVWR EHORQJWR JUDQWHGDFFHVVWR WDUJHWHGDW VXEMHFWRI WDUJHWHGDW VXEMHFWRI WDUJHWHG DW VXEMHFWRI PDQDJHG E RSHUDWH VXEMHFWRI PDGHIRU LQFOXGHGLQ VXEMHFWRI IRU VXEMHFWRI IXQGHGE IRU IRU VXEMHFWRI VXEMHFWRI IRU IXQGHGE IRU VXSSRUWV VXEMHFWRI SDUWRI FRQVLVWRI ILQDQFHGE IRU RULJLQDORI FRQVROLGDWLRQRI IRU XVH
  • 73. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 73 Marketing Campaign This ERD (see Figure 28) illustrates campaign management, execution, and evolution. Campaign management can 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 can 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 can 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, the contact is typically deleted from the database. Table 28 lists the entities in this ERD and their corresponding tables. Table 28. Marketing Campaign ERD Entities and Tables Entity Table Activity S_EVT_ACT Call List S_CALL_LST 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 Literature Item S_LIT Marketing Event S_SRC Opportunity S_OPTY Opportunity Contact S_OPTY_CON Order S_ORDER Organization Unit S_ORG_EXT, S_PARTY Person S_CONTACT, S_PARTY Position S_POSTN, S_PARTY Prospective Contact S_PRSP_CONTACT Response S_COMMUNICATION Territory S_ASGN_GRP
  • 74. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 74 Figure 28. Marketing Campaign Title:MarketingCampaign Author:Oracle,Confidential RESPONSE ORDER MARKETINGEVENTORACTIVITY OTHER MARKETING EVENTOR ACTIVITY MARKETINGCAMPAIGN FULFILLMENT RECIPIENT FULFILLMENT REQUESTITEM LITERATURE ITEM FULFILLMENT REQUEST CALLLIST MEMBER ACTIVITY CAMPAIGNCONTACT OPPORTUNITYCONTACT OPPORTUNITY CAMPAIGN TEAMMEMBER CALLLIST MARKETING SEGMENT PURCHASED LIST PERSON OTHERPERSON PROSPECTIVECONTACT TERRITORY POSITION ORGANIZATIONUNIT NOTE CAMPAIGNCALLLIST generatedby originatorof generatedbyoriginatorof generatedbyoriginatorof partof made for userofresponsibilityof responsiblefor associatedwith introductionto for targetedat relevantto promotedvia partof subjectof partof conductedas initiatorof initiatedby for subjectof addressedto recipientof of subjectof partof madeup of of for of subjectof of subjectof of subject of for targetedat assignedto roleplayedby managedwithin focusof assignedto assignedtosellin assignedto assignedto for composedof partof madeupof areportto aparent to of subject of of usedin inmadeupof primarilyfrom sourceof of subject of
  • 75. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 75 Marketing Collaboration Collaborative marketing (see Figure 29) assists marketers in maintaining the balance between the need for consistent customer management among partners and effective brand building with local expertise. It consists of two features. Marketing program collaboration allows companies to develop marketing programs in a more collaborative environment, resulting in reduced costs. It encourages collaboration on programs through the sharing of information with key action groups (internal and external). Partner marketing enhancements provides the ability to associate and track partner participation in marketing programs and campaigns to measure and report on opportunities, orders, and ROI. It also closes the loop by providing the ability to track partner sources for responses and opportunities orders. Table 29 lists the entities in this ERD and their corresponding tables. Table 29. Marketing Collaboration ERD Entities and Tables Entity Table Internal Partner/Organization S_ORG_EXT, S_PARTY Marketing Event or Activity S_SRC 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
  • 76. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 76 Figure 29. 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 item of collaboration for collaborating on item of collaboration for collaborating on item of collaboration for collaborating on responsibility of responsible for responsibility of responsible for responsibility of responsible for responsibility of responsible for item of collaboration for collaborating onresponsibility of responsible for
  • 77. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 77 Marketing Encyclopedia This ERD (see Figure 30) illustrates how Siebel Business Applications track competitive information about products and companies. A standard set of metrics can 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 can be associated both with organizations and with products. The relevance of key decision issues to the various competitive metrics can be defined. Table 30 lists the entities in this ERD and their corresponding tables. Table 30. 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 Literature Item S_LIT Organization Unit S_ORG_EXT, S_PARTY Product Comparison S_PROD_CMP Product Detail S_PROD_SPEC Product External S_PROD_EXT Product Internal S_PROD_INT Product Literature S_PROD_LIT
  • 78. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 78 Figure 30. Marketing Encyclopedia Title:MarketingEncyclopedia Author:Oracle,Confidential COMPANY LITERATURE PRODUCT LITERATURE PRODUCT DETAIL COMPETITIVE COMPANY FEATURE COMPETITIVE PRODUCT FEATURE COMPETITIVEMETRIC COMPETITIVEPRODUCTMETRICCOMPETITIVECOMPANYMETRIC ORGANIZATIONUNIT INTERNAL/PARTNER ORGANIZATIONUNIT EXTERNALORGANIZATIONUNIT LITERATUREITEM DECISION ISSUE PRODUCTORSERVICE EXTERNAL PRODUCT INTERNALPRODUCT ORSERVICE PRODUCTCOMPARISON about subjectof usageof referenceto about subjectof usageof referenceto for subjectof of classificationfor relevantto subjectof of classificationfor for subjectof of characterizedby producedby vendorof of competitorof to competitorof
  • 79. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 79 Marketing Event Driven Dialogue The Event Driven Dialogue feature enables timely sales and services to be designed around specific customer needs. Specific events are tracked for different customers and these events are used to trigger appropriate program stages for the marketing program. This ERD (see Figure 31) illustrates the various relationships between Marketing Program, Stage, and Event Triggers. The wait period between stages is also tracked. Table 31 lists the entities in this ERD and their corresponding tables. Table 31. Marketing Event Drive Dialogue ERD Entities and Tables Entity Table Action List S_MKTPRGACT_LST Call List S_CALL_LST Campaign Contact S_CAMP_CON Event Trigger S_MKT_EVT_TRG Event Trigger History S_MKTEVTRG_HST Event Trigger Mapping S_MKTEVTRG_MAP Lead Source S_SRC Marketing Campaign S_SRC Marketing Event or Activity S_SRC Marketing Program S_SRC Marketing Program Action S_SRC Marketing Stage S_SRC Marketing Stage Wait S_MKT_STGWAIT, S_MKT_STGWT_REL Offer S_DMND_CRTN_PRG Party S_PARTY Person S_CONTACT Position S_POSTN Response S_COMMUNICATION
  • 80. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 80 Figure 31. Marketing Event Driven Dialogue Title:MarketingEvent-DrivenDialogue Author:Oracle,Confidential RESPONSE OFFER CALLLIST CAMPAIGNCONTACT PARTY PERSON OTHERPERSON PROSPECT CONTACT POSITION LEADSOURCE MARKETINGSTAGE MARKETINGPROGRAM MARKETING EVENTOR ACTIVITY MARKETING CAMPAIGN EVENTTRIGGERHISTORY EVENT TRIGGER MAPPING EVENT TRIGGER MARKETING STAGEWAIT ACTIONLIST MARKETING PROGRAMACTION createdfor sourceof promoted vehicle for associatedwith for associated with for subjectof for subjectof belongsto subjectof belongsto subjectof belongsto subjectof of subjectof attached of targetof for from of of subjectof madeup subjectof for subjectof for relatedby partof consistsof
  • 81. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 81 Marketing Events This ERD (see Figure 32) illustrates how Siebel Business Applications support marketing events and activities planning. A marketing event can 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 can 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 can then register for the event or even for specific sessions. Attendees can be quoted registration prices through a quote and purchase tickets to the event through an order. Table 32 lists the entities in this ERD and their corresponding tables. Table 32. 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 Literature Item S_LIT Location Room S_EVTLOC_ROOM Marketing Event or Activity S_SRC Order S_ORDER Organization Unit S_ORG_EXT, S_PARTY Parent Event S_SRC_EVT, S_SRC Position S_POSTN, S_PARTY Price List S_PRI_LST Product or Service S_PROD_INT Quote S_DOC_QUOTE Room Avail Equipment S_EVTLOC_RM_EQP Travel Participant S_EVT_TRVL_PER
  • 82. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 82 Travel Plan S_EVT_TRVL_PLAN Vendor Offer S_EVT_VNDR_OFR Vendor Review S_EVT_VNDR_RVW Vendor Service S_EVT_VNDR_SVC Venue S_ORG_EXT, S_PARTY Venue Offer S_EVT_VENUE_OFR Venue Review S_EVT_VENUE_RVW Venue Service S_EVT_VENUE_SVC Table 32. Marketing Events ERD Entities and Tables Entity Table
  • 83. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 83 Figure 32. Marketing Events Title:MarketingEvent Author:Oracle,Confidential PRICE LIST ORGANIZATION UNIT EVENTLOCATION OTHERLOCVENUE EVENTCOST TRAVEL PARTICIPANT TRAVELPLAN VENUE SERVICE PRODUCTORSERVICE EVENTPRODUCTOTHERPRODUCTOR SERVICE EVENTVENDOR POSITION CONTRACT ORDER OTHER CONTRACT QUOTE CONTRACTLINEITEM PERSON EVENT REGISTRATION ATTENDEE WAITLIST CANCELLED REGISTRANT LITERATURE ITEM EQUIPMENT REQUIREMENT ACTIVITY LOCATIONROOM VENDOR REVIEW VENDOR OFFER VENDOR SERVICE EVENTVENUE VENUE OFFER VENUE REVIEW ROOMEQUIPMENT AVAILABILITY MARKETINGEVENTORACTIVITY EVENTPARENT EVENT OTHERMARKETING EVENTORACTIVITY EVENT SESSION uses auction pricelist for belongto parentcompanyof usedby use for composedof in supplierof of for incurredby incur incurredby incur incur associatedwith amemberof classifiedasparticipate have servicedby service createdfor have offeredby providerof staffedbyonstafffor inviterofinvitedto for composedof for subjectof offeredby providerof offeredby providerof for subjectof reviewedbyreviewerof requiredby inneedof for subjectofsubjectof for recipientof orderedby for subjectof for subjectof availablein equippedwith relevantto promotedvia responsiblefor responsibilityof for subjectof heldat locationof for composedof reviewedbyreviewerof offeredat subjectof locationof heldat for subjectof
  • 84. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 84 Marketing Plans This ERD (see Figure 33) 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 33 lists the entities in this ERD and their corresponding tables. Table 33. Marketing Plans ERD Entities and Tables Entity Table Call List S_CALL_LST Marketing Development Fund S_MDF 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
  • 85. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 85 Figure 33. Marketing Plans Title:MarketingPlans Author:Oracle,Confidential BUDGET REQUEST INVOICEITEM INVOICE PERIOD CAMPAIGN CALLLIST CALLLIST PRODUCTORSERVICE PRODUCT PROMOTION MARKETING GOAL MARKETING EVENTCOST MARKETINGEVENT ORACTIVITY MARKETING PLAN OTHER MARKETING EVENTOR ACTIVITY PLANNED MARKETING DEVELOPMENT FUNDALLOC MARKETING DEVELOPMENT FUND for uses FOR SUBJECTOF basisof basedon partof madeupof belongto composeof launchedin definedforlaunchof validin definedfor validin definedforthebudgetof validin definedfor definedfor has attributedto has usedfor userof typeof ownerfor createdforpromotionitemfor createdfrom sourceofcreatedfor requirerof createdfrom sourceof estimatedfor consistsof attributedto incur reservedfrom sourceof
  • 86. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 86 Marketing Program This ERD (see Figure 34) illustrates how Siebel Business Applications support the more complex program planning and execution used for Database Marketing. Marketing segments are dynamic lists of people defined by a set of database criteria and available to marketing programs. These criteria can be defined on measures and attributes based on complex mathematical scores, ratios, and formulas applied to customer demographics or behavior data sourced from the Siebel database or from external applications such as a data warehouse. After a data dictionary describing the external data store has been defined, segment definitions can be created and attached to one or more campaigns, together with purchased lists. Filters allow the exclusion of segment members based on predefined clauses. Segment prioritization and deduplication make sure that individuals qualified for more than one segment do not receive conflicting messages from more than one campaign. Waves can be generated as a subset of the qualifying people within the targeted segments. Recurring marketing programs can be defined in which each stage can be based on customer response behavior or any other event. Marketers can define customer hierarchies, so that campaigns can be driven by data summarized from any level of the hierarchy (for example household level and customer level). People to be contacted are listed as campaign contacts for a specific campaign or wave. Each campaign can be presented with one or more offers. An offer is a type of demand creation program that is directly presented to a target audience. It is intended to generate awareness of or demand for one or more products. Responses are tracked through Communications. Table 34 lists the entities in this ERD and their corresponding tables. Table 34. Marketing Program ERD Entities and Tables Entity Table Assignment Rule Group S_ASGN_RULE_GRP Call List S_CALL_LST Campaign Allocation S_CAMP_CALL_LST Campaign Contact S_CAMP_CON Campaign Load S_CAMP_LD_WAVE Campaign Offer S_SRC_OFFR Campaign Wave S_DD_CAMP_WAVE Contact S_CONTACT, S_PARTY Contact Status S_ SRCDCP_CONSTA Deal S_DEAL Filter S_DD_FILTER Filter Clause S_DD_FILTER_DTL Load Wave S_CAMP_LD_WAVE
  • 87. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 87 Marketing Activity S_SRC Marketing Segment S_CALL_LST Offer S_MKTG_OFFR Offer Media Package S_DMND_CRTN_PKG Program Segment S_CAMP_CALL_LST Prospective Contact S_PRSP_CONTACT Purchased List S_CALL_LST Response S_COMMUNICATION Table 34. Marketing Program ERD Entities and Tables Entity Table
  • 88. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 88 Figure 34. Marketing Program 7LWOH0DUNHWLQJ3URJUDP $XWKRUOracleRQILGHQWLDO %86,1(6681,7 352'87256(59,( 2))(50(',$3$.$*( $03$,*1/,67 ',675,%87,21 *2$/ /2$':$9( 6285(2'( )250$7 6285(2'( (/(0(17 3$57 25*$1,=$7,21 81,7 3(5621 35263(7,9( 217$7 27+(5 3(5621 326,7,21 $03$,*1/2$' $///,67 6(*0(17 385+$6(' /,67 $03$,*12))(52))(5 $03$,*1217$7 352*5$0 6(*0(17 /($'6285( 0$5.(7,1* (9(17 0$5.(7,1*$03$,*1 0$5.(7,1* 67$*( 0$5.(7,1* 352*5$0 0$5.(7,1* 3/$1 $03$,*1 :$9( WDUJHWDW SURPRWHG EHORQJWR RZQ IRU GHOLYHUHG JHQHUDWHG UHOHYDQW SURPRWHGYLD SURPRWLRQYHKLFOHIRU SDUWRI PDGHXSRI SDUWRI LQFOXGH SDUWRI PDGHXSRI IRU SULPDURIIHU UHIHUUHGELQWURGXFH IRU WDUJHWDW SURPRWLRQYHKLFOHIRU SURPRWHGYLD EHORQJWR VXEMHFWRI EHORQJWR VXEMHFWRI LQVWDQFH WHPSODWH SDUWRI FRQVLVWRI SDUWRI FRQVLVWRI LQ IRU LQFOXGH SDUWRI LQVWDQFHRI WHPSODWHIRU LQVWDQFHRI VXEMHFWRI WDUJHWRI VXEMHFWRI SDUWRI SURPRWLRQRI GHILQHGIRU VXEMHFWRI GHILQHGIRU VXEMHFWRI WDUJHWRI IRU VXEMHFWRI PDGHXSRI RI VXEMHFWRIIURP RI RI WDUJHWRI
  • 89. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 89 Marketing Resource Management: Document This ERD (see Figure 35) illustrates the marketing content processing of the enhanced Marketing Resource Management module. It shows the relationship between the content and various entities such as project, offer media package, and lead source. It also illustrates the process of managing content inventory by region and location, and shows how fulfillment requests are completed through vendor bidding. Table 35 lists the entities in this ERD and their corresponding tables. Table 35. Marketing Resource Management: Document ERD Entities and Tables Entity Table Marketing Material S_CB_ASSET Material Inventory by Location S_MKTG_DOC_INVT Event Location S_EVTLOC Region S_REGION Material Fulfillment Request S_EVT_FUL_REQ Material Fulfillment Item S_FUL_REQ_ITEM Mat Fulfill Request Attachment S_NOTE_FUL_REQ Vendor Bidding S_FUL_REQ_BID Vendor Bidding Item S_FR_BID_LITM External Organization S_ORG_EXT Offer Media Package S_DMND_CRTN_PRG Offer Document S_OFFR_CBAST Lead Source S_SRC Lead Source Document S_SRC_CBAST Project S_PROJ Project Document S_PROJ_CBAST
  • 90. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 90 Figure 35. Marketing Resource Management: Document 7LWOH050'RFXPHQW0DQDJHPHQW $XWKRUOracleRQILGHQWLDO 352-(7 '280(17 /($'6285('280(17 2))(5 '280(17 0$7)8/),// 5(48(67 $77$+0(17 (;7(51$/ 25*$1,=$7,21 2))(5$03$,*1 /($'6285( 2))(50(',$ 3$.$*(352-(7 9(1'25%,'',1*,7(0 9(1'25%,'',1* 5(*,21 0$7(5,$/,19(1725%/2$7,21 (9(17 /2$7,21 0$7(5,$/ )8/),//0(17,7(0 0$5.(7,1*0$7(5,$/ 0$7(5,$/)8/)IL/0(175(48(67 VXSSOLHG YLD SURGXFH IRU GRFXPHQWHGYLD FRQWDLQV XVHGLQ IRU GRFXPHQWHG YLD FRQWDLQV XVHGLQ IRU GRFXPHQWHG YLD FRQWDLQV XVHGLQ VXSSRUW LOOXVWUDWHGYLD IRU IXOILOOHG E VXEMHFWRI IRUSDUWRI PDGHXSRI PDGHE VXEPLW FRSRI VXEMHFWRI SDUWRI FRQVLVWRI SKVLFDOO VWRUH GLVWULEXWHGWR LQ IRU EHORQJWR JRYHUQ FRQWDLQV LVSDUWRILVRIIHUHGWR LVRIIHUHG SDUWRI SDUHQWRI IRU ZLWKLQ SULPDULO ORFDWHGLQ IRU
  • 91. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 91 Opportunity Management This ERD (see Figure 36) illustrates the significant entities related to an opportunity (or lead), including relationships to contacts, employees (generally sales representatives), products, accounts, and so on. Table 36 lists the entities in this ERD and their corresponding tables. Table 36. Opportunity Management ERD Entities and Tables Entity Table Address S_ADDR_ORG (Siebel Cross-Industry Applications) S_ADDR_PER (Siebel Industry Applications) Agreement S_DOC_AGREE Contact S_CONTACT, S_PARTY Employee S_EMP_PER, S_CONTACT, S_PARTY Event S_EVT_ACT External Organization Unit S_ORG_EXT, S_PARTY Issue S_ISS Opportunity S_OPTY Opportunity Relationship S_OPTY_REL Organization Unit S_ORG_EXT, S_PARTY Person S_CONTACT, S_PARTY Product S_PROD_INT Quote S_DOC_QUOTE Sales Stage S_STG Source S_SRC Territory S_ASGN_GRP
  • 92. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 92 Figure 36. Opportunity Management Title:OpportunityManagement Author:Oracle,Confidential OPPORTUNITYISSUE EVENTACTIVITY SALESDOCUMENT CORRESPONDENCEQUOTEAGREEMENT SALES METHODOLOGY ISSUE MARKETINGEVENTOR ACTIVITY ORGANIZATIONUNIT INTERNAL/PARTNER ORGANIZATIONUNIT OTHERORGANIZATIONUNIT PERSON OTHER PERSON EMPLOYEE/ AGENT PRODUCTOR SERVICE PRODUCT STRUCTURE SALES STAGETERRITORY OPPORTUNITY ADDRESS OPPORTUNITY RELATIONSHIP subjectof relevanttorelevanceof relevantas ownedby resourcefor targetedat subjectof performedby performerof ownedby responsiblefor for sourceof for locatedat for composedof of collectionof for partof on involverof within subjectto considerationon subjectto consideredon considerationof producedby vendorof for acollectionof of acomponentof composedof affiliatedwith classificationof classifiedin driverof drivenby initiatorof initiatedby involvedon nvolverof for locatedat basedon basisfor areporttoaparentto partof madeupof madeupof partof areportto managerof inpartnershipwithapartnerto
  • 93. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 93 Order and Promotion This ERD (see Figure 37) describes the relationship between Product Promotions and Order, Quote and Assets. Table 37 lists the entities in this ERD and their corresponding tables. Table 37. Order and Promotion ERD Entities and Tables Entity Table Asset S_ASSET Order Item S_ORDER_ITEM Product Promotion S_PROD_INT Product Promotion Item S_PROM_ITEM Product Promotion Operation S_PROM_OPER Quote Item S_QUOTE_ITEM
  • 94. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 94 Figure 37. Order and Promotion Title : Order and Promotion Author : Oracle, Confidential QUOTE ITEM ORDER ITEM ASSET PRODUCT PROMOTION OPERATION PRODUCT PROMOTION ITEM PRODUCT PRODUCT PROMOTION uses used by uses used by for has for associated to for associated to for has has associated to has for defined for has made up contain
  • 95. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 95 Order Life Cycle This ERD (see Figure 38) 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 can 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 38 lists the entities in this ERD and their corresponding tables. Table 38. Order Life Cycle ERD Entities and Tables Entity Table Account S_ORG_EXT, S_PARTY Invoice S_INVOICE Invoice Item S_INVOICE_ITEM Opportunity S_OPTY Opportunity Product S_REVN Order S_ORDER Order Item S_ORDER_ITEM Order Part Movement S_ORDPART_MVMT Product or Service S_PROD_INT Quote S_DOC_QUOTE Quote Item S_QUOTE_ITEM Shipment S_SHIPMENT
  • 96. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 96 Figure 38. Order Life Cycle Title:OrderLifeCycle Author:Oracle,Confidential ACCOUNT PRODUCTORSERVICE INVOICEITEM INVOICE QUOTE OPPORTUNITY PRODUCT SHIPMENT ORDERPARTMOVEMENT SHIP MVMT ALLOCATION OTHERPART MOVEMENT RECEIPT MVMT ORDERITEMQUOTEITEM ORDEROPPORTUNITY baseitemfor has has originalitemfor has originalitemfor has baseitemfor has backuporderfor has originalorderfor generatedfor reasonfor for billedvia takenfor targetof preparedfor receiveroftargetof of partof composedof for considerationofpurchaseof for composedof of quotedforpurchaseon of consideredforpurchaseon of deliveredby for billedvia of orderedon for billedvia for billedvia composedof for for billedvia from subjectof for leadto leadto for createdfrom leadto for leadto partof composedof precededbyfollowedby asteptowardthe fulfillmentof fulfilledby on vehicleforfulfillmentof partofmadeupof partof composedof partof composedof
  • 97. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 97 Orders This ERD (see Figure 39) 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 can be assigned or credited to one or more positions. Table 39 lists the entities in this ERD and their corresponding tables. Table 39. Orders ERD Entities and Tables Entity Table Activity S_EVT_ACT Asset S_ASSET Inventory Location S_INVLOC Inventory Transaction S_INV_TXN Inventory Transaction Type S_INV_TXN_TYPE Order S_ORDER Order Item S_ORDER_ITEM 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
  • 98. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 98 Figure 39. Orders Title:Orders Author:Oracle,Confidential ASSET PRODUCT INVENTORY TRANSACTION TYPE PARTY ORGANIZATIONUNIT OTHERORGANIZATION INTERNAL/PARTNERORGANIZATION POSITION PERSON OTHER PARTY INVENTORY TRANSACTION PARTMOVEMENT ORDERPARTMOVEMENT OTHERPART MOVEMENT ACTIVITYPART MOVEMENT ACTIVITY INVENTORYLOCATION ORDERITEM PART MOVEMENT TYPE ORDERTYPE ORDER SERVICEORDER SALESORDER PURCHASEORDER RMA OTHERORDER for primarycontactfor for customerof resultof causeof of subjectto of movedon for subjectof for subjectof aninstanceof madeinto to destinationof from sourceof to destinationof of for responsibilityof responsiblefor responsibilityof responsiblefor procededbyfollowedby partofcomposedof of for for subjectof of for relatedto relatedto from sourceof for fulfilledby partof composedof partof composedof
  • 99. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 99 Partner Collaboration Partner collaboration (see Figure 40) 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 might want to add the resource to a project or an opportunity. Table 40 lists the entities in this ERD and their corresponding tables. Table 40. 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
  • 100. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 100 Figure 40. Partner Collaboration 7LWOH3DUWQHUROODERUDWLRQ $XWKRUOracle,RQILGHQWLDO %86,1(6675$16$7,217($00(0%(5 %86,1(6675$165(63216,%/( 25*$1,=$7,21 %86,1(6675$165(63216,%/( 326,7,21 %86,1(6675$16$7,21 0(66$*( 27+(50(66$*( 2//$%25$7,21,19,7$7,21 3$57 27+(53$57 326,7,21 25*$1,=$7,2181,7 27+(525*$1,=$7,O1 81,7 ,17(51$/3$571(5 25*$1,=$7,21 2//$%25$7,21 2//$%25$7,216+$5('5(6285( 6+$5('25*$1,=$7,21)252//$%25$7,21 6+$5('326,7,21)252//$%25$7,21 SODHGE SODHURI SODHGE SODHURI UHVSRQVLEOHIRUDVVLJQHGWR FRPSRVHGRI PHPEHURI IRU VXEMHFWRI IRU UHFLSLHQWRI VHQWE VHQGHURI IRU SOHGJHGDV IRU SOHGJHGDV IRU VRXUFHRI
  • 101. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 101 Partner Program Registration Partner Program Registration (see Figure 41) 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 41 lists the entities in this ERD and their corresponding tables. Table 41. 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
  • 102. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 102 Figure 41. Partner Program Registration 7LWOH3DUWQHU3URJUDP$SSOLFDWLRQ $XWKRUOracle,RQILGHQWLDO $33/,$7,21 $77$+0(17 0$5.(7 6(*0(17 352'87/,1( %86,1(6681,7 352*5$07($0 /,7(5$785(,7(0 5(1(:/,67 $33529$//,67 (/,*,%,/,7/,67 /$1*8$*( $7$/2* $7(*25 ,7(0 $7$/2* $7(*25 $7$/2* $// 65,37581 $//65,373$7+ 326,7,21 3$571(5352*5$0$33/,$7,21 $33/,$7,21 48(67,21 $16:(5 $33/,$7,21 $33529$/7($0 3$571(5352*5$0 *5283 3$571(5352*5$0 %$6(352*5$0 $''(1'$352*5$0 3$571(5 3$571(5352*5$00(0%(56+,3 IRU VXSSRUWHG YLD EHORQJ WR RZQ IRU WDUJHWDW IRU WDUJHWDW IRU VXEMHFWRI IRU VXEMHFWRI LQLWLDOUXQRI IRU EHORQJ WR RZQ IRU VXEMHFWRI FRQVLVWRI RQ FRQVLVWRI RQ IRU VXEMHFWRI FRQVLVWRI RQ IRU VXEMHFWRI IRU LQWKH FKDUJH RI PDGHXSRI DVVLJQHGWR UHODWH DVVRFLDWHG ZLWK SDUWRI PDGH XSRI DSSOIRU VXEPLWWHGE IRU SURFHVVHG YLD IRU UHQHZDOUXQRI DFFHVVHd FKDQQHO IRU DFFHVVHGDV DFFHVVHG WKURXJK DFFHVV FRQWUROIRU IRU KDV PDGH XSRI LQ DVVLJQHGWR DSSURYHG E IRU VXEMHFWRI LQ IRU IRU VXEMHFWRI FRQVLVWRI PHPEHURI
  • 103. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 103 Party Model This ERD (see Figure 42) 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 can be an employee or agent of the company using Siebel Business Applications. A person can 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 can be tracked for a person, a household, or an organization. Table 42 lists the entities in this ERD and their corresponding tables. Table 42. Party Model ERD Entities and Tables Entity Table Access Group S_PARTY Account S_ORG_EXT, S_PARTY Business Address S_ADDR_ORG (Siebel Cross-Industry Applications) S_ADDR_PER (Siebel Industry Applications) Employee/Agent S_EMP_PER, S_CONTACT, S_PARTY Group S_PARTY Household S_ORG_GROUP, S_PARTY Organization Relationship S_ORG_REL (Siebel Cross-Industry Applications) S_PARTY_REL (Siebel Industry Applications) Organization Unit S_ORG_EXT, S_PARTY Party S_PARTY Party Relationship S_PARTY_REL Person S_CONTACT, S_PARTY Person Relationship S_PARTY_REL or S_CONTACT_REL Personal Address S_ADDR_PER Position S_POSTN, S_PARTY User List S_PARTY User Login S_USER
  • 104. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 104 Figure 42. Party Model 7LWOH 3DUW 0RGHO $XWKRU Oracle RQILGHQWLDO $''5(66 %86,1(66 $''5(663(5621$/ $''5(66 3$57 5(/$7,216+,3 3(5621 5(/$7,216+,3 27+(5 5(/$7,216+,3 25*$1,=$7,21 5(/$7,216+,3 3$57 *5283 +286(+2/' 326,7,21 86(5 /,67 25*$1,=$7,21 81,7 $2817 27+(5 25*$1,=$7,21 81,7 27+(5 *5283 $(66 *5283 27+(5 3$57 86(5 /2*,1 3(5621 (03/2(( $*(17 27+(5 3(5621 GHILQHG PDGH XS PHPEHU RI FRPSRVHG RI PDGH XS RI PHPEHU RI UHSRUW WR PDQDJHU RI FKLOG RI SDUHQW RI FKLOG RI SDUHQW RI IRU ORFDWHG DW IRU ORFDWHG DW IRU ORFDWHG DW IRU ORFDWHG DW ZLWK LQ RI LQ JUDQWHG WR DVVLJQHG
  • 105. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 105 Payments This ERD (see Figure 43) 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 can be made to directly settle an order or to settle one or more Invoices. An invoice can be paid through one or more payments. A payment can be taken as a deduction from a prepayment balance available to the paying party. Table 43 lists the entities in this ERD and their corresponding tables. Table 43. Payments ERD Entities and Tables Entity Table Address S_ADDR_ORG (Siebel Cross-Industry Applications) S_ADDR_PER (Siebel Industry Applications) Invoice S_INVOICE Order S_ORDER Organization Unit S_ORG_EXT, S_PARTY Party S_PARTY Payment S_SRC_PAYMENT Person S_CONTACT, S_PARTY Prepayment Balance S_PREPAY_BAL
  • 106. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 106 Figure 43. Payments Title : Payments Author :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
  • 107. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 107 Performance Review This ERD (see Figure 44) 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 can 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 can 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 can 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 44 lists the entities in this ERD and their corresponding tables. Table 44. 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 Employee/Agent S_EMP_PER, S_CONTACT, S_PARTY Evaluation Script S_CS_PATH, S_CS_PATH_SCPT Evaluation Script Answer S_CS_RUN, S_CS_RUN_ANSWR Job Family S_JOB_FAMILY Organization Unit S_ORG_EXT, S_PARTY Party S_PARTY Performance Measurement Item S_PERF_MEAS_ITM Performance Review S_EMP_PERF_MEAS Period S_PERIOD Person S_CONTACT, S_PARTY Position S_POSTN, S_PARTY Review Component S_PERF_RVW_CMP Review Component Language S_RVW_COMP_LANG Review For Skill Item S_PERF_CMPTNCY
  • 108. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 108 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 44. Performance Review ERD Entities and Tables Entity Table
  • 109. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 109 Figure 44. Performance Review 7LWOH3HUIRUPDQFH5HYLHZ $XWKRUOracleRQILGHQWLDO (03/2(( 5,7(5,$ 3'4
  • 110. (9$/8$7,2165,37 $16:(5 (9$/8$7,2165,37 (9$/8$7,21 5(9,(: 20321(17 /$1*8$*( -2%)$0,/ 5(9,(:5$7,1* 6$/(20321(17 73( 3(5,2'73( 5(9,(:7(03/$7( 3(5,2',5(9,(: $118$/5(9,(:0%227+(55(9,(:73( (03/2((3(5)250$1( 0($685(0(17 27+(5(03/2(( 3(5)250$1( 0($685(0(17 (03/2(( 3(5)250$1(5(9,(: (03/2((86720(5 6$7,6)$7,21625( 5(9,(:20321(17 5(9,(:0(75, 3(5,2' 3(5)250$1(0($685(0(17,7(0 3(5)250$1( 2%-(7,9( 3(5)250$1( 5(9,(:0(75, 5(9,(:)256.,//,7(0 5(9,(: 5$7,1* 3$57 326,7,21 25*$1,=$7,2181,7 %86,1(6681,727+(525*$1,=$7,21 ,17(51$/3$571(5 25*$1,=$7,21 3(5621 (03/2(($*(17 27+(53(5621 5(9,(:7(03/$7(20321(17 203(7(1 DSSOLFDEOHWRHPSORHHVGHILQHGE XVHGIRU HYDOXDWHGE HYDOXDWRU IRU DQVZHUIRU HYDOXDWHGLQ XVHURI TXHVWLRQVIRU IRU WSHRI IRU WSHRI EDVHGRQ EDVLVIRU EDVHGRQ EDVLVIRU UHYLHZIRU VXEMHFWRI WUDQVODWHGYDOXH KDV VSHFLILFWRSHUIRUPDQFH VXEMHFW DSSOLFDEOH KDV DSSOLFDEOHWR KDV KDV GHIDXOWVFDOHVHWIRU SDUWRI FRPSRVHG RI DSSURYHG DSSURYHU RI IRU GHILQHG IRU GHILQHG KDV GHILQHG PDGHXS DSSOLFDEOH VXEMHFW PHDVXUHPHQWRI VXEMHFWRI VFRUHG VFRUHIRU VFRUHG VFRUHIRU HPSORHGE HPSORHURI GHILQHGIRU KDV REMHFWLYHIRU VXEMHFWRI IRU PDGHXSRI RI XVHGLQ KDV VFDOHVHWIRU KROGHURI KHOGE IRU FRPSRVHGRI EDVHGRQ WHPSODWHIRU
  • 111. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 110 Personal Account This ERD (see Figure 45) 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 45 lists the entities in this ERD and their corresponding tables. Table 45. Personal Account ERD Entities and Tables Entity Table Account S_ORG_EXT, S_PARTY Activity S_EVT_ACT Contact S_CONTACT, S_PARTY Opportunity S_OPTY Organization Unit S_ORG_EXT, S_PARTY Personal Account S_ASSET Personal Account Contact S_ASSET_CON Personal Address S_ADDR_PER Product S_PROD_INT Service Request S_SRV_REQ
  • 112. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 111 Figure 45. Personal Account Title : Personal Account Author : Oracle, Confidential CONTACT SERVICE REQUEST ACTIVITY 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 of defined for subject of of subject of by user of
  • 113. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 112 Personal Financial Review This ERD (see Figure 46) 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 can be located at a personal address and can be a source of income. Similarly, a liability, such as a mortgage, can be secured by an associated asset and can have periodic expenses associated with the liability. Table 46 lists the entities in this ERD and their corresponding tables. Table 46. 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 S_CONTACT, S_PARTY 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 Organization Unit S_ORG_EXT, S_PARTY 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
  • 114. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 113 Figure 46. Personal Financial Review Title:PersonalFinancialReview Author:Oracle,Confidential ASSETLIAB. CONTACT ASSET(LIABILITY) NEEDCONTACT RCIVDPROD.INST. ACTIVITYPROD. INST. FINANCIALNEED ADDRESSEDNEED INCOME(EXPENSE) INC.EXP. CONTACT PERSONALADDRESS ACTIVITYCONTACT RECOMMENDATIONCONTACT FINANCIALRECOMMENDATION HOUSEHOLD/ ACCOUNT CONTACT RELATIONSHIP ORGMEMBER PROD.INST. CONTACT PRODUCTINSTANCECONTACT ACTIVITY FINANCIAL REVIEW PROCESS OPPORTUNITY ORGANIZATIONUNITPRODUCTORSERVICE isprimarilyincurredby has of associatedwith with has from sourceof ownedby owns managedby vendorof of incurredby reportedduring toreview locatedat locationof becauseof sourceof withjointlyhas withassociatedto of of ofhas of subjectof ownedby owns consideredon considerationof isa isa with subjectofof from reportedduring toreview onhasa of regarding of subjectof of subjectof addresses isaddressedby of subjectof communicatedduring tounderstand for primarysubjectof partofmadeupof with sourceof recommendedduring sourceof for subjectof locatedat for in participatesin in involves with subjectof of for in madeupof madeupof memberof definedfor headof to has of has of memberof with associatedto ofassociatedwith ownedby owns partof madeof becauseof affects for sourceof partof madeupof producedby vendorof
  • 115. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 114 Pricing Comparison This ERD (see Figure 47) 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 47 lists the entities in this ERD and their corresponding tables. Table 47. Pricing Comparison ERD Entities and Tables Entity Table Object Class S_VOD, S_VOD_VER Object Class Extended Attribute S_XA_ATTR Opportunity S_OPPTY Price List S_PRI_LST Price List Item S_PRI_LST_ITEM Pricing Matrix S_PRI_MTRX Pricing Matrix Item S_PRI_MTRX_ITEM Product Extended Attribute S_PROD_INT_XA Product or Service S_PROD_INT Product or Service Structure S_PROD_ITEM Quote S_DOC_QUOTE Quote Item S_QUOTE_ITEM Quote Item Extended Attribute S_QUOTE_ITEM_XA Tier Price Value S_VDISCNT_ITEM Tier Pricing S_VOL_DISCNT
  • 116. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 115 Figure 47. Pricing Comparison Title : Pricing Comparison Author : Oracle, Confidential PRICING MATRIX PRICING MATRIX ITEM TIER PRICING TIER PRICE VALUE PRICE LIST INTERNAL 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 by for based on for subject of for subject of priced via used by for described by of component of for assembly of for subject of for composed of quotation for subject of for described by for subject of
  • 117. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 116 Pricing This ERD (see Figure 48) 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 can be adjusted for certain extended attributes as defined in a specified pricing matrix. They can be adjusted based on changes to a customizable product through component price adjustments. They can also be modified through a specified pricing model made up of pricing factors. Table 48 lists the entities in this ERD and their corresponding tables. Table 48. Pricing ERD Entities and Tables Entity Table Component Price Adjustment S_PRI_CFG_ITEM Object Class S_VOD, S_VOD_VER Object Class Extended Attribute S_XA_ATTR Price List S_PRI_LST Price List Item S_PRI_LST_ITEM 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 S_PROD_INT Product or Service Structure S_PROD_ITEM
  • 118. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 117 Figure 48. Pricing Title:Pricing Author:Oracle,Confidential INTERNAL PRODUCTOR SERVICE PRODUCTOR SERVICE STRUCTURE COMPONENTPRICE ADJUSTMENT PRICINGFACTOR ITEMATTRIB PRICINGFACTORITEM PRICINGMATRIX PRICELIST PRICELIST ITEM PRICINGMODEL FACTOR PRODUCT EXTENDED ATTRIBUTE OBJECTCLASS EXTENDED ATTRIBUTE OBJECTCLASS PRICINGMODEL PRICINGMATRIX VALUE PRICINGMATRIX ITEM PRICINGMATRIX ATTRIBUTE anadjustmentfor thesubjectof of acomponentof for anassemblyof of subjectof definedfor referencedby for describedby configuredvia usedby basedon basisof classifiedas classificationfor for adjustedvia constraintfor constrainedby for madeupof for basedon partof madeupof ofobjectclass havetypes pricedvia usedby for composedof for madeupof for describedby for subjectof subclassof parentclassof
  • 119. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 118 Product Promotion Product Promotion (see Figure 49) 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 49 lists the entities in this ERD and their corresponding tables. Table 49. Product Promotion ERD Entities and Tables Entity Table Conditional Charge Prorata 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 Operation S_PROM_OPER Product Promotion Operation Component S_PROM_OPER_CPT Product Promotion Pricing Matrix Rule S_PROM_PMTRX Product Promotion Term S_PROMITM_TRMS Product Promotion Term Description S_PROD_TRM_DESC
  • 120. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 119 Figure 49. Product Promotion Title:ProductPromotion Author:Oracle,Confidential PRODUCTPROMOTION PRICINGMATRIXRULE PRODUCTPROMOTION CHARGE PRODUCTPROMOTION TERM CONDITIONAL CHARGE PRORATAPLAN ADJUSTMENT GROUP PRODUCTPROMOTION OPERATIONCOMPONENT PRODUCT PROMOTION OPERATION PRODUCT PROMOTIONTERM DESCRIPTION PRODUCTPROMOTIONITEM ATTRIBUTEVALUE PRODUCTPROMOTIONITEM ATTRIBUTE PRODUCTPROMOTIONITEM PRODUCT PRODUCTPROMOTION applies applicable to uses usedby associated to has uses usedby definefor has definefor has definefor has associateto associateby for contain definedfor has definefor has childof rootof definefor has parentofchildof definefor has madeup contain definefor has
  • 121. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 120 Product Quality Tracking This ERD (see Figure 50) illustrates the significant entities related to product defect tracking. Defects can be associated with service requests and can have associated activities defined to fix the defect. Associations can 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 can be recorded. Defects can be associated with other, related defects. Table 50 lists the entities in this ERD and their corresponding tables. Table 50. Product Quality Tracking ERD Entities and Tables Entity Table Activity S_EVT_ACT Defect Symptom S_PRDFCT_SYMP Employee/Agent S_EMP_PER, S_CONTACT, S_PARTY Organization Unit S_ORG_EXT, S_PARTY 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 Service Request S_SRV_REQ
  • 122. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 121 Figure 50. Product Quality Tracking Title:ProductQualityTracking Author:Oracle,Confidential PERSON EMPLOYEE/AGENTOTHERPERSON PROJECT PRODUCT RELEASE PROJECT OTHER PROJECTS ORGANIZATIONUNIT OTHER ORGANIZATION UNIT INTERNAL/ PARTNER ORGANIZATION UNIT DEFECT SYMPTOM PROJECTITEM REQUIRED FEATURE QATEST RESOLUTIONITEM PRODUCTORSERVICE EXTERNALPRODUCT INTERNALPRODUCTORSERVICE INTERNALPRODUCTVERSIONOTHERINTERNALPRODUCT ORSERVICE INTERNALPRODUCT SERVICEREQUEST PRODUCTQUALITYITEM PRODUCTPATCH/ ENHANCEMENT REQUEST PRODUCTDEFECT OTHERPRODUCTQUALITYITEM ACTIVITY SERVICEREQUESTACTIVITY QUALITYENHANCEMENT ACTIVITY OTHERACTIVITY reportedby reporterof reportedby reporterof ownedby ownerof ownedby ownerof acomponentofanassemblyof reportedviacausedby definedfor handledvia basedon basisfor primarilyby primaryof definedfor fixedvia belongto includes resolvedby solutionto partof madeupof solutionto resolvedby ownedby ownerof observedfor exhibitionof inenvironmentof partof versionof producedin partof madeupof relatedtorelation of duplicate of duplicated as reportedfor afflicted with plannedto befixedin target fixfor actuallyfixedin actualfixfor
  • 123. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 122 Product Recommendation Product Recommendation (see Figure 51) 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 51 lists the entities in this ERD and their corresponding tables. Table 51. 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 or Service S_PROD_INT Product Recommendation S_PROD_RECMNDTN
  • 124. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 123 Figure 51. 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
  • 125. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 124 Products or Services This ERD (see Figure 52) 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 52 lists the entities in this ERD and their corresponding tables. Table 52. Products or Services ERD Entities and Tables Entity Table Catalog S_CTLG Catalog Category S_CTLG_CAT Class Attribute S_XA_ATTR Class of Product or Service S_VOD, S_VOD_VER Language S_LANG Price List S_PRI_LST Price List Item S_PRI_LST_ITEM Product Assembly Port S_PROD_ITEM Product Line S_PROD_LN Product or Service S_PROD_INT or S_PROD_EXT Product or Service Attribute S_PROD_INT_XA Product Structure S_PROD_ITEM, S_PROD_REL Product User Defined Attribute S_PROD_USRDEFATR Vendor S_ORG_EXT, S_PARTY
  • 126. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 125 Figure 52. Products or Services Title:ProductsorServices Author:Oracle,Confidential PRODUCT USER DEFINED ATTRIBUTE VENDOR PRODUCTASSEMBLYPORT CATALOG CATEGORY CATALOG LANGUAGE PRODUCTORSERVICE ATTRIBUTE CLASSATTRIBUTE CLASSOFPRODUCTOR SERVICE PRICELISTITEM PRODUCT STRUCTURE PRODUCT LINE PRODUCTORSERVICE INTERNALPRODUCTORSERVICE EXTERNALPRODUCTORSERVICE PRICE LIST for has grouped by for producedby producerof areportto aparentto translationfor translatedinto validfor constrainedbydefinedfor describedvia translationfor translatedintochildof parentto translationfor translatedinto basedon basisfor translationfor translatedinto translationfor translatedinto for categorizedin partof madeupof of subjectof of subjectof of subjectof aclassificationfor classifiedin composedof partof for composedof a collection of partof anassembly of for a component of of
  • 127. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 126 Professional Services This ERD (see Figure 53) 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 53 lists the entities in this ERD and their corresponding tables. Table 53. Professional Services ERD Entities and Tables Entity Table Activity S_EVT_ACT Address S_ADDR_ORG (Siebel Cross-Industry Applications) S_ADDR_PER (Siebel Industry Applications) Billing Rate List S_PRI_LST Employee/Agent S_EMP_PER, S_CONTACT, S_PARTY Internal/Partner Organization S_ORG_EXT, S_PARTY Invoice S_INVOICE Lead Source S_SRC Opportunity S_OPTY Organization Unit S_ORG_EXT, S_PARTY Person S_CONTACT, S_PARTY Position S_POSTN, S_PARTY Potential Project Resource S_PROJ_PTL_RSRC Project S_PROJ Project Contact S_PROJ_CON Project Issue S_PROJ_ISS Project Team Role S_PROJ_RSRC Skill S_PROJRSRC_SKL
  • 128. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 127 Figure 53. Professional Services Title:ProfessionalServices Author:Oracle,Confidential ADDRESS ORGANIZATIONUNIT OTHER ORGANIZATION UNIT INTERNAL/PARTNER ORGANIZATION PERSON OTHER PERSON EMPLOYEE/ AGENTINVOICE SKILL LEAD SOURCE OPPORTUNITY BILLINGRATE LIST SERVICE BILLING POSITION TYPE POSITION ACTIVITY PROJECTTEAMROLE PROJECTISSUE POTENTIALPROJECT RESOURCE PROFESSIONALSERVICEPROJECT PROJECTCONTACT fortheresolutionof subjectof responsibilityof responsiblefor accessibleto accessorof subcontractedto apartnerfor for theclientof sentto for locatedat for for locatedat employedby composedof filledby assignedtofill of definedas for subjectof for subjectof requiredby requirerof requirerof requiredby billedfor billedby billedfor billedin of involvedinoccupantof heldbysourceof becauseof definedfor requirerof for subjectof definedby subjectoftotrackworkon subjectofsourceof theoutcomeof billedas billingtypefor billingtypefor billedas billedvia for assignedto assignedto for targetedat
  • 129. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 128 Promotion Group Promotion Groups (see Figure 54) offer advanced product and service bundling and new community offerings that tie various customer assets in a loosely-coupled network and provide shared benefits and provisioning functions. Promotion Group Validation provides the ability to define and enforce validation rules for Promotion Groups, such as eligibility and compatibility rules or rules validating the consistency in a Promotion Group. Promotion Group pricing provides the ability to define and enforce all pricing-related aspects of a Promotion Group, such as assigning charges to Promotion Group memberships or adjusting prices for Promotion Group components. Promotion Group Access Control provides the ability to define and enforce business rules governing who can manage the membership of a given Promotion Group. Promotion Group Notification provides the ability to define the different types of notifications to be sent to Promotion Group owners and members in response to business events like new or canceled membership. Table 54 lists the entities in this ERD and their corresponding tables. Table 54. Promotion Group ERD Entities and Tables Entity Table Account S_ORG_EXT Adjustment Group S_ADJ_GROUP Asset S_ASSET Communication Template S_DMND_CRTN_PRG Conditional Charge Prorata Plan S_AGR_PR_PLAN Order Item S_ORDER_ITEM Product Compatibility Matrix S_PRODCOMP_MTRX Product Membership Compatibility S_PRODCOMP_MEM Promotion Configuration Item S_PRO_CFG_ITEM Promotion Group S_PROD_INT Promotion Group Access S_PROMGRP_ACESS Promotion Group Charge S_PROM_CHRG Promotion Group Item S_PROM_ITEM Promotion Group Member S_PROD_INT Promotion Group Notification S_PROM_GRP_NTFY Promotion Group Pricing Matrix Rule S_PROM_PMTRX
  • 130. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 129 Promotion Group Term Description S_PROD_TRM_DESC Quote Item S_QUOTE_ITEM Table 54. Promotion Group ERD Entities and Tables Entity Table
  • 131. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 130 Figure 54. Promotion Group Title:ProductPromotionGroup Author:Oracle,Confidential ACCOUNT QUOTE ITEM ORDERITEMPROMOTION GROUP CHARGE PROMOTION GROUPTERM DESCRIPTION PROMOTIONGROUP PRICINGMATRIXRULE COMMUNICATION TEMPLATE CONDITIONAL CHARGE PRORATA PLAN ADJUSTMENT GROUP ASSET PRODUCTMEMBERSHIPCOMPATIBILITY PROMOTIONGROUP NOTIFICATION PRODUCTCOMPATIBILITYMATRIX PROMOTIONCONFIGURATIONITEM PROMOTION GROUP ACCESS PROMOTION GROUPITEM PRODUCT PROMOTIONGROUP MEMBER PROMOTIONGROUP for has for has for associated to definedfor has definedfor has notify notifiedby for associatedto has for belongsto associated to ownedby ownerof ownedby ownerof definedfor has associate to associate by uses usedby defined for has relatedto has for has appliesto has related to has for has for has has for for has for has for has definedfor has definedfor has definedfor has definedfor has defined for has userof usedby madeupof contains
  • 132. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 131 Revenue This ERD (see Figure 55) illustrates how revenue items are tracked and analyzed in Siebel Business Applications. Revenue Items can 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 55 lists the entities in this ERD and their corresponding tables. Table 55. Revenue ERD Entities and Tables Entity Table Agreement S_DOC_AGREE Agreement Item S_AGREE_ITEM Invoice S_INVOICE Invoice Item S_INVC_ITEM Marketing Event S_SRC Opportunity S_OPTY Organization Unit S_ORG_EXT, S_PARTY Person S_CONTACT, S_PARTY Position S_POSTN, S_PARTY Product Line S_PROD_LN Product or Service S_PROD_INT Project S_PROJ Revenue Item S_REVN Revenue Template S_REVN_TMPL Revenue Template Item S_REVN_TMPL_ITM Service Request S_SRV_REQ
  • 133. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 132 Figure 55. Revenue Title:Revenue Author:Oracle,Confidential REVENUETEMPLATE ITEM REVENUETEMPLATE REVENUEITEM OPPORTUNITY POSITION PERSON EMPLOYEE/AGENT OTHERPERSON AGREEMENT SERVICEREQUEST ORGANIZATIONUNIT INTERNAL/ PARTNER ORGANIZATION UNIT OTHER ORGANIZATION UNIT PRODUCTLINE CONTRACTITEM PROJECT INVOICEITEM PRODUCTORSERVICE MARKETINGEVENTOR ACTIVITY INVOICE for attributedto basedon templateitemfor basedon templatefor for subjectof for attributedto detaileditemof revenueplanfor detailsof consistof areporttomanagerof for attributedto partof madeupof heldby occupantof for ownerof for subjectof for attributedto for subjectof for attributedto for attributedto for attributedto for attributedto for attributedto belongsto subjectof composedof partof
  • 134. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 133 Sales Hierarchy and Credit Assignment The 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 (see Figure 56) 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 56 lists the entities in this ERD and their corresponding tables. Table 56. 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 S_POSTN, S_PARTY Position Territory Assignment S_SLSTERR_POSTN Sales Hierarchy S_SLS_HIER Sales Territory S_SLS_TERR
  • 135. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 134 Figure 56. Sales Hierarchy and Credit Assignment Title:SalesHierarchyandCreditAssignment Author:Oracle,Confidential POSITIONTERRITORYASSIGNMENT PARTY OTHERPARTY POSITION CREDITALLOCATION CREDITRULECRITERIA VALUE CREDITRULECRITERIA CREDITASSIGNMENT RULE RULETYPE VALIDATIONRULE HIERARCHYVERSION TERRITORY HIERARCHY VERSION SALESTERRITORY SALESHIERARCHY transferto recipientof rollupto recipientof subordinateto parentof partof composedof assignedterritory assignedto applicableto subjectof allocatedto recipientof approved approveapprovedby approve approvedby approve approvedby approve definedfor characterizedby definedfor characterizedby allocationof subjectof assignmentof consistsof categoriedby subjectof appliedto validatedby versionof assignedto versionof versionedby belongsto consistsof
  • 136. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 135 Sales Portfolio Management This ERD (see Figure 57) illustrates the process of creating and managing sales portfolios for employees in sales positions within the sales organization. It shows the process for creating a sales portfolio, setting target accounts for a given portfolio, and defining the business or service units for each associated account as well as the associated account’s business drivers and initiatives. Also illustrated are partners and partner's competitors associated with the portfolio accounts. In addition, this ERD covers the marketing campaigns which are targeted at the accounts in the portfolios. Table 57 lists the entities in this ERD and their corresponding tables. Table 57. Sales Portfolio Management ERD Entities and Tables Entity Table Sales Portfolio S_SLS_PORTFOLIO Portfolio Category S_PRTFL_CTGRY Portfolio Account S_PRTFL_ACCNT Product Offering S_ENT_SOLN Portfolio Partner S_PRTFL_PRTNR Portfolio Attachment S_PRTFL_ATT Portfolio Product Offering S_PRTFL_ENTSOLN Account Prod Offering S_PRTFL_ACCSOLN Portfolio Sub_Account S_PRTFL_SUBACC Portfolio Account Attachment S_PRTFL_ACC_ATT Portfolio Business Driver S_PRTFL_BU_DRVR Portfolio Business Initiative S_PRTFL_BU_INTV Campaign S_SRC Portfolio Account Campaign S_PRTFL_CAMP Portfolio Partner Competitor S_PRTFL_CMPTR Organization Unit S_ORG_EXT
  • 137. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 136 Figure 57. Sales Portfolio Management 7LWOH6DOHV3RUWIROLR0DQDJHPHQW $XWKRUOracleRQILGHQWLDO 25*$1,=$7,2181,7 27+(5 $2817 3$571(5 25*$1,=$7,21 203(7,725 25*$1,=$7,21 $2817 3257)2/,2$2817$03$,*1 3257)2/,2 3$571(5 203(7,725 3257)2/,2 3$571(5 $03$,*1 3257)2/,2%86,1(66 ,1,7,$7,9( 3257)2/,2%86,1(66 '5,9(5 3257)2/,2 $2817 $77$+0(17 3257)2/,2 $77$+0(17 3257)2/,268%B$2817 $2817352' 2))(5,1* 3257)2/,2352'87 2))(5,1* 3257)2/,2$2817 3257)2/,2 $7(*25 352'87 2))(5,1* 6$/(63257)2/,2 IRU VXEMHFWRI IRU WDUJHWHG E IRU LQFOXGHG LQ IRU LQFOXGHG LQ IRU KDV GHILQHGIRU VXEMHFWRI GHILQHGIRU VXEMHFWRI IRU VXEMHFWRI GHOLYHUHGYLD IRU IRU VXEMHFWRI IRU FRQWDLQ IRU KDV SDUWRI PDGHXSRI FDWHJRUL]HG DV FRPSRVHGRI FRQWDLQ SDUWRI IRU SURYLGHG ZLWK RI RIIHUHGWR IRU WDUJHWDW RI VXEMHFWRI EHORQJWR GLYLGHG LQWR
  • 138. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 137 Service Agreement This ERD (see Figure 58) 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 coverage that exists 24 hours a day and seven days a week, for example), and can be subject to one or more metrics (that describe a guaranteed two-hour response, for example). Table 58 lists the entities in this ERD and their corresponding tables. Table 58. Service Agreement ERD Entities and Tables Entity Table Account S_ORG_EXT, S_PARTY Agreement S_DOC_AGREE Agreement Entitlement S_ENTLMNT Agreement Item S_AGREE_ITEM Asset S_ASSET Contact S_CONTACT, S_PARTY 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 Service Request S_SRV_REQ Work Type S_PROJ
  • 139. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 138 Figure 58. Service Agreement Title:AgreementEntitlement Author:Oracle,Confidential AGREEMENT ITEM AGREEMENT ITEMRENEWAL TERM SERVICE CALENDER MATERIAL WORK TYPE EXPENSE TYPE ACTION TYPE PREVENTIVE MAINTENANCE SERVICE METRIC ORDER SERVICE REQUEST ENTITLED SERVICE ACCOUNT CONTACT ASSET AGREEMENT PRICEADJUSTMENT PRODUCT ENTITLEDPRODUCTORASSET AGREEMENTENTITLEMENT for subjectof for subjectof basedon basisfor partof madeupof constrainedby usedby employedat employerof billablefor billableas billablefor billableas billablefor billableas definedfor sujectof of for an instance of made into with subjectof for subjectof for subjectof basedon basis for coveredby for for coveredby entitledby basisfor entitledby basisfor basedon basisfor basedon basisfor basedon basisfor for subjectof partof madeupof
  • 140. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 139 Service Calendars and Work Shifts This ERD (see Figure 59) 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 nonworking hours expressed as employee exception hours. Table 59 lists the entities in this ERD and their corresponding tables. Table 59. 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 Person S_CONTACT, S_PARTY Schedule Calendar S_SCHED_CAL Schedule Calendar Hours S_SCHED_CAL_HRS Service Calendar S_SCHED_CAL Work Shift S_SCHED_CAL
  • 141. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 140 Figure 59. Service Calendars and Work Shifts Title : Service Calendars and Work Shifts Author : Oracle, Confidential PERSON OTHER PERSON EMPLOYEE / 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
  • 142. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 141 Service Request This ERD (see Figure 60) 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 60 lists the entities in this ERD and their corresponding tables. Table 60. 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
  • 143. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 142 Figure 60. Service Request Title:ServiceRequest Author:Oracle,Confidential SERVICE REGION PARTY ORGANIZATIONUNIT INTERNAL/PARTNER ORGANIZATIONUNIT OTHERORGANIZATION UNIT OTHERPARTY PERSON OTHERPERSON EMPLOYEE/AGENT ASSET(PRODUCT INSTANCE) ACTIVITY OTHERACTIVITYSERVICEREQUESTACTIVITY EXTERNAL PRODUCT PRESENCE SERVICEREQUEST PRODUCTORSERVICE EXTERNAL PRODUCTOR SERVICE INTERNALPRODUCTORSERVICE at subjectof responsibilityof responsiblefor responsibilityof responsiblefor responsibilityof responsiblefor ownedby ownerof responsibilityof responsiblefor responsibilityof responsiblefor in environment of partof profileof of subjectof forproblems with subjectof forproblems with subjectof aninstanceof manufacturedinto partofmadeupof in environment of partof profileof for subjectofmadeupof partof reportedby reporterof
  • 144. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 143 Shipment This ERD (see Figure 61) 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 61 lists the entities in this ERD and their corresponding tables. Table 61. Shipment ERD Entities and Tables Entity Table Inventory Location S_INVLOC 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 Product Internal S_PROD_INT 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
  • 145. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 144 Figure 61. Shipment 7LWOH6KLSPHQW $XWKRUOracleRQILGHQWLDO 3$57029(0(17 73( 25'(53$57029(0(17 27+(53$57029(0(17 25'(5,7(0'(/,9(53520,6( 6+,30(17/,1(,7(0 25'(5,7(0 '(/,9(55(48(67 6+,30(1725'(5/,1(,7(0 4827(,7(0 '(/,9(55(48(67 4827(,7(0 '(/,9(5 3520,6( 4827(/,1(,7(0 4827( 25'(5 352'87 ,17(51$/ ,19(1725/2$7,21 WSHRI WSHIRU SUHFHGHGE IROORZHGE IRU IXOILOOHGE WUDQVODFWLRQVIRU KDV FRPSRVHGRI SDUWRI IRU KDV EDVHGRQ EDVLVIRU GHOLYHUYHKLFOHRI GHOLYHUHGE SDUWRI FRPSRVHGRI IRU KDV IRU KDV IRU KDV VRXUFHGIURP VRXUFHRI SDUWRI FRPSRVHGRI EDVLVIRU EDVHGRQ SDUWRI FRPSRVHGRI WR GHVWLQDWLRQRI VRXUFHGIURP VRXUFHRI VWRUHGLQ VWRUDJHORFDWLRQIRU SDUWRIPDGHXSUHSOHQLVKHGIURPUHSOHQLVKPHQWVRXUFHIRU
  • 146. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 145 Siebel Assistant This ERD (see Figure 62) 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 62 lists the entities in this ERD and their corresponding tables. Table 62. Siebel Assistant ERD Entities and Tables Entity Table Account S_ORG_EXT, S_PARTY Activity S_EVT_ACT Activity Plan S_EVT_ACT Activity Plan Template S_TMPL_PLANITEM Assessment Template S_TMPL_PLANITEM Assessment S_ASSESS Assessment Attribute S_ASSESS_ATTRIB Assessment Attribute Valid Value S_ASSESS_ATTVAL Assessment Value S_ASSESS_VAL Employee/Agent S_EMP_PER, S_CONTACT, S_PARTY Opportunity S_OPTY Opportunity Stage S_OPTY_STG Person S_CONTACT, S_PARTY 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
  • 147. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 146 Figure 62. Siebel Assistant Title:SiebelAssistant Author:Oracle,Confidential ACCOUNT ACTIVITY OTHERACTIVITY TEMPLATE ACTIVITY ACTIVITY PLAN OPPORTUNITYSTAGE SALES METHODOLOGY PERSON OTHER PERSON EMPLOYEE/ AGENT STAGE RECOMMENDATION SALESSTAGE OPPORTUNITY SALESPLANNINGITEM ACTIVITYPLANTEMPLATEASSESSMENT TEMPLATE STAGEPLANITEM ASSESSMENTVALUEASSESSMENTATTRIBUTE VALIDVALUE ASSESSMENTATTRIBUTE ASSESSMENT of subjectof for containerof for madeupof instanceof instantiatedas definedfor validatedvia definedfor assesedvia for acomponentof for of for at for of for plannedby createdfrom for createdduring for of for currentlyat forfor composedof governedby governorof of subjectof of subjectof partofmadeupof of for
  • 148. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 147 Territory Management This ERD (see Figure 63) 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 63 lists the entities in this ERD and their corresponding tables. Table 63. 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 S_TERRITORY Territory Hierarchy S_TERR_HIER Territory Version S_TERRHIER_NODE Zipcode (None)
  • 149. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 148 Figure 63. Territory Management 7LWOH7HUULWRU0DQDJHPHQW $XWKRUOracleRQILGHQWLDO *(2*5$3+,$/$5($ =,32'( 5(*,21 7(55,7250$33,1* 217$77(55 0$33,1* *(27(55 0$33,1* $66(77(55 0$33,1* $28177(55 0$33,1* $28177($00(0%(5 217$77($00(0%(5 $66(77($0 0(0%(5 $66(7 217$7 326,7,21',9,6,21 27+(5',9,6,216$/(6)25( %86,1(6681,7 $2817 7(55,725 +,(5$5+ 7(55,725 7(55,725 9(56,21 326,7,217(55,725 $66,*10(17 GHILQHG IRU JUDQWHG DFFHVV WR SDUWRI PDGHXSRI RI SDUWRI WR UHVSRQVLELOLWRI RUJDQL]HGE XVHG E VSHFLILF WR UHVSRQVLEOHIRU RI DVVLJQHGWR WR UHVSRQVLELOLWRI RI DVVLJQHGWR WR UHVSRQVLELOLWRI RI DVVLJQHGWR WR UHVSRQVLELOLWRI GHILQHGE PDGHXSRI SDUWRI FRPSRVHGRI GHILQHG IRU JUDQWHG DFFHVV WR YHUVLRQRI DVVLJQHG WR RI SDUW RI RI SDUWRI RI SDUWRI WR FRPSRVHGRI SDUWRIFRPSRVHGRI RI DVVLJQHGWR
  • 150. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 149 Territory Quota Rollup This ERD (see Figure 64) covers sales quotas setup and quota rollup in the territory management system. It illustrates assigning sales quotas to periods, contacts, accounts, regions, and ZIP codes. These assignments can be spread over different periods. As each territory consists of a set of contacts, accounts, regions, and ZIP codes assigned with quotas; the quotas can be rolled up to each territory or each territory for each period. Table 64 lists the entities in this ERD and their corresponding tables. Table 64. Territory Quota Rollup ERD Entities and Tables Entity Table Sales Quota S_SLS_QUOTA Territory S_TERRITORY Territory Quota S_TERR_QUOTA Account/Quota S_QUOTA_ACCNT Contact/Quota S_QUOTA_CON Geo/Quota S_QUOTA_REGN, S_QUOTA_ZIP Quota Assignment Breakdown S_QTA_ACC_PD, S_QTA_CON_PD, S_QTA_REGN_PD, S_QTA_ZIP_PD Contact /Terr Mapping S_TERR_CON Account / Terr Mapping S_TERR_ACCNT Geo/Terr Mapping S_TERR_REGION, S_TERR_ZIP Terr/Qta/Geo S_TERR_QTA_REGN, S_TERR_QTA_ZIP Terr/Qta/Con S_TERR_QTA_CON Terr/Qta/Accnt S_TERR_QTA_ACCT Accnt Quota Credit S_TRQT_ACC_CRDT Contact Quota Credit S_TRQT_CON_CRDT Geo Quota Credit S_TRQT_REGNCRDT, S_TRQT_ZIP_CRDT Period Quota S_QTA_PD_BRKDN Terr Quota Breakdown S_TRQT_PD_BRKDN
  • 151. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 150 Figure 64. Territory Quota Rollup 7LWOH7HUULWRU4XRWD5ROOXS $XWKRUOracleRQILGHQWLDO 7(554827$ %5($.'2:1 3(5,2' 4827$ *(24827$ 5(',7 217$74827$ 5(',7 $174827$ 5(',7 7(554827$0$33,1* %5($.'2:1 7(55,7254827$0$33,1* 7(5547$217(5547$$177(5547$*(2 7(55,7254827$7(55,725 7(55,7250$33,1* $28177(55 0$33,1* *(27(55 0$33,1* 217$7 7(55 0$33,1* 4827$$66,*10(17 %5($.'2:1 4827$$66,*10(17 $28174827$*(24827$217$74827$ 3(5,2' 217$7$2817*(2*5$3+,$/$5($ =,32'(5(*,21 6$/(64827$ IRU JRYHUQHGE EHORQJWR JRYHUQ RI GHILQHGIRU EHORQJWR JRYHUQ DVVLJQHGWR UHFLSLHQWRI DVVLJQHGWR UHFLSLHQWRI DVVLJQHGWR UHFLSLHQWRI RI SDUWRI RI SDUWRI RI SDUWRI DVVLJQHGWR WDUJHWRI DVVLJQHGWR WDUJHWRI DVVLJQHGWR WDUJHWRI EUHDNGRZQRI VXEMHFWRI VSUHDGRYHU IRU UROOHGXSWR FRPSRVHG EUHDNGRZQ VXEMHFWRI VSUHDGRYHU IRU IRU WDUJHWRI IRU WDUJHWRI IRU WDUJHWRI RI DVVLJQHGWR IRU WDUJHWRI DVVLJQPHQWRI VXEMHFWRI WR FRPSRVHG RI WSHRI RZQHUIRU
  • 152. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 151 Textile, Apparel, and Footwear This ERD (see Figure 65) 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 can be found within a supertype. They are not intended to indicate strict subtypes. Table 65 lists the entities in this ERD and their corresponding tables. Table 65. Textile, Apparel, and Footwear ERD Entities and Tables Entity Table Marketing Segment S_MKT_SEG Order S_ORDER Order Item S_ORDER_ITEM 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 Quote Item S_QUOTE_ITEM
  • 153. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 152 Figure 65. Textile, Apparel, and Footwear Title:Textile,ApparelandFootwear Author:Oracle,Confidential QUOTEITEM ASSORTMENTPLANITEM SCHEDULEDDELIVERY ASSORTMENT PLANITEM ORGANIZATION EXTERNAL OTHER ORGANIZATION ACCOUNT STORE PRODUCTINTERNAL LINEOFBUSINESS CATEGORY STYLE/COLOR/DIMENSION QUOTE ASSORTMENT PLAN ORDER ORDERITEM ORDERED ASSORTMENT PLANITEM PROPORTION ORDERED ASSORTMENT PLANITEM MARKETING SEGMENT PERIOD SEASON OTHERPERIODTYPESWEEK PRODUCTOPTION RANGEMEMBER PRODUCT ATTRIBUTE TYPE PERIODRELATIONSHIP PRODUCTOPTIONRANGE NON-SEASONAL SIZERUN SEASONAL COLORPALETTE PRODUCTATTRIBUTEVALUE SHOESIZE COLOR FAMILY OTHERATTRIBUTEVALUE COLOR PRODUCTOPTIONMIXPREFERENCE (SPREAD) ACCOUNT SPECIFIC MIX RECOMMENDED MIX PRODUCTOPTION MIXPROPORTION for belongingto recommendedtobeorderedin the default mixfor launched in debutseasonfor billedtofor definedfor subjectof relevantto includer of of splitinto of scheduled by applicable to acollectionof definedforparentto defined for deliveryperiodfor for composed of createdfrom leadto for composed of of orderedon forof secondarily manufacturedinin primarily manufacturedinin primarydefinedbycollectionof secondarydefinedbycollectionof specificto definerof thetargetoftargettedat for subjectof secondarily specify specified on primarily specify specified on primarilycomposedofsubjectof secondarilycomposedofsubjectof for subjectof defined for deliveryperiodfor specificto itemswithin scopeof definedfor composedof definedfor composed of for collection of secondarily of subjectof primarilly of subject of secondarilyofsubjectof secondarily definedby secondary domainfor topartof ofmadeup of definedforsubjectof primarily definedby primary domain for avalue of thedomain for applicableto subjectof primarilyofsubjectof
  • 154. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 153 Time Sheet This ERD (see Figure 66) 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 66 lists the entities in this ERD and their corresponding tables. Table 66. Time Sheet ERD Entities and Tables Entity Table Activity S_EVT_ACT Organization Unit S_ORG_EXT, S_PARTY Period S_PERIOD Person S_CONTACT, S_PARTY Project S_PROJ Project Team Role S_PROJ_RSRC Service Request S_SRV_REQ Time Unit S_TMSHT_ITEM Timesheet S_TMSHT Timesheet Approval S_TMSHT_APPR Timesheet Line S_TMSHT_LN Work Type S_PROJ
  • 155. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 154 Figure 66. Time Sheet Title:TimeSheet Author:Oracle,Confidential PROJECTTASKOPPORTUNITY SERVICE REQUEST PROJECTTEAMROLE TIMEUNIT TIMEADJUSTMENTWORKTIMEUNIT ACTIVITY TIMESHEET TIMESHEETLINE PERIOD PERSON EMPLOYEE/AGENT OTHERPERSON ORGANIZATIONUNIT INTERNAL ORGANIZATIONUNIT OTHER ORGANIZATION UNIT WORKTYPE NON-PROJECT WORKTYPE PROJECT approved approver classifiedas classificationfor belongsto madeup based basisfor subjectof reportoftime workedon for subjectof adjustment adjusted reportedvia madeupof associatedwith contactfor ownedby ownerof reportedby reporterof submittedfor referencedby ownedby haveownershipof targetedat subjectof reportedby reporterofaffiliatedwith composedof definedfor require for subjectof for subjectof reportedfor for partof madeupof
  • 156. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 155 Trade Promotions This ERD (see Figure 67) 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 67 lists the entities in this ERD and their corresponding tables. Table 67. Trade Promotions ERD Entities and Tables Entity Table Account S_ORG_EXT, S_PARTY Contract S_D0C_AGREE, S_DOC_QUOTE, S_ORDER Contract Item S_AGREE_ITEM, S_QUOTE_ITEM, S_ORDER_ITEM Fund Allocation S_MDF_ALLOC Internal Product Presence S_ORG_PROD Marketing Development Fund S_MDF Marketing Event or Activity S_SRC, S_SRC_CHNL Note S_NOTE_SRC Order S_ORDER Other Contract S_DOC_AGREE, S_DOC_QUOTE Person S_CONTACT, S_PARTY Product S_PROD_INT, S_PROD_EXT
  • 157. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 156 Figure 67. Trade Promotions 7LWOH7UDGH3URPRWLRQV $XWKRUOracleRQILGHQWLDO 3(5621 25'(5,7(0 0$5.(7,1*'(9(/230(17)81' )81' $//2$7,21 2175$7 25'(5 27+(5 2175$7 $2817 0$5.(7,1*(9(1725$7,9,7 352027,21$2817 27+(50$5.(7,1* (9(1725$7,9,7 352027,21 $2817352'87 352027,21 352027,21 352'87 352027,213/$1 127( 352'87 352'87(;7(51$/ 352'87,17(51$/ UHIHUHQFHWR VXEMHFWRI DIILOLDWHGZLWK FRPSRVHGRI UHTXHVWHGE UHTXHVWRURI VWDIIHGE RQVWDIIIRU LQYLWHURI LQYLWHGWR SDUWRI PDGHXSRI IXQGHGE IXQGLQJVRXUFHRI IURP WR FRPSDUHGWR FRPSDULVRQRI GHILQHGIRU VXEMHFWRI GHVLJQDWHGWR WDUJHWRI RI VXEMHFWRI WR UHFLSLHQWRI UHIHUHQFHWR FRYHUHGE WDUJHWRI SDUWWR GHILQHGIRU VXEMHFWRI IRU VXEMHFWRI SDUWRIPDGHXSRI
  • 158. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 157 Training Curriculum Course This ERD (see Figure 68) 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 can 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 68 lists the entities in this ERD and their corresponding tables. Table 68. Training Curriculum Course ERD Entities and Tables Entity Table Catalog Category S_CTLG_CAT Access Group S_PARTY Employee Course S_EMP_CRSE Employee Course Status S_EMP_CRSE_STAT
  • 159. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 158 Figure 68. Training Curriculum Course Title:TrainingCurriculumCourse Author:Oracle,Confidential CATALOGCATEGORY EMPLOYEECOURSESTATUS EMPLOYEECOURSE ACCESSGROUP MARKETINGEVENTORACTIVITY OTHERMARKETINGEVENTOR ACTIVITY TRAININGCOURSEOFFERING LITERATURE PERSONPRODUCTORSERVICE TRAININGCOURSE OTHERPRODUCTORSERVICE COURSE AVAILABLE LANGUAGE JOBPROFILECURRICULUM PERSON TRAINING CURRICULUM STEPCOURSE TRAINING CURRICULUMSTEP TRAININGCURRICULUM CURRICULUM TARGETAUDIENCE CURRICULUM CATEGORY certifiedfor subjectofsubjectof forsatisfiedby providetrainingfor accessedby grantedaccesstofor belongsto targetof targetedat partof composedof path categorizedinto for categorizedinto of trackedby for inneedof neededby for instructedby instructorof providetrainingfor satisfiedby availablefor offeredin registeredby enrolledin basedon basisof of subjectof partof composedof partof composedof for subjectof certificationof subjectof
  • 160. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 159 Training Test Engine This ERD (see Figure 69) illustrates the entities and relationships relevant to the training test engine business function. Tests can be defined for one or more course offerings, or for one or more courses, including test questions and possible answers, and can 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 69 lists the entities in this ERD and their corresponding tables. Table 69. 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 Marketing Event or Activity S_SRC Pool Question S_POOL_QUES Product or Service S_PROD_INT 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
  • 161. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 160 Figure 69. Training Test Engine 7LWOH7UDLQLQJ7HVW(QJLQH $XWKRUOracleRQILGHQWLDO (9(17/2$7,21 48(67,21 $7(*25 48(67,2148(67,21322/ 48(67,21 322/ 48(67,21 7(6748(67,21 ,1',9,'8$/ 67(67 48(67,21 ,1',9,'8$/ 6 7(67$16:(5 ,1',9,'8$/ 67(67 0$5.(7,1*(9(1725$7,9,7 27+(50$5.(7,1*(9(1725$7,9,7 75$,1,1*2856(2))(5,1* 352'87256(59,( 75$,1,1*2856( 27+(5352'87256(59,( 7(67$9$,/$%/( /$1*8$*( 2856(2856(2))(5,1*7(67 ,1',9,'8$/ 67(67 $7(*25 322/48(67,21 723,2%-(7,9( 75$,1,1*7(67 48(67,213266,%/($16:(5 SDUWRI VHOHFWHGE ORFDWLRQRI RIIHUHGDW FRPSRVHGRI VXEMHFWRI SDUWRI VXEMHFWRI FRQFHUQHGDERXW PDGHXSRI FDWHJRUL]HGLQWR DFROOHFWLRQRI SDUWRI VHOHFWHGE IRU PDGHXSRI FKRVHQIURP IRU IRU VXEMHFWRI HYDOXDWHGE HYDOXDWHGDJDLQVW IRU VXEMHFWRI LQFOXGHGLQ LQFOXGLQJ FDWHJRURI JURXSHGE DYDLODEOHIRU RIIHUHGLQ IRU PDGHXSRI IRU VXEMHFWRI LQVWDQFHRI WHPSODWHIRU EDVHGRQ EDVLVRI DVVRFLDWHGZLWK VXEMHFWRI DVVRFLDWHGZLWK VXEMHFWRI DVVRFLDWHGZLWK VXEMHFWRI
  • 162. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 161 Versioned Object Definition Versioned Object Definition (see Figure 70) 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 70 lists the entities in this ERD and their corresponding tables. Table 70. 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
  • 163. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 162 Figure 70. Versioned Object Definition Title:VersionedObjectDefinition Author:Oracle,Confidential JOINTWORKSPACE ITEM JOINTWORKSPACEOBJECTATTRIBUTEVALUE PRODUCTTEMPLATE ATTRIBUTEVALUE PRODUCTATTRIBUTEVALUE OBJECTATTRIBUTE PRODUCT ATTRIBUTE PRODUCTTEMPLATE ATTRIBUTE ATTRIBUTEVALUEATTRIBUTEDEFINITIONOBJECTDEFINITION PRODUCTTEMPLATE DEFINITION PRODUCTDEFINITION VERSIONEDOBJECT DEFINITIONVERSION VERSIONEDOBJECTDEFINITION ATTRIBUTEHEADERDEFINITIONOTHERVERSIONEDOBJECTHEADER DEFINITION PRODUCTHEADER DEFINITION PRODUCTTEMPLATEHEADER DEFINITION for groupedin for have for have for have for have for have globallydefinedvia for locally defined for have locally defined for have for have have for childfor parentof for have for have for have
  • 164. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 163 Warranty This ERD (see Figure 71) 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. The products covered under the warranty coverage are specified directly through product warranty coverage entries. Warranty service can be provided by one or more authorized service providers. The various warranty coverages are applied to an asset through a Warranty Policy. It can be tracked throughout its life, and can be applied to fully or partially compensate the service provider for service requested in a service order. Warranties can also have coverage lists, exclusions from coverage, fault codes, trouble codes, repair operation codes, and repair operation times associated with them. A Supplier Warranty Policy is an agreement between the parts supplier and the original equipment manufacturer. Parts are covered as line items of the agreement with the rules and conditions of compensation specified. Table 71 lists the entities in this ERD and their corresponding tables. Table 71. Warranty ERD Entities and Tables Entity Table Account S_ORG_EXT Asset S_ASSET Asset Warranty Coverage S_ASSET_WRNTY Contact S_CONTACT Coverage List S_CVRG_LST Exclusion S_EXCLUSION Fault/Trouble Code S_FAULT_CODE Labor Operation Code S_LAB_OPER_CODE Labor Operation Time S_LAB_OPER_TM Order S_ORDER Order Item S_ORDER_ITEM Organization Unit S_ORG_EXT, S_PARTY Partner Labor Rate S_PRTNR_LAB_RATE Position S_POSTN Product S_PROD_INT Product Line S_PROD_LN Product Line Warranty Coverage S_PRDLN_WRNTY Product Warranty Coverage S_PROD_WRNTY User S_USER
  • 165. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 164 Warranty Coverage S_WRNTY_CVRG Warranty Coverage Attachment S_WRNT_CVRG_ATT Warranty Service Provider S_WRNTY_SRV_ORG Table 71. Warranty ERD Entities and Tables Entity Table
  • 166. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 165 Figure 71. Warranty Title:Warranty Author:Oracle,Confidential USER CONTACT ACCOUNT WARRANTY COVERAGE ATTACHMENT AGREEMENT LINEITEM LABOROPERATION TIME PARTNER LABORRATE LABOROPERATION CODE FAULT/TROUBLE CODE COVERAGELIST POSITION EXCLUSION PRODUCT ORGANIZATIONUNIT WARRANTY SERVICE PROVIDER ORDER SERVICEORDER OTHERORDER ORDERLINE ITEM PRODUCT LINE ASSET PRODUCT LINE WARRANTY COVERAGE PRODUCT WARRANTY COVERAGE WARRANTYCOVERAGE ASSET WARRANTY COVERAGE approvedby approverof heldby holderof for relatedto forparentof for subjectto specifiedfor has associatedto for for associated to assignedto for associated to for has for for belongsto for associated to for policy holderof for dealer of providedto policyholder for for has applicableto has for has associatedto for for associated to vendedby vendorof of subjectofpartof composedof asinstanceof madeinto claimedagainst appliedto roleplayedby subjectof of providedby apartofmadeupof partof composedof providedby warrantorof of subjectof by madeupof by madeupof of subject of by made upof
  • 167. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 166 Warranty Claim Warranty Claim (see Figure 72) is the dealer's or service provider's claim for repair or replacement, or compensation for nonperformance or under-performance, of an item as provided for in its warranty. Prewarranty authorization is the request submitted by the dealer or service provider to seek approval to carry out the repair work for the claim. Warranty claim items can relate to repair or replacement of certain parts of the asset. The compensation details for the failures are included. Compensation can be claimed for repair or replacement of parts, labor charges, and sublet charges. Table 72 lists the entities in this ERD and their corresponding tables. Table 72. Warranty Claim ERD Entities and Tables Entity Table Account S_ORG_EXT Agreement S_DOC_AGREE Asset S_ASSET Asset Warranty Coverage S_ASSET_WRNTY Business Unit S_BU Campaign S_SRC Contact S_CONTACT Event Activity S_EVT_ACT Exclusion S_EXCLUSION Fault/Trouble Code S_FAULT_CODE Labor Operation Code S_LAB_OPER_CODE Order S_ORDER Order Item S_ORDER_ITEM Partner Labor Rate S_PRTNR_LAB_RATE Position S_POSTN Product S_PROD_INT Service Request S_SRV_REQ Source Asset S_SRC_ASSET Source Payment S_SRC_PAYMENT Source Payment Item S_SRC_PAYMT_ITM User S_USER Validation Message S_ISS_VALDN_MSG Warranty Claim S_WRNTY_CLAIM Warranty Claim Attachment S_WRNTY_CLM_ATT
  • 168. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 167 Warranty Claim Item S_WRNTY_CLM_IT Warranty Claim Part S_WRNTY_IT_PROD Table 72. Warranty Claim ERD Entities and Tables Entity Table
  • 169. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 168 Figure 72. Warranty Claim Title:WarrantyClaim Author:Oracle,Confidential USER FAULT/TROUBLECODE SOURCEPAYMENTITEM SOURCEPAYMENT SOURCEASSETPARTNERLABORRATE LABOROPERATIONCODE WARRANTY CLAIMPART BUSINESSUNIT VALIDATION MESSAGE WARRANTYCLAIM ATTACHMENT EVENTACTIVITY EXCLUSION ORDERITEM ORDER AGREEMENT PRODUCT POSITION CONTACT ACCOUNT SERVICEREQUEST CAMPAIGN ASSET WARRANTY COVERAGE ASSET WARRANTYCLAIMITEM WARRANTYCLAIMapprovedbyapproverof submittedbysubmitterfor approvedbyapproverof submittedbysubmitterfor has prewarranty authorization for has prewarranty authorizationfor has prewarranty authorizationfor for consistsof hastroublecodefor hasfaultcodefor has for uses usedby has recallcampaignfor for subjectof associatedto for forhas forassignedto assignedtohas vendedbyvendorof forpartnerof forhas filedbyfilerof has for has for has original partfor associated to for hasclaimedagainst has claimedagainst hasforusesused for forhas hasfor hasfor for has has for for has for associatedto associatedto for composedof for
  • 170. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 169 Work Order A work order (see Figure 73) is created when a dealer performs any kind of service, which can be part of a warranty claim or a paid service on the asset. The work order is used to document all repair- related information. Work Order Items can relate to replacement of certain parts of the asset. Compensation details for failures are included. Compensation can be claimed for parts replacement, labor charges, and sublet charges. A supplier recovery claim is the claim for failed parts supplied by the supplier. The claim is based on the supplier warranty policy and made by the original equipment manufacturer to the supplier. Table 73 lists the entities in this ERD and their corresponding tables. Table 73. Work Order ERD Entities and Tables Entity Table Account S_ORG_EXT Asset S_ASSET Asset Warranty Coverage S_ASSET_WRNTY Business Unit S_BU Contact S_CONTACT Event Activity S_EVT_ACT Exclusion S_EXCLUSION Fault/Trouble Code S_FAULT_CODE Labor Operation Code S_LAB_OPER_CODE Order Item S_ORDER_ITEM Position S_POSTN Product S_PROD_INT Service Request S_SRV_REQ User S_USER Warranty Claim S_WRNTY_CLAIM Warranty Claim Item S_WRNTY_CLM_IT Work Order S_WORK_ORDER Work Order Attachment S_WRKORDR_ATT Work Order Item S_WRK_ORDR_ITEM Work Order Part S_WRKORDER_PART
  • 171. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Cross- Industry Applications 170 Figure 73. Work Order Title:WorkOrder Author:Oracle,Confidential USER EVENTACTIVITY WARRANTYCLAIM ITEM WARRANTYCLAIM WORKORDERPART WORKORDERITEM WORKORDER WORKORDER ATTACHMENT FAULT/TROUBLE CODE LABOROPERATIONCODE BUSINESSUNIT EXCLUSION ORDERITEMPRODUCT POSITION CONTACT ACCOUNT SERVICEREQUEST ASSET WARRANTY COVERAGE ASSET approvedbyapproverof submittedbysubmitterfor approvedbyapproverof submittedbysubmitterfor associatedto for forassignedto assignedtohas has originalpartfor has for assignedtofor for has hasfor for has for associatedto associatedto for forhas hasfor haspartnerfor hasfor hastroublecodefor hasfaultcodefor has prewarranty authorizationfor has prewarranty authorizationfor has for createdfor associatedto associatedtofor for consistsof for consistsof
  • 172. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 171 Entity Relationship Diagrams and Descriptions for Siebel Industry Applications The ERD descriptions and diagrams in this topic apply to Siebel Industry Applications. These applications are designed for specific industries such as the pharmaceutical, energy, insurance, and healthcare industries. They include Siebel Consumer Sector, Siebel Energy, Siebel Finance, Siebel High Tech and Manufacturing, Siebel Life Sciences, Siebel Public Sector, and Siebel Travel and Transportation, and other applications. Table 74 provides a list of ERDs in alphabetic order. Table 74. Entity Relationship Diagrams for Siebel Industry Applications ERD Name Figure Number and Page Functional Area Account Targeting Figure 74 on page 175 Consumer Sector Activity Figure 75 on page 177 Life Sciences Affiliations and Best Times Figure 76 on page 179 Life Sciences Agencies/Agent Figure 77 on page 181 Financial Services Automotive Retail Figure 78 on page 183 Automotive Brick Figure 79 on page 185 Life Sciences Clinical Study Management Figure 80 on page 188 Life Sciences Communications, Media, and Energy (CME) Account Figure 81 on page 190 CME CME Agreement Figure 82 on page 192 CME CME Alert Figure 83 on page 194 CME CME Energy Products, Service, and Usage Figure 84 on page 196 CME CME Order Management Figure 85 on page 198 CME Commercial Banking Figure 86 on page 201 Financial Services Commercial Insurance Figure 87 on page 203 Financial Services Community/Chat Discussion Figure 88 on page 205 Life Sciences Dealer Sales and Service Promotion Figure 89 on page 207 Automotive Document ID and Tax ID Figure 90 on page 209 Handheld Event Tax Administration Figure 91 on page 211 Hospitality Financial Account Figure 92 on page 213 Financial Services Financial Account Application Figure 93 on page 215 Financial Services Financial Investments Figure 94 on page 217 Financial Services Financial Products Figure 95 on page 219 Financial Services
  • 173. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 172 Financial Services Events Figure 96 on page 222 Financial Services Fleet Management Figure 97 on page 225 Transportation Flexcube Universal Banking Integration Figure 98 on page 227 Financial Services Group Insurance Policies Figure 99 on page 229 Financial Services Group Pensions Figure 100 on page 231 Financial Services Health Provider and Provider Group Figure 101 on page 233 Financial Services High Tech Special Pricing Authorization Figure 102 on page 235 Sales Hospitality Category Figure 103 on page 237 General Institutional Sales Figure 104 on page 239 Financial Services Insurance Claims Figure 105 on page 242 Financial Services Insurance Policies Figure 106 on page 244 Financial Services Life Insurance Policy Figure 107 on page 246 Financial Services Loyalty Figure 108 on page 250 General Loyalty Flowchart and Formula Figure 109 on page 252 General Managed Care Figure 110 on page 254 Life Sciences Medical Education Event Management Figure 111 on page 256 Life Sciences Objectives Figure 112 on page 258 Consumer Sector Personalized Content Delivery Figure 113 on page 260 Life Sciences Public Sector Benefit Case Management Figure 114 on page 263 Public Sector Public Sector Case Lead Management Figure 115 on page 266 Public Sector Public Sector Child Welfare Figure 116 on page 268 Public Sector Public Sector Contact Identity Figure 117 on page 270 Public Sector Public Sector Evidence Management Figure 118 on page 272 Public Sector Public Sector Incident Management Figure 119 on page 274 Public Sector Public Sector Service Provider and Referral Management Figure 120 on page 276 Public Sector Real-Time Scheduler Integration Figure 121 on page 278 Service Routes and Best Call Hours Figure 122 on page 280 Sales Sales Volume Planning Figure 123 on page 282 Consumer Sector Sample Management Figure 124 on page 284 Life Sciences Special Rate List Figure 125 on page 286 Communications Table 74. Entity Relationship Diagrams for Siebel Industry Applications ERD Name Figure Number and Page Functional Area
  • 174. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 173 Syndicated Data Figure 126 on page 288 Life Sciences Teller Administration Figure 127 on page 290 Financial Services Territory Alignment–Quota Assignment Figure 128 on page 292 Sales Territory Management - Consumer Sector Figure 129 on page 294 Service Territory Management - Life Sciences Figure 130 on page 296 Sales Universal Customer Master Figure 131 on page 298 General Vehicle Figure 132 on page 300 Automotive Vehicle Collection Figure 133 on page 302 Automotive Vehicle Financing Figure 134 on page 304 Automotive Vehicle Sales Figure 135 on page 306 Automotive Table 74. Entity Relationship Diagrams for Siebel Industry Applications ERD Name Figure Number and Page Functional Area
  • 175. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 174 Account Targeting This ERD (see Figure 74) 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 75 lists the entities in this ERD and their corresponding tables. Table 75. Account Targeting ERD Entities and Tables Entity Table Account S_ORG_EXT, S_PARTY Criteria S_CG_QUERY_ITEM Employee S_CONTACT, S_PARTY Objective S_SRC Query S_CG_QUERY Route S_ACCNTRT
  • 176. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 175 Figure 74. 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 combine consist of appear on
  • 177. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 176 Activity This ERD (see Figure 75) 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 76 lists the entities in this ERD and their corresponding tables. Table 76. Activity ERD Entities and Tables Entity Table Account S_ORG_EXT, S_PARTY Activity S_EVT_ACT Contact S_CONTACT Employee S_EMP_PER, S_CONTACT, S_PARTY Indication S_PROD_APPLCTN Issue S_PROD_ISS Person S_CONTACT, S_PARTY Product S_PROD_INT
  • 178. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 177 Figure 75. Activity Title:Activity Author:Oracle,Confidential SIGNATURE ACCOUNT ISSUE INDICATION PRODUCT DETAIL PROMOTIONALITEM SAMPLE PERSON CONTACT EMPLOYEE ACTIVITY MEETING ATTENDEE/INVITEE CONTACTCALL ATTENDEECALL ACCOUNTCALL have belongs capturedfor contain composedof affiliatedwith subjectof for for subjectof considerationon subjectto responsiblefor responsibilityof subjectto considerationon discussedat discussionoffor contains invitedto/attend invite/attend personallistof belongto subjectof for sampledat samplingof droppedat for
  • 179. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 178 Affiliations and Best Times This ERD (see Figure 76) 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 77 lists the entities in this ERD and their corresponding tables. Table 77. 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 S_CONTACT, S_PARTY Person Position S_POSTN_CON Position S_POSTN, S_PARTY Type S_PARTY_PER_DTL
  • 180. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 179 Figure 76. 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
  • 181. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 180 Agencies/Agent This ERD (see Figure 77) 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 78 lists the entities in this ERD and their corresponding tables. Table 78. 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
  • 182. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 181 Figure 77. 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
  • 183. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 182 Automotive Retail This ERD (see Figure 78) 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 might 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 79 lists the entities in this ERD and their corresponding tables. Table 79. 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
  • 184. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 183 Figure 78. Automotive Retail SALESSTEP GOAL POSITION PERSON OTHER PERSON EMPLOYEE OPPORTUNITY SALESSTEP ASSET OTHERASSETVEHICLE ACTIVITY STOREBUDGET/FORECAST SHOWROOMLOG ENTRY SALESSTEP PERIOD ORGANIZATION OTHER ORGANIZATION DEALER/PARTNER OPPORTUNITY EMPLOYEE BUDGET/FORECAST incontextof subjectof instanceof usedby of has ownerof owned by responsible for handled by on involverofhastrade-inof tradedin for sourceof of for for subjectof of usedin ownerof assignedto presentedin presented visibleto visibilityof ofhas for in setby set definedfor subjectof definedfor subjectof assignedto ownerof submittedby submitterof responsiblefor responsibilityof for setup
  • 185. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 184 Brick This ERD (see Figure 79) 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 80 lists the entities in this ERD and their corresponding tables. Table 80. Brick ERD Entities and Tables Entity Table Activity S_EVT_ACT Account Address S_CON_ADDR Address S_ADDR_PER Contact S_CONTACT, S_PARTY Organization S_ORG_EXT, S_PARTY Position S_POSTN Region S_REGION Syndicated Data S_SYND_DATA
  • 186. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 185 Figure 79. Brick POSITION ACCOUNTADDRESSCONTACTACTIVITY ORGANIZATION ADDRESS SYNDICATEDDATA REGION BRICKOTHERREGION holdersof heldby assignedto locatedat for assignedto definedby for parentof childof parentof childof for locatedat for subjectof for sourceof
  • 187. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 186 Clinical Study Management This ERD (see Figure 80) 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 126. Table 81 lists the entities in this ERD and their corresponding tables. Table 81. Clinical Study Management ERD Entities and Tables Entity Table Account S_ORG_EXT, S_PARTY 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 Contact S_CONTACT, S_PARTY 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
  • 188. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 187 Trip Report S_EVT_ACT Visit S_EVT_ACT Table 81. Clinical Study Management ERD Entities and Tables Entity Table
  • 189. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 188 Figure 80. Clinical Study Management Title:ClinicalStudyManagement Author:Oracle,Confidential PROJECT SUBCONTRACTOR PROJECT SUBCONTACTOR CONTACT PROJECT ACCOUNT CONTACT APPLICATION AFFILIATIONADDRESS SUBJECT STATUS TEMPLATEVERSION PRODUCT DESIGN SUBJECT TEMPLATE TEMPLATE VISIT SUBJECT CLINICAL PAYMENT ACTIVITY TRIP REPORT VISIT POSITION PROGRAM PROTOCOL REGION PROTOCOLSITE defined subjectof usedby using applied to having belongto apartnerfor subcontractorfor subcontractedto composedof forcontactfor having belongsto consistsof for having having associatedto havingstudyconductedby foraffiliatedto forlocatedat forprimaryinvestigator having forhaving having composedof for associatedwith madefor subjectof madeby involvedin sourceof composedof for sourceof participantat for recipientof paidto composedoffor teamcomposedof teammembersof teammembersof havingteamof for participatingin participantof conductedat generatorofgeneratedby for associatedwith having usedby for consistingof
  • 190. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 189 Communications, Media, and Energy (CME) Account This ERD (see Figure 81) 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 82 lists the entities in this ERD and their corresponding tables. Table 82. 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 Contact S_CONTACT, S_PARTY Exemption Profile S_SUBSIDY Financial Profile S_FINAN_PROF Trouble Ticket S_SRV_REQ
  • 191. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 190 Figure 81. Communications, Media, and Energy (CME) Account BILLING PROFILE STATEMENT INVOICE EXEMPTION PROFILE FINANCIAL PROFILE ACCOUNT CUSTOMER ACCT PREMISE ACCT BILLING ACCT SERVICE ACCT ACTIVITY TROUBLE TICKET CONTACT ADDRESS PREMISE SERVICE ADDR located at for child of parent of for associated with located at for for described 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
  • 192. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 191 CME Agreement This ERD (see Figure 82) 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 83 lists the entities in this ERD and their corresponding tables. Table 83. 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
  • 193. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 192 Figure 82. CME Agreement Title:CMEAGREEMENTS Author:Oracle.Confidential QUOTEITEM QUOTE EVENTACTIVITYAGREEMENT NOTE AGREEMENT TERMS AGREEMENT ACCOUNTS belongsto has childof parentof hasa associated with consistsof partof associated with tracked by associated with for forsubjectof childof parentof boundby governs
  • 194. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 193 CME Alert This ERD (see Figure 83) illustrates how credit and fraud alerts are managed for communications and utilities customers. 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 types of alerts. Table 84 lists the entities in this ERD and their corresponding tables. Table 84. CME Alert ERD Entities and Tables Entity Table Account S_ORG_EXT, S_PARTY Activity S_EVT_ACT Alert Attachment S_ALERT_ATT_CUT Alerts S_ALERT_CUT Asset S_ASSET Bill Transactions S_BILL_MAINT Billing Profile S_INV_PROF Energy Consumption S_USAGE Fraud Profile S_FRD_PROF_CUT
  • 195. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 194 Figure 83. CME Alert Title : CME Alert Author : Oracle, Confidential BILLING PROFILE ACTIVITY ASSET METER EQUIPMENT OTHER ENERGY CONSUMPTION USAGE BILL ACCOUNT ALERT ATTACHMENT INVOICE LINE ITEMS ALERT FRAUD PROFILE created for has for has part of made up of for described by subject for for consists subject of on for attached to generates for for associated with for attached to generated by has child of parent of child of parent of
  • 196. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 195 CME Energy Products, Service, and Usage This ERD (see Figure 84) 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 CRM 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 85 lists the entities in this ERD and their corresponding tables. Table 85. CME Energy Products, Service, and Usage ERD Entities and Tables Entity Table Account S_ORG_EXT, S_PARTY 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 Payment S_SRC_PAYMENT Period S_PERIOD Product: External S_PROD_EXT Product: Internal S_PROD_INT Service Instance S_ASSET Usage S_USAGE
  • 197. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 196 Figure 84. CME Energy Products, Service, and Usage Title:CMEEnergyProducts,Services,andUsage Author:Oracle,Confidential USAGEINVOICE ADJUSTMENT PAYMENT INVOICEITEM INVOICE SERVICEINSTANCE PRODUCT EXTERNALPRODUCT INTERNALPRODUCT ACCOUNT BILLINGCUSTOMERSERVICE PERIOD ASSET METER OTHER EQUIPMENT EXTERNALPRODUCT PRESENCE for subject of associated with for for recorded in for recorded in recorded for displayer of used by consumer of for subjectof for subject of lineitemof made of subjectof for madeby responsiblefor service at of madeupof isa ismadeinto of subjectof at subjectof
  • 198. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 197 CME Order Management This ERD (see Figure 85) 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. Order synchronization failures can also be tracked. Table 86 lists the entities in this ERD and their corresponding tables. Table 86. CME Order Management ERD Entities and Tables Entity Table Account S_ORG_EXT, S_PARTY Asset S_ASSET Asset Attribute S_ASSET_XA Order S_ORDER Order Item S_ORDER_ITEM Order Item Attribute S_ORDER_ITEM_XA Product or Service S_PROD_INT Quote S_DOC_QUOTE Quote Item S_QUOTE_ITEM Quote Item Attribute S_QUOTE_ITEM_XA Failed Service Order S_SRV_ORD_FAIL Service Request S_SRV_REQ
  • 199. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 198 Figure 85. CME Order Management Title : CME Order Management Author : Oracle, Confidential FAILED SERVICE ORDER SERVICE REQUEST ACCOUNT OTHER ACCOUNT SERVICE ACCOUNT BILLING ACCOUNT QUOTEORDER QUOTE ITEMORDER ITEM ASSET ORDER ITEM ATTRIBUTE ASSET ATTRIBUTE QUOTE ITEM ATTRIBUTE PRODUCT OR SERVICE for associated to for associated to associated to has an instance of made into part of composed of part of composed of serviced by associated with serviced by associated with billed by associated with created from leads to for composed of for composed of of subject of of quoted for purchase on for subject of of subject of subject of ordered on for provision of subject of of subject of instance of subject ofinstance of subject of billed by associated with
  • 200. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 199 Commercial Banking This ERD (see Figure 86) 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 87 lists the entities in this ERD and their corresponding tables. Table 87. 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 Employee S_EMP_PER, S_CONTACT, S_PARTY 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 Organization S_ORG_EXT, S_PARTY Person S_CONTACT, S_PARTY Portfolio Type S_MKT_SEG Product S_PROD_INT Rating S_OPTY_ORG_FNXM Revenue S_REVN Revenue S_REVN
  • 201. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 200 Trailing Document S_OPTY_DOC Underwriting Standard S_MKT_SEG_VAL Table 87. Commercial Banking ERD Entities and Tables Entity Table
  • 202. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 201 Figure 86. Commercial Banking Title:CommercialBanking Author:Oracle,Confidential ACTIVITY FACILITYORGANIZATION SYNDICATEGUARANTOR ORGANIZATION RATINGEXCEPTION TRAILING DOCUMENT CORRESPONDENCEATTACHMENTNOTE FACILITY UNDERWRITING STANDARD BORROWER EMPLOYEE OPPORTUNITYDETAIL REQUESTPOLICY EXCEPTION DECISION KEYCREDIT ISSUES UNDERWRITING STANDARD APPROVAL APPROVAL LEVEL APPROVAL STAGE OPPORTUNITY PORTFOLIOTYPE FEE COLLATERAL PRODUCT FACILITYDETAIL PRICE POLICY COVENANT FINANCIALACCOUNT generates generatedby for generates representedby participatedas participatedin subjectof based on associated with representedby appliedas areportto aparentto ownerof ownedby for has for subjectof for subjectto of subjectof of has of subjectof of subjectof of has for subject of for subject of partof includes issuedby issuesof for has subjectto needfor belongsto for of has partof madeupof subjectto requiredby has associated with partof madeup
  • 203. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 202 Commercial Insurance This ERD (see Figure 87) 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 88 lists the entities in this ERD and their corresponding tables. Table 88. 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
  • 204. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 203 Figure 87. Commercial Insurance Title : Commercial Insurance Author :Oracle, Confidential INSURANCE COVERAGE INSURED ITEM ASSET INSURANCE POLICY GROUP CLASS REGIONCLASS LOCATION POLICY CONTACT CONTACT belongs to covers covers covered by part of made up of insured as for associated with subject of part of covers for subject of of subject of for associated with
  • 205. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 204 Community/Chat Discussion This ERD (see Figure 88) 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 89 lists the entities in this ERD and their corresponding tables. Table 89. Community Chat/Discussion ERD Entities and Tables Entity Table Contact S_CONTACT, S_PARTY Discussion Post S_MESG_BRD_LS Product S_PROD_INT Registration S_TOPIC_CON_LS Topic S_TOPIC_LS
  • 206. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 205 Figure 88. Community/Chat Discussion Title : Community Chat/Discussion Author : Oracle, Confidential PRODUCT DISCUSSION POST TOPIC REGISTRATION CONTACT of registered for for registration of about subject of involving posted to for subject of authored by author of
  • 207. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 206 Dealer Sales and Service Promotion This ERD (see Figure 89) illustrates how a call list can be created by searching on specific attributes of vehicle, person, sales history, or service history. A person can 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 might be due), and so on. The dealer can launch a campaign for sales or service specials and include one or more call lists to be targeted through the campaign. Table 90 lists the entities in this ERD and their corresponding tables. Table 90. 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 Marketing Event or Activity S_SRC Person S_CONTACT, S_CONTACT_ATX Vehicle S_ASSET, S_ASSET_ATX
  • 208. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 207 Figure 89. 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
  • 209. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 208 Document ID and Tax ID This ERD (see Figure 90) 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 can 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 91 lists the entities in this ERD and their corresponding tables. Table 91. Document ID and Tax ID ERD Entities and Tables Entity Table Account S_ORG_EXT, S_PARTY Authorized Product S_ORG_PROD Document Mask Component S_DOC_NUM_SEG Document Types S_DOC_NUM Document Values S_DOC_NUM_VAL Invoice S_INVOICE Order S_ORDER Order Item S_ORDER_ITEM Price List S_PRI_LST Price List Item S_PRI_LST_ITEM
  • 210. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 209 Figure 90. Document ID and Tax ID Title : Document ID and Tax ID Author : Oracle, Confidential ORDER ITEM AUTHORIZED PRODUCTPRICE LIST ITEM PRICE LIST ACCOUNT ORDER INVOICE DOCUMENT MASK COMPONENTS 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
  • 211. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 210 Event Tax Administration This ERD (see Figure 91) 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 might be taxable. The taxes and service charges linked with the charge code apply to the product. Table 92 lists the entities in this ERD and their corresponding tables. Table 92. 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 S_PRI_LST 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
  • 212. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 211 Figure 91. 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
  • 213. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 212 Financial Account This ERD (see Figure 92) 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. Table 93 lists the entities in this ERD and their corresponding tables. Table 93. 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 S_CONTACT, S_PARTY Contact Profitability S_CON_PRFTBLTY Fee S_FN_ACCNT_FEE Financial Account S_ASSET Financial Account Contact S_ASSET_CON Financial Transaction S_FN_ACCNT_TXN Note S_NOTE_ASSET Organization Unit S_ORG_EXT, S_PARTY Product S_PROD_INT Schedule S_FN_ACCNT_SCHD Service Request S_SRV_REQ
  • 214. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 213 Figure 92. Financial Account Title:FinancialAccount Author:Oracle,Confidential ASSIGNMENT GROUP(TERRITORY) CONTACT ADDRESS PERSONAL ADDRESS BUSINESS ADDRESS BALANCE HISTORY ATTACHMENT NOTE ACCOUNT PROFITABILITY ASSET RELATIONSHIP ACCOUNT ANALYSIS SERVICE REQUEST FINANCIAL TRANSACTION ORGANIZATIONUNIT EXTERNAL ORGANIZATION UNIT INTERNAL ORGANIZATION UNIT PRODUCT ACTIVITY CONTACT PROFITABILITY AUTHORIZATION FINANCIALACCOUNTCONTACT ACCOUNT AGGREGATION SERVICE FEE SCHEDULE FINANCIALACCOUNT EXTERNALACCOUNT INTERNALACCOUNT forproblemswith subjectof forproblemswith subjectof definedfor subjectof of subjectof usedby uses for subjectof for subjectof for subjectof for subjectof for subjectof for subjectof of subjectof for subjectof participantin targetof for associated with subject of for of associated with for associated with for subjectof located at for currentlyowned by owner of currentlyownedby ownerof
  • 215. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 214 Financial Account Application This ERD (see Figure 93) 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 94 lists the entities in this ERD and their corresponding tables. Table 94. 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 Contact S_CONTACT, S_PARTY Credit Report S_FN_CRDT_RPT Credit Report Item S_CRDT_RPT_ITEM Fee S_FN_OFFR_FEE Financial Account S_ASSET Inc. Exp. Contact S_FN_INCEXP_CON Income/Expense S_FN_INCM_EXP Note S_NOTE_OPTY Organization S_ORG_EXT, S_PARTY Product S_PROD_INT Quote S_DOC_QUOTE Sales Stage S_STG Trailing Document S_OPTY_DOC
  • 216. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 215 Figure 93. Financial Account Application Title:FinancialAccountApplication Author:Oracle,Confidential CREDIT REPORTITEM #SEQ_NUM CREDITREPORT PRODUCT DISCLOSURE APPROVAL INC.EXP. CONTACT ASSETLIAB. CONTACT ADDRESS APPLICATIONCONTACT LENDERAPPLICANT SALES STAGE APPLICATION ORGANIZATION APPLICATIONPRODUCTNOTE ASSESSMENT VALUE FINANCIAL ACCOUNT FEECOLLATERAL ASSETLIABILITY INCOME/EXPENSE ASSESSMENT ACTIVITY OTHERACTIVITY STATEMENT TRAILING DOCUMENT QUOTE CONTACT PRODUCT inreferencetosubjectof supported by insupport of belong to contain acknowledgedby acknowledgeroffor has for based on with has of incurred by with associated to of associated with for locatedat for locatedat has for associated with has for uses associated with has associated with has partof generates for based on for based on for subject to basedon generates generates generated by for subjectof for subjectof for acomponentof uses usedby hasa on for subjectof reportedin toreview for has for has reportedin toreview for subject of
  • 217. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 216 Financial Investments This ERD (see Figure 94) 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 95 lists the entities in this ERD and their corresponding tables. Table 95. Financial Investments ERD Entities and Tables Entity Table Contact S_CONTACT,S_PARTY Distribution S_FNSEC_DSTRBTN External Organization S_ORG_EXT, S_PARTY Earning S_FNSEC_ERNG Financial Account S_ASSET Holding S_FN_HLDNG Industry S_INDUST Literature S_LIT Security S_PROD_INT Transaction S_FN_ACCNT_TXN
  • 218. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 217 Figure 94. Financial Investments Title : Financial Investments Author :Oracle, Confidential DISTRIBUTION LITERATURE TRANSACTIONHOLDING CONTACT FINANCIAL ACCOUNT EARNING CAPITAL GAINS DIVIDEND SECURITY STOCK FUND INTERNAL EXTERNAL BOND INDUSTRY EXTERNAL ORGANIZATION PUBLIC COMPANY INSTITUTIONAL INVESTOR 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
  • 219. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 218 Financial Products This ERD (see Figure 95) 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 96 lists the entities in this ERD and their corresponding tables. Table 96. 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 Product Line S_PROD_LN Rate S_PROD_RATE
  • 220. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 219 Figure 95. Financial Products Title : Financial Products Author :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
  • 221. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 220 Financial Services Events This ERD (see Figure 96) 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 97 lists the entities in this ERD and their corresponding tables. Table 97. 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 Literature Item S_LIT Location Room S_EVTLOC_ROOM Marketing Event or Activity S_SRC Organization Unit S_ORG_EXT, S_PARTY Person S_EMP_PER, S_CONTACT, S_PARTY Position S_POSTN Product S_PROD_INT Product Line S_PROD_LN 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
  • 222. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 221 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 97. Financial Services Events ERD Entities and Tables Entity Table
  • 223. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 222 Figure 96. Financial Services Events Title:FinancialServicesEvents Author:Oracle,Confidential TRAVEL PARTICIPANT EVENTCOST REVENUE COST TRAVELPLAN EVENT REGISTRATION ATTENDEE CANCELLED REGISTRANT WAITLIST REGION INDUSTRY ROOMAVAIL EQUIPMENT PRODUCTLITERATURE ITEM PRODUCTLINE POSITION LOCATIONROOM EQUIPMENT REQUIREMENT ACTIVITY VENUE REVIEW VENUE SERVICE VENUE OFFER EVENTVENUE VENDOR REVIEW VENDOR SERVICE VENDOR OFFER PERSON ORGANIZATIONUNIT INVESTING COMPANY OTHER ORGANIZATION UNIT EVENTLOCATION VENUEOTHERLOC MARKETINGEVENTORACTIVITY SUBEVENTPARENTEVENTEVENTSESSION VENDOR participates hasincludes memberof servicedby services associatedwith has associatedwith has includes partof for has for subjectoffor subjectof inviterof invitedto staffedby onstafffor subjectof dealswith subjectof dealswith subjectof dealswith in supplierof heldat locationof available in equipped with relevantto promoted via subjectof dealswith responsible for responsibilityof requiredby inneedof for subject of reviewedbyreviewerof for subjectof of for locationof heldat for subjectof offeredat providerof offeredat subjectof from participated as partof composed of partof composed of reviewedby reviewerof for subjectof offeredby providerof offeredby providerof
  • 224. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 223 Fleet Management Fleet Management enables transportation management customers to perform order capture, rating, and order management of transportation orders. Figure 97 shows the Fleet Management ERD. Return Route Orders functionality allows multiple stops to be created for a given location and allows both origin and destination locations to reference the same location. Order Revision Enhancements functionality provides stricter constraints for revising, rejecting, and cancelling orders. Users will not be able to revise any inactive order or rejected order. Furthermore, users will not be able to revise any order in which there is a relationship with a cancelled order. After completing the order, the customer service representative submits the order to Oracle Transportation Management. Oracle Transportation Management takes over the fulfillment of the order from the Siebel application. The marketing department of the transportation provider defines the targeted lanes; that is, the lanes where the company wants to focus on selling transportation routes. A lane is a route between an origin and a destination, using a given line of business. Whenever Oracle Transportation Management sends information that an order is complete, the Siebel application adds information about this order to its order history. The order history aggregates weekly orders for each account for each lane. Table 98 lists the entities in this ERD and their corresponding tables. Table 98. Fleet Management ERD Entities and Tables Entity Table Account S_ORG_EXT Address S_ADDR_PER Business Unit S_BU Contact S_CONTACT Favorite Product Action S_PRDFAVITM_ACT Favorite Product Item S_QUOTE_ITEM Fleet Management Location S_LOCATION Fleet Management Location Role S_LOC_ROLE Fleet Management Order S_ORDER Fleet Management Order Detail S_ORDER_FM_DTL Fleet Management Order History S_FM_ORDER_HIST Order Account S_ORG_EXT Order Item S_ORDER_ITEM Order Item Stop S_ORDITEM_STOP Order Stop S_ORDER_STOP Order Stop Action S_ORDSTOP_ACTN Order Stop Detail S_ORDERSTOP_DTL
  • 225. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 224 Quote S_DOC_QUOTE Quote Item S_QUOTE_ITEM Rating Solution S_RTNG_SLTN Rating Solution Detail S_RTNG_SLTN_DTL Rating Solution Detail Pricing S_SLTN_DTL_PRC Targeted Lane S_TARGETED_LANE Table 98. Fleet Management ERD Entities and Tables Entity Table
  • 226. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 225 Figure 97. Fleet Management Title:FleetManagement Author:Oracle,Confidential CONTACT FLEETMANAGEMENT ORDERHISTORY TARGETEDLANE FAVORITE PRODUCT ACTION FAVORITE PRODUCTITEM FLEET MANAGEMENT ORDERDETAIL ACCOUNT BUSINESS UNIT ADDRESS QUOTE ITEM QUOTE ORDERSTOPACTION ORDER STOPDETAIL ORDERITEMSTOP FLEET MANAGEMENT LOCATIONROLE ORDERSTOP RATING SOLUTION DETAIL PRICING RATING SOLUTION DETAIL RATING SOLUTION ORDERITEM ORDER FLEETMANAGEMENTORDEROTHER ORDER FLEET MANAGEMENT LOCATION forhas placedbyownerfor hasprimaryfor forhas ownedbyownerof hasprimaryfor forbelongsto hasprimaryfor has associated to associated tohas for has has for has for has destination for has originfor for has for has for associated to for associated to primarystopfor has for has for has for has for has primaryfor has for has for has for has for has for composedof composedof for
  • 227. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 226 Flexcube Universal Banking Integration The Flexcube Universal Banking Integration ERD (see Figure 98) describes the integration of Siebel CRM with an external banking system. It provides new features, such as financial plans, goals, and limits that can be specified for a customer. Financial plans are investment plans created for customers after analyzing the customer’s financial position, expected future cash-flows, inflation, returns, and goals. Financial goals include but are not limited to education, retirement, investment, buying property, and so forth. The individual's goals are used as guidelines to map a course of action to reach those goals. A financial limit specifies the total liabilities of the customer arising out of the credit facilities used by the customer. A customer can also provide financial mandates, which are instructions to initiate payment transactions at a predetermined future time or frequency or for such future transactions. Table 99 lists the entities in this ERD and their corresponding tables. Table 99. Flexcube Universal Banking Integration ERD Entities and Tables Entity Table Account S_ORG_EXT, S_ORG_EXT_FNX Branch S_ORG_EXT Contact S_CONTACT, S_CONTACT_FNX Financial Account S_ASSET, S_FN_ACCNT1_FNX Financial Goal S_FN_GOAL Financial Limit S_FN_LIMIT Financial Mandate S_FN_MANDATE Financial Plan S_FN_PLAN Offer S_DMND_CRTN_PRG Party S_PARTY Product S_PROD_INT
  • 228. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 227 Figure 98. Flexcube Universal Banking Integration Title:FlexcubeUniversalBankingIntegration Author:Oracle,Confidential FINANCIAL ACCOUNT OFFER BRANCH PARTY ACCOUNT CONTACT PRODUCT FINANCIALGOAL FINANCIALPLAN FINANCIAL MANDATE FINANCIAL LIMIT sub-limitfor partof for has for has madeby makerof ownedby ownerof heldat for ownedby ownerof associatedto for associatedtofor for subjectof for subjectof issuedby issuerof specifiedfor subjectto availableto has
  • 229. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 228 Group Insurance Policies This ERD (see Figure 99) 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 employee’s 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 100 lists the entities in this ERD and their corresponding tables. Table 100. 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 Contact S_CONTACT,S_PARTY Coverage Role S_FN_CVRG_ROLE Employee Class S_FN_GRP_CLASS Instance Attribute S_ASSET_ITEM_XA Organization Unit S_ORG_EXT, S_PARTY 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 Product Internal S_PROD_INT Rate Band S_PROD_RATE
  • 230. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 229 Figure 99. Group Insurance Policies Title:GroupInsurancePolicy Author:Oracle,Confidential PRODUCT ENROLLMENT PRIMARYPOLICYMEMBER PRODUCTFOR MEMBERS EMPLOYEE CLASS PRODUCT ATTRIBUTECLASS INSTANCEATTRIBUTE CLASS ATTRIBUTE PRODUCT COMPONENT PRODUCT INSTANCE RATE BAND PRODUCTCLASS PRODUCTCLASSRATE POLICYINSTANCE GROUPLIFEOTHEREMPLOYEE BENEFITS GROUPHEALTH ORGANIZATIONUNIT EXTERNALORGANIZATIONUNIT PRODUCTINTERNAL CENSUS DETAIL CENSUS CONTACT COVERAGEROLE primaryof of partof madeupof partof madeupof basedon for appliedto subjectto for subjectof partof madeup of beneficiaryof benefits under for for subjectof for has usedfor uses for has belongsto has belongs to has availablefor has partof madeupof for subjectof part of has partof has partof madeupof basedon basis of ofhas has of associated with has belongs to has for has of has based on basis of based on basis of of has basedon basisof ownerof ownedby for has for subjectof for subjectof
  • 231. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 230 Group Pensions This ERD (see Figure 100) 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 101 lists the entities in this ERD and their corresponding tables. Table 101. 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 Person S_CONTACT, S_PARTY
  • 232. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 231 Figure 100. Group Pensions Title : Group Pensions Author : 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
  • 233. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 232 Health Provider and Provider Group This ERD (see Figure 101) illustrates how Siebel Financial Services supports generation of health- 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 102 lists the entities in this ERD and their corresponding tables. Table 102. Health Provider and Provider Group ERD Entities and Tables Entity Table Contact S_CONTACT,S_PARTY Encounter S_FN_HLTH_ENCTR Health Product S_PROD_INT Language S_CONTACT_FNXM Organization S_ORG_EXT, S_PARTY Payment S_SRC_PAYMENT Provider Group Schedule S_ORG_TIME Provider Schedule S_CON_LOCTN Specialty S_CONTACT_FNXM
  • 234. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 233 Figure 101. Health Provider and Provider Group Title : Health Provider/Provider Groups Author :Oracle, Confidential LANGUAGE PROVIDER GROUP SCHEDULE ORGANIZATION EXTERNAL ORGANIZATION UNIT PROVIDER GROUP PAYMENT HEALTH PRODUCT SPECIALTYPROVIDER SCHEDULE ENCOUNTER CONTACT PATIENT PROVIDER made by make in subject of provides provided by employs part of involves part of delivered by delivers made to beneficiary of spoken by speaks for specialized in belongs to subject of serve serve at belongs to subject of involves part of
  • 235. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 234 High Tech Special Pricing Authorization This ERD (see Figure 102) 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 103 lists the entities in this ERD and their corresponding tables. Table 103. High Tech Special Pricing Authorization ERD Entities and Tables Entity Table Account S_ORG_EXT Address S_ADDR_PER Agreement S_DOC_AGREE 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
  • 236. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 235 Figure 102. High Tech Special Pricing Authorization Title:HighTechSpecialPricingAuthorization Author:Oracle,Confidential ADDRESS PRODUCT POINTOFSALEITEM OTHERPOS ITEM CLAIMITEM POINTOF SALE HEADER OPPORTUNITY OTHER OPPORTUNITY DESIGN REGISTRATION QUOTELINE ITEM ACCOUNT ENTITLEMENT PRODUCTPRICE ENTITLEMENT AGREEMENTMEET COMPETITION QUOTE for subjectof for located at designed for subjectof speciallyquotedfor subjectof for subjectof referencing support for for having for composed of for associated with createdfor subjectof partof composed of initiated by subjectof for subjectof for having for madeup of for associated with
  • 237. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 236 Hospitality Category This ERD (see Figure 103) 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 104 lists the entities in this ERD and their corresponding tables. Table 104. 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 Product or Service S_PROD_INT Tax/Service List S_PRI_LST
  • 238. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 237 Figure 103. Hospitality Category Title : Hospitality Category Author : Oracle, Confidential OPPORTUNITY OPPORTUNITY 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 of parent of for subject of associated with for related with subject of child of parent of child of parent of
  • 239. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 238 Institutional Sales This ERD (see Figure 104) 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 105 lists the entities in this ERD and their corresponding tables. Table 105. Institutional Sales ERD Entities and Tables Entity Table Activity S_EVT_ACT Call List S_CALL_LST Contact S_CONTACT, S_PARTY Employee S_EMP_PER, S_CONTACT, S_PARTY Industry S_INDUST Literature S_LIT Organization Unit S_ORG_EXT, S_PARTY Position S_POSTN, S_PARTY Product S_PROD_INT Product Line S_PROD_LN
  • 240. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 239 Figure 104. Institutional Sales Title:InstitutionalSales Author:Oracle,Confidential ORGANIZATIONUNIT EXTERNAL ORGANIZATION UNIT CALLLIST INDUSTRY LITERATURE EMPLOYEEACTIVITY PRODUCTLINE CONTACT POSITION PRODUCT SECURITY issued by issuesholds held by author of authoredby uses attachedtocovers subject of about subjectof associated with subject of subject of part of owns ownedby covers covered by covers coveredby interestedin objectof interestof interested in objectofinterestof
  • 241. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 240 Insurance Claims This ERD (see Figure 105) 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 106 lists the entities in this ERD and their corresponding tables. Table 106. 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_CLAIM S_INSCLM_FRAUD S_INSCLM_SBRGTN S_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
  • 242. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 241 Loss Event S_INSCLM_EVT Organization S_ORG_EXT S_PARTY S_ORG_EXT_FNX Party S_PARTY Payment S_SRC_PAYMENT S_SRCPAYMT_CON S_SRCPAYMT_ORG S_INVC_PAYMENT Position S_POSTN, S_PARTY Reserve Code S_INS_RSRV_CODE Service Request S_SRV_REQ, S_SRV_REQ2_FNX Table 106. Insurance Claims ERD Entities and Tables Entity Table
  • 243. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 242 Figure 105. Insurance Claims 7LWOH,QVXUDQFHODLPV $XWKRUOracleRQILGHQWLDO /$,03$0(17 3$0(17 ,192,(/,1(,7(0 '()$8/7 29(5$*( /2662'( 29(5$*( 5(6(59(2'( /266 2'( /$,0$2817 ,192,( $7,9,7 $66,*10(17 *52837(55) ,1685$1( 32/,,7(0 ,1685$1( 32/, 3$57 217$7 326,7,21 25*$1,=$7,2N /$,03523(57 /$,0 217$7 ,1-85 /$,0),/( $77$+0(17 /$,0 $335$,6$/ $77$+0(17 /$,0 $335$,6$//$,0(/(0(17 /$,0 '280(17 /$,0 5(29(5 /266 (9(17 6(59,( 5(48(6T ,1685$1(/$,0 TTIRU QDPHGDV RZQHURI RZQHG E PDGH WR SDHH IRU PDGH DJDLQVW UHODWHGWRLQYROYHG LQ VXEMHFW RI DVVLJQHG WR VXEMHFW RI FRYHUHG E VXEMHFW RI SDHH IRU PDGH WR IRU VXEMHFWRIPDGHDJDLQVW SDLG WKURXJK SDLGDJDLQVW VXEMHFWRI DVVRFLDWHG ZLWK VXEMHFW RI DVVRFLDWHG ZLWK VXEMHFW RI DVVRFLDWHG ZLWK VXEMHFW RI DVVRFLDWHG ZLWK VXEMHFW RI EHORQJWR FRQWDLQ DSSOLFDEOH WR VXEMHFW RI UHIHUHQFHGE SHUWDLQWR UHVSRQVLEOH IRU UHVSRQVLELOLW RI SHUWDLQ WR UHIHUHQFHG E EHORQJV WR VXEMHFW RI DVVRFLDWHGWR DSSOLFDEOH WR FRYHUDJH IRU IRU LQVXUHG E LQVXUHURI LQVXUHGE LQVXUHURI IRU VXEMHFW RI IRUQDPHGDV DSSURYHG E DSSURYHU RI DVVRFLDWHG ZLWK VXEMHFW RI DVVRFLDWHG ZLWK VXEMHFW RI DVVRFLDWHGWR LQYROYHGZLWK LQFXUUHG E VXEMHFW WR DVVRFLDWHG ZLWK VXEMHFW RI RQ VXEMHFW RI DVVRFLDWHG WR VXEMHFWRI DVVRFLDWHG ZLWK VXEMHFW RI FRYHUHGE FRYHUHU RI PDGH DJDLQVW VXEMHFWRI IRU VXEMHFW RI DVVRFLDWHG ZLWK VXEMHFWRI VXEMHFW WR SDUWLFLSDQW LQSDUWRI FRYHUHU RI DJDLQVW VXEMHFW RI
  • 244. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 243 Insurance Policies This ERD (see Figure 106) 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 107 lists the entities in this ERD and their corresponding tables. Table 107. Insurance Policies ERD Entities and Tables Entity Table Account S_ORG_EXT, S_PARTY Claim Summary S_INS_CLAIM Condition S_INSITEM_CNDTN Contact S_CONTACT,S_PARTY 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
  • 245. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 244 Figure 106. Insurance Policies Title:InsurancePolicies Author:Oracle,Confidential CONDITION ACCOUNT INSURANCEPOLICYITEM ACCOUNT CLAIM SUMMARY PAYMENT PLAN HOUSEHOLD INSURANCEPOLICYITEM SCHEDULED PERSONAL PROPERTY OTHER INSURANCE POLICYITEM WATERCRAFT DWELLING VEHICLE INSURANCEPOLICY PERSONAL UMBRELLA LINES POLICYINSTANCE OTHERPROPERTY AUTO LICENSE RESTRICTION HOUSEHOLDCONTACT CONTACT POLICYCONTACT INSURANCEDOCUMENTATION ITEM DRIVERS LICENSE INSURANCECOVERAGE DISCOUNT partof composedof characteristicof characterizedby on subjectof on subjectof associatedwith subjectto associatedwith subjectto appliedto subjectof partof composedof membershipof subjectof appliedto subjectof madeagainst subjectof applicableto subjectto appliedto subjectof subjectto parentof ownerof ownedby membershipin madeupof on subjectof coveredby covererof applicableto subjectto for namedas issuedto holderof
  • 246. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 245 Life Insurance Policy This ERD (see Figure 107) 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 108 lists the entities in this ERD and their corresponding tables. Table 108. Life Insurance Policy ERD Entities and Tables Entity Table Activity S_EVT_ACT Assessment S_ASSESS Assessment Value S_ASSESS_VAL 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 Account S_ASSET 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 Organization S_ORG_EXT, S_PARTY Pay Plan S_PAY_PLAN Person S_CONTACT, S_PARTY Product S_PROD_INT Service Request S_SRV_REQ Withdrawal/Surrender S_PAYMT_REQ
  • 247. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 246 Figure 107. Life Insurance Policy Title:LifeInsurancePolicy Author:Oracle,Confidential WITHDRAWAL /SURRENDER ASSESSMENT VALUE BENEFICIARY COVERAGE OPTION ASSESSMENT BILL ACCOUNT INSURANCE CLAIM ACTIVITY INSURANCE COVERAGE ASSET CONTACT PAYPLAN PERSON SERVICE REQUEST ORGANIZATION HOLDING FINANCIAL TRANSFER FINANCIALTRANSACTION BENEFICIARY CLASS PRODUCTFINANCIALACCOUNT POLICYINSTANCE LIFEPOLICY ANNUITY LOAN for subject of for acomponentofbelongs to subject of requestedby initiateof includes partof of subject of contact contactof for subject of contact of contact applicable to subject of for subject of for associated with for has for setup for subject of ownerof owned by partof madeupof for subjectof for subjectof for subjectof undertake undertaken by incontextof responsiblefor for subjectof for associatedwith partof includes for has for associated with basedon basisof ownerof owned by basedon basisof guaranteedby guarantees guaranteedby guarantees
  • 248. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 247 Loyalty This ERD (see Figure 108) 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. Pricing rule, Pricing Range, Point Subtype, Incentive Choice, and Partner Statement entities support enhancements to features such as Post-Paid and Pre-Paid Partnership Management, Promotion Registration Service and so on. Accrual, redemption, promotion, enrollment, member administration, partner administration and other functions are described in more detail as follows: ■ 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. ■ 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.
  • 249. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 248 ■ 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 Coterminal Identification. Tracks zone details of airports. Loyalty programs can use zone details to allow members to accrue points based on zone travel. Table 109 lists the entities in this ERD and their corresponding tables. Table 109. 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 Loyalty Transaction Log S_LOY_TXN_LOG, S_LOY_TXNEN_LOG 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
  • 250. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 249 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 109. Loyalty ERD Entities and Tables Entity Table
  • 251. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 250 Figure 108. Loyalty Title:Loyalty Author:Oracle,Confidential LOYALTY TRANSACTION LOG STATEMENT POINT TYPE BUCKET VOUCHER MEMBERSHIP CARD STATUS RESTRICTION SERVICE PRODUCT ASSOCIATION PURCHASE TRANSFER LIMITS PRICING OPTIONS PRODUCT ... HOSTING COMPANY TIER REWARD ATTRIBUTE DEFINITION LOAN ACCRUAL TEMPLATE POINTBLOCK PROGRAMPARTNER PARTNER PRODUCT OFFERING PARTNER TRANSACTION REDEMPTION ITEM ACCRUALITEM INDIVIDUALHOUSEHOLDACCOUNT LOYALTYTRANSACTION PACKAGE PRODUCT REDEMPTION ACTIVITY TRAVEL INFORMATION ACTIVITY LOYALTYPROGRAMMEMBER TIERCLASS TIER LOYALTY PROMOTION LOYALTYPROGRAM for has for subjectof basedon basisfor for subjectof in madeof ownedby ownerof definedfor uses uses for definedfor subjectof definedfor uses belongsto for usedby uses ownedby owns usesusedby partof madeof partof madeof usedby uses definedfor uses runby hostfor for qualifiedfor availablefor qualifiesfor for of of typefor definedfor subjectof for subjectof in for partneredwith involvedin ownedby ownerof subjectof definedfor for subjectof definedfor subjectofpartneredwith involvedin usedby uses enrolledby in enrolledby in enrolledby in for subjectof for subjectof childof parentof for subjectof doneby executerof partof madeupof referredby referencefor qualifiedfor optedinby partof madeupof
  • 252. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 251 Loyalty Flowchart and Formula Loyalty Promotion flowcharts help to execute promotions in a particular sequence. They can be used to validate the sequence of the promotions and calculate the points awarded for a particular flow. Figure 109 shows the Loyalty Flowchart and Formula ERD. Loyalty Formulas are used to create and store a set of objects and operators specific to a loyalty program. Values can be calculated based on input from third parties and then the resulting value can be taken into account within a promotion. A formula can be available for use by a promotion only if it is associated with the same loyalty program as that promotion. Once validated, a formula is available for use in promotion criteria and actions. When used in promotion criteria and actions, the object is the formula and the attributes are a list of user-defined formulas. Table 110 lists the entities in this ERD and their corresponding tables. Table 110. Loyalty Flowchart and Formula ERD Entities and Tables Entity Table Attribute Definition S_LOY_ATTRDEFN Loyalty Flow Connector S_LOY_FLW_CNCTR Loyalty Flow Step S_LOY_FLOW_STEP Loyalty Formula Step S_LOY_FRML_STEP Loyalty Process Flowchart S_LOY_PROC_FLOW Loyalty Program S_LOY_PROGRAM Loyalty Program Formula S_LOY_PRG_FRML Loyalty Promotion S_LOY_PROMO Loyalty Promotion Phase S_LOY_PHASE_PRM Program Partner S_ORG_EXT, S_LOY_PROG_ORG
  • 253. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 252 Figure 109. Loyalty Flowchart and Formula Title : Loyalty Flowchart and Formula Author : Oracle, Confidential LOYALTY FORMULA STEP LOYALTY PROGRAM FORMULA LOYALTY PROMOTION PHASE LOYALTY FLOW STEP LOYALTY FLOW CONNECTOR PROGRAM PARTNER LOYALTY PROCESS FLOWCHART ATTRIBUTE DEFINITION LOYALTY PROMOTION LOYALTY PROGRAM defined for subject of evaluated in evaluated by defined for consists of available for uses defined for subject of for associated with for associated with refers tohas has to step has from step defined for consists of defined for subject of part of consists of partnered with involved in part of consists of for of defined for subject of
  • 254. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 253 Managed Care This ERD (see Figure 110) 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 child products for the market that the formulary is associated with. Table 111 lists the entities in this ERD and their corresponding tables. Table 111. Managed Care ERD Entities and Tables Entity Table Account S_ORG_EXT, S_PARTY 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
  • 255. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 254 Figure 110. 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
  • 256. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 255 Medical Education Event Management This ERD (see Figure 111) 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 112 lists the entities in this ERD and their corresponding tables. Table 112. 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 Person S_CONTACT, S_PARTY Plan S_ME_PLN_LS Position S_POSTN, S_PARTY 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
  • 257. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 256 Figure 111. Medical Education Event Management Title:MedicalEducationEventManagement Author:Oracle,Confidential ACTIVITY LITERATURE MATERIAL SESSION INVITEE EVENT INVITEE PERSON EMPLOYEE CONTACT EVENTPOSITION POSITION PRODUCT PERIOD FUND SESSION EVENT PLAN in for of teammemberfor ownerof ownedby topplanfor childplanof for sourceof for team composedof subject to for relevantto usageof for having composedof partof having speakerat to inviterof of for to inviterof of inviteefor promotionof promotedat promotionof promotedat allocatedfundsby allocatingfundsforpromotionof parentofchildof allocatedto using
  • 258. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 257 Objectives This ERD (see Figure 112) 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 113 lists the entities in this ERD and their corresponding tables. Table 113. Objectives ERD Entities and Tables Entity Table Account S_PARTY, S_ORG_EXT Activity Details S_EVT_ACT Contact S_PARTY, S_CONTACT Objective S_SRC Position S_POSTN
  • 259. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 258 Figure 112. Objectives Title : OBJECTIVES Author : Oracle, Confidential ACTIVITY DETAILS POSITION CONTACTACCOUNT OBJECTIVE assigned to responsible for has subject to target of for target of for
  • 260. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 259 Personalized Content Delivery The Personalized Content Delivery feature allows pharmaceutical sales representatives to deliver a sales communication to general practitioners and medical specialists using multimedia visualizations. This ERD (see Figure 113) illustrates how a Message Plan is associated with Messages, Products Presentation Details and Party Entities such as Account, Contact, Position and Business Unit. Table 114 lists the entities in this ERD and their corresponding tables. Table 114. Personalized Content Delivery ERD Entities and Tables Entity Table Account S_PARTY, S_ORG_EXT Activity S_EVT_ACT, S_EVT_ACT_LSX Assessment Template S_TMPL_PLANITEM Business Unit S_PARTY, S_BU Contact S_PARTY, S_CONTACT 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
  • 261. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 260 Figure 113. Personalized Content Delivery Title:LSPersonalizedContentDelivery Author:Oracle,Confidential ASSESSMENTTEMPLATE MESSAGINGPLAN ITEM DECISION ISSUES MESSAGEPRODUCT APPLICATION PRODUCT MESSAGE ACTIVITYPRESENTATION DETAILS PARTY CONTACT ACCOUNT POSITION BUSINESS UNIT OFFER PERIOD OBJECTIVE MESSAGING PLAN for has periodof periodfor has for has for parentof childof forhas parentof childofparentof childof has for for associatedto associatedto has associatedto for has for has for for has associatedto for has for has for creatorof createdby has for has for associatedto for associatedto for has for
  • 262. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 261 Public Sector Benefit Case Management This ERD (see Figure 114) 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. Enhancements for Siebel 8.2 include Benefits Plan History, Lock Benefits, Reassess Circumstances, and Payment History. This ERD illustrates that a Benefit Plan is created under a Benefit Program that consists of one or more Benefit Program Items. Benefit Program Items include one or more Products. A Benefit Plan also consists of Benefit Plan Items that are associated with a Recipient, provided by a Provider and associated with a Product. This ERD also shows that a Benefit Plan belongs to a Case and that a Case can have a Change of Circumstance which might or might not be associated with a Benefit Plan. ■ Effective Dating. Allows the application to capture, store and output change history for an effective-dating enabled (ED-enabled) business component in terms of its field data as well as its relationship to other business components. Using the change history, the system can reconstruct data for a given point in time. Effective Dating is preconfigured for the Contact, Household and Income Business Components. ■ 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. As the ERD shows, a Case Verification Template is associated with a Case and can consist of one or more Case Verification Items. The Case Verification Template Items can be associated with 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 is reviewed in the same way. Table 115 lists the entities in this ERD and their corresponding tables. Table 115. Public Sector Benefit Case Management ERD Entities and Tables Entity Table Account S_PARTY, S_ORG_EXT Activity S_EVT_ACT Benefit Plan S_CASE_BNFTPLAN Benefit Plan Item S_BNFT_PLAN_ITM Benefit Plan Item Payment S_SRC_PAYMENT Benefit Program S_BNFT_PGM Benefit Program Item S_BNFT_PGM_ITM Case S_CASE, S_CASE_PSX
  • 263. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 262 Case Verification Item S_ASSESS_ATTRIB Case Verification Template S_TMPL_PLANITEM Change of Circumstance S_CASE_CHGOFCCM Contact S_PARTY, S_CONTACT Party S_PARTY Product S_PROD_INT Quality Assurance Items S_ASSESS_ATTRIB Quality Assurance Template S_TMPL_PLANITEM User S_PARTY, S_CONTACT, S_USER Table 115. Public Sector Benefit Case Management ERD Entities and Tables Entity Table
  • 264. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 263 Figure 114. Public Sector Benefit Case Management Title:PSBenefitCaseManagement Author:Oracle,Confidential BENEFIT PROGRAM BENEFIT PROGRAM ITEM PRODUCT QUALITY ASSURANCE ITEMS QUALITYASSURANCE TEMPLATE USERCASEVERIFICATIONITEM CASEVERIFICATION TEMPLATE ACTIVITY PARTY CONTACT ACCOUNT BENEFITPLAN ITEMPAYMENT BENEFITPLANITEMCHANGEOF CIRCUMSTANCE BENEFIT PLAN CASE paymentfor has has for associatedto for belongsto has associatedto usedby has for submittedby submitterof completedby completerof submittedby submitterof for has for has for has belongsto has for has verifiedby verifierof for has for has for has receivedby recipientof providedby providerof for has
  • 265. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 264 Public Sector Case Lead Management This ERD (see Figure 115) 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 and 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. Features 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 and 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 Siebel Public Sector application. During the upload process, relevant data from the form(s) is imported into the appropriate Siebel contact, household and case records. Table 116 lists the entities in this ERD and their corresponding tables. Table 116. 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 APPLICATION S_PS_APPL
  • 266. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 265 APPLICATION ATTACHMENT S_PS_APPL_ATT APPLICATION/BUSINESS UNIT VISIBILITY S_PS_APPL_BU Table 116. Public Sector Case Lead Management ERD Entities and Tables Entity Table
  • 267. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 266 Figure 115. Public Sector Case Lead Management Title:PublicSectorCaseLeadManagement Author:Oracle,Confidential APPLICATION APPLICATION BUSINESSUNIT APPLICATION ATTACHMENT INCIDENT SERVICEREQUEST PHYSICALOBJECT PERSONDESCRIPTION INVESTIGATIVELEAD ACTIVITY ADDRESS PARTY POSITIONORGANIZATION/GROUP SUSPICIOUS GROUP OTHER ORGANIZATION AGENCY PERSON SUSPECTAGENTOTHER PERSON DISEASE EVIDENCE/SUPPORTINGDOCUMENT CASE isrelatedto has relatedto hasvisibilityto relatedto has isrelatedto isvisibleto partof composed of relatedwith involvedin matchingwith forfor subject of for has conductedfor initiationof targetat subjectof approvedby approverof investigatedby assignedto responsiblefor responsibilityof generatedby servicedthrough servicedthrough generatedby generatedby servicedvia for supportedby for relatedto servicedthrough generatedby relevantto associatedwith locatedin for basedon subjectfor for relatedto addressfor locationof forsupportedby basisfor triggeredby relatedto leadto subjectof for associatedwith theuseof relevantto
  • 268. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 267 Public Sector Child Welfare The Child Welfare feature addresses the intake and case management needs of social service agencies working to provide child welfare services. Intake, Screening Decision, Assessment Management, Court Processing Interface, and Service Plan Creation functions are included. As the ERD (see Figure 116) depicts, a Case can have one or more Incidents and one or more Benefit Plans. An Incident can have multiple Assessments, can be approved by one or more Positions, can have one or more Contacts and uses an Approval Template. An Incident can also have one or more Allegations that can be allegations on one or more Contacts associated with the Incident. A Benefit Plan can have one or more Court Hearings and a Court Hearing can have one or more Court Decisions. Table 117 lists the entities in this ERD and their corresponding tables. Table 117. Public Sector Child Welfare ERD Entities and Tables Entity Table Allegation S_ALLEGATION Approval Template S_APPR_TEMPLATE Assessment S_ASSESS Benefit Plan S_CASE_BNFTPLAN Case S_CASE, S_CASE_PSX Contact S_CONTACT, S_PARTY Court Decision S_COURT_DECISN Court Hearing S_EVT_ACT Incident S_INCIDENT Position S_POSTN, S_PARTY Service Plan S_CASE_BNFTPLAN Time Sheet S_TMSHT Time Sheet Item S_TMSHT_ITEM Time Sheet Line S_TMSHT_LN
  • 269. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 268 Figure 116. Public Sector Child Welfare Title:PSChildWelfare Author:Oracle,Confidential APPROVAL TEMPLATE CONTACT POSITION TIMESHEETLINE TIMESHEET COURTHEARING COURTDECISION ALLEGATION TIMESHEETITEM ASSESSMENT PLAN SERVICE PLAN BENEFITPLAN INCIDENT CASE uses usedby refersto referedin involvedin allegationon has forpartof has involvedin involves approverof approvedby partof madeupof subjectof of timespenton hashas belongsto timespenton has relatedto has outcomeof has part has for has for has
  • 270. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 269 Public Sector Contact Identity Public Sector Contact Identity (see Figure 117) 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 118 lists the entities in this ERD and their corresponding tables. Table 118. 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
  • 271. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 270 Figure 117. Public Sector Contact Identity 7LWOH3XEOLF6HFWRURQWDFW,GHQWLW $XWKRUOracleRQILGHQWLDO 25*$1,=$7,21*5283 ,668,1*$*(127+(5632572)(175 67$ $55,9$/B76 5('(17,$/ $7(*25B' 5('(17,$/B180 ,668,1*B28175 3$663257 9,6$ 38%/,6(725217$7 3$57 217$7 ,'(17,7 ,'(17,7B180 GHSDUWDW IRU HQWHUDW IRU DOORZE DOORZ DOORZE DOORZ LVVXHE LVVXH SDUWRIPDGHXSRI IRU KDV IRU KDV REWDLQE SRVVHVV SRVVHVVE KDYH
  • 272. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 271 Public Sector Evidence Management This ERD (show in Figure 118) 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 119 lists the entities in this ERD and their corresponding tables. Table 119. 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 PHYSICAL OBJECT S_ASSET QUOTE ITEM S_QUOTE_ITEM ORDER ITEM S_ORDER_ITEM QUOTE S_DOC_QUOTE ORDER S_ORDER SERVICE REQUEST S_SRV_REQ ACTIVITY S_EVT_ACT INVESTIGATIVE LEAD S_CASE_LEAD INCIDENT S_INCIDENT CASE S_CASE
  • 273. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 272 Figure 118. Public Sector Evidence Management 7LWOH3XEOLF6HFWRU(YLGHQFH0DQDJHPHQW $XWKRUOracleRQILGHQWLDO $7,9,7 3+6,$/ 2%-(7 ,19(67,*$7,9( /($' 6(59,( 5(48(67 $6( ,1,'(17 (9,'(1(6833257,1*'280(17 3$57 326,7,21 25*$1,=$7,21*5283 +286(+2/'27+(5 25*$1,=$7,21 6863,,286 *5283 $*(1 3(5621 $*(176863(727+(53(5621 $''5(66 4827(,7(04827( 25'(5,7(025'(5 UHODWHGZLWK LQYROYHGLQ ORJJHGE VXEPLWWHUIRU SDUWRI FRPSRVHGRIEDVHGRQ VXEMHFWIRU REWDLQHGIURP VRXUFHRI IRU UHODWHGWR VXSSRUWLQJGRFXPHQWVIRU VXSSRUWHGE VHUYLFHGWKURXJK IRU IRUIXOILOOPHQWRIEHQHILWVUHTXHVW IXOILOOHGEFRPSRVHGRI IRU VXSSRUWLQJGRFXPHQWVIRU VXSSRUWHGE EDVLVIRU EDVHGRQ DSSURYHGE DSSURYHURI KDQGOHGE RZQHURI UHVSRQVLELOLWRI UHVSRQVLEOHIRU IRU KDYH IRU LQLWLDWLRQRI SDUWRI PDGHXSRI UHODWHGZLWK LQYROYHGLQ IRU VXSSRUWHGE IRUIXOILOOPHQWRIEHQHILWVDSSOLFDWLRQ IXOILOOHGE ORFDWHGDW ORFDWLRQIRU IRU VHUYLFHGWKURXJK EDVLVIRU WULJJHUHGE DGGUHVVIRU ORFDWLRQRI IRU FRPSRVHGRI IRU VHUYLFHGWKURXJK IRU VXSSRUWHGE PDLQHYLGHQFHRIUHODWHGWR
  • 274. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 273 Public Sector Incident Management This ERD (see Figure 119) 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 120 lists the entities in this ERD and their corresponding tables. Table 120. 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 SERVICE REQUEST S_SRV_REQ ACTIVITY S_EVT_ACT INVESTIGATIVE LEAD S_CASE_LEAD CASE S_CASE PHYSICAL OBJECT S_ASSET ARREST S_ARREST ARREST FORCE S_ARREST_FORCE OFFENSE S_OFFENSE OFFENSE CRIMINAL ACTIVITY S_OFFENSE_ACT
  • 275. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 274 Figure 119. Public Sector Incident Management 7LWOH3XEOLF6HFWRU,QFLGHQW0DQDJHPHQW $XWKRUOracleRQILGHQWLDO 2))(16(5,0,1$/$7,9,7 ,1,'(17$2817 :,71(66 $2817 27+(5 ,1,'(17 $2817,1,'(17 6863,,286 *5283 ,19(67,*$7,1*$2817 2))(1'(5$2817 9,7,0$2817 ,1,'(17 9,7,073( 3+6,$/2%-(7 ,19(67,*$7,9( /($' $6( ,1,'(17217$7 ,1,'(17 6863(7 27+(5,1,'(17217$7 ,1,'(17:,71(66 ,1,'(17 2))(1'(5 ,1,'(17 9,7,0 ,19(67,*$7,1* $*(17 ,58067$1( 3$57 3(5621 6863(727+(5 3(5621 $*(17 25*$1,=$7,21*5283 27+(5 25*$1,=$7,21 $*(16863,,286 *5283 6(59,( 5(48(67 $7,9,7 $55(67)25( ,1-85 $55(67 2))(16( ,1,'(17 FRQGXFWHGIRU LQLWLDWLRQRI IRU LQLWLDWLRQRI VXEMHFWRI IRUIRU UHODWHGWR IRU LQYROYHGLQDV UHODWHGWR VXEMHFWRI LQYROYHGLQ UHODWHGWR IRU LQYROYHGLQDV PDGHE IRU FRQGXFWHGIRU LQLWLDWLRQRI UHODWHGWR VXEMHFWRI IRU DUUHVWHGLQ IRU LQLWLDWLRQRI XVHGLQ HIIHFWHGZLWK FRPPLWWHGZLWK XVHGLQ FRPPLWWHGXQGHU FRPSRVHGRI PDLQLQFLGHQWRI UHODWHGWR IRU RI LQUHODWLRQWR UHODWHGZLWK EDVLVIRU EDVHGRQ IRU VXEMHFWRI IRU VHUYLFHGWKURXJK VXVWDLQHGE VXIIHUUHGIURPLQYROYHGLQ VXEMHFWIRU FRPPLWWHGZLWK XVHGLQ FRPPLWWHGZLWK XVHGLQ FRPSRVHGRI FRPPLWWHGXQGHU
  • 276. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 275 Public Sector Service Provider and Referral Management The Service Provider and Referral Management feature allows social service agencies to locate service providers and manage the referral process. Features include Service Provider Information Management, Service Provider Contract Management, Service Provider Transaction Management, Service Provider Portal, Service Provider Portal Resource and Inventory Control, Service Provider Locator, Service Provider Referral and Benefits Administration. This ERD (see Figure 120) illustrates that Service Providers can have a Profile, be the subject of Contracts and own Assets. Contracts consist of Contract Items for Products that are made into Asset instances. Benefit Plans with Benefit Plan Items can be associated with a Case. Benefit Plan Items are also associated with a Product and a Service Provider who provides the Benefit. A Benefit Plan is created under a Benefit Program that consists of Benefit Program Items. Each Benefit Plan Item is associated with a Product and can have one or more Orders (created as part of Referral) that are serviced by Service Providers and are composed of Order Items. Order Items are associated with the Product, which is also associated with the related Benefit Plan Item. Table 121 lists the entities in this ERD and their corresponding tables. Table 121. Public Sector Service Provider and Referral Management ERD Entities and Tables Entity Table Asset S_ASSET Benefit Fund S_BNFT_FUND Benefit Plan S_CASE_BNFTPLAN Benefit Plan Item S_BNFT_PLAN_ITM, S_BNFT_PLNIT_XA Benefit Plan Item Payment S_SRC_PAYMENT Benefit Program S_BNFT_PGM Benefit Program Item S_BNFT_PGM_ITEM Case S_CASE, S_CASE_PSX Contract Header S_DOC_AGREE Contract Item S_AGREE_ITEM Internal Product or Service S_PROD_INT Order S_ORDER, S_ORDER_PSX Order Line Item S_ORDER_ITEM Other Organization S_ORG_EXT, S_PARTY Party S_PARTY Service Provider Profile S_ORG_EXT_ATTR, S_ORG_EXT_LANG Service Provider S_ORG_EXT, S_ORG_EXT_PSX, S_PARTY
  • 277. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 276 Figure 120. Public Sector Service Provider and Referral Management Title:PSSvcProviderReferralMgmt Author:Oracle,Confidential ORDERLINE ITEM ORDER BENEFITPLANITEM PAYMENT INTERNALPRODUCTORSERVICE CONTRACTHEADER BENEFITPROGRAM BENEFITPLAN BENEFIT FUND PARTY OTHER ORGANIZATION SERVICEPROVIDER SERVICE PROVIDER PROFILE CONTRACTITEM ASSET BENEFIT PROGRAMITEM BENEFITPLANITEM CASE for has servicedby services for has createdfor has partof composedof subjectof ordered ownedby owns paymentfor has has usedfor providedby providerof has forfor has aninstanceof madeinto for subjectof for subjectof belongsto has under for for has has belongsto belongsto has for has for has has usedfor
  • 278. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 277 Real-Time Scheduler Integration In a typical field service scenario, technicians are sent to a customer's location to do a job such as performing an installation, upgrade, or repair. Real-Time Scheduler is an external application that performs the scheduling (ERD see Figure 121). Scheduling involves matching an available service technician to a job or service request. Each job has a set of necessary skills. For example, installation of a set-top box might require a skill, such as training in electrical wiring. Each technician has a distinct set of skills. The job of the scheduler is to find the best technician who is available and has the necessary skills to perform the job. The following information is mastered and stored in the Siebel application: ■ Technician details (name, phone number, and so on.) ■ Technician schedule and availability ■ Technician skill set ■ Job details ■ Job skills (skills required to accomplish the job) ■ Service requests for jobs Real-Time Scheduler can use the above information to prepare a schedule that contains a timetable for each technician. To enable this, the Siebel application must use the Real-Time Scheduler Web service to pass the skills needed to do the job to the Real-Time Scheduler. Table 122 lists the entities in this ERD and their corresponding tables. Table 122. Real-Time Scheduler Integration ERD Entities and Tables Entity Table Address S_ADDR_PER Buscomp S_BUSCOMP Buscomp Field S_FIELD Business Object S_BUSOBJ Resource Scheduler Rule Criteria Value S_RS_CRIT_VAL Resource Scheduler Object Link S_RS_OBJ_LNK Resource Scheduler Object Link Relation S_RS_OBJLNK_REL Resource Scheduler Skill Rule Criteria S_RS_RULE_CRIT Resource Scheduler Rule Definition S_RS_RULE_DEF Resource Schedule Item S_RS_SCHD_EVENT Resource Scheduler Skill Item S_RS_SKILL_ITM Resource Scheduler Skill Set S_RS_SKILL_SET Technician S_USER
  • 279. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 278 Figure 121. Real-Time Scheduler Integration Title:Real-TimeSchedulerIntegration Author:Oracle,Confidential RESOURCESCHEDULEITEM TECHNICIAN BUSINESSOBJECT BUSCOMPFIELD BUSCOMP ADDRESS RESOURCE SCHEDULERRULE CRITERIAVALUE RESOURCE SCHEDULER SKILLRULE CRITERIA RESOURCE SCHEDULER OBJECTLINK RELATION RESOURCESCHEDULERSKILLITEM RESOURCE SCHEDULER SKILLSET RESOURCESCHEDULER OBJECTLINK RESOURCESCHEDULERRULE DEFINITION belongsto has madeupof usedin definedfor ownerfor has ending locationfor has starting locationfor userof sourcefor comparedto valuefor definedfortargetjoin definedforsourcejoin definedfortargetfor definedforsourcefor definedforsourcefor for has specifiedfor has requiredskill setfor requires has child linkfor has parent linkfor uses used for evaluated for has
  • 280. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 279 Routes and Best Call Hours This ERD (see Figure 122) 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 123 lists the entities in this ERD and their corresponding tables. Table 123. 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
  • 281. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 280 Figure 122. Routes and Best Call Hours Title : Routes and Best Call Hours Author : Oracle, Confidential EXTERNAL ORGANIZATION RETAILER OTHER ORGANIZATION SYNDICATE GROUP STORE BEST CALL HOUR ROUTE defined for appear onfor have part of made up of
  • 282. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 281 Sales Volume Planning This ERD (see Figure 123) 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 can 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 can 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 124 lists the entities in this ERD and their corresponding tables. Table 124. Sales Volume Planning ERD Entities and Tables Entity Table Authorized Product S_ORG_PROD 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 Internal Product S_PROD_INT Marketing Event S_SRC 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 Line S_PROD_LN 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
  • 283. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 282 Figure 123. Sales Volume Planning Title : Sales Volume Planning Author : 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 EXTERNAL ORGANIZATION RETAILER SYNDICATE GROUP SUPPLIER STORE OTHER ORGANIZATIONpart of composed of have exist for exist for have exist for have of subject of at subject of for has have for an part of made up of
  • 284. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 283 Sample Management This ERD (see Figure 124) 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 125 lists the entities in this ERD and their corresponding tables. Table 125. Sample Management ERD Entities and Tables Entity Table Audit Report Attachment S_INVADTRPT_ATT Call S_EVT_ACT Contact S_CONTACT, S_PARTY Employee S_EMP_PER, S_CONTACT, S_PARTY Internal Product S_PROD_INT 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
  • 285. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 284 Figure 124. Sample Management Title:SampleManagement Author:Oracle,Confidential SIGNATURE AUDIT TRANSACTION ATTACHMENT VALIDATION RESULT AUDITREPORT ATTACHMENT INVENTORYAUDIT REPORT PERSON EMPLOYEE CONTACT TRANSFERITEM INTERNALPRODUCT STOCKPERIOD PRODUCTINVENTORY TRANSACTIONITEM SAMPLETRANSACTION SAMPLETRANSFER SAMPLEORDER ORDERITEM CALLfor associatedwith for associated with associated with consistsof for subjectof associatedwith consistsof ownedby own belongstoPersonlistfactor transferredby transfer belongingto of belongingto of ownedby own transferredby transfer ownedby own transferredby transfer ownedby own transferredby transfer ownedby own for inventoriedin for composedof for composedof belongingto for adjustmentofadjustedfrom belongingto of itemsof composedof droppedat dropof
  • 286. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 285 Special Rate List Special Rate List (see Figure 125) is a list of phone numbers, country codes, area codes, and so on, to be used for special rates in telephone rate plans. This list is defined for a telephone user account in the communications industry. This special rate list is subsequently used in quotes and orders for the customer in relation to the telephone owned by the customer. Table 126 lists the entities in this ERD and their corresponding tables. Table 126. Special Rate List ERD Entities and Tables Entity Table Account S_ORG_EXT, S_PARTY Asset S_ASSET Order Item S_ORDER_ITEM Quote Item S_QUOTE_ITEM Special Rate List S_SPL_RATE_LST Special Rate List Item S_SPL_RATE_ITEM
  • 287. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 286 Figure 125. Special Rate List Title : Special Rate List Author : Oracle, Confidential SPECIAL RATE LIST ITEM SPECIAL RATE LIST ACCOUNT QUOTE ITEMORDER ITEM ASSET has defined for has defined for has defined for for has primary for has defined for has part of composed of part of composed of for subject of for provision of subject of
  • 288. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 287 Syndicated Data This ERD (see Figure 126) illustrates how the syndicated data (sales and prescription information) is associated with a period, plan, account, contact, postal code, territory, and area. Table 127 lists the entities in this ERD and their corresponding tables. Table 127. Syndicated Data ERD Entities and Tables Entity Table Account S_ORG_EXT, S_PARTY Contact S_CONTACT, S_PARTY Period S_PERIOD Plan S_INS_PLAN Position S_POSTN, S_PARTY Postal Code S_ZIPCODE Product S_PROD_INT Region S_REGION Syndicated Data S_SYND_DATA Territory S_ASGN_GRP
  • 289. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 288 Figure 126. Syndicated Data Title:SyndicatedData Author:Oracle,Confidential AREA PRODUCT TERRITORY POSTALCODE SYNDICATEDDATA SALES PRESCRIPTION POSITION PLAN CONTACT PERIOD ACCOUNT in for for subjectof of for in for for subjectof for recipientof for subjectof for subjectof for subjectof
  • 290. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 289 Teller Administration This ERD (see Figure 127) 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 tellers execute different activities and service requests for the customer. Table 128 lists the entities in this ERD and their corresponding tables. Table 128. 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 Contact S_CONTACT, S_PARTY Container S_FN_CONTAINER Container Limits S_FNCONTNR_LMTS Employee S_EMP_PER, S_CONTACT, S_PARTY Employee Teller Limits S_EMP_TLR_LMTS Holdover S_FN_TXN_HLDVR, S_FN_HLDVR_CTF Organization Unit S_ORG_EXT, S_PARTY Person S_CONTACT, S_PARTY Service Request S_SRV_REQ Transaction Limits S_FN_TXN_LMTS
  • 291. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 290 Figure 127. Teller Administration Title:TellerAdministration Author:Oracle,Confidential PARTY PERSON CONTACTEMPLOYEE ORGANIZATIONUNIT BRANCH SERVICE REQUESTLINE ITEM BAIT/TRAP SETTLEMENTBATCH ACTIVITY HOLDOVER CALENDAR TRANSACTION LIMITS EMPLOYEE TELLERLIMITS TRANSACTION LIMITS CONTAINER LIMITS SERVICE REQUEST ACTIVITY CONTAINER DRAWERBATCHVAULTBIN associatedwith from partof includes associated with has has for usedby has to from generated by generates from to associated with has associated with has for has for has associated with has assoicated with has assoicated with has madeupof partof includes subjectof
  • 292. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 291 Territory Alignment–Quota Assignment This ERD (see Figure 128) shows how to set up territory alignment to determine whether the results of quota assignments are as expected. It covers assigning quotas to alignments, breaking these assignments down by contacts, accounts, regions, or ZIP code, and changes included in a given alignment. Table 129 lists the entities in this ERD and their corresponding tables. Table 129. 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
  • 293. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 292 Figure 128. Territory Alignment–Quota Assignment 7LWOH7HUULWRU$OLJQPHQW4XRWD$VVLJQPHQW $XWKRUOracleRQILGHQWLDO 214827$ +$1*( *(24827$ +$1*( $174827$ +$1*( $/,*10(177(5547$%5($.'2:1 *(27(550$33,1*+$1*( 217$77(55 0$33,1*+$1*( $28177(55 0$33,1*+$1*( $/,*10(177(554827$ $/,*10(174827$ 3(5,2' 7(55,725 +,(5$5+ 7(55,725 $/,*10(17 6$/(64827$ 7(55,725 SDUWRI PDGHXSRI IRU FRPSRVHGRI DSSOLHGWR LQFOXGH IRU FRPSRVHGRI DSSOLHGWR LQFOXGH IRU FRPSRVHGRI IRU FRPSRVHGRI IRU FRPSRVHGRI DSSOLHGWR LQFOXGH IRU FRPSRVHGRI VSUHDGRYHU IRUIRU EUHDNGRZQRI DVVLJQHGWR UHFHLYH DVVLJQPHQWRI IRUDOORFDWLRQRI VXEMHFWRI IRU FRPSRVHGRI GHILQHGIRU DOWHUHGYLD
  • 294. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 293 Territory Management - Consumer Sector This ERD (see Figure 129) 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 130 lists the entities in this ERD and their corresponding tables. Table 130. Territory Management - Consumer Sector 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 Catalog Category S_CTLG_CAT 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 S_TERRITORY Territory Hierarchy S_TERR_HIER Territory Position Role S_TERR_POS_ROLE Territory Version S_TERRHIER_NODE
  • 295. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 294 Figure 129. Territory Management - Consumer Sector 7LWOH7HUULWRU0DQDJHPHQW6,$6
  • 296. $XWKRUOracleRQILGHQWLDO 7(55,725 326,7,21 52/( $28177($052/( 326,7,2152/( $7$/2*$7(*25 $7,9,7 7(55,7250$33,1* $28177(55 0$33,1* 217$77(55 0$33,1* $28177($0 0(0%(5 217$77($00(0%(5 217$7 326,7,21 ',9,6,21 6$/(6)25(27+(5',9,6,21 %86,1(6681,7 $2817 7(55,725 +,(5$5+ 7(55,725 7(55,7259(56,21 326,7,217(55,725$66,*10(17 GHILQHG JUDQWHG DFFHVVWR DVVLJQHGWR VXEMHFWRI LQYROYHV VXEMHFW RI IRU VXEMHFWRI DVVLJQHGWR VXEMHFWRI IRU VXEMHFWRI DFWLRQIRU VXEMHFWRI DFWLRQIRU WDUJHWRI WR UHVSRQVLELOLW RUJDQL]HGE XVHGE VSHFLILFWR UHVSRQVLEOH IRU RI DVVLJQHGWR WR UHVSRQVLELOLW RI DVVLJQHGWR WR UHVSRQVLELOLW GHILQHGE PDGHXSRI SDUWRI FRPSRVHG GHILQHG IRU JUDQWHG DFFHVVWR YHUVLRQRI DVVLJQHGWR RI SDUWRI RI SDUWRI WR FRPSRVHGRI SDUWRI FRPSRVHGRI RI DVVLJQHGWR SDUWRI PDGHXSRI
  • 297. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 295 Territory Management - Life Sciences For Life Science companies, a key business process is territory alignment (sales force alignment). This ERD (see Figure 130) 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 131 lists the entities in this ERD and their corresponding tables. Table 131. Territory Management - Life Sciences 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 S_TERRITORY Territory Alignment S_TERRALGN Territory Alignment Condition S_TERRALGN_COND Territory Hierarchy S_TERR_HIER Territory Version S_TERRHIER_NODE Zipcode (None)
  • 298. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 296 Figure 130. Territory Management - Life Sciences 7LWOH7HUULWRU0DQDJHPHQW6,$/6
  • 299. $XWKRUOracleRQILGHQWLDO 326,7,217(55 $66,*10(17 +$1*( *(27(550$33,1* +$1*( $66(77(55 0$33,1*+$1*( 217$77(55 0$33,1*+$1*( $28177(55 0$33,1*+$1*( 7(55,725 $/,*10(17 21',7,21 7(55,725$/,*10(17 *(2*5$3+,$/$5($ 5(*,21=,32'( $66(7 217$7 326,7,21 ',9,6,216$/(6)25(27+(5',9,6,21 %86,1(6681,7 $2817 7(55,725+,(5$5+ 7(55,725 7(55,7259(56,21 GHILQHG IRU JUDQWHG DFFHVV WR WRDGGGURS DIIHFWHGE RI UHPDSSHGLQ IRU FRPSRVHGRI WRDGGGURS DIIHFWHGE RI UHPDSSHGLQ IRU FRPSRVHGRI WRDGGGURS DIIHFWHGERI UHPDSSHGLQ WRDGGGURS DIIHFWHGE RI UHPDSSHGLQ IRU FRPSRVHGRI IRU FRPSRVHGRI WRDGGGURS DIIHFWHGE RI UHPDSSHGLQ IRU FRPSRVHGRI GHILQHGIRU DOWHUHGYLD IRU JRYHUQHGE RUJDQL]HGE XVHGE GHVLJQHGIRU VXEMHFWWR VSHFLILF WR UHVSRQVLEOHIRU GHILQHGE PDGHXSRI SDUWRI FRPSRVHGRI GHILQHG IRUJUDQWHG DFFHVV WR YHUVLRQRI DVVLJQHGWR SDUWRIFRPSRVHGRI SDUW RI PDGHXSRI
  • 300. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 297 Universal Customer Master This ERD (see Figure 131) 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 history of changes. Table 132 lists the entities in this ERD and their corresponding tables. Table 132. 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_ATGP, S_UCM_OGP_ATGP Confidence Level S_UCM_CONF_LVL Contact Additional Name S_CONTACT_NAME Contact Identity S_CON_IDNTY_DOC 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_CHILD, S_UCM_OGP_CHILD, S_UCM_ORG_CHILD UCM Decay Indicator S_UCM_CON_DECAY, S_UCM_ORG_DECAY UCM Deduplication S_UCM_DEDUP UCM Merge Association S_UCM_MRG_ASSOC UCM Merge History S_UCM_CON_MERGE, S_UCM_ORG_MERGE, S_UCM_ORGRP_MRG UCM Merge Request S_UCM_MERGE_REQ UCM Object S_UCM_CONTACT, S_UCM_ORG_EXT, S_UCM_ORGGRP UCM Party Ext S_PARTY_UCMX, S_CONTACT_UCMX UCM Privacy S_UCM_PRIVACY
  • 301. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 298 Figure 131. Universal Customer Master Title:UniversalCustomerMaster Author:Oracle,Confidential CONTACT IDENTITY CONTACT ADDITIONAL NAME UCMMERGE ASSOCIATION UCMDECAY INDICATOR UCMMERGEREQUEST UCM PRIVACY UCMASSET UCMADDRESS UCMMERGE HISTORY RULESET REPOSITORYBUSINESS COMPONENT REPOSITORYFIELDOBJECT ATTRIBUTEGROUP FIELDMAPPING ATTRIBUTEGROUPUPDATEHISTORY EXTERNAL SYSTEM PRIVILEGE EXTERNALINFORMATIONSYSTEM UCMPARTY EXT UCMOBJECT UCM HOUSEHOLD UCM ORGANIZATION UCMPERSON EXTERNALINFORMATION SYSTEMMAPPING UCMDEDUP CONFIDENCELEVEL ATTRIBUTE GROUPRULE ATTRIBUTEGROUP PARTY PERSONORGANIZATIONHOUSEHOLD for has for has for has for has for has for has from usedin belongsto has for has storeshas associatedwith has belongsto composedof refin refto refin refto referencedin referenced to belongsto has referenced to has pointsto referencedin mappedfor mappedto belongsto has pointsto referencedin belongsto has stores has stores usedin of master copyof of duplicateof for usedin for has
  • 302. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 299 Vehicle This ERD (see Figure 132) illustrates how Siebel Automotive tracks the configuration and relationships associated with a vehicle. Vehicles represent a physical asset based on a product that can 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 can 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 133 lists the entities in this ERD and their corresponding tables. Table 133. Vehicle ERD Entities and Tables Entity Table Asset S_ASSET Contact S_CONTACT, S_PARTY 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 Service Request S_SRV_REQ Specifications S_PROD_SPEC Vehicle S_ASSET, S_ASSET_ATX Vehicle Product S_PROD_INT
  • 303. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 300 Figure 132. Vehicle Title:Vehicle Author:Oracle,Confidential FINANCIALDETAIL SALESHISTORY POSITION SERVICEHISTORY PERSON EMPLOYEE OTHER PERSON ASSET INSTALLED OPTION VEHICLE PRODUCTDETAILS SPECIFICATIONS FEATURES ORGANIZATION OTHERORGANIZATION DEALER/PARTNER SERVICEREQUEST PRODUCT VEHICLE PRODUCT OPTION havevisibilityto visibleto prefer serviceproviderof belongto ownerof forofof involvedin of for of for soldby sellerof performedby perform routedto assignedto of involvedin of involvedin for subjectof for of for Subjectofreportedby reporterof composedof madeinto for subjectof assignedto for madeinto aninstanceof Currentlyownedby/relatedto for belongsto contains aninstanceof madeinto primarily composedof for secondarilycomposedof for areportto aparentto
  • 304. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 301 Vehicle Collection This ERD (see Figure 133) 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 134 lists the entities in this ERD and their corresponding tables. Table 134. 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
  • 305. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 302 Figure 133. Vehicle Collection ASSET VEHICLEOTHER ASSET FINANCIALACCOUNT VEHICLELEASE OTHERFINANCIAL ACCOUNT PARTY ORGANIZATION VEHICLELEASE HOLDING COMPANY OTHERORGANIZATION INSURANCECOMPANYIMPOUNDAGENCYREPOSESSION AGENCY PERSON CONTACTCOLLECTION AGENT OTHER PERSON SERVICEREQUEST IMPOUNDNOTIFICATION REPOSESSION REQUEST BANKRUPTCY *CASE_NUM VEHICLEINSURANCE *EFF_START_DT PROMISETOPAY *SEQ_NUM associatedto subjectof insured for insuredby insuredfor insuredby filedby filerof insuredby insurefor recordedfor hasbeenfiledfor issuedby workon assignedto workon
  • 306. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 303 Vehicle Financing Asset financing (see Figure 134) 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 135 lists the entities in this ERD and their corresponding tables. Table 135. Vehicle Financing ERD Entities and Tables Entity Table Asset S_ASSET Contract S_DOC_AGREE Financial Account S_ASSET 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 Service Request S_SRV_REQ 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
  • 307. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 304 Figure 134. Vehicle Financing Title:VehicleFinancing Author:Oracle,Confidential ASSET VEHICLE VEHICLE OPTION HISTORICALRESIDUALVALUE HISTORICALFMVPRICE HISTORICALAUCTIONPRICE PRODUCT VEHICLETURNIN INSPECTIONCHARGE #SEQ_NUM SERVICE REQUEST VEHICLEINSPECTION #SEQ_NUM VEHICLEFMV #CALCULATIONTYPE #EVALUATIONDATE CONTRACT OTHER CONTRACT LEASE AGREEMENT VEHICLETITLE LOG #SEQ_NUM CONSIGNMENT FEE CONSIGNMENT DETAIL VEHICLECONSIGNMENT FINANCIAL ACCOUNT STATE VEHICLEOPTION ATLEASE VEHICLEFINANCIAL ACCOUNT #SEQ_NUM FINANCIALACCOUNT OTHER FINANCIAL ACCOUNT VEHICLELEASEVEHICLE LOAN for consists ofbased on subjectof incontext subject of performedfor subject of for has for subject offor subject of for subjectof subjectof for subjectof for inreferenceto subjectof inreferencetosubjectof inreferencetosubjectof for subject of associated to subject of incontextof subject of forsubjectof associatedto subject of associatedto subject of for subjectof for subjectof associatedto subject of associated to subject of for subjectof for has
  • 308. Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications Siebel Data Model Reference Version 8.2 Rev. A 305 Vehicle Sales This ERD (see Figure 135) 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 136 lists the entities in this ERD and their corresponding tables. Table 136. Vehicle Sales ERD Entities and Tables Entity Table Contact Access Log S_CON_ACCSS_LOG Employee S_EMP_PER, S_CONTACT, S_USER Marketing Event or Activity S_SRC 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 S_ASSET, S_ASSET_ATX Vehicle Sale S_VHCL_SALES, S_VHCL_SALES_BU, S_VHCL_SALE_EMP
  • 309. Siebel Data Model Reference Version 8.2 Rev. A Siebel Logical Model ■ Entity Relationship Diagrams and Descriptions for Siebel Industry Applications 306 Figure 135. Vehicle Sales Title:VehicleSales Author:Oracle,Confidential VEHICLESALE SHOWROOMLOG ENTRY OPPORTUNITY MARKETINGEVENTOR ACTIVITY ORGANIZATION OTHER ORGANIZATION DEALER/ PARTNER CONTACT ACCESSLOG #ACCESSDATE VEHICLE PERSON OTHER PERSON EMPLOYEE madeby involvedin for subjectof participatein handledby subjectof incontextof havevisibilityto visibleto incontextof subjectof for subjectof soldby sellerof subjectof incontextof subjectof target resultof resultin resultof resultin createdby record target targetedin incontextof initiatorof ownerof belongto
  • 310. Siebel Data Model Reference Version 8.2 Rev. A 307 3 Siebel Physical Model This chapter describes the Siebel physical model, which encompasses the tables, their columns, and their indexes. It covers the following topics: ■ Data Model Naming Conventions ■ Data Model Type Definitions on page 310 ■ Columns of Numeric Physical Type on page 314 ■ Siebel System Fields on page 314 ■ INTEGRATION_ID Columns on page 315 ■ Include Only Field on page 315 ■ Siebel Repository on page 315 ■ Database Schema Version on page 315 ■ Limit Checking for Data Types on page 316 ■ Validating the Siebel Schema on page 316 ■ Party Model Unifies Access to Data on page 316 ■ Generating a Report about Tables on page 317 Data Model Naming Conventions This topic describes the following conventions: ■ Table Naming Conventions ■ Index Naming Conventions on page 309 ■ Column Naming Conventions on page 309 ■ Abbreviations Used in the Physical Model Listings on page 310 Table Naming Conventions Tables 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.
  • 311. Siebel Data Model Reference Version 8.2 Rev. A Siebel Physical Model ■ Data Model Naming Conventions 308 The prefix indicates the part of the Siebel schema to which a table belongs. Table 137 provides some of the prefixes and their descriptions. The suffix indicates a table type. Table 138 provides some of the suffixes and their descriptions. SUFFIX A supertype name can 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 137. 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 138. 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.
  • 312. Siebel Physical Model ■ Data Model Naming Conventions Siebel Data Model Reference Version 8.2 Rev. A 309 Index Naming Conventions Indexes are named the same as the table on which they are created plus a one-character to four-character suffix as shown in Table 139. CAUTION: Before modifying or deleting indexes, create a service request (SR) on My Oracle Support. Modifying or deleting indexes can negatively affect the performance of Siebel Business Applications and might 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. Column Naming Conventions Suffixes are used to indicate columns that must contain specific values. Table 140 shows the standard suffixes for column names and their possible values. Table 139. Standard Index Suffixes Suffix Value Unique or Not Unique _F# Foreign key index. Not unique _II Index on INTEGRATION_ID columns that are used for integrating Siebel Business Applications with back-office applications. 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 140. 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.
  • 313. Siebel Data Model Reference Version 8.2 Rev. A Siebel Physical Model ■ Data Model Type Definitions 310 Abbreviations Used in the Physical Model Listings Descriptions that appear in the physical model listings might use the abbreviations shown in Table 141. Data Model Type Definitions This topic contains the following type definitions: ■ Table Type Definitions on page 311 ■ Table Status Definitions on page 312 ■ Column Type Definitions on page 313 ■ Domain Type Definitions on page 313 _NUM This column contains a number or an identifying alphanumeric value. _TEXT This column contains text data. _TM This column contains a time value. _TS This column contains a timestamp value. Table 141. 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 146 on page 314. Table 140. Standard Column Suffixes Suffix Value
  • 314. Siebel Physical Model ■ Data Model Type Definitions Siebel Data Model Reference Version 8.2 Rev. A 311 Table Type Definitions Table 142 provides descriptions of the types of tables in the Siebel database. Table 142. 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.
  • 315. Siebel Data Model Reference Version 8.2 Rev. A Siebel Physical Model ■ Data Model Type Definitions 312 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 143. Table Status Definitions Table 143 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 might be 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 143. 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 might be used by customers. Table 142. Table Types in the Siebel Database Table Type Description
  • 316. Siebel Physical Model ■ Data Model Type Definitions Siebel Data Model Reference Version 8.2 Rev. A 313 Column Type Definitions Table 144 provides descriptions for the types of columns in the Siebel database. Domain Type Definitions Table 145 provides descriptions for the domain types of certain columns in the Siebel database. Table 144. 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 146 on page 314. Table 145. 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) can be associated with 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.
  • 317. Siebel Data Model Reference Version 8.2 Rev. A Siebel Physical Model ■ Columns of Numeric Physical Type 314 Columns of Numeric Physical Type Columns 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 Fields Every Siebel table contains the system fields described in Table 146. 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 146. 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 145. Domain Types Domain Type Meaning Domain Contains
  • 318. Siebel Physical Model ■ INTEGRATION_ID Columns Siebel Data Model Reference Version 8.2 Rev. A 315 INTEGRATION_ID Columns Many tables contain a column called INTEGRATION_ID that is used to support integration with back- office applications. Customers use this column to store the unique reference identifiers for corresponding records in their back-office application. For Application Integration Architecture (AIA) integrations, use AIA_INTEG_ID columns. Include Only Field Include 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 Repository Siebel Business Applications includes a set of tables referred to as the Siebel repository tables. These tables store the full definition of a given configuration of Siebel Business Applications, including the database schema and the client configuration. As with other Siebel tables, do not manipulate information in the Siebel repository tables directly. Instead, use Siebel Tools. For more information on how to use Siebel Tools, see Using Siebel Tools. To learn more about the information stored in the repository, see Siebel Object Types Reference. Database Schema Version Each 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, then 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. 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 146. Siebel System Fields Column Name Description
  • 319. Siebel Data Model Reference Version 8.2 Rev. A Siebel Physical Model ■ Limit Checking for Data Types 316 Limit Checking for Data Types The Object Manager imposes limit checking on data of specific types to make sure that every input, regardless of its source, is within specified limits (see Table 147). 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 Schema To make sure that there are no inconsistencies between the Siebel Database Server and the physical database schema, use the Siebel Server utility dbchck.exe (Windows) or dbchck (UNIX). You can use the dbchck utility to validate data relationships, including foreign keys and the list of values. You can also use the DICTUTL utility to verify that all doc objects and rule definitions are correct. For more information about how to use these utilities, see Siebel Enterprise Integration Manager Administration Guide. Party Model Unifies Access to Data The 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 148 lists the extension tables and their corresponding EIM interface tables. Table 147. Input Limits on Data Types Data Type Limit Checking Dates Dates must be in the range of January 1, 1753 to December 31, 4712. Long Maximum size of 16K Text Maximum size of 16K CLOB Maximum size of 128K Table 148. 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
  • 320. Siebel Physical Model ■ Generating a Report about Tables Siebel Data Model Reference Version 8.2 Rev. A 317 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 Tables You 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. 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. Organizations S_ORG_BU EIM_ORG_BU Positions S_POSTN EIM_POSITION Users S_USER EIM_USER Table 148. S_PARTY Extension Tables and Corresponding EIM Interface Tables Data Type Extension Table to S_PARTY EIM Interface Table
  • 321. Siebel Data Model Reference Version 8.2 Rev. A Siebel Physical Model ■ Generating a Report about Tables 318 8 Choose to open, save or cancel the report. NOTE: For more information about generating reports, see Siebel Reports Guide.
  • 322. Siebel Data Model Reference Version 8.2 Rev. A 319 4 Schema Changes This chapter lists the table, table column, and table index changes in the schema for Siebel CRM version 8.2.2.3. It includes the following topics: ■ Siebel Repositories are Combined ■ New Tables for Siebel Business Applications ■ Table Column Changes for Siebel Business Applications on page 320 ■ Table Index Changes for Siebel Business Applications on page 323 Siebel Repositories are Combined For Siebel CRM 8.2 and later, the Siebel Cross-Industry Applications and Siebel Industry Applications repositories have been combined into one. All existing customers who upgrade to Siebel CRM version 8.2, whether they use Siebel Cross-Industry Applications or Siebel Industry Applications, now use the same Siebel Industry Applications repository. New Tables for Siebel Business Applications Table 149 lists tables that are new in version 8.2.2.3. All of these new tables are active. Table 149. New Tables in Version 8.2.2.3 Table Type Project S_BCSTMSG_USER Data (Intersection) Table Sales S_CASE_SKILL_IT Data (Public) Table HS S_DIAG Data (Public) Table Crash Diagnosis S_DIAG_DATA Extension (Siebel) Table Crash Diagnosis S_DIAG_DTL Data (Public) Table Crash Diagnosis S_ED_APPR_POSTN Data (Public) Table Effective Dating S_EVT_KM Extension (Siebel) Table KnowledgeManagement S_EVT_MAIL_STAT Data (Public) Table Activity S_FN_ASSETLB_ED Data (Public) Table Effective Dating S_INC_SKILL Data (Public) Table Incident
  • 323. Siebel Data Model Reference Version 8.2 Rev. A Schema Changes ■ Table Column Changes for Siebel Business Applications 320 Table Column Changes for Siebel Business Applications This topic lists the following changes to table columns that have been implemented in version 8.2.2.3 of the schema: ■ New Table Columns in This Version 8.2.2.3 ■ Changed Table Columns in Version 8.2.2.3 on page 323 New Table Columns in This Version 8.2.2.3 Table 150 lists table columns that are new in version 8.2.2.3. All of these tables are active. Some of the column headings are abbreviated as follows: ■ Opt indicates optional. ■ Len indicates length. ■ Prec indicates precision. NA in a row indicates not applicable. S_INC_SKILL_IT Data (Public) Table Incident S_KM_TMP_DATA Data (Public) Table KnowledgeManagement S_PSAP_SKILL_IT Data (Public) Table Case S_PS_APPL_CON Data (Intersection) Table Case S_PS_APPL_SKILL Data (Public) Table Case S_TAG Data (Public) Object Tagging S_TAG_OBJECT Data (Public) Object Tagging S_TAG_SEED Data (Public) Object Tagging S_TAG_USER Data (Public) Object Tagging Table 150. New Table Columns in Version 8.2.2.3 Table Column Opt Data Type Len Prec Scale Default S_ADDR_PER_ED BUSOBJ_NAME Yes Varchar 75 NA NA NA S_ADDR_PER_ED FUTURE_FLG No Char 1 NA NA No S_ADDR_PER_ED REQUEST_DELETE_FLG No Char 1 NA NA No Table 149. New Tables in Version 8.2.2.3 Table Type Project
  • 324. Schema Changes ■ Table Column Changes for Siebel Business Applications Siebel Data Model Reference Version 8.2 Rev. A 321 S_ADDR_PER_ED STATUS_CD No Varchar 30 NA NA Approved S_BRDCST_MSG DISA_DISMISS_FLG No Char 1 NA NA No S_BRDCST_MSG PR_RECIP_USER_ID Yes Varchar 15 NA NA NA S_CASE_BNFTPLAN PS_APPL_ID Yes Varchar 15 NA NA NA S_CONTACT_ED BUSOBJ_NAME Yes Varchar 75 NA NA NA S_CONTACT_ED FUTURE_FLG No Char 1 NA NA No S_CONTACT_ED REQUEST_DELETE_FLG No Char 1 NA NA No S_CONTACT_ED STATUS_CD No Varchar 30 NA NA Approved S_CON_ADDR_ED BUSOBJ_NAME Yes Varchar 75 NA NA NA S_CON_ADDR_ED FUTURE_FLG No Char 1 NA NA No S_CON_ADDR_ED REQUEST_DELETE_FLG No Char 1 NA NA No S_CON_ADDR_ED STATUS_CD No Varchar 30 NA NA Approved S_ED_FIELD ENABL_STAT_DSP_FLG No Char 1 NA NA No S_ED_FIELD ENBL_FUT_EFFDT_FLG No Char 1 NA NA No S_ED_LINK ENABL_STAT_DSP_FLG No Char 1 NA NA No S_ED_LINK ENBL_FUT_EFFDT_FLG No Char 1 NA NA No S_FN_ASSET_LIAB ED_DELETED_FLG No Char 1 NA NA No S_FN_ASSET_LIAB ED_ENABLED_FLG No Char 1 NA NA Yes S_FN_INCMEXP_ED BUSOBJ_NAME Yes Varchar 75 NA NA NA S_FN_INCMEXP_ED FUTURE_FLG No Char 1 NA NA No S_FN_INCMEXP_ED REQUEST_DELETE_FLG No Char 1 NA NA No S_FN_INCMEXP_ED STATUS_CD No Varchar 30 NA NA Approved S_GROUP_CON_ED BUSOBJ_NAME Yes Varchar 75 NA NA NA S_GROUP_CON_ED FUTURE_FLG No Char 1 NA NA No S_GROUP_CON_ED REQUEST_DELETE_FLG No Char 1 NA NA No S_GROUP_CON_ED STATUS_CD No Varchar 30 NA NA Approved S_INCIDENT ASGN_DT Yes UTC DateTime 7 NA NA NA S_LOCALE FRIDAY_WORK_FLG No Char 1 NA NA Yes S_LOCALE MONDAY_WORK_FLG No Char 1 NA NA Yes Table 150. New Table Columns in Version 8.2.2.3 Table Column Opt Data Type Len Prec Scale Default
  • 325. Siebel Data Model Reference Version 8.2 Rev. A Schema Changes ■ Table Column Changes for Siebel Business Applications 322 S_LOCALE POSIX_LOCALE_CD Yes Varchar 30 NA NA NA S_LOCALE SATURDAY_WORK_FLG No Char 1 NA NA No S_LOCALE SUNDAY_WORK_FLG No Char 1 NA NA No S_LOCALE THURSDAY_WORK_FLG No Char 1 NA NA Yes S_LOCALE TUESDAY_WORK_FLG No Char 1 NA NA Yes S_LOCALE WEDNESDAY_WORK_FLG No Char 1 NA NA Yes S_LOCALE WEEK_START_DAY_CD Yes Varchar 30 NA NA NA S_ORG_GROUP_ED BUSOBJ_NAME Yes Varchar 75 NA NA NA S_ORG_GROUP_ED FUTURE_FLG No Char 1 NA NA No S_ORG_GROUP_ED REQUEST_DELETE_FLG No Char 1 NA NA No S_ORG_GROUP_ED STATUS_CD No Varchar 30 NA NA Approved S_PS_APPL APPLICANT_COMMENTS Yes Varchar 150 0 NA NA NA S_PS_APPL EXT_PLCY_SESS_REF Yes Varchar 15 NA NA NA S_PS_APPL PROC_TYPE_CD Yes Varchar 30 NA NA NA S_REP_PARM_DEF FILTER_COLUMN_FLG No Char 1 NA NA No S_REP_PARM_DEF MAX_DATETM_ALWD_TS Yes UTC DateTime 7 NA NA NA S_REP_PARM_DEF MAX_DATE_ALWD_DT Yes Date 7 NA NA NA S_REP_PARM_DEF MAX_NUM_VAL_ALWD Yes Number 22 22 7 NA S_REP_PARM_DEF MAX_TEXT_SIZE_ALWD Yes Number 22 10 0 NA S_REP_PARM_DEF MIN_DATETM_ALWD_TS Yes UTC DateTime 7 NA NA NA S_REP_PARM_DEF MIN_DATE_ALWD_DT Yes Date 7 NA NA NA S_REP_PARM_DEF MIN_NUM_VAL_ALWD Yes Number 22 22 7 NA S_USER PR_TAG_ID Yes Varchar 15 NA NA NA S_XMLP_REPOUTPT VIEW_MODE_CD Yes Varchar 30 NA NA NA T_DETAIL1_ED BUSOBJ_NAME Yes Varchar 75 NA NA NA T_DETAIL1_ED FUTURE_FLG No Char 1 NA NA No T_DETAIL1_ED REQUEST_DELETE_FLG No Char 1 NA NA No T_DETAIL1_ED STATUS_CD No Varchar 30 NA NA Approved Table 150. New Table Columns in Version 8.2.2.3 Table Column Opt Data Type Len Prec Scale Default
  • 326. Schema Changes ■ Table Index Changes for Siebel Business Applications Siebel Data Model Reference Version 8.2 Rev. A 323 Changed Table Columns in Version 8.2.2.3 Table 151 lists table columns that have changed in version 8.2.2.3. Table Index Changes for Siebel Business Applications This topic lists the following changes to table indexes that have been implemented in version 8.2.2.3 of the schema: ■ New Table Indexes in Version 8.2.2.3 ■ Changed Table Indexes in Version 8.2.2.3 on page 325 T_DETAIL2_ED BUSOBJ_NAME Yes Varchar 75 NA NA NA T_DETAIL2_ED FUTURE_FLG No Char 1 NA NA No T_DETAIL2_ED REQUEST_DELETE_FLG No Char 1 NA NA No T_DETAIL2_ED STATUS_CD No Varchar 30 NA NA Approved T_MASTER_DTL_ED BUSOBJ_NAME Yes Varchar 75 NA NA NA T_MASTER_DTL_ED FUTURE_FLG No Char 1 NA NA No T_MASTER_DTL_ED REQUEST_DELETE_FLG No Char 1 NA NA No T_MASTER_DTL_ED STATUS_CD No Varchar 30 NA NA Approved T_MASTER_ED BUSOBJ_NAME Yes Varchar 75 NA NA NA T_MASTER_ED FUTURE_FLG No Char 1 NA NA No T_MASTER_ED REQUEST_DELETE_FLG No Char 1 NA NA No T_MASTER_ED STATUS_CD No Varchar 30 NA NA Approved Table 151. Table Columns That Have Changed in Version 8.2.2.3 Table Column Type of Change Previous Value New Value S_CASE_TMPLITM NAME Length 50 100 S_XMLP_REPOUTPT BOOKMARK_VAL Length 250 1999 Table 150. New Table Columns in Version 8.2.2.3 Table Column Opt Data Type Len Prec Scale Default
  • 327. Siebel Data Model Reference Version 8.2 Rev. A Schema Changes ■ Table Index Changes for Siebel Business Applications 324 New Table Indexes in Version 8.2.2.3 Table 152 lists table indexes that are new in version 8.2.2.3. All of these new table indexes are active and none of them are unique. Table 152. New Table Indexes in Version 8.2.2.3 Table Index Columns S_ADDR_PER_ED S_ADDR_PER_ED_M1 (PAR_ROW_ID,FIELD_NAME,EFF_START_DATE, INTER_ROW_ID) S_ADDR_PER_ED S_ADDR_PER_ED_M2 (PAR_ROW_ID,FIELD_NAME,STATUS_CD, EFF_END_DATE,EFF_START_DATE) S_ADDR_PER_ED S_ADDR_PER_ED_M3 (PAR_ROW_ID,FIELD_NAME,FIELD_VALUE, STATUS_CD) S_CASE_BNFTPLAN S_BNFT_PLAN_F3 (PS_APPL_ID) S_CONTACT_ED S_CONTACT_ED_M1 (PAR_ROW_ID,FIELD_NAME,EFF_START_DATE, INTER_ROW_ID) S_CONTACT_ED S_CONTACT_ED_M2 (PAR_ROW_ID,FIELD_NAME,STATUS_CD, EFF_END_DATE,EFF_START_DATE) S_CONTACT_ED S_CONTACT_ED_M3 (PAR_ROW_ID,FIELD_NAME,FIELD_VALUE, STATUS_CD) S_CON_ADDR_ED S_CON_ADDR_ED_M1 (PAR_ROW_ID,FIELD_NAME,EFF_START_DATE) S_CON_ADDR_ED S_CON_ADDR_ED_M2 (PAR_ROW_ID,FIELD_NAME,STATUS_CD, EFF_END_DATE,EFF_START_DATE) S_CON_ADDR_ED S_CON_ADDR_ED_M3 (PAR_ROW_ID,FIELD_NAME,FIELD_VALUE, STATUS_CD) S_FN_INCMEXP_ED S_FN_INCMEXP_ED_M1 (PAR_ROW_ID,FIELD_NAME,EFF_START_DATE, INTER_ROW_ID) S_FN_INCMEXP_ED S_FN_INCMEXP_ED_M2 (PAR_ROW_ID,FIELD_NAME,STATUS_CD, EFF_END_DATE,EFF_START_DATE) S_FN_INCMEXP_ED S_FN_INCMEXP_ED_M3 (PAR_ROW_ID,FIELD_NAME,FIELD_VALUE, STATUS_CD) S_GROUP_CON_ED S_GROUP_CON_ED_M1 (PAR_ROW_ID,FIELD_NAME,EFF_START_DATE) S_GROUP_CON_ED S_GROUP_CON_ED_M2 (PAR_ROW_ID,FIELD_NAME,STATUS_CD, EFF_END_DATE,EFF_START_DATE) S_GROUP_CON_ED S_GROUP_CON_ED_M3 (PAR_ROW_ID,FIELD_NAME,FIELD_VALUE, STATUS_CD) S_ORG_GROUP_ED S_ORG_GROUP_ED_M1 (PAR_ROW_ID,FIELD_NAME,EFF_START_DATE, INTER_ROW_ID)
  • 328. Schema Changes ■ Table Index Changes for Siebel Business Applications Siebel Data Model Reference Version 8.2 Rev. A 325 Changed Table Indexes in Version 8.2.2.3 Table 153 lists table indexes that have been activated in version 8.2.2.3. S_ORG_GROUP_ED S_ORG_GROUP_ED_M2 (PAR_ROW_ID,FIELD_NAME,STATUS_CD, EFF_END_DATE,EFF_START_DATE) S_ORG_GROUP_ED S_ORG_GROUP_ED_M3 (PAR_ROW_ID,FIELD_NAME,FIELD_VALUE, STATUS_CD) S_PS_APPL S_PS_APPL_M2 (EXT_PLCY_SESS_REF) T_DETAIL1_ED T_DETAIL1_ED_M1 (PAR_ROW_ID,FIELD_NAME,EFF_START_DATE, INTER_ROW_ID) T_DETAIL2_ED T_DETAIL2_ED_M1 (PAR_ROW_ID,FIELD_NAME,EFF_START_DATE, INTER_ROW_ID) T_MASTER_DTL_ED T_MASTER_DTL_ED_M1 (PAR_ROW_ID,FIELD_NAME,EFF_START_DATE) T_MASTER_ED T_MASTER_ED_M1 (PAR_ROW_ID,FIELD_NAME,EFF_START_DATE, INTER_ROW_ID) Table 153. Table Indexes That Have Been Activated in Version 8.2.2.3 Table Index S_ACT_CONTACT S_ACT_CONTACT_M1 S_ACT_EMP S_ACT_EMP_M5 S_CONTACT S_CONTACT_M23 S_CONTACT_BU S_CONTACT_BU_M3 S_CONTACT_INFO S_CONTACT_INFO_M1 S_EVT_ACT S_EVT_ACT_M12 S_OPTY S_OPTY_M10 S_ORG_EXT S_ORG_EXT_M23 S_PARTY S_PARTY_M5 S_POSTN S_POSTN_M4 S_POSTN_CON S_POSTN_CON_M4 S_PROJ S_PROJ_M9 S_SRV_REQ S_SRV_REQ_M12 S_USER S_USER_M3 Table 152. New Table Indexes in Version 8.2.2.3 Table Index Columns
  • 329. Siebel Data Model Reference Version 8.2 Rev. A Schema Changes ■ Table Index Changes for Siebel Business Applications 326 Table 154 lists table indexes that have been changed from nonunique to unique in version 8.2.2.3. Table 154. Table Indexes That Have Changed from Nonunique to Unique in Version 8.2.2.3 Table Index S_ADDR_PER_ED S_ADDR_PER_ED_U1 S_CONTACT_ED S_CONTACT_ED_U1 S_CON_ADDR_ED S_CON_ADDR_ED_U1 S_FN_INCMEXP_ED S_FN_INCMEXP_ED_U1 S_GROUP_CON_ED S_GROUP_CON_ED_U1 S_ORG_GROUP_ED S_ORG_GROUP_ED_U1 T_DETAIL1_ED T_DETAIL1_ED_U1 T_DETAIL2_ED T_DETAIL2_ED_U1 T_MASTER_DTL_ED T_MASTER_DTL_ED_U1 T_MASTER_ED T_MASTER_ED_U1
  • 330. Siebel Data Model Reference Version 8.2 Rev. A 327 Index A account ERD about 20 diagram 22 support for Dynamic Hierarchy 20 support for Global Account Views 20 tables 20 account targeting ERD about 174 diagram 175 tables 174 activity ERD about 176 diagram 177 tables 176 adjustment group ERD about 23 diagram 24 tables 23 affiliations and best times ERD about 178 diagram 179 tables 178 agencies/agent ERD about 180 diagram 181 tables 180 agreement See CME agreement ERD AIA_INTEG_ID columns, about 315 alerts See CME alert ERD apparel See textile, apparel, and footwear ERD asset management ERD about 25 diagram 26 tables 25 tracking asset instances 25 assets See CME energy products, service, and usage ERD auction ERD about 27 diagram 28 tables 27 auto email response generator ERD about 29 diagram 30 tables 29 Automotive automotive retail ERD 182 dealer sales and service promotion 206 vehicle collection ERD 301 vehicle ERD 299 vehicle financing ERD 303 vehicle sales ERD 305 automotive retail ERD about 182 diagram 183 tables 182 B banking See commercial banking ERD See Flexcube universal banking integration ERD benefit case management ERD. See public sector benefit case management ERD best call hours See routes and best call hours ERD brick ERD about 184 diagram 185 tables 184 C campaign management See marketing campaign ERD case lead management ERD. See public sector case lead management ERD CG promotion planning ERD about 31 diagram 33 tables 31 chat See community/chat discussion ERD child welfare ERD. See public sector child welfare ERD clinical study management ERD about 186 diagram 188 tables 186
  • 331. Siebel Data Model Reference Version 8.2 Rev. A Index ■ D 328 CME account ERD about 189 diagram 190 tables 189 CME agreement ERD about 191 diagram 192 tables 191 CME alert ERD about 193 diagram 194 tables 193 CME energy products, service, and usage ERD about 195 diagram 196 tables 195 CME order management ERD about 197 diagram 198 tables 197 columns AIA_INTEG_ID columns, about 315 domain type definitions 313 INTEGRATION_ID columns, about 315 naming conventions 309 numeric physical type 314 type definitions 313 commercial banking ERD about 199 diagram 201 tables 199 commercial insurance ERD about 202 diagram 203 tables 202 Communications, Media, Energy CME account ERD 189 CME agreement ERD CME alert ERD 193 CME energy products, service, and usage ERD 195 CME order management ERD 197 pricing comparison ERD 114 community/chat discussion ERD about 204 diagram 205 tables 204 compensation planning administration ERD about 34 diagram 35 tables 34 compensation planning execution ERD about 36 diagram 37 tables 36 competency management system ERD about 38 diagram 39 tables 38 Consumer Sector account targeting ERD 174 best hours entity 279 CG promotion planning ERD 31 objectives ERD 257 sales volume planning ERD 281 consumer sector territory management - consumer sector ERD 293 contact identity ERD See public sector contact identity ERD content management ERD about 40 diagram 41 tables 40 content object See content management ERD content process See content management ERD contract conditions ERD about 42 diagram 43 tables 42 contracts ERD about 44 diagram 45 tables 44 credit alerts See CME alert ERD cross-industry applications ERD descriptions 17 Customer Data Item, about 46 D data (intersection) table type about 311 obsolete, table marked as 311 data (private) table type, about 311 data (public) table type about 311 obsolete, table marked as 311 data model overview 13 data types limit checking 316 data visibility ERD about 46 diagram 48
  • 332. Index ■ E Siebel Data Model Reference Version 8.2 Rev. A 329 tables 46 Database Marketing, marketing program ERD 86 database schema version number, finding and format 315 dealer sales and service promotion ERD about 206 diagram 207 tables 206 defect tracking See product quality tracking ERD design See schema discussion See community/chat discussion ERD document ID and tax ID ERD about 208 diagram 209 tables 208 domain type definitions 313 Dun Bradstreet integration ERD about 49 diagram 50 tables 49 Dynamic Hierarchy, support by account entity 20 E employee KPI ERD about 51 diagram 52 tables 51 Employee Relationship Management compensation planning administration ERD 34 compensation planning execution ERD 36 competency management system ERD 38 employee KPI ERD 51 performance review ERD 107 employees field service scheduler ERD 57 time sheet ERD 153 entitlement items, service agreement ERD 137 ERDs account targeting, diagram 175 account targeting, tables 174 account, diagram 22 account, tables 20 activity, diagram 177 activity, tables 176 adjustment group, diagram 24 adjustment group, tables 23 affiliations and best times, diagram 179 affiliations and best times, tables 178 agencies/agent, diagram 181 agencies/agent, tables 180 asset management, diagram 26 asset management, tables 25 auction, diagram 28 auction, tables 27 auto email response generator, diagram 30 auto email response generator, tables 29 automotive retail, diagram 183 automotive retail, tables 182 brick, diagram 185 brick, tables 184 CG promotion planning, diagram 33 CG promotion planning, tables 31 clinical study management, diagram 188 clinical study management, tables 186 CME account, diagram 190 CME account, tables 189 CME agreement, diagram 192 CME agreement, tables 191 CME alert, diagram 194 CME alert, tables 193 CME energy products, service, and usage, diagram 196 CME energy products, service, and usage, tables 195 CME order management ERD, diagram 198 CME order management ERD, tables 197 commercial banking, diagram 201 commercial banking, tables 199 commercial insurance, diagram 203 commercial insurance, tables 202 community/chat discussion, diagram 205 community/chat discussion, tables 204 compensation planning administration, diagram 35 compensation planning administration, tables 34 compensation planning execution, diagram 37 compensation planning execution, tables 36 competency management system, diagram 39 competency management system, tables 38 content management, diagram 41 content management, tables 40 contract conditions, diagram 43 contract conditions, tables 42 contracts, diagram 45
  • 333. Siebel Data Model Reference Version 8.2 Rev. A Index ■ E 330 contracts, tables 44 conventions, description of 14 data visibility, diagram 48 data visibility, tables 46 dealer sales and service promotion, diagram 207 dealer sales and service promotion, tables 206 document ID and tax ID, diagram 209 document ID and tax ID, tables 208 Dun Bradstreet integration, diagram 50 Dun Bradstreet integration, tables 49 employee KPI, diagram 52 employee KPI, tables 51 event tax administration, diagram 211 event tax administration, tables 210 exclusive arc relationship, diagram conventions 15 expense reports, diagram 54 expense reports, tables 53 field service inventory, diagram 56 field service inventory, tables 55 field service scheduler, diagram 58 field service scheduler, tables 57 financial account application, diagram 215 financial account application, tables 214 financial account, diagram 213 financial account, tables 212 financial investments, diagram 217 financial investments, tables 216 financial products, diagram 219 financial products, tables 218 financial services events, diagram 222 financial services events, tables 220 fleet management, diagram 225 fleet management, tables 223 Flexcube universal banking integration, diagram 227 Flexcube universal banking integration, tables 226 forecasts, diagram 60 forecasts, tables 59 general diagram conventions 14 group insurance policies, diagram 229 group insurance policies, tables 228 group pensions, diagram 231 group pensions, tables 230 health provider/provider group, diagram 233 health provider/provider group, tables 232 high tech marketing development fund, tables 61 high tech special pricing authorization, diagram 235 high tech special pricing authorization, tables 234 hospitality category, diagram 237 hospitality category, tables 236 institutional sales, diagram 239 institutional sales, tables 238 insurance claims, diagram 242 insurance claims, tables 240 insurance policies, diagram 244 insurance policies, tables 243 invoiceable charges, diagram 65 invoiceable charges, tables 63 invoices, diagram 67 invoices, tables 66 lead management, diagram 70 lead management, tables 68 life insurance policy, diagram 246 life insurance policy, tables 245 loyalty flowchart and formula, diagram 252 loyalty flowchart and formula, tables 251 loyalty, diagram 250 loyalty, tables 248 managed care, diagram 254 managed care, tables 253 marketing budget request, diagram 72 marketing budget request, tables 71 marketing campaign, diagram 74 marketing campaign, tables 73 marketing collaboration, diagram 76 marketing collaboration, tables 75 marketing encyclopedia, diagram 78 marketing encyclopedia, tables 77 marketing event driven dialogue, diagram 80 marketing event driven dialogue, tables 79 marketing events, diagram 83 marketing events, tables 81 marketing plans, diagram 85 marketing plans, tables 84 marketing program, diagram 88 marketing program, tables 86 marketing resource management: document, diagram 90 marketing resource management: document, tables 89 medical education event management, diagram 256 medical education event management, tables 255 objectives, diagram 258 objectives, tables 257 opportunity management, diagram 92 opportunity management, tables 91
  • 334. Index ■ E Siebel Data Model Reference Version 8.2 Rev. A 331 order and promotion, diagram 94 order and promotion, tables 93 order life cycle, diagram 96 order life cycle, tables 95 orders, diagram 98 orders, tables 97 partner collaboration, diagram 100 partner collaboration, tables 99 partner program registration, diagram 102 partner program registration, tables 101 party model, diagram 104 party model, tables 103 payments, diagram 106 payments, tables 105 performance review, diagram 109 performance review, tables 107 personal account, diagram 111 personal account, tables 110 personal financial review, diagram 113 personal financial review, tables 112 personalized content delivery, diagram 260 personalized content delivery, tables 259 pricing comparison, diagram 115 pricing comparison, tables 114 pricing, diagram 117 pricing, tables 116 product promotion, tables 118 product quality tracking, diagram 121 product quality tracking, tables 120 product recommendation, diagram 123 product recommendation, tables 122 products or services, diagram 125 products or services, tables 124 professional services, diagram 127 professional services, tables 126 promotion group, diagram 130 promotion group, tables 128 public sector benefit case management, diagram 263 public sector benefit case management, tables 261 public sector case lead management, diagram 266 public sector case lead management, tables 264 public sector child welfare, diagram 268 public sector child welfare, tables 267 public sector contact identity, diagram 270 public sector contact identity, tables 269 public sector evidence management, diagram 272 public sector evidence management, tables 271 public sector incident management, diagram 274 public sector incident management, tables 273 public sector service provider and referral management, diagram 276 public sector service provider and referral management, tables 275 real-time scheduler integration, diagram 278 real-time scheduler integration, tables 277 recursive relationship, diagram conventions 16 revenue, diagram 132 revenue, tables 131 revision table 17, 171 routes and best call hours, diagram 280 routes and best call hours, tables 279 sales hierarchy and credit assignment, diagram 134 sales hierarchy and credit assignment, tables 133 sales portfolio management, diagram 136 sales portfolio management, tables 135 sales volume planning, diagram 282 sales volume planning, tables 281 sample management, diagram 284 sample management, tables 283 service agreement, diagram 138 service agreement, tables 137 service calendars and work shifts, diagram 140 service calendars and work shifts, tables 139 service request, diagram 142 service request, tables 141 shipment, diagram 144 shipment, tables 143 Siebel Assistant, diagram 146 Siebel Assistant, tables 145 special rate list, diagram 286 special rate list, tables 285 syndicated data, diagram 288 syndicated data, tables 287 teller administration, diagram 290 teller administration, tables 289 territory alignment - quota assignment diagram 292 territory alignment - quota assignment, tables 291 territory management - consumer sector, diagram 294 territory management - consumer sector, tables 293
  • 335. Siebel Data Model Reference Version 8.2 Rev. A Index ■ F 332 territory management - life sciences, diagram 296 territory management - life sciences, tables 295 territory management, diagram 148 territory management, tables 147 territory quota rollup, diagram 150 territory quota rollup, tables 149 textile, apparel, and footwear, diagram 152 textile, apparel, and footwear, tables 151 time sheet, diagram 154 time sheet, tables 153 trade promotions, diagram 156 trade promotions, tables 155 training curriculum course, diagram 158 training curriculum course, tables 157 training test engine, diagram 160 training test engine, tables 159 universal customer master, diagram 298 universal customer master, tables 297 vehicle collection, diagram 302 vehicle collection, tables 301 vehicle financing, diagram 304 vehicle financing, tables 303 vehicle sales, diagram 306 vehicle sales, tables 305 vehicle, diagram 300 vehicle, tables 299 versioned object definition, diagram 162 versioned object definition, tables 161 warranty claim, diagram 168 warranty claim, tables 166 warranty, diagram 165 warranty, tables 163 work order, diagram 170 work order, tables 169 event tax administration ERD about 210 diagram 211 tables 210 evidence management ERD. See public sector evidence management ERD exclusive arc relationship about 15 diagram conventions 15 expense reports ERD about 53 diagram 54 tables 53 extension (Siebel) table type about 311 obsolete table marked as 311 extension table type, about 311 F field service inventory ERD about 55 diagram 56 tables 55 field service scheduler ERD about 57 diagram 58 tables 57 financial account application ERD about 214 diagram 215 tables 214 financial account ERD about 212 diagram 213 tables 212 financial accounts financial account application ERD 214 financial account ERD 212 personal account ERD 110 financial investments ERD about 216 diagram 217 tables 216 financial products ERD about 218 diagram 219 tables 218 financial review, personal financial review ERD 112 Financial Services agencies/agent ERD 180 commercial banking ERD 199 commercial insurance ERD 202 financial account application ERD 214 financial account ERD 212 financial investments ERD 216 financial products ERD 218 financial services events ERD 220 Flexcube universal banking integration ERD group insurance policies ERD 228 group pensions ERD 230 health provider/provider group ERD 232 institutional sales ERD 238 insurance claims ERD 240 insurance policies ERD 243 life insurance policy ERD 245 teller administration ERD 289 financial services events ERD about 220 diagram 222 tables 220
  • 336. Index ■ G Siebel Data Model Reference Version 8.2 Rev. A 333 fleet management ERD about 223 diagram 225 tables 223 Flexcube universal banking integration ERD about 226 diagram 227 tables 226 footwear See textile, apparel, and footwear ERD forecasts ERD about 59 diagram 60 tables 59 fraud alerts See CME alert ERD G generating table report 317 Global Account Views, support by account entity 20 group insurance policies ERD about 228 diagram 229 tables 228 group pensions ERD about 230 diagram 231 tables 230 H health provider/provider group ERD about 232 diagram 233 tables 232 high tech marketing development fund ERD about 61 tables 61 high tech special pricing authorization ERD about 234 diagram 235 tables 234 Hospitality event tax administration ERD 210 hospitality category ERD about 236 diagram 237 tables 236 I incident management ERD. See public sector incident management ERD Include Only field 315 index column fields 315 index naming conventions 309 industry applications ERD descriptions 171 institutional sales ERD about 238 diagram 239 tables 238 insurance commercial insurance ERD 202 group insurance policies ERD 228 insurance claims ERD 240 insurance policies ERD 243 life insurance policy ERD 245 personal account ERD 110 insurance claims ERD about 240 diagram 242 tables 240 insurance policies ERD about 243 diagram 244 tables 243 INTEGRATION_ID columns, about 315 invoiceable charges ERD about 63 diagram 65 tables 63 invoices ERD about 66 diagram 67 tables 66 L lead management ERD about 68 diagram 70 tables 68 life insurance policy ERD about 245 diagram 246 tables 245 Life Sciences activity ERD 176 affiliations and best times ERD 178 brick ERD 184 clinical study management ERD 186 community/chat discussion ERD 204 managed care ERD 253 medical education event management ERD 255 personalized content delivery ERD 259 sample management ERD 283
  • 337. Siebel Data Model Reference Version 8.2 Rev. A Index ■ M 334 syndicated data ERD 287 territory management - life sciences ERD 295 limit checking for data types 316 loans, commercial banking entity 199 logical model ERD conventions 14 ERD descriptions for Siebel cross-industry applications 17 ERD descriptions for Siebel industry applications 171 loyalty ERD about 247 diagram 250 tables 248 loyalty flowchart and formula ERD about 251 diagram 252 tables 251 M managed care ERD about 253 diagram 254 tables 253 Marketing CG promotion planning ERD 31 Dun Bradstreet integration ERD 49 forecasts ERD 59 high tech marketing development fund ERD 61 lead management ERD 68 marketing budget request ERD 71 marketing campaign ERD 73 marketing collaboration ERD 75 marketing encyclopedia ERD 77 marketing event driven dialogue ERD 79 marketing events ERD 81 marketing plans ERD 84 marketing program ERD 86 marketing resource management: document ERD 89 marketing budget request ERD about 71 diagram 72 tables 71 marketing campaign ERD about 73 diagram 74 tables 73 marketing collaboration ERD about 75 diagram 76 tables 75 marketing development funds See CG promotion planning ERD marketing encyclopedia ERD about 77 diagram 78 tables 77 marketing event driven dialogue ERD about 79 diagram 80 tables 79 marketing events ERD about 81 diagram 83 tables 81 marketing plans ERD about 84 diagram 85 tables 84 marketing program ERD about 86 diagram 88 tables 86 marketing resource management: document ERD about 89 diagram 90 tables 89 Master Data Item, about 46 MDFs See CG promotion planning ERD MedEd event management See medical education event management ERD medical education event management ERD about 255 diagram 256 tables 255 mini brick See brick ERD N naming conventions columns 309 indexes 309 physical model listings, abbreviations used 310 table names 307 table prefixes 308 table suffixes 308 non-Siebel application products, caution about inserting or updating data 14
  • 338. Index ■ O Siebel Data Model Reference Version 8.2 Rev. A 335 normalized, defined 13 O objectives ERD about 257 diagram 258 tables 257 opportunity management ERD about 91 diagram 92 tables 91 Oracle Applications about use of AIA_INTEG_ID columns 315 about use of INTEGRATION_ID columns 315 order and promotion ERD about 93 diagram 94 tables 93 order life cycle ERD about 95 diagram 96 tables 95 orders ERD about 97 diagram 98 tables 97 overview of Siebel data model 13 P partner collaboration ERD about 99 diagram 100 tables 99 partner program registration ERD about 101 diagram 102 tables 101 party model ERD about 103 diagram 104 tables 103 party model, about 316 party, defined 103 payments ERD about 105 diagram 106 tables 105 performance review ERD about 107 diagram 109 tables 107 personal account ERD about 110 diagram 111 tables 110 personal financial review ERD about 112 diagram 113 tables 112 personalized content delivery ERD about 259 diagram 260 tables 259 physical model AIA_INTEG_ID columns, about 315 column naming conventions 309 column type definitions 313 columns of numeric physical type 314 database schema version number, finding and format 315 domain type definitions 313 Include Only field 315 index naming conventions 309 INTEGRATION_ID columns, about 315 limit checking for data types 316 party model, about 316 physical model listings, abbreviations used 310 Siebel repository tables, about 315 Siebel system fields 314 table naming conventions 307 table report, about 317 table status definitions 312 table type definitions 311 validating Siebel Schema 316 physicians, health provider/provider group ERD 232 prescription information, syndicated data ERD 287 pricing comparison ERD about 114 diagram 115 tables 114 pricing ERD about 116 diagram 117 tables 116 product promotion ERD about 118 tables 118 product quality tracking ERD about 120 diagram 121 tables 120 product recommendation ERD about 122
  • 339. Siebel Data Model Reference Version 8.2 Rev. A Index ■ R 336 diagram 123 tables 122 products or services ERD about 124 diagram 125 tables 124 professional services ERD about 126 diagram 127 tables 126 projects, professional services ERD 126 promotion group ERD about 128 diagram 130 tables 128 protocols See clinical study management ERD public sector benefit case management ERD about 261 diagram 263 tables 261 public sector case lead management ERD about 264 diagram 266 tables 264 public sector child welfare ERD about 267 diagram 268 tables 267 public sector contact identity ERD about diagram 270 tables 269 public sector evidence management ERD about 271 diagram 272 tables 271 public sector incident management ERD about 273 diagram 274 tables 273 public sector service provider and referral management ERD about 275 diagram 276 tables 275 R real-time scheduler integration ERD about 277 diagram 278 tables 277 recursive relationship about 16 diagram conventions 16 report about tables generating 317 repository, about Siebel repository 315 revenue ERD about 131 diagram 132 tables 131 routes and best call hours ERD about 279 diagram 280 tables 279 S Sales Dun Bradstreet integration ERD 49 forecasts ERD 59 high tech special pricing authorization ERD 234 lead management ERD 68 marketing encyclopedia ERD 77 opportunity management ERD 91 routes and best call hours ERD 279 sales hierarchy and credit assignment ERD sales portfolio management ERD 135 territory alignment - quota assignment ERD 291 territory management - life sciences ERD 295 territory management ERD 147 territory quota rollup ERD 149 sales hierarchy and credit assignment ERD about 133 diagram 134 tables 133 Sales Hierarchy Module See sales hierarchy and credit assignment ERD sales portfolio management ERD about 135 diagram 136 tables 135 sales volume planning ERD about 281 diagram 282 tables 281 sample management ERD about 283 diagram 284 tables 283 schema database schema version number, finding and
  • 340. Index ■ T Siebel Data Model Reference Version 8.2 Rev. A 337 format 315 defined 13 validating Siebel Schema 316 Service field service inventory ERD 55 field service scheduler ERD 57 invoiceable charges ERD 63 invoices ERD 66 products or services ERD 124 service agreement ERD 137 service calendars and work shifts ERD 139 service request ERD 141 territory management - consumer sector ERD 293 warranty ERD 163 service activities, field service scheduler ERD 57 service agreement ERD about 137 diagram 138 tables 137 service calendars and work shifts ERD about 139 diagram 140 tables 139 service provider and referral management ERD. See public sector service provider and referral management ERD service region, field service scheduler ERD 57 service request ERD about 141 diagram 142 tables 141 service requests See CME account ERD services See CME energy products, service, and usage ERD shipment ERD about 143 diagram 144 tables 143 Siebel Assistant ERD about 145 diagram 146 tables 145 Siebel repository, about 315 Siebel system fields 314 special ERD conventions exclusive arc relationship 15 recursive relationship 16 special rate list ERD about 285 diagram 286 tables 285 syndicated data ERD about 287 diagram 288 tables 287 system fields 314 T table columns changed in version 8.2.2.3 323 new in version 8.2.2.3 320 table indexes changed in version 8.2.2.3 325 new in version 8.2.2.3 324 tables generating report 317 naming conventions 307 new in version 8.2.2.3 319 prefix naming conventions 308 suffix naming conventions 308 table status definitions 312 types of 311 tax ID See document ID and tax ID ERD teller administration ERD about 289 diagram 290 tables 289 territory alignment - quota assignment ERD about 291 diagram 292 tables 291 territory management - consumer sector ERD about 293 diagram 294 tables 293 territory management - life sciences ERD about 295 diagram 296 tables 295 territory management ERD about 147 diagram 148 tables 147 territory quota rollup ERD about 149 diagram 150 tables 149 tests, training test engine ERD 159 textile, apparel, and footwear ERD
  • 341. Siebel Data Model Reference Version 8.2 Rev. A Index ■ U 338 about 151 diagram 152 tables 151 time sheet ERD about 153 diagram 154 tables 153 trade promotions ERD about 155 diagram 156 tables 155 training curriculum course ERD about 157 diagram 158 tables 157 training test engine ERD about 159 diagram 160 tables 159 trouble tickets See CME account ERD U universal customer master ERD about 297 diagram 298 tables 297 V validating Siebel Schema 316 vehicle collection ERD about 301 diagram 302 tables 301 vehicle ERD about 299 diagram 300 tables 299 vehicle financing ERD about 303 diagram 304 tables 303 vehicle sales ERD about 305 diagram 306 tables 305 versioned object definition ERD about 161 diagram 162 tables 161 W warranty claim ERD about 166 diagram 168 tables 166 warranty ERD about 163 diagram 165 tables 163 work order ERD about 169 diagram 170 tables 169 work shifts See service calendars and work shifts ERD workflow process See content management ERD

×