Posts Tagged ‘S_PARTY’

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: