Siebel Party Model – History

Siebel 7.x introduced a party table – S_PARTY as the primary table in Party model and the base table for all Party business components. Accounts, Organizations, Internal Divisions, Contacts, Employees, Positions, and Households are all considered parties and can be referenced from this table.

Impact on Database Architecture

Some tables previously used to store above data were retained as Extension Tables of S_PARTY:

  • S_USER stores Siebel User information.
  • S_EMP_PER stores attributes for Brand-Owner Employees and Partner Users who are considered agents of the Brand-Owner.
  • S_BU stores Organization information.
  • S_CONTACT
  • S_ORG_EXT
  • S_POSTN

And some of the tables become obsolete:

  • S_EMPLOYEE – Its functionality is merged into S_CONTACT leading to use of single-person table.
  • S_ORG_INT – Its functionality is merged into S_ORG_EXT. leading to use of single-organization unit table.
  • S_EMP_POSTN – It is replaced by S_PARTY_PER.
  • S_EMPLOYEE_ATT
  • S_ORG_INT_ATT
  • S_POSTN_RPT_REL

Complete Overview of Party Data Model

To study Siebel’s Party Data Model in detail, please purchase our ebook on this topic:

Appreciate your feedback

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: