Академический Документы
Профессиональный Документы
Культура Документы
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.
E.G:
Features:
E.G:
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
2) The S_PER_RESP intersection table specifies the responsibility for this user
E.G:
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.
E.G:
Features:
An account is typically made up of contacts It can have parent and child accounts.
Base Table (S_PARTY) and extension table (S_ORG_EXT) defines Account data
Model.
6) PARTY => DIVISION
Features:
A division exists for the purposes of mapping a company’s physical structure into the
Siebel Database and for providing a container for position hierarchies.
A division may have a parent division. It may also have child divisions.
Data cannot be associated directly with a division. (Divisions that are not designated as
organizations do not drive visibility.)
Base table (S_PARTY) and extension table (S_ORG_EXT) define division data model
along with INT_ORG_FLG=Y (in S_ORG_EXT) table
E.G: An Organizational unit within the company such as Asian organization and
A partner company
Features:
An organization exists for the purpose of providing a container in which positions can be
associated with data.
A division can be associated with only one organization: itself or an ancestor division that
is also an organization.
Base Table (S_PARTY) and extension tables (S_ORG_EXT and S_BU) define
Organizational data model.
An Organization, sometimes known as a business unit, is also a Division, but has a record
in the S_BU table.
The base table and extension tables (S_ORG_EXT, S_BU, and S_ORG_PRTNR) define
a Partner Organization.
A group of people, typically a family, who reside at the same residence forms Household
A household may have any combination of contacts, users, employees, and partner users
as members.
Base table (S_PARTY) and extension table (S_USERLIST) defines User list.
E.G:
A support team made up of some internal employees and some partner users.
Features:
A user list is an ad hoc group of people. It may have any combination of contacts, users,
employees, and partner users as members
A user list cannot have a parent or children.
Base table (S_PARTY) and extension table (S_PARTY_GROUP) defines access group
E.G:
An access group may have a parent access group. It may also have child access groups.
Divisions, organizations, and accounts are instances of the Organization party type.
Doubts
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?
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 introductions of Party model following tables are made obsolete in Siebel 7.
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
2) User Lists and Access Groups facilities were not in Siebel 6?If they were there how
were they implemented?
3) Please elaborate more as how the Data Redundancy was removed with introduction of
the Data model…(May be I am not getting clarity in terms of Database concepts here!)
Hello Ashay,
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