|Bookshelf Home | Contents | Index | PDF|
A business object represents a major functional area of the enterprise. An opportunity, account, or contact is each an example of a business object. For more information, see Business Object. For an introduction to the relationships described in this topic, see Hierarchy of Object Types and Relationships.
Figure 21 illustrates an example of how a business object groups business components into a logical unit. For example, the Opportunity business object groups together the Opportunity, Contact, and other business components.
Each business object includes one business component that serves as the parent business component. In Figure 21 the parent business component is Opportunity. A link establishes a relationship between the parent business component and other child business components, such as Contact and Product. For example, the link allows the business object to display products that are related to an opportunity or contacts that are related to an opportunity.
A business object provides the foundation for a view and a screen. Typically, each view that a screen references uses the same data for the view when Siebel CRM derives the data from the same business component. For example, the Opportunities Screen references the following views:
Siebel CRM derives the data for each of these views from the Opportunity business component. Therefore, the Siebel schema groups views that derive most of their data from an opportunity into the Opportunity screen. Because views in a screen usually derive their data through the same business object, a screen is indirectly related to the business object.
Figure 22 illustrates the relationships and objects that Siebel CRM uses with a business object, screen, and view.
A one-to-one relationship usually exists between a screen and a business object. A view references a business object through a formal property of the view. However, a screen does not reference a business object through a formal property. An informal relationship exists between a business object and a screen. Siebel CRM applies desired design principles to establish this informal relationship. Siebel Tools does not formally enforce this relationship. In general, all the views in a screen are informally related to the same business object.
NOTE: Not all business components that a business object references participate in a parent-child relationship. A business object can reference a business component that is not part of the business model.
Multiple business objects can reference a business component or a link. For example, two business components can each possess a one-to-many relationship in one business object, but can also possess a many-to-one relationship or no relationship in another business object. However, in the context of one business object, there is an unambiguous set of relationships between the business components that a business object references.
Each view references a business object. A master-detail view can define only a one-to-many relationship that the business object that the view references supports. To examine an example of this relationship, in the Siebel client, navigate to the Contacts List, drill down on the Last Name field of a contact, and then click the Opportunities tab. The parent Contact form displays above the Opportunities list. This contact to opportunities relationship is a one-to-many relationship that Siebel CRM defines in the Contact business object. To examine this relationship in Siebel Tools, locate the Contact Detail - Opportunities View in the Views list. This view references the Contact business object.
To implement a view that displays a many-to-one relationship between contacts and an opportunity, where many contact child records are related to one parent opportunity, a view references the Opportunity business object. To view this relationship in the Siebel client, navigate to the Opportunities List, drill down on the Opportunity Name field, and then click the Contacts tab.
|Configuring Siebel Business Applications||Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.|