Configuring Siebel eBusiness Applications > Configuring Tables and Columns >

About the S_Party Table


The party model organizes entities such as Person, Organization, Position, and Household. A party always represents a single person or a group that can be translated into a set of people such as a company or a household. Siebel data access technology makes use of the Party model. Certain parts of the data model use the Party model to abstract the difference between people, companies, households and other legal entities. 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 15 lists the extension tables and their corresponding EIM interface tables.

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

Households

S_ORG_GROUP

EIM_GROUP

Positions

S_POSTN

EIM_POSITION

Users

S_USER

EIM_USER

Because these extension tables are implicitly joined to S_PARTY, they are available through S_PARTY. Two preconfigured intersection tables (S_PARTY_PER and S_PARTY_REL) implement M:M relationships between party business components, such as Account and Contact. Which one you use depends on whether or not you need to enforce access control.

Use S_PARTY_PER when implementing M:M relationships between two party business components where you need to define access control. Records in S_PARTY_PER propagate data access rights from the parent to the child parties. However, it is important to minimize the number of rows in S_PARTY_PER to maintain good response times in visibility-constrained queries. Therefore, when implementing M:M relationships where you do not need to enforce access control, such as when implementing a recursive M:M relationship between a party business component and itself, use S_PARTY_REL.

For example, use S_PARTY_PER to implement relationships between members:

  • Access groups and members
  • Accounts and contacts
  • Employees and positions
  • User lists and users

If you need to extend tables in the party model, you need to create an extension table from S_PARTY. For example, S_CONTACT is an extension table of S_PARTY. Because S_CONTACT is of type Extension (Siebel), you cannot use it as a base table for an extension table. You must create an extension table and use S_PARTY as the base table. To display data from the new extension table, create a Join object (explicit join) to bring in data from the new extension table to the business component you are using.

Configuring Siebel eBusiness Applications