The Siebel Party Model and Oracle BI Applications – Part 1/2

In this post I’m focussing on the Siebel Party Model and how this is relevant and brought over to the pre-built Oracle BI Applications for Analysis.

From a CRM perspective it is very important to model:

  • the own Organization
  • Internal Employees
  • Employee Hierarchy
  • Customers (of the own Organization)

Customer’s can be other Company’s (in Siebel known as Accounts) in B2B  or Individual Persons in B2C Scenarios (in Siebel known as Contacts).  This is relevant as e.g. a specific Sales Employee of the own Organization sells a Product to a purchase authorized Contact of another Company (Accounts).

To organizes all this, Siebel uses the Party Concept to relate all above mentioned (and some more) entities such as: Person, Organization, Position, Household etc. within a single entity: the Party.

image

All Entities surrounding (extending) the Party have at least one record stored in the Party entity itself. The Party also has a Party Type (S_PARTY.PARTY_TYPE_CD), which provides some further aggregation/classification for the Party Entities.

The following Table describes the Party Entities (Extension Entities to the Party Entity), the Physical table references and the associated Party Type’s (S_PARTY.PARTY_TYPE_CD) in the Party Entity:

Party ext. Entity

Phy. Table

Party Type in Party Entity

Description

Person (or Contact)

S_CONTACT

Person

A Person is an [real world] individual who is represented by a Person, Without additional attributes, a Person has no access to your database. E.g. An employee at a customer’s company

User

S_USER

Person

A User is a Person who can log into your database and has a responsibility that defines what application views are accessible

Partner User

S_USER

Person

An employee at a partner company, who is associated with a position in a division within an external organization. Therefore, a Partner User is also an Employee, but not an internal one.

Employee

S_EMP_PER

Person

An Employee is a User who is associated with a position in a division within your company.

Position

S_POSTN

Position

A job title within your company that exists for the purpose of representing reporting relationships. Every position is associated with a division. The position is then also automatically associated with one organization: the organization with which the division is associated. Thus, a position within your company is associated with a division and is associated with the organization to which that division belongs. Data is associated with a Position, which drives the Position Visibility.

Account

S_ORG_EXT

Organization

A company with whom you do business. An account is not a division, an internal organization, or an external organization. Can have Parent and Child Accounts.

Division

S_ORG_EXT

Organization

