Module 18 Party Business Components

Siebel 8.
0 Essentials
Party Business Components
1 of 25
Module 18: Party Business Components
Module Objectives
To define a party business component To describe the role of S_PARTY and its extension tables in storing
party business component data Describe how data is stored differently for non-party business components and party business components Describe how implicit and explicit joins are used with party business components
3 of 25
Business Challenge: Modeling Party Data

Party data is the ubiquitous information found in most RDBMS Some prominent party types include Contacts, Employees,
Positions, Accounts, User Lists, Organizations, and Access Groups Party types are often related to each other
Employees are related to positions Positions are related to accounts Access groups are related to organizations and so forth
Relationships may be dynamic or ad hoc
4 of 25
Business Challenge: Modeling Party Data

Representing these relationships could result in data models that do
not have optimal normalization

Multiple records may be created for each relationship A separate record is created for a contractor, another for an intern, and a third for an employee A special entity may have to be created for each new ad hoc relationship
5 of 25
Business Solution: Party Business Component

Provides a way to create a network of relationships between party
types to reflect changes and complexities in the business environment Infuses flexibility into the data model
Can establish and change relationships between various party types, as needed
6 of 25

Are similar to standard business components; they:
Group data according to business logic Are referenced by applets Specify access to tables Have fields that map to columns
7 of 25
Party Vs Non-Party BCs

In standard BCs, most data is stored in the base table In party BCs, data is stored in extension tables S_PARTY acts solely as a linking mechanism between types
8 of 25
Extension Tables of S_PARTY

There are eight prominent extension tables for S_PARTY that
store data
Tables such as S_CONTACT_X (which is the 1:1 extension table for the S_CONTACT table) are formally an S_PARTY extension table
9 of 25
Commonly Used Party Business Components

Represent a variety of entities that can be arranged into groups
related to persons, organizations, or access control
10 of 25
Person-Related Party BCs

Store their main data in S_CONTACT May store additional data in S_USER and S_EMP_PER
Serve as logical extension tables
11 of 25

Primarily reference person-related S_PARTY extension tables
12 of 25

A number of person-related business components use these tables
13 of 25
Organization-Related Party BCs

Store their main data in S_ORG_EXT May store additional data in S_BU May include account, division, organization, or household data
14 of 25
Organization-Related Party BCs

Multiple organization-related business components use these tables
BusComp: Account Name Location 3 Com HQ
BusComp: Organization Name Internal Org Flag Aaron Inc., Y
Organization BU Name Aaron Inc
PAR_ROW_ID NAME INT_ORG_FLAG 1 3 Com N 2 Aaron Inc., Y Table: S_ORG_EXT
LOC HQ
PAR_ROW_ID 2
NAME Aaron Inc Table: S_BU
BU_FLG Y
3 Com is an Account and not an Organization. Hence no record in S_BU
15 of 25
Groupings for Access Control

Represent groupings of party instances
User List Access Group Position
16 of 25
Groupings for Access Control

Access Group, User List, and Position are party business components
17 of 25
Example, Relating Party Data

A user list can be associated with persons via the S_PARTY
intersection table S_PARTY_PER There are relationships in S_PARTY

They are represented in S_PARTY_PER ROW_ID in S_PARTY is used to relate party types
18 of 25
Example, Relating Party Data

An access group can then be networked with those users, or other
user lists, or most any other S_PARTY type

Person, User List, Organization and Account party types can be related to an Access List party type
19 of 25
Party Implicit Joins

Used to populate the prominent S_PARTY extension tables Created automatically for these extension tables Are similar to implicit joins for standard business components Do not appear in join object definitions ROW_ID in base table is always the PK PAR_ROW_ID in extension is always the FK
20 of 25
Explicit Join: Non-Party Business Component

Data in a party table can be joined into a non-party business
component
Example: Bringing account data into the Opportunity business component for display in an Opportunity applet
21 of 25
Explicit Join Definition

References the extension table that contains data of interest
22 of 25
Explicit Join: Another Party BC

Uses an explicit join to the party table, and not the implicit one Example: Bringing parent account data into the Account business component for display in an Account applet
23 of 25
Module Highlights
Party BCs create relationships between party types Party BCs are similar to standard BCs but data is stored in extension tables Person-related party BCs store data in S_CONTACT Organization-related party BCs store data in S_ORG_EXT Access Group, User List, and Position are party BCs Party implicit joins populate S_PARTY extension tables
Explicit joins reference extension tables that contain data
24 of 25
Lab
In the lab you will:
Examine how fields in a (non-party) business component map to columns in base and joined tables Examine how fields in a party business component map to columns in S_PARTY, its extension tables, and joined tables
25 of 25

Module 18 Party Business Components

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Module 18 Party Business Components

Transféré par

Droits d'auteur :

Formats disponibles

Siebel 8.

Party Business Components