Siebel Data Model ReferenceVersion 8.0December 2006 Copyright 2005, 2006, Oracle. All rights reserved.The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.PRODUCT MODULES AND OPTIONS. This guide contains descriptions of modules that are optional and for which you may not have purchased a license. Siebels Sample Database also includes data related to these optional modules. As a result, your software implementation may differ from descriptions in this guide. To find out more about the modules your organization has purchased, see your corporate purchasing agent or your Siebel sales representative.If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:U.S. GOVERNMENT RIGHTS. Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party. Siebel Data Model Reference Version 8.0 3ContentsSiebel Data Model Reference 1Chapter 1: Whats New in This ReleaseChapter 2: Data Model OverviewChapter 3: Understanding the Logical ModelEntity Relationship Diagram Conventions11General Entities12Exclusive Arc Relationship12Recursive Relationship13Entity Relationship Diagrams and Descriptions14Account17Adjustment Group20Asset Management22Auction24Auto Email Response Generator26CG Promotion Planning28 Compensation Planning Administration31Compensation Planning Execution33Competency Management System35Content Management37Contract Conditions39Contracts41Data Visibility43Dun & Bradstreet Integration46Employee KPI48Expense Reports50Field Service Inventory52Field Service Scheduler54Forecasts56High Tech Marketing Development Fund58Invoiceable Charges60Invoices62Marketing Budget Request64Marketing Campaign 66Marketing Collaboration68Siebel Data Model Reference Version 8.0Contents 4 Marketing Encyclopedia70Marketing Events72Marketing Plans75Marketing Program77Marketing Resource Management: Document80Opportunity Management82Order Life Cycle84Orders86Partner Collaboration88Partner Program Registration90Party Model92Payments94Performance Review96Personal Account99Personal Financial Review101Pricing Comparison103Pricing105Product Promotion107Product Quality Tracking109Product Recommendation111Products or Services113Professional Services115Revenue117Sales Hierarchy and Credit Assignment119Sales Portfolio Management121Service Agreement123Service Calendars and Work Shifts125Service Request127Shipment129Siebel Assistant131Territory Management133Territory Quota Rollup135Textile, Apparel, and Footwear137Time Sheet139Trade Promotions141Training Curriculum Course143Training Test Engine145Versioned Object Definition147Warranty149Chapter 4: Understanding the Physical ModelData Model Naming Conventions151Contents Siebel Data Model Reference Version 8.0 5Table Naming Conventions151Index Naming Conventions153Column Naming Conventions153Abbreviations Used in the Physical Model Listings154Data Model Type Definitions154Table Type Definitions155Table Status Definitions156Column Type Definitions157Domain Type Definitions157Columns of Numeric Physical Type158Siebel System Fields158INTEGRATION_ID Columns159Include Only Field159Siebel Repository159Database Schema Version160Limit Checking for Data Types160Validating the Siebel Schema160Party Model Unifies Access to Data161Chapter 5: Schema ChangesTable Changes in This Version163Tables That Are New in this Version163Tables That Changed in this Version169Table Column Changes in This Version169Table Columns That Are New in This Version169System Columns That Are New in This Version182Table Columns That Changed in This Version182Table Index Changes in This Version183Table Indexes That Are New in This Version183Table Indexes That Changed in This Version185Table Indexes That Are Deprecated in This Version188IndexSiebel Data Model Reference Version 8.0Contents 6 Siebel Data Model Reference Version 8.0 71 Whats New in This ReleaseWhats New in Siebel Data Model Reference, Version 8.0Table 1 lists changes described in this version of the documentation to support release 8.0 of the software.Table 1. Whats New in Siebel Data Model Reference, Version 8.0Topic DescriptionColumn changesSee Table Column Changes in This Version on page 169.A listing of column changes in this schema including new columns, deprecated columns, and changes to existing column definitions.Marketing Budget Request ERDSee Marketing Budget Request on page 64.A new entity-relationship diagram.This ERD illustrates the Marketing Resource Management budget request process. Marketing Program ERDSee Marketing Program on page 77.This entity-relationship diagram has been modified.A new entity Offer has been added and campaign targeting is now performed at the offer level.Marketing Resource Management: Document ERDSee Marketing Resource Management: Document on page 80.A new entity-relationship diagram.This ERD illustrates the Marketing Resource Management marketing content process. Sales Portfolio Management ERDSee Sales Portfolio Management on page 121.A new entity-relationship diagram.The Portfolio Management Process allows portfolio managers to manage a group of strategic accounts by: Assessing the potential of their assigned accounts Engaging the high-potential accounts within their portfolio Directing and managing the resources at their disposal Managing ongoing relationships with customers and partnersTable changesSee Table Changes in This Version on page 163.A listing of table changes in this schema including new tables, deprecated tables, and changes to existing table definitions.Siebel Data Model Reference Version 8.0Whats New in This Release 8 Table index changesSee Table Index Changes in This Version on page 183.A listing of index changes in this schema including new indexes, deprecated indexes, and changes to existing index definitions.Territory Management ERDSee Territory Management on page 133.The relationship from Territory to Territory Hierarchy has been changed from mandatory to optional and moved out of the Territory user key. Territory is now multi-org enabled.Territory Quota RollupSee Territory Quota Rollup on page 135.A new entity-relationship diagram.This data model supports quota assignment and quota rollup to a territory. Users can define quotas, spread them over several periods, and assign them to contacts, accounts, regions, and ZIP codes.Table 1. Whats New in Siebel Data Model Reference, Version 8.0Topic DescriptionSiebel Data Model Reference Version 8.0 92 Data Model OverviewOracles Siebel Data Model defines how the data used by Siebel Business Applications is stored in a standard third-party relational DBMS such as DB2, Microsoft SQL Server, or Oracle. The Siebel Data Model also defines some of the data integrity constraints validated by Siebel Business Applications.NOTE: The terms and conditions of your license agreement with Oracle permits use only of those portions of the Siebel Data Model that correspond to the Siebel products you have purchased. You are not entitled to use any portion of the Siebel Data Model to support Siebel products for which you have not purchased the required licenses.The Siebel Data Model is designed for speed and performance in data entry, running limited scope queries, and managing processes like call scripting. These tasks are considered transactions, and the database used is called an online transaction processing (OLTP) database.Optimizing a database used for these purposes requires a design, or schema, that puts each unit of information in a single location in the database. This allows you to update the data efficiently, since you do not have to update the same unit of data in several different locations. Most tables in an OLTP database have links, or join paths, to other tables, sometimes to many other tables. The database design used in an OLTP database is usually normalized. There are several levels of database normalization, ranging from first to fifth normal form. The Siebel database is in third normal form.The information in this reference is intended as an aid in configuring and using Siebel Business Applications.CAUTION: Do not attempt to insert or update data in the Siebel Business Applications tables through non-Siebel application products. Doing so can render your Siebel database unusable; additionally, you limit the ability of Oracle to provide you with quality support.To learn how to configure an application to insert, update, and delete data interactively, read the Siebel Developers Reference. To learn how to insert, update, and delete data in large quantities, read the Siebel Enterprise Integration Manager Administration Guide.Siebel Data Model Reference Version 8.0Data Model Overview 10 Siebel Data Model Reference Version 8.0 113 Understanding the Logical ModelThe Siebel logical model represents the following in Siebel Business Applications: Entities Relationships between entitiesThis information is represented in entity relationship diagrams (ERDs).Oracle has made and continues to make a significant investment in modeling the business functions of sales, marketing, and service organizations. The entity relationship diagrams included in this chapter represent the logical model for the current release of Siebel Business Applications. In some areas, the model extends beyond the current implementation. Published entities, therefore, might appear in the logical model that may not be implemented in the physical model at the present time.The ERDs included in this publication are those that are the most useful to individuals involved in implementing or integrating Siebel Business Applications. These diagrams cover the application areas that are most relevant to a functional understanding of the application.The information on ERDs is organized as follows: Entity Relationship Diagram Conventions Entity Relationship Diagrams and Descriptions on page 14Entity Relationship Diagram ConventionsThis topic describes entity relationship diagram conventions, as follows: General Entities on page 12 Exclusive Arc Relationship on page 12 Recursive Relationship on page 13Siebel Data Model Reference Version 8.0Understanding the Logical Model Entity Relationship Diagram Conventions12 General EntitiesFigure 1 shows the diagram conventions for general entities used in this publication.Exclusive Arc RelationshipFigure 2 illustrates an example of the exclusive arc relationship. An exclusive arc is an arc across two or more relationship ends; you can read each exclusive arc relationship as follows:Figure 1. General Entity Relationship Diagram ConventionsUnderstanding the Logical Model Entity Relationship Diagram ConventionsSiebel Data Model Reference Version 8.0 13Each [entity] must be [relationship name] either to one and only one [entity] or [relationship name] to one and only one [entity]. For example, each Product Comparison must be to either one and only one Product Internal or to one and only one Product External as shown in Figure 2.Recursive RelationshipFigure 3 illustrates an example of the recursive relationship. A recursive relationship is one in which an entity has a relationship to itself. For example, each activity might be part of one and only one activity, or each activity might be made up of one or more activities, as shown in Figure 3.Recursive relationships are almost always optional, and either one-to-many or many-to-many.Figure 2. Exclusive Arc Relationship Diagram Convention ExampleFigure 3. Recursive Relationship Diagram Convention ExampleActivityEntity 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 ofMade up ofSiebel Data Model Reference Version 8.0Understanding the Logical Model Entity Relationship Diagrams and Descriptions14 Entity Relationship Diagrams and DescriptionsERDs represent the significant entities and relevant relationships in a functional area. To enhance their readability, the diagrams do not include every relationship and subtype. Some many-to-many relationships have also been preserved instead of showing them as one-to-many relationships around intersection tables in the logical model.Table 2 provides a list of ERDs in alphabetic order.Table 2. Entity Relationship DiagramsERD NameFigure Num. and Page Functional AreaRevised in 8.0Newin 8.0Account Figure 4 on page 19GeneralAdjustment Group Figure 5 on page 21GeneralAsset Management Figure 6 on page 23GeneralAuction Figure 7 on page 25GeneralAuto Email Response Generator Figure 8 on page 27GeneralCG Promotion Planning Figure 9 on page 30MarketingCompensation Planning Administration Figure 10 on page 32ERMCompensation Planning Execution Figure 11 on page 34ERMCompetency Management System Figure 12 on page 36ERMContent Management Figure 13 on page 38GeneralContract Conditions Figure 14 on page 40GeneralContracts Figure 15 on page 42GeneralData Visibility Figure 16 on page 45GeneralDun & Bradstreet Integration Figure 17 on page 47Sales/MarketingUnderstanding the Logical Model Entity Relationship Diagrams and DescriptionsSiebel Data Model Reference Version 8.0 15Employee KPI Figure 18 on page 49ERMExpense Reports Figure 19 on page 51GeneralField Service Inventory Figure 20 on page 53ServiceField Service Scheduler Figure 21 on page 55ServiceForecasts Figure 22 on page 57Sales/MarketingHigh Tech Marketing Development Fund Figure 23 on page 59MarketingInvoiceable Charges Figure 24 on page 61ServiceInvoices Figure 25 on page 63ServiceMarketing Budget Request Figure 26 on page 65Marketing YesMarketing Campaign Figure 27 on page 67MarketingMarketing Collaboration Figure 28 on page 69MarketingMarketing Encyclopedia Figure 29 on page 71Sales/MarketingMarketing Events Figure 30 on page 74GeneralMarketing Plans Figure 31 on page 76MarketingMarketing Program Figure 32 on page 79Marketing YesMarketing Resource Management: DocumentFigure 33 on page 81Marketing YesOpportunity Management Figure 34 on page 83SalesOrder Life Cycle Figure 35 on page 85GeneralTable 2. Entity Relationship DiagramsERD NameFigure Num. and Page Functional AreaRevised in 8.0Newin 8.0Siebel Data Model Reference Version 8.0Understanding the Logical Model Entity Relationship Diagrams and Descriptions16 Orders Figure 36 on page 87GeneralPartner Collaboration Figure 37 on page 89GeneralPartner Program Registration Figure 38 on page 91GeneralParty Model Figure 39 on page 93GeneralPayments Figure 40 on page 95GeneralPerformance Review Figure 41 on page 98ERMPersonal Account Figure 42 on page 100Industry-SpecificPersonal Financial Review Figure 43 on page 102Industry-SpecificPricing Comparison Figure 44 on page 104EnergyPricing Figure 45 on page 106GeneralProduct Promotion Figure 46 on page 108GeneralProduct Quality Tracking Figure 47 on page 110GeneralProduct Recommendation Figure 48 on page 112GeneralProducts or Services Figure 49 on page 114ServiceProfessional Services Figure 50 on page 116GeneralRevenue Figure 51 on page 118GeneralSales Hierarchy and Credit Assignment Figure 52 on page 120SalesSales Portfolio Management Figure 53 on page 122Sales YesTable 2. Entity Relationship DiagramsERD NameFigure Num. and Page Functional AreaRevised in 8.0Newin 8.0Understanding the Logical Model Entity Relationship Diagrams and DescriptionsSiebel Data Model Reference Version 8.0 17AccountFigure 4 shows the Account ERD. The account entity is a key entity in the Siebel Data Model. The account entity appears in many diagrams in this publication, and is often referred to as an organization unit.Service Agreement Figure 54 on page 124ServiceService Calendars and Work Shifts Figure 55 on page 126ServiceService Request Figure 56 on page 128ServiceShipment Figure 57 on page 130GeneralSiebel Assistant Figure 58 on page 132GeneralTerritory Management Figure 59 on page 134Sales YesTerritory Quota Rollup Figure 60 on page 136Sales YesTextile, Apparel, and Footwear Figure 61 on page 138Industry-SpecificTime Sheet Figure 62 on page 140GeneralTrade Promotions Figure 63 on page 142GeneralTraining Curriculum Course Figure 64 on page 144GeneralTraining Test Engine Figure 65 on page 146GeneralVersioned Object Definition Figure 66 on page 148GeneralWarranty Figure 67 on page 150ServiceTable 2. Entity Relationship DiagramsERD NameFigure Num. and Page Functional AreaRevised in 8.0Newin 8.0Siebel Data Model Reference Version 8.0Understanding the Logical Model Entity Relationship Diagrams and Descriptions18 The account entity is a subtype of party composed of one or more people or contacts. An account is any organization or subset of an organization that can be sold to or serviced. An account might represent a company, a site, a subsidiary, a division, or any other subset of an organization. An account might also represent a governmental agency, club, or other formal or informal group of individuals. Each account might be accessible at one or more addresses.The account entity supports Global Account Views and Dynamic Hierarchy. This allows a universal view of all customer interactions. The Global Account Views present accounts in the context of a customizable hierarchy, allowing navigation to parent and child accounts. Roll-up and roll-down functionality gives users access to account-specific information, and aggregate information including child accounts, activities, contacts, opportunities, and the account team.Dynamic Hierarchy allows the Global Account Views to display a different hierarchy depending on the business unit of the user. Each custom account hierarchy is represented completely in a relationship table. The relationships are then denormalized into a separate table to be used for roll-up support.Table 3 lists the entities in this ERD and their corresponding tables.Table 3. Account ERD Entities and TablesEntity TablesAccount S_ORG_EXT, S_PARTYAccount Synonym S_ORG_SYNActivity S_EVT_ACTAddress S_ADDR_ORGAssignment Group (Territory) S_ASGN_GRPBusiness Unit S_BU, S_ORG_EXT, S_PARTYCharacteristics S_CHRCTRDynamic Account Hierarchy S_DYN_HRCHYDynamic Account Hierarchy Node S_DYN_HRCHY_RELEmployee/Agent S_EMP_PER, S_CONTACT, S_PARTYIndustry S_INDUSTMarket Segment S_MKT_SEGParty S_PARTYPayment Term S_PAYMENT_TERMPerson S_CONTACT, S_PARTYPosition S_POSTN, S_PARTYPrice List S_PRI_LSTSales or Service Team Member S_ACCNT_POSTNUnderstanding the Logical Model Entity Relationship Diagrams and DescriptionsSiebel Data Model Reference Version 8.0 19Figure 4. AccountNAMED HIERARCHYNAMED HIERARCHY ACCOUNTPAYMENT TERMACCOUNT SYNONYMINDUSTRYCORRESPONDENCEPRICE LISTSALES OR SERVICE TEAM MEMBERMARKET SEGMENTDECISION ISSUESPARTYPOSITIONACCOUNTOTHER PARTYBUSINESS UNITPERSONOTHER PERSONEMPLOYEE / AGENTACTIVITYASSIGNMENT GROUP (TERRITORY)ADDRESSCHARACTERISTICconstrained to useacessible toofmade visible throughformade up ofa report toa parent ofaction fortarget ofclassification fortype offorpart ofparticipant intarget ofresponsible forresponsibility ofuser characteristics fordescribed ina report toa parent ofanother name forknown asuser ofcurrent price list forapplicable toaccess toforbelong toaddressed toparticipate inforlocated atholders ofheld bypay or payed bydefault payment term forcomposed ofcontact ofresponsibility ofresponsible forSiebel Data Model Reference Version 8.0Understanding the Logical Model Entity Relationship Diagrams and Descriptions20 Adjustment GroupFigure 5 shows the Adjustment Group ERD. This ERD illustrates the system for managing the various matrices for pricing, compatibility, eligibility, product promotions, and so on. It allows the user to define a matrix, its dimensions, and all of its rules. This new infrastructure allows the adjustment to be any value, not just a price amount.Table 4 lists the entities in this ERD and their corresponding tables.Table 4. Adjustment Group ERD Entities and TablesEntity TablesAdjustment Group S_ADJ_GROUPAdjustment Group Dimension S_ADJ_GROUP_DIMProduct Compatibility Matrix Rule S_PRODCOMP_MTRXProduct Eligibility Matrix Rule S_PRODELIG_MTRXProduct Promotion Pricing Matrix Rule S_PROM_PMTRXStandard Entitlement Pricing Matrix Rule S_STDENTL_PMTRXStandard Product Pricing Matrix Rule S_STDPROD_PMTRXStandard Training Pricing Matrix Rule S_STDTRNG_PMTRXUnderstanding the Logical Model Entity Relationship Diagrams and DescriptionsSiebel Data Model Reference Version 8.0 21Figure 5. Adjustment GroupSTANDARD TRAINING PRICING MATRIX RULE# MTRX_RULE_NUMSTANDARD PRODUCT PRICING MATRIX RULE# MTRX_RULE_NUMSTANDARD ENTITLEMENT PRICING MATRIX RULE# MTRX_RULE_NUMPRODUCT PROMOTION PRICING MATRIX RULE# MTRX_RULE_NUMPRODUCT ELIGIBILITY MATRIX RULE# MTRX_RULE_NUMPRODUCT COMPATABILITY MATRIX RULE# MTRX_RULE_NUMADJUSTMENT GROUP DIMENSION# FIELD_NAMEADJUSTMENT GROUP# ADJ_GROUP_NAMEforcontainforcontainforcontainforcontainforcontainforcontainforcontainSiebel Data Model Reference Version 8.0Understanding the Logical Model Entity Relationship Diagrams and Descriptions22 Asset ManagementFigure 6 shows the Asset Management ERD. This ERD illustrates how Siebel Business Applications track instances of assets. Moving counter-clockwise from the lower-right corner, the diagram shows how internal products can be made into assets and associated with an account or a contact to register ownership. Additional relationships between assets and accounts, contacts, and employees are illustrated in the upper-right corner. Additional information such as the related opportunities, the current business or personal address location of the asset, notes, and related assets are shown across the top of the diagram. The left side of the diagram shows the relationships with service requests, activities, and related part movements.Table 5 lists the entities in this ERD and their corresponding tables.Table 5. Asset Management ERD Entities and TablesEntity TablesActivity S_EVT_ACTActivity Part Movement S_ACTPART_MVMTAsset Contact Relationship S_ASSET_CONAsset Employee Relationship S_ASSET_EMPAsset External Organization S_ASSET_ACCNTAsset Feature S_ASSET_FEAAsset Modification S_ASSET_TXNAsset Relationship S_ASSET_RELBusiness Address S_ADDR_ORGCompetitive Metric S_CMPT_MTRCCompetitive Product Feature S_CMPT_PROD_FEAContact S_CONTACT, S_PARTYEmployee S_EMP_PER, S_CONTACT, S_PARTYExternal Product S_PROD_EXTInternal Product S_PROD_INTOpportunity S_OPTYOpportunity Asset S_OPTY_ASSETPerson S_CONTACT, S_PARTYPersonal Address S_ADDR_PERProduct Instance (Asset) S_ASSETService Request S_SRV_REQUnderstanding the Logical Model Entity Relationship Diagrams and DescriptionsSiebel Data Model Reference Version 8.0 23Figure 6. Asset ManagementACTIVITY PARTMOVEMENTACTIVITYSERVICE REQUESTADDRESSPERSONAL ADDRESSBUSINESS ADDRESSNOTECOMPETITIVE PRODUCT FEATURECOMPETITIVE METRICOPPORTUNITYPRODUCTINTERNAL PRODUCTNON-SERIALIZABLE PRODUCTSERIALIZABLE PRODUCTEXTERNAL PRODUCTPRODUCT INSTANCE (ASSET)PERSONCONTACTEMPLOYEEOPPORTUNITY ASSETASSET MODIFICATIONASSET RELATIONSHIPASSET FEATUREASSET EMPLOYEE RELATIONSHIPASSET CONTACT RELATIONSHIPASSET EXTERNAL ORGANIZATIONEXTERNAL ORGANIZATIONVENDORACCOUNTOTHER EXTERNAL ORGANIZATIONforsubject ofdefined forsubject ofperformed onsubject offor problems withsubject offor problems withsubject ofpart ofmade up ofofmoved byofmoved byinitiated byinitiator ofpart ofmade up ofdefined forsubject oflocated atforforsubject ofofclassification forforsubject ofofclassification forforinitiated byuse ofinvolved inforassociated withcurrently owned byowner ofcurrently owned byowner ofcurrently possessed bypossessor ofa component ofan assembly ofinstance ofmade intochild ofparent ofproduced byvendor oftoassociated withofsubject oftoassociated withofsubject ofofsubject oftoassociated withofassociated withuse ofinvolved informodified byofinitiator ofSiebel Data Model Reference Version 8.0Understanding the Logical Model Entity Relationship Diagrams and Descriptions24 AuctionFigure 7 shows the Auction ERD. This ERD illustrates how the Siebel Data Model represents the auctioning of goods or services to bidders. An auction item may be a stand-alone offering, or may be a specific instance of an offering of a quantity of product or of a particular asset for sale. An auction item must be listed by a corporate or individual user, but that user may be either internal to or external to the Siebel-owning company. Auction items are displayed to bidders through one or more categories in a catalog. Fulfillment of an auction item to the winning bidders may be tracked through one or more order items. Finally, users may set up watched items, may define alerts, and may rate fellow listers or bidders.Table 6 lists the entities in this ERD and their corresponding tables.Table 6. Auction ERD Entities and TablesEntity TablesAsset S_ASSETAuction Alert Definition S_AUC_ALRT_DEFAuction Item S_AUC_ITEMAuction Item Bid S_AUC_BIDAuction Item Promotion S_AUC_ITM_PROMOAuction Item Watch S_AUC_WATCHAuction Lister/Bidder Rating S_AUC_RATINGCatalog S_CTLGCatalog Category S_CTLG_CATCatalog Category Item S_CTLG_CAT_PROD, S_CTLGCAT_ASSET, S_CTLG_CAT_AUCOrder S_ORDEROrder Item S_ORDER_ITEMParty S_PARTYPerson S_CONTACTProduct S_PROD_INTTriggered Auction Alert Item S_AUC_ALRTUser S_USER, S_CONTACT, S_PARTYUnderstanding the Logical Model Entity Relationship Diagrams and DescriptionsSiebel Data Model Reference Version 8.0 25Figure 7. AuctionORDERAUCTION LISTER/BIDDER RATINGTRIGGERED AUCTION ITEM ALERTORDER ITEMPARTYOTHER PARTYPERSONOTHER PERSONUSERCATALOGPRODUCTASSETCATALOG CATEGORY ITEMCATALOG CATEGORYAUCTION ITEM WATCHAUCTION ITEM PROMOTIONAUCTION ALERT DEFINITIONAUCTION ITEM BIDAUCTION ITEMcreated bycreator ofpart ofcomposed ofapplicable tosubject ofpart ofmade up ofrating ofsubject ofmade bycreator ofplaced byplacer oflisted bylister offorsubject offorsubject offorcreator offoralerted bycreated fromgenesis offorfeatured inrepresented bydisplayed asrepresented bydisplayed ascreated fromrepresented asaccessed viaowner offorowner ofpricing mechanism forpriced bypricing mechanismforpriced byfulfillment offulfilled asforsubject ofSiebel Data Model Reference Version 8.0Understanding the Logical Model Entity Relationship Diagrams and Descriptions26 Auto Email Response GeneratorFigure 8 shows the Auto Email Response Generator ERD. This ERD illustrates the data model for the automatic generation of a response to an inbound communication. Incoming messages (inbound communications) are compared against a database of previously categorized messages to categorize them in one or more categories. The categories are associated with predefined template communication responses, used to generate a default response to each category of message. A notification mechanism can be defined to alert a person whenever the usage of a category or template exceeds a predefined limit.Table 7 lists the entities in this ERD and their corresponding tables.Table 7. Auto Email Response Generator ERD Entities and TablesEntity TablesActivity S_EVT_ACTCatalog S_CTLGCatalog Category S_CTLG_CATCategory Usage Notification S_COMM_CTG_NTFYCommunication Template Usage Notification S_COMMTMPL_NTFYPerson S_CONTACT, S_PARTYProblem Resolution Document S_RESITEMTemplate Communication Response S_DMND_CRTN_PRGUnderstanding the Logical Model Entity Relationship Diagrams and DescriptionsSiebel Data Model Reference Version 8.0 27Figure 8. Auto Email Response GeneratorTEMPLATE COMMUNICATION RESPONSEPROBLEM RESOLUTION DOCUMENTACTIVITYOUTBOUND RESPONSEINBOUND COMMUNICATIONCATALOG CATEGORYCATALOGPERSONCOMMUNICATION TMPL USAGE NOTIFICATIONCATEGORY USAGE NOTIFICATIONfor usage ofsubject ofcategorized withinclassification forclassification ofdefault response forcategorized underclassification forpart ofmade up ofpart ofmade up to notifytarget ofto notify target offor usage of subject ofSiebel Data Model Reference Version 8.0Understanding the Logical Model Entity Relationship Diagrams and Descriptions28 CG Promotion Planning Figure 9 shows the CG Promotion Planning ERD. This ERD illustrates how Siebel Business Applications support the funding of trade promotions in channel management and the Consumer Goods (CG) industry. Marketing development funds (MDFs) are defined for an account, for a product line or product category, and for an accounting period. An MDF can be a fixed sum of money, an accrual fund, or a mixture of the two. The value of the accrual fund is typically determined based on an accrual rate multiplied by either the number of units sold, or the revenue in a given period from one or more specific products that are representative of the product line or category of the fund. Planned expenses for the various tactics involved in the planning and execution of product promotions can be allocated to one or more MDFs. Allocations that have not yet been approved are considered fund requests. One or more such MDF allocations may be covered by a single payment to the partner account.Advanced Planning is a feature designed to address the process used by CG organizations to plan sales volume and sales revenue at key accounts. Advanced Planning is part of a broader process called Trade Marketing. Trade Marketing includes planning, executing, and analyzing sales.Table 8 lists the entities in this ERD and their corresponding tables.Table 8. CG Promotion Planning ERD Entities and TablesEntity TablesAccount S_ORG_EXT, S_PARTYAuthorized Product S_ORG_PRODFund Allocation S_MDF_ALLOCMarketing Development Fund S_MDFMarketing Event or Activity S_SRCMDF Accrual S_MDF_ACCRUALPayment S_SRC_PAYMENTPeriod S_PERIODPerson S_CONTACT, S_PARTYPosition S_POSTN, S_PARTYPrice List S_PRI_LSTPrice List Item S_PRI_LST_ITEMProduct Internal S_PROD_INTProduct Line S_PROD_LNProduct Structure S_PROD_REL or S_PROD_ITEMPromotion Plan S_SRCPromotion S_SRCPromotion Account S_SRCUnderstanding the Logical Model Entity Relationship Diagrams and DescriptionsSiebel Data Model Reference Version 8.0 29Promotion Product S_SRCPromotion Category S_SRCPromotion Account Product S_SRCTable 8. CG Promotion Planning ERD Entities and TablesEntity TablesSiebel Data Model Reference Version 8.0Understanding the Logical Model Entity Relationship Diagrams and Descriptions30 Figure 9. CG Promotion PlanningMARKETING EVENT OR ACTIVITYPROMOTION PLANPROMOTION ACCOUNT PRODUCTPROMOTION ACCOUNTPROMOTIONOTHER MARKETING EVENT OR ACTIVITYPROMOTION PRODUCTPROMOTION CATEGORYPAYMENTOTHER PAYMENTPROMOTION PAYMENTPERSONEMPLOYEE / AGENTOTHER PERSONPOSITIONACCOUNTPRODUCT LINEAUTHORIZED PRODUCTMDF ACCRUALPRICE LIST ITEMFUND ALLOCATIONPRICE LISTPRODUCT STRUCTUREMARKETING DEVELOPMENT FUNDMIXED FUNDACCRUAL FUNDFIXED FUNDINTERNAL PRODUCT OR SERVICEPERIODsub allocated tosub allocation ofpart ofmade ofofpromoted viadefined forsubject ofuser ofused bytarget ofavailable todefined forsubject oftorecipient offorsubject ofcovered byforassigned toresponsible forrelated torelation ofapproved byapprover ofrequested byrequestor ofof subject ofearned insubject ofmade up ofpart ofatsubject ofdesignated totarget ofcomposed ofpart ofsubject toapplicable toassigned toresponsible forfor promotion ofsubject ofearned byearner ofearned byearner offorfunded throughhierarchy child ofhierarchy parent ofofsubject ofcomposed offorbased onbasis forofsubject ofdefined forsubject ofan assembly offora component ofoffor promotion ofsubject of7LWOH

&*3URPRWLRQ3ODQQLQJ$XWKRU

Oracle

&RQILGHQWLDOUnderstanding the Logical Model Entity Relationship Diagrams and DescriptionsSiebel Data Model Reference Version 8.0 31 Compensation Planning AdministrationFigure 10 shows the Compensation Planning Administration ERD. The administration activities of compensation planning involve setting up salary structures such as salary plan, salary grades, and job codes. In addition to salary structures, an organization sets up compensation budgets, compensation types such as merit increase, bonus, promotion, and stock options, planning periods, budget calculation and eligibility rules, guidelines and calculation of budget allocations for employees.Table 9 lists the entities in this ERD and their corresponding tables.Table 9. Compensation Planning Administration ERD Entities and TablesEntity TablesBusiness Unit S_BUCompensation Budget Definition S_CP_BDGTCompensation Budget Item S_CP_BDGT_ITEMCompensation Budget Item For Employee S_CP_BDGT_EMPCompensation Cycle Planning Period S_CP_PD_BDGTITMCompensation Guideline Definition S_CP_GDLNCompensation Guideline Factor LOVCompensation Guideline Set S_CP_GDLN_SETCompensation Guideline Table S_CP_GDLN_TBLCompensation Planning Period S_CP_PERIODCompensation Region S_CP_REGNCompensation Type LOVCompensation Valid Effectivity Date S_CP_EFF_DATEEmployee Eligibility S_APP_QUERY (PDQ)Employee/Agent S_EMP_PERJob Category LOVJob Code S_JOBJob Family S_JOB_FAMILYJob Profile S_JOB_PRFLPeriod S_PERIODSalary Grade S_SALARY_GRADE, S_SALPLAN_GRADESalary Plan S_SALARY_PLANSiebel Data Model Reference Version 8.0Understanding the Logical Model Entity Relationship Diagrams and Descriptions32 Figure 10. Compensation Planning AdministrationTitle : Compensation Planning AdministrationAuthor : Oracle, ConfidentialPOSITIONSALARY PLAN FOR SALARY GRADEJOB FAMILYJOB CATEGORYCOMPENSATION REGIONJOB CODECOMPENSATION GUIDELINE DEFINITIONCOMPENSATION TYPESALARY PLANBUSINESS UNITPERIODQUARTERLY PERIODANNUAL PERIODCOMPENSATION CHANGE EFFECTIVITY DATECOMPENSATION CYCLE PLANNING PERIODCOMPENSATION PLANNING PERIODEMPLOYEE / AGENTCOMPENSATION BUDGET ITEM FOR EMPLOYEEEMPLOYEE ELIGIBILITY (PDQ)COMPENSATION BUDGET ITEMCOMPENSATION BUDGET DEFINITIONCOMPENSATION GUIDELINE FACTORCOMPENSATION GUIDELINE TABLECOMPENSATION GUIDELINE SETSALARY GRADEsupportmanage bysalary plan grade defined inforsalary plan fordefined insalary grades forhavedefined forused byperiod forhavepart ofgrouping forcategorized incategory forhavedefined forhasjob code forlocated incompensation location forsalary grade defined inforsalary defined infordefined forcomponent oftype oftype forvalues forhave2 factor defined inused in1 factor defined inused intype oftype forconstrained bydefined forbudget forhaveemployed byemployer ofsub-org ofcomposed ofdefined forused indefined forused invalid date forhavedefined foruser ofdefined forused bysubject ofcontainer forallocated forhasbudget allocation forhasconstrained bydefined forsubject ofcontainer fordefined forcomponent ofsubject ofcontainer forUnderstanding the Logical Model Entity Relationship Diagrams and DescriptionsSiebel Data Model Reference Version 8.0 33Compensation Planning ExecutionFigure 11 shows the Compensation Planning Execution ERD. In the execution phase of compensation planning, a workbook is created for each of the authorized managers with the list of employees who report to them. The manager goes through the planning process and decides on the merit, bonus, promotion, and stock option changes that he may grant to his employees. Authorized persons such as managers, or HR personnel approve the plans. Totals are maintained for each manager and organization.Table 10 lists the entities in this ERD and their corresponding tables.Table 10. Compensation Planning Execution ERD Entities and TablesEntity TablesBusiness Unit S_BUCompensation Budget Definition S_CP_BDGTCompensation Budget Item S_CP_BDGT_ITEMCompensation Budget Item For Employee S_CP_BDGT_EMPCompensation Cycle Planning Period S_CP_PD_BDGTITMCompensation Guideline Definition S_CP_GDLNCompensation Guideline Set S_CP_GDLN_SETCompensation Guideline Table S_CP_GDLN_TBLCompensation Plan S_CP_PLANCompensation Plan Comments S_NOTE_CP_PLANCompensation Plan For Employee S_CP_PLAN_EMPCompensation Plan Item Detail S_CP_PLNITM_DTLCompensation Plan Item For Employee S_CP_PLAN_ITEMCompensation Plan Total S_CP_PLNITM_TOTCompensation Planning Period S_CP_PERIODCompensation Type LOVCompensation Valid Effectivity Date S_CP_EFF_DATEPlan Approval S_CP_APPROVALProxy Access To Plan S_USER_PROXYSiebel Data Model Reference Version 8.0Understanding the Logical Model Entity Relationship Diagrams and Descriptions34 Figure 11. Compensation Planning Execution7LWOH

&RPSHQVDWLRQ3ODQQLQJ([HFXWLRQ$XWKRU

Oracle

&RQILGHQWLDO3(5,2'&203(16$7,21*8,'(/,1('(),1,7,21&203(16$7,213/$1727$/&203(16$7,217