An organizational unit within your company such as Manufacturing or Corporate e.g. operating within a particular country. 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 can have a Hierarchy with parent division and have child divisions. A division can be associated with only one organization. Data cannot be associated directly with a division. (Divisions that are not designated as organizations do not drive visibility.

Organization

S_ORG_EXT

Organization

An organizational unit within your company. The Organization is a division that is designated as an organization. Positions are not assigned directly to Organizations to drive Visibility, but only via Divisions. An organization exists for the purpose of providing a container in which positions can be associated with Data to drive Position and Organization Visibility. Organizations can also have a Hierarchy like divisions.

Household

S_GROUP_ORG

Household

A group of people, typically a family, who reside at the same residence, who are economically affiliated and share a common purchasing or service interest.

User List

S_USERLIST

User List

A user list is a group of some internal employees and some partner users. It can have any combination of contacts, users, employees, and partner users as members

Access Group

S_PARTY_GROUP

Access Group

An access group is a group of any combination of parties of type Position, Organization, and User List. That is, it is a group of groups

Business Unit

S_BU

Organization

Not officiall mentioned: Internal Organizations are also represented as Business Units.

To  model relationships between the own Organization (and own Employees) and Customer Organizations (and their Employees) the most important “Party Types”  are: Organization and Person/Contact.

Person/Contact:
image
Organization:
image

What are the Entities for Party Type: Persons?

image

The Entity Contact/Persons represents everything necessary for Siebel to model an Individual e.g. with First Name, Last Name, Date of Birth, Phone Number. That might be a Purchasing authorized Person within a customer’s company. A User can be assigned with a User Id to the Person to specify the credentials like Login and password. If the User is an internal, it is represented as Employee by assigning the Contact with a Position within the Organization.

How does this look in the Siebel UI?

image

To administer this, one needs to navigate to “Administration – User” Screen for setting up Persons/Contacts, Employees and Users.

As can be seen below, certain Person/Contacts also have been configured with a User for Logging into the Siebel Application:

image

Using the Employee Screen it is also possible to assign the Employee to a Organization and a Position for steering the Visibility. (Additionally the Employee can also be assigned to a Division, however this doesn’t affect Visibility).

image

Detailed Screen of a single Employee Record:

image

Even though a Employee Record exists, the Employee needs to be assigned with a User for being able to Login to the Siebel Application.

-The setup of Partner Users is not covered within this Article-

How is this stored in the Siebel Database?

For Contacts:


select ou_id,fst_name,last_name,birth_dt,work_ph_num,login,
emp_flg,emp_num,sex_mf, priv_flg,status_cd,prospect_flg
from S_CONTACT;

image

For Users:

select LOGIN,USER_FLG,PASSWORD
from S_USER;

image

For Employees:

select CNTRCTR_FLG,BURDENED_RATE,CURR_SALARY_AMT,TERMINATION_DT,
EMP_STAT_CD from S_EMP_PER;

image

And for the Party of Type Person:

select ROW_ID,PARTY_TYPE_CD,PARTY_UID,PAR_PARTY_ID,NAME
from S_PARTY
where PARTY_TYPE_CD = 'Person';

image

The following is an example of joining all above mentioned the Information of the Entities via the S_PARTY:

Select S_CONTACT.ou_id,S_CONTACT.fst_name,S_CONTACT.last_name,
S_CONTACT.birth_dt,S_CONTACT.work_ph_num,S_CONTACT.login,
S_CONTACT.emp_flg,S_CONTACT.emp_num,S_CONTACT.sex_mf,
S_CONTACT.priv_flg,S_CONTACT.status_cd,
S_CONTACT.prospect_flg --from S_CONTACT
,S_PARTY.PARTY_TYPE_CD,S_PARTY.Name AS "PARTY NAME" --from S_PARTY
,S_USER.LOGIN,S_USER.USER_FLG,S_USER.PASSWORD --from S_USER
,S_EMP_PER.CNTRCTR_FLG,S_EMP_PER.BURDENED_RATE,
S_EMP_PER.CURR_SALARY_AMT,S_EMP_PER.TERMINATION_DT,
S_EMP_PER.EMP_STAT_CD --from S_EMP_PER
from S_CONTACT INNER JOIN S_PARTY
ON S_PARTY.ROW_ID = S_CONTACT.PAR_ROW_ID
LEFT OUTER JOIN S_USER ON S_USER.PAR_ROW_ID = S_CONTACT.EMP_ID
LEFT OUTER JOIN S_EMP_PER ON S_PARTY.ROW_ID=S_EMP_PER.PAR_ROW_ID;

image

For this I’ve used Outer Joins for User and Employee Entity since not every Contact belongs to this Entity.

What are the Entities for Party Type: Organizations?

image

The Account is the representation of a Business Customer’s (also known as “Company” in real life terms). The own Company is represented as: Organization’s (for steering Visibility), Division’s (not influencing Visibility) and Business Unit’s.

How does this look in the Siebel UI?

Accounts (or Business Customers are administered from the Account List View:

image

The Contact/Persons within the Business Customer Company can be seen below the Account (when clicking a particular Account) and each contact has a certain role or Job Title within the Customer Account.:

image

The own Organization can be Administered using the (internal) Organization (and Business Unit) and Divisions, from the “Administration – Group Organization” Screen:

image

And the Organizations List Screen:

image

And the detailed Screen e.g. to setup (internal) Organization Hierarchy:

image

The Divisions can be listed from the Divisions Screen:

image

The main Screen shows the association of Divisions with one (and maximum only one) Organization:

image

And on the detailed Screen shows the Positions which are assigned to the Division. (And from this link implicitly to the Organization):

image

How is this stored in the Siebel Database?

External Organizations, which represent Business Customers as Accounts use the S_ORG_EXT Table.

select bu_id,par_bu_id, name,cmpny_name,legal_form_cd, accnt_flg,
accnt_type_cd,prospect_flg, int_org_flg,prtnr_flg,active_flg,
pay_type_cd
from S_ORG_EXT
where int_org_flg = 'N';

image

Previous Version of Siebel used a Table called “S_ORG_INT” for Internal Organizations, however this Table is not used/part of the shipped Standard Model any further. It’s functionality is merged into S_ORG_EXT with INT_ORG_FLG = “Y” and an associated S_BU record.

select S_BU.BU_FLG,S_BU.NAME,S_BU.ROW_ID,S_BU.PAR_ROW_ID,
/*S_ORG_EXT.ACCNT_FLG,*/S_ORG_EXT.ACTIVE_FLG,S_ORG_EXT.ROW_ID,
S_ORG_EXT.PAR_ROW_ID,S_ORG_EXT.BU_ID,S_ORG_EXT.DIVISION,
S_ORG_EXT.DIVN_CD,S_ORG_EXT.INT_ORG_FLG,S_ORG_EXT.NAME,
/*S_ORG_EXT.ACCNT_TYPE_CD,*/OU_NUM,OU_TYPE_CD,PAR_BU_ID,
PAR_DIVN_ID,PAR_OU_ID
from S_BU INNER JOIN S_ORG_EXT ON S_ORG_EXT.BU_ID = S_BU.ROW_ID
where BU_FLG ='Y' and INT_ORG_FLG = 'Y' ;

image

Divisions are also just stored in the S_ORG_EXT with INT_ORG_FLG = “Y” but have no record in the S_BU table. :

select *
from S_ORG_EXT --no Record in S_BU Table
;

image

Where are the relationships maintained?

image

The relationships between the own Organization and Employees and the customer’s Organization and Employees is maintained within the Party Relationships and Party Members Table “S_PARTY_REL” and “S_PARTY_PER”. The S_PARTY_REL must be used to model multiple relationships between the same Entities e.g. when the same Contact has multiple roles (Purchase Authorized, Business Owner, Fleet Manager) within the same one Account. Because the S_PARTY_PER has unique indexes defined not allowing this multiple Relationships.

How is this stored in the Siebel Database?

The S_PARTY_REL and S_PARTY_PER Table are used to relate the Party Entities.

select * from s_party_rel;

image

How is this modelled in BI Applications?

Within a next blog Post I’ll cover how this is brought to BI Applications covering:

  • How Contacts and Accounts are represented in the Oracle Business Analytics Warehouse (OBAW) Data Model as Dimensions
  • How the Fact  to relate Account and Contacts (W_PERSON_F) is extracted using the S_PARTY_PER
  • How other Facts use the Account and Contact Dimensions, like W_CAMP_HIST_F

Other Helpful resources are: