17 Siebel Business Components

8/13/2019 17 Siebel Business Components

1/18

17Copyright 2007, Oracle. All rights reserved.

Module 17: Siebel Business

Components

Siebel 8.0 Essen tials


2/18

2 of 18Copyright 2007, Oracle. All rights reserved.

Module Objectives

After completing this module you should be able to:

Define a business componentDescribe how business component fields at the business objectlayer are mapped to columns at the data layer Describe how base and joined tables are used as a part of thismapping

Why you need to know:The business component is a fundamental object in the Siebel

Application Architecture


3/18


Application Architecture: Business Components

Provide a way to group data according to business logic

Are referenced by appletsSpecify access to tables (read, write, and update)

Are used by business objects to provide data to views

TableColumn

Screen Application

Business

Component

BusinessObject

ViewApplet

Field

List Column

or Control

UILayer

BusinessLayer

DataLayer

Siebel Application Architecture

1 or many

References


4/18


Business Component

A business component (BC) is a person, place, thing, or

event about which data must be storedRepresents a fundamental business entity

Provides the foundation for controlling how data isselected, inserted, and updated in underlying tables

Opportunity

Product Contact

Opportunity

Quote

= Business Component


5/18


Business Component Continued

Arranges data from one or more tables into a logical grouping

Consists primarily of fields and joinsEach field references a single column in a table

Is not a tableDoes not store dataStores metadata: data about data

Opportunity

Name Sales Stage Sales Stage PhaseDecision Level

S_OPTY

R OW

_I D

NAME

DE S C _T E X T

C UR C Y

_ C D

S_STG

R OW

_I D

NAME

P HA S E

_ C D

S T G _ ORDE R

S_OPTY_X

R OW

_I D

P AR _R OW

_I D

AT T RI B

_ 0 1

AT T RI B

_ 0 9

AT T RI B

_ 3 9

Description

Base Table Joined Tables

Field

BC


6/18


Business Component Reuse

A business component can be:

Defined once in terms of a logical collection of columns from oneor more tablesThen used in many different business object contexts

Opportunity

Product Contact

Opportunity

Quote

Contact

Product Account

Contact

Contact BC appears aschild in Opportunity BO

Contact BC appears asmaster in Contact BO

Quote


7/187 of 18Copyright 2007, Oracle. All rights reserved.

Base Table

Contains the main columns for the business component

Every business component references only one base tableMany BC fields are mapped to base table columnsFields referencing base tables are editable in the UI

S_OPTYR OW

_I D

NAME

DE S C _T E X T

C UR C Y

_ C D

Base table

Table:

S_OPTY

Column:

DESC_TEXT

BusinessComponent:Opportunity

Field:

Description

Mapping Example

Opportunity

Name Sales Stage Sales Stage PhaseDescription Decision Level



Business Component Table Property

Each business component contains a table property thatspecifies the base table

Basetable



Fields That Map to a Base Table

Column property maps to a column in the base table

Join property is blank

Join is blank

Status fieldreferences base table

Base table



Explicit Join

Is a join that brings in data from tables other than the base tableto meet the business components data display requirements

Most fields referencing explicitly joined tables are read-only in theapplet

Includes a join definition and a join specificationBC field references the join definition

S_OPTYR OW

_I D

NAME

DE S C _T E X T

C UR C Y

_ C D

S_STGR OW

_I D

NAME

P HA S E

_ C D

S T G

_ ORDE R

Opportunity

Base table Joined table

Name Sales StageDescription



Fields That Map to a Joined Table

Join property specifies the join object definition being referenced

Column property maps to a column in the joined table

The S_STGcolumn, NAME,

contains salesstage data

Sales Stage field maps toSales Stage join

Name of join thatmaps to S_STG table



Joining Data from Joined Tables

Returns only one row from the joined table

There is a 1:1 or 1:M relationship from the joined table to the BCRelationship is established using a FK column on the base tableto join to the PK column on the joined table

S_OPTYR OW

_I D

NAME

DE S C _T E X T

C UR C Y

_ C D

S_STGR OW

_I D

NAME

P HA S E

_ C D

S T G

_ ORDE R

C URR

_ S T G _I D

FK column on base table PK column on joined table

Base Table Joined Table

FK PK



Displaying Fields from Joined Tables

The UI layer specifies how information joined at the businesslayer will be displayed

From Base Table From Joined Table

S_STGS_OPTY

OpportunityBC

OpportunityList Applet

Data Layer

BusinessLayer

UI Layer



Join Definition

Specifies the joined table from which to retrieve data

Is a child object of the business componentDefaults the alias property to the name of the joined table

Modify alias when there is more than one join to same table

Alias of joinJoined table



Join Specification

Specifies how to retrieve the related row from the joined table

Based on the foreign and primary keys used to relate the base and joined tables

S_OPTY

R OW

_I D

NAME

DE S C _T E X T

C UR C Y

_ C D

S_STG

R OW

_I D

NAME

P HA S E

_ C D

S T G _ ORDE R

C URR

_ S T G

_I D

OpportunityName Sales Stage IdDescription

FK PK

Primarykey

column

ForeignKeyfield



Implicit Joins

Base tables are automatically joined to their extension tables

Known as implicit joinsMake extension table rows available to the BC An explicit join to describe the relationship is not needed

Come pre-configured as part of the Siebel object architectureName of an implicit join is always the name of the _X table

Do not appear as Join object definitionsDo appear in the picklist for the Join property in an SVF

S_OPTY_X Appears HereS_OPTY_X does not

appear here

S_OPTY_Xdoes appear

here



Fields That Map to an Extension Table

Join property specifies the extension table being referenced

Column property references a column in the extension tableField is editable in the UI

The S_OPTY_Xcolumn,

ATTRIB_44,contains budget

amount data

The Budget Amtfield referencesthe S_OPTY_X

table


18/1818 of 18C i ht 2007 O l All i ht d

Module Highlights

A BC is a person, place, thing, or event about which data isstored

A BC can be defined once then re-used by different BOsEach BC references a single base table

A BC can include data from joined tables A join definition specifies joined table A join specification specifies how to access joined table viaPK/FK

An extension table extends data in the BCFields on extension tables use implicit joins

17 Siebel Business Components

Documents

Transcript of 17 Siebel Business Components