S_PARTY model is the major change seen in Siebel 7.X and later version. The S_PARTY table is the base table for all the party related entities:  Person (Contact), User, Employee, Partner User, Account, Division, Organization, Partner Organization, Household, Access Group and User list.

Party components have M: M relationships among them. For each party record stored in the S_PARTY table, the value of the PARTY_TYPE_CD column denotes the party type. Along with the party type, extension tables provide the primary differentiation between the different parties.






  • An employee at the customer company.
  • An employee at the competitor’s company


  • A Person is an individual who is represented by a Person record in the database
  • Without additional attributes, a Person has no access to your database

The base table (S_PARTY) and extension table (S_CONTACT) that define a contact or person. A person is the simplest representation of an individual in the database




  • A registered customer on (your) Web site
  • A self-registered partner user, that is, one who has no position.


  • A User is a Person who can log into your database and has a responsibility that defines what application views are accessible.
  • A self-registered partner on a Siebel partner application has a responsibility, but does not have a position like a full Partner User has.         

The base table (S_PARTY) and extension tables that define a user (S_CONTACT and S_USER) form User Data Model. A User is a person with following added qualities

1)      The S_USER table contains a login for this user

2)      The S_PER_RESP intersection table specifies the responsibility for this user

3)      It is possible to promote a contact to a user. For example, adding a User ID value for a person in the All Persons view in the Administration – User screen causes the person to appear as a user in the Users view.



  • An Employee at your company – An Employee is a User who is associated with a position in a division within your company

Base table (S_PARTY) and the extension tables (S_CONTACT, S_USER, and S_EMP_PER) define employee. This includes internal employees and Partner users. An Employee is a User with the following added qualities:

  1. S_EMP_PER provides employee data for this user.
    1. A position defined using the S_POSTN table is typically (but not necessarily) associated with an employee.
    2. If the organization to which the position belongs is not a partner organization, then the employee is an internal employee.
    3. If the organization is a partner organization, then the employee is a partner user. 



  • A job title within (your) company
  • A job title within the partner company

Base table (S_PARTY) and extension table (S_POSTN)  Features:

  • Position exist for the purpose of representing reporting relationships
  • A position within your company is associated with a division and is associated with the organization to which that division belongs.
  • A position can be associated with one division only.
  • A position may have a parent position. It may also have child positions
  • One or more employees can be associated with an internal position, and one or more partner users can be associated with an external position.
  • An employee or partner user can be associated with more than one position, but only one position is active at any time.

5) PARTY =>  ACCOUNT PARTY TYPE =>  ORGANIZATION Account is a company or group of individuals with whom you do business. An account is typically made up of contacts It can have parent and child accounts. An account can be promoted to partner organization, but it is not a division, an internal or external organization. Base Table (S_PARTY) and extension table (S_ORG_EXT) defines Account data Model.

                                                                                                                                                            Next Article >>>>

21 comments on “Siebel PARTY DATA MODEL”

  1. Ashay Reply

    Hi thanks for this information but I would like to know why this Data model was designed.what are the uses from database point of view for such arrangement of Party related data… what do we achieve making the S_PARTY base table for all the related tables?
    Thanks and Regards,

  2. Santosh Reply

    Hi Mandeep,

    U are doing a very good job by sharing your knowledge and educating people like me.

    I am a beginner in SIEBEL and I’m finding difficulty in identifying the Parent key and foreign key when I’m configuring any join or any link.Can u please explain my doubt.

    Thank you and Regards,

  3. Pankaj Reply

    You are simply GREAT!!! God bless the people like you… My sincere thanks to you for sharing your knowledge… May I would get a chance or not but my blessings would definately with you for your success… Thanks again…

  4. Anuj Mishra Reply

    Mandeep Dear,
    I was strugling like any thing to understand Party concept by the help of Book shelf and all but some how I was not understanding. After going through your update, Now its clear to me. You are just great. Please keep posting this kind of thing.

    Anuj Mishra

  5. Manikumar Reply

    Hi Mandeep,
    This is very informative and understandable. Keep sharing more topics.. 🙂


  6. Kishore Reply

    HI Mandeep,

    thsi is a good post, PARTY_TYPE_CD column denotes the party type, can you please eloborate this?


  7. Suansh Reply

    Thanks a lot Mandeep…This article clears out a lot of doubts….



  8. sonu Reply

    Sir, i have doubt in S_ORG_EXT and S_BU..If we r storing a Division then the flag in the S_ORG_EXT will be “Y”,if it “N” it may be a organisation or an Account,how we will distingush wether it is an Organisation or Account.I know there is S_BU flag but for account and org its showing “Y”.So pls help me to clear it

  9. John Reply


    I am new to Siebel and need the complete data model for Siebel UCM. Can someone please direct me to any resources?


  10. LP Reply

    Would you consider providing a similar explanation for the ASSETS area?

  11. qwert Reply

    Can you elaborate with an example the pre/post cases data redundancy and how it was avoided with the new data model?

  12. Ram_TechMahindra Reply

    Hi Manideep,
    Nicely articulated . One of the best article which i had come across so far ..

  13. Harvey Reply

    Did you know that the party data model was based on an industry spec call the Customer Profile Exchange which can still be found on the idealliance web-site.  This spec had some very large companies including Siebel and IBM behind it.  You will discover that it goes back to the late 90's and was last revised last about 2001.  You will see columns that Siebel did not fully implement and took shortcuts like repeating ROW_ID value in the PARTY_UID column.

Leave A Reply

Your email address will not be published. Required fields are marked *

error: Content is protected !!