Module 19 Business Objects

8/18/2019 Module 19 Business Objects

1/15

1 of 15 Business Objects

Siebel 8.0 Essentials


2/15

Module 19: Business Objects


3/15


Module Objectives

• To know how Business objects focus data presented in the UI basedon the context

• To understand how the business components are grouped and thewa the parent and child relationships appear


4/15


Business !hallenge

• Business components provide a wa to group data according tobusiness logic" but the do not address the need for context # $or example" the opportunit B! defines how to retrieve opportunit

data" but not related activit data

%ow activities forthis specific &' are

retrieved (


5/15


Business &olution) Business Objects *rovide focus• Business objects contain relationships used to access records from a

child business component # Identifies records to displa depending on context in which the are

viewed # +nsures that onl records related to parent B!s are returned from ,ueries


6/15


Business Objects

• 'epresent a major functional area of the enterprise• *rovide a container for grouping business components

# !ontain parent and child business components # 'elate parent and child components via links # -inks focus records displa ed based on the context in which the are viewed # *rovide context for the views

Service Request

ActivitylanAction

Service Request

Attac!"ent

Service Request BO-ink focuses datain view

!hild B!s providedata related to

parent


7/157 of 15 Business Objects

*rimar Business !omponent• +ach business object has one business component that serves as the

master.parent/ or driving business component

*arent B!)&ervice 'e,uest

!hild B!) 0ction



-ink 1efinition• 0 link defines a 2)M .or master3detail/ and M)M relationship between two

*arent and !hild B!s

# Identifies the *45$4 relationship• Identifies which records to retrieve from the child business component• Identifies the foreign ke s to populate when new child records are created

# -ink object t pe makes master3detail views possible # 0lso used in the implementation of multivalue group applets



2)M -inkUsed for 2)M relationship between parent and child businesscomponents

The &earch &pecification propert of a link is applied to the childbusiness component6$4 field in child

B!

1efaults to*arentB!5!hildB!



M)M -ink

• Used for M)M relationship between parent and child businesscomponents

• Uses an intersection table to resolve the link



!ascade 1elete *ropert• The !ascade 1elete propert of a link specifies whether child

records of a 2)M relationship are deleted when the parent record is

deleted # 7one) 7either deletes nor clears the foreign ke column # !lear) 1oes not delete" but clears the foreign ke column # 1elete) If a parent record is deleted" all child records are deleted

1eletes the 0ctivities when the

&' is deleted



*arent3!hild38randchild views

• Business objects ma include grandchild business components

*arent B!)&ervice'e,uest

8rand !hild)0ctivit*lan 0ction

!hild B!) 0ctivit*lan



-inks for 8randchild 1ata

• &pecif how the grandchild and child business component are

related # Used to retrieve grandchild records on parent3child3grandchild views



Module %ighlights

• Business objects # *rovide a wa to group B!s according to business logic # *rovide context to views # !ontain parent and child B!s associated via links # Ma include grandchild B!s

• -inks relate parent and child B!s and specif which records to retrieve

from the child B!s # 2)M links are used for a 2)M relationship # M)M links are used for a M)M relationship


15/1515 f 15Business Objects

-ab

• In this lab ou will) # +xplore the 9iews" Business Objects and -inks definitions

Documents

Module 19 Business Objects