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:

Siebel – Training Module

 

Introduction

Siebel Training Module is out-of-the-box functionality. It allows to  collate all Training materials and courses with in the Siebel application. Users can search for available courses and enroll themselves.

 

Training Materials

  • For each training, there are associated materials such as documents and presentations.
  • Siebel provides Training Library screen to store all training materials (including doc, xls, ppt and pdf files).
  • Make sure to include Literature Type as ‘Training Literature’.

 

Training Courses

  • A course is the main training element in Siebel Training.
  • Create training courses under Administration – Training > Course Details screen.
  • Mark the status as ‘Active’ to publish the course.
  • Associate Training Materials added above with the courses under ‘Links‘ detail tab.

 

Enrollment Process

  • A user can enroll themselves to any available trainings under Trainings > Find Trainings view.
  • Alternatively, administrator can also delegate course trainings to any other user.
  • Enroll’ button invokes two vanilla workflows –
    • eTraining Enrollment Process
    • eTraining Enrollment Message Process
    • It is required to deploy and activate these two workflows.

 

Tracking

  • Users can track and monitor progress of their trainings under Trainings > My Trainings view.
  • Users can see the details for any training course by clicking hyperlink in course list column.
  • Users may de-register themselves from selected courses by clicking ‘Drop‘.

 

Managerial Role – View Trainings

  • Managers can see all training enrollments of their subordinates under Trainings > My Team’s Trainings view.

 

Managerial Role – Assign Trainings

  • Managers can also assign training to their team members under Training > Find Training view.
  • Click on ‘Enroll’ button under Enroll Others column. Then select all the users to whom training is to be assigned. Click ‘Finish’.

 

To download this post in PPT format, click here >> Siebel Training Module – Presentation

 

Siebel Party Model – History

Siebel 7.x introduced a party table – S_PARTY as the primary table in Party model and the base table for all Party business components. Accounts, Organizations, Internal Divisions, Contacts, Employees, Positions, and Households are all considered parties and can be referenced from this table.

Impact on Database Architecture

Some tables previously used to store above data were retained as Extension Tables of S_PARTY:

  • S_USER stores Siebel User information.
  • S_EMP_PER stores attributes for Brand-Owner Employees and Partner Users who are considered agents of the Brand-Owner.
  • S_BU stores Organization information.
  • S_CONTACT
  • S_ORG_EXT
  • S_POSTN

And some of the tables become obsolete:

  • S_EMPLOYEE – Its functionality is merged into S_CONTACT leading to use of single-person table.
  • S_ORG_INT – Its functionality is merged into S_ORG_EXT. leading to use of single-organization unit table.
  • S_EMP_POSTN – It is replaced by S_PARTY_PER.
  • S_EMPLOYEE_ATT
  • S_ORG_INT_ATT
  • S_POSTN_RPT_REL

Complete Overview of Party Data Model

To study Siebel’s Party Data Model in detail, please purchase our ebook on this topic:

Authentication Methods in Siebel

 

Authentication is the process of verifying the identity of the user before he gains access to the application. The process consists of collection of user credentials (such as User Id and Password) and comparing them with pre-stored values.

Following three general authentication methods are supported by Siebel:

 

1)    Database Authentication

  • A separate database login for each user.
  • Users will provide credential details to DBA. DBA will add/modify/delete those users to database.

 

2)    Directory Server Authentication

  • Single database login can be shared among multiple users.
  • Users can directly modify their credentials within Siebel application. It will automatically be synchronized with the directory server.
  • Third party directory server is required.

 

3)    Web Single Sign-On

  • Login once and access multiple applications. This facility is internally managed through tokens.
  • Single database login can be shared among multiple users.
  • Users need to provide their credentials to the DBA.
  • Third party directory server is required.

 

Integration Components

Integration Components (ICs) are the building blocks of Integration Objects. As IO is mapped to BO, in the same fashion, IC is mapped to corresponding BC.

  • One or more IC constitutes the integration object.
  • At least one IC will be primary corresponding to primary business component of the business object.
  • There would be zero or more child IC with respect to child business components in the business object.
  • Each MVG in business component is exposed as a child IC under the integration object.

Integration components have following Integration Component Keys (ICK):

  • User Keys – Set of fields to determine the records uniquely
  • Status Keys – To store the Siebel Row ID and operation status for insert, update or delete scenarios

On creating the integration objects through Siebel Wizard:

  • Calculated Fields at the business component are imported automatically as inactive fields in Integration Component.
  • For any unneeded field, mark it as Inactive. Never delete a field from Integration component as it will be added again when Business Object is upgraded.