Bookshelf Home | Contents | Index | Search | PDF

Siebel Tools Reference > Data Objects Layer > Access Control >

S_PARTY Table

---

The S_PARTY table serves as the base table for all party business components and stores the party name and party type. It has multiple extension tables that store the business data for the party business components. The S_PARTY table allows you to model the complicated business relationships from the real world into Siebel applications (Figure 71).

Figure 71. S_Party Table

Party

Party includes business components that represent groupings of party instances (Figure 72).

User List: Group of Users
Access Group: Grouping of Access Group Members (for example, household, account, organization, division, position, user list).

Figure 72. Party

S_PARTY_PER

S_PARTY_PER is an intersection table that relates two instances of parties and is used to implement group-member relationships between the following, respectively (Figure 73):

User Lists and Users
Accounts and Contacts
Employees and Positions
Access Groups and Members

Figure 73. S_PARTY_PER

In the implied join between S_PARTY_PER and S_PARTY:

S_PARTY_PER.PARTY_ID maps to the group's row ID (S_ORG_EXT.ROW_ID)
S_PARTY_PER.PERSON_ID maps to the member's row ID (S_CONTACT.ROW_ID)

Summary

In summary, S_PARTY and its extension tables are used to store data for many business components (Figure 74).

Figure 74. Overview of S_PARTY and Its Extension Tables

Use the following guidelines when working with S_PARTY-related tables:

Configuring business components:
All person-related business components use S_CONTACT.
All organization-related business components use S_ORG_EXT.
Over 100 party-related business components reference S_PARTY but store their data in one of the many S_PARTY extension tables.
Importing data for party-related business components:
You must populate columns in S_PARTY table in addition to tables that store the data of interest to users.
Importing data for organization-related business components:
For single-organization data, you must populate BU_ID.
For multi-organization data, you must populate the corresponding intersection table.

Bookshelf Home | Contents | Index | Search | PDF