Siebel PARTY DATA MODEL

Home » Interview Question, Siebel Architecture, Siebel EIM

7 July 2009 12,686 views 18 Comments

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.

PARTY DATA MODEL:

PARTY TYPE AND PARTIES:

1) PARTY => PERSON (CONTACT) PARTY TYPE => PERSON

E.G:

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

Features:

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

2) PARTY => USER PARTY TYPE => PERSON

E.G:

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

Features:

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.

3) PARTY => EMPLOYEE PARTY TYPE => PERSON

E.G:

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:

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.

4) PARTY => POSITION PARTY TYPE => POSITION E.G:

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 >>>>

Readers who viewed this page, also viewed:

(1 votes, average: 5.00 out of 5)

Loading ...

18 Comments »

Ashay said:

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,
Ashay

# 8 July 2009 at 1:09 pm

Mandeep Grewal said:

Below points will help u
1) The main objective of introducing party model is to provide better access control mechanism and to improve performance of the system.

The introduction of Party model following tables are made obsolete in Siebel 7.

* S_EMPLOYEE now merged into S_CONTACT
* S_EMPLOYEE_ATT
* S_ORG_INT now merged into S_ORG_EXT
* S_ORG_INT_ATT
* S_POSTN_RPT_REL

2) It allows the configuring the business components related to access control and import access control data.

3) To introduced the concept of the relational database to a very good access control mechanism functionality in siebel.

4) The data redundancy was removed , now the we have a master base table which further linked to various tables for the entities as discussed in article

# 8 July 2009 at 3:19 pm

Ashay said:

Hi Mandeep,
Thanks for the reply,it does help!
Still I have few Qs.:-)

1) Prior Siebel 7.0 you said there were 2 tables
S_EMPLOYEE now merged into S_CONTACT
S_EMPLOYEE_ATT, what was
S_EMPLOYEE_ATT being used for?

2) User Lists and Access Groups facilities were not in Siebel 6?If they were there how were they implemeted?

3) Please elaborate more as how the Data Redundancy was removed with introduction of thie Data model…(May be i am not getting clarity in terms of Database conepts here!)

Thanks and Regards,
Ashay

# 8 July 2009 at 4:01 pm

Mandeep Grewal said:

Hello Ashay,

1) S_EMPLOYEE_ATT : This table was used to stored additional detail information regarding employee
.

2) I am not sure about this, but will update you soon on this.

3) In siebel 7 their was not much major in business layer but the data layer was changed to a major extent. In siebel 7.x they introduced administrative consoles were you can easily provide access to the various views and responsibilities etc. But in siebel 6.x there was not any such concept. The other major change was in siebel 6.x these S_view , s_resp etc these tables exists but they were having the explicit joins and in siebel 7.x they have implicit joins.
The data redundancy was removed with these implicit joins having 1:M relationship among the parent and child entities.

Thanks
Mandeep Singh Grewal

# 8 July 2009 at 5:47 pm

Santosh said:

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,
Santosh

# 17 July 2009 at 11:29 pm

Ashish Kumar said:

Hi Santosh,
Please ask questions in ask question page so that only comments related to the post can be answered in this page.

# 17 July 2009 at 11:48 pm

Pankaj said:

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…

# 20 August 2009 at 5:02 pm

Anuj Mishra said:

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.

Regards,
Anuj Mishra

# 19 February 2010 at 10:50 pm

Manikumar said:

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

Regards,
Mani

# 20 February 2010 at 9:06 am

Kishore said:

HI Mandeep,

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

Thx
Kishore

# 10 March 2010 at 1:16 pm

Suansh said:

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

Cheers!!!

Suansh

# 13 March 2010 at 9:46 pm

sonu said:

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

# 29 April 2010 at 5:32 pm