Bookshelf Home | Contents | Index | PDF |
Upgrade Guide > Siebel Database and UI Upgrade Planning > About the Siebel Party ModelUpgrades: Applies to Siebel Financial Services upgrades from Siebel 7.x that have retained the Siebel 6.x form of household associations. Environments: Development, production test, production. Siebel 7.x introduced a party table (S_PARTY) in which all persons and organizational units are held. Accounts, Organizations, Internal Divisions, Contacts, Employees, Positions, and Households are all considered parties and can be referenced from this table. Most of the tables that formerly contained this data still exist and are still used, but they are now extension tables to the S_PARTY base table. Data is loaded into the business components through an implicit join. Additionally, Siebel 7.x uses a single-person table and a single-organization unit table. For example, Employees and Contacts are now combined in the same table (S_CONTACT). Similarly, internal and external Organization Units are now combined in the same table (S_ORG_EXT). The S_PARTY table is the primary table in the Party or Single-Person model and is the base table for all Party business components. Several extension tables support the Party Model:
Each non-person party directly or indirectly has person members, such as employees or contacts. The Party model makes several tables obsolete:
Figure 3 depicts the Party changes to the data model that occur during upgrades from Siebel 6.x to Siebel 7.x. How the Party Model Is Implemented During UpgradeWhen you upgrade to Siebel 7.x, the upgrade process implements the Party model as follows: Data Migration
Business Component Definitions
How the Party Model Affects Siebel Financial Services Household DataAt Siebel 7.0.x, the Party model changed the relationship between a household and the following entities for Siebel Financial Services: The relationship changed as follows:
To implement direct relationships between the entity tables and household table in Siebel Financial Services 6.x, intersection tables were used for many-to-many relationships. A foreign key was used for one-to-many relationships. This design allowed a contact to be assigned to an entity but not be part of the household assigned to that entity. This caused possible data integrity problems, which the Party model resolves. The tables required for maintaining the 6.x direct-relationship design are retained in Siebel 7.x. You can choose to maintain direct relationships between households and entities. However, this is not recommended. To maintain the 6.x direct-relationship design, contact Oracle's Siebel Technical Support or Oracle's Siebel Expert Services for assistance in revising business components in the current release to support this model. How Siebel Financial Services 6.x Household Data Is MigratedDuring the upgrade to Siebel 7.x, relationships in S_CONTACT_REL are migrated to S_PARTY_REL. Relationships in S_PER_ORG_UNIT are migrated to S_PARTY_PER. When defining relationships between entities, no records are written to S_PARTY. Instead, the "PARTY (FIN)" and "Party Relationship To" business components drive the relationships displayed in the Relationship Hierarchy applet and adjacent Party Relationship list applet. S_PARTY_REL can be used to define custom relationships such as lawyer, accountant, board member, and influencer. Valid relationships can be created between the following entities: |
Upgrade Guide | Copyright © 2006, Oracle. All rights reserved. | |