Posts Tagged ‘Party Model’

Siebel Party Model – What is a User?

User is a person/contact with User ID. For example – A registered customer on your Web site browsing/ordering products online.

Parties Person - Venn Diagram

Parties Person – Venn Diagram

User records can be seen in following application view:

  • Administration – User > Users
  • Contacts > All Contacts

Characteristics of a User

  • May have associated responsibility leading to application access.
  • May have any associated positions.
  • Must have a User ID leading to database login.
  • It is possible to promote a contact/person to a user.
    • Adding a User ID value for a person record in Persons view causes it to appear as a user in the Users view.
What is User - Application View

What is User – Application View

Database Tables

Tables representing a User record are highlighted below:

  • Base Table – S_PARTY
  • Extension Tables
    • S_CONTACT – Stores First and Last Name of user.
    • S_USER – Stores User ID.
  • Intersection table – S_PER_RESP (not shown) stores responsibilities for users.
Table Architecture - User

Table Architecture – User

Complete Overview of Party Data Model

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

Siebel Party Model – What is a Contact or Person?

Contact (or Person) represents an individual in the Siebel system. For example, an employee of your client company speaking to your Sales Representatives to purchase a product.

Parties Person - Venn Diagram
Contact/Person records can be seen under following two application views:

  • Administration – User > Persons
  • Contacts > All Contacts

Characteristics of a Contact/Person

  • May have associated responsibilities.
  • May have associated positions.
  • May have a User Id.
  • Contact/Person record is the parent/ancestor of other person parties – User, Employee and Partner User.
What is Person or Contact - Application View

What is Person or Contact – Application View

Please note that when a Contact/Person is promoted as a User, additional attributes such as User ID & Responsibilities are defined. For e.g. – last two records highlighted in RED above.

Database Tables

Tables representing a Person/Contact record are highlighted below:

Table Architecture - Contact/Person

Table Architecture – Contact/Person

Complete Overview of Party Data Model

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

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: