Siebel 8.
0 Essentials
Module 19: Siebel Business Objects
19
Copyright © 2007, Oracle. All rights reserved.
Module Objectives
After completing this module you should be able to:
Describe how business objects focus data presented in the UI
based on context
Describe how views reference business objects
Describe how links are used to relate parent business components
to child business components
Why you need to know:
Business objects enable you to configure your company’s
business logic
Copyright © 2007, Oracle. All rights reserved. 2 of 15
Application Architecture: Business Objects (BO)
Provide a way to organize BCs into major areas according to
your business logic requirements
Provide context to views
Siebel Application Architecture
UI List Column
Layer Applet View Screen Application
or Control
Business Business Business
Layer Field
Component Object
1 or many
Data References
Layer Column Table
Copyright © 2007, Oracle. All rights reserved. 3 of 15
Business Challenge
Business components provide a way to group data according to
business logic, but they do not address the need for context
For example, the opportunity BC defines how to retrieve
opportunity data, but not related activity data
How is it that the Activities
view shows only activities
?
related to the Kaboom
opportunity?
Copyright © 2007, Oracle. All rights reserved. 4 of 15
Business Solution: Business Objects Provide
Focus
Business objects contain relationships used to access records
from a child business component
Identifies records to display depending on context in which they
are viewed
Ensures that only records related to parent BCs are returned from
queries
Activities pertaining to
Kaboom opportunity, and
only Kaboom, are displayed
Copyright © 2007, Oracle. All rights reserved. 5 of 15
Business Objects
Are a collection of related business components that represent a
major area of the business
Contain parent and child business components
Relate parent and child components via links
Links focus records displayed based on the context in which they
are viewed
Provide a container for grouping business components
Provide context for views
Opportunity
Business Link focuses data in
Object view
Opportunity
Children BCs
Parent BC provides provide data related
most data; data is Action Product Source to parent
specific to the BO
Copyright © 2007, Oracle. All rights reserved. 6 of 15
Business Object Component
Contains Link and BusComp properties that relate the parent
and child business components to each other
Link
relates
parent to
child
Child BC Parent BC
Copyright © 2007, Oracle. All rights reserved. 7 of 15
Link Definition
Identifies the PK/FK relationship
Identifies which records to retrieve from the child business
component
Identifies the foreign keys to populate when new child records are
created
Is used with both 1:M and M:M relationships between parent
and child data
Opportunity
Link Definition
Opportunity
Action Product Source
Copyright © 2007, Oracle. All rights reserved. 8 of 15
1:M Link
Used for 1:M relationship
between parent and FK field in
child BC
child business components
Link Definition
Defaults to parent
BC/child BC
PK field in
parent BC
(defaults to
ROW_ID if
blank)
Copyright © 2007, Oracle. All rights reserved. 9 of 15
M:M Link
Used for M:M relationship between parent and child business
components
Uses an intersection table to resolve the link
Intersection table
with FK columns
Copyright © 2007, Oracle. All rights reserved. 10 of 15
Cascade Delete Property
The Cascade Delete property of a link specifies whether child
records of a 1:M relationship are deleted when the parent record
is deleted
None: Neither deletes nor clears the foreign key column
Clear: Does not delete, but clears the foreign key column
Delete: If a parent record is deleted, all child records are deleted
Copyright © 2007, Oracle. All rights reserved. 11 of 15
Cascade Delete Property Continued
Determined by your business logic
Should all activities be deleted if parent contact is deleted?
Should all child opportunities be deleted if the parent account is
deleted?
Deletion
cascades
Copyright © 2007, Oracle. All rights reserved. 12 of 15
Grandchild Business Components
Business objects may include grandchild business components
Used in parent-child-grandchild views
Parent BC:
Account
Activity plans
for Art.net
Child BC:
Activity Plan
Activities for
selected Art.net
activity plan
Grandchild BC:
Activity Plan
Action
Copyright © 2007, Oracle. All rights reserved. 13 of 15
Links for Grandchild Data
Specify how the grandchild and child business component are
related
Used to retrieve grandchild records on parent-child-grandchild
views
Parent/Child
Child/Grandchild
Copyright © 2007, Oracle. All rights reserved. 14 of 15
Module Highlights
Business objects
Provide a way to group BCs according to business logic
Provide context to views
Contain parent and child BCs associated via links
Links provide a way to focus records based on context
Links relate parent and child BCs
Link definitions specify which records to retrieve from child BCs
A 1:M link is used for a 1:M relationship between parent and
child BCs
A M:M link is used for a M:M relationship between parent and
child BCs
A M:M link uses an intersection table to resolve the link
BOs may include grandchild BCs
Copyright © 2007, Oracle. All rights reserved. 15 of 15
