Siebel Reports Administration Guide > Using Master-Detail Reports > Process of Creating a Report With a Parent-Child Relationship >

Creating Object Definitions For a Parent-Child Report

This task is a step in Process of Creating a Report With a Parent-Child Relationship.

Each report design normally has its own report object definition in Siebel Tools and a corresponding data supply library file. In Using Reports with Group Sections the report object definition is copied from an existing object definition, and then minor changes are made to the definition. In this example the same technique is employed with additional modifications.

To create object definitions for a parent-child report

  1. If the Siebel client is open, log out of it now, and then open Siebel Tools.
  2. Verify the Account business object contains the appropriate child business object components to implement this example:
    1. Click Business Object in the Object Explorer, and then query the Name property in the Business Objects OBLE for Account.
    2. In the Object Explorer, expand the Business Object type, and then click Business Object Component.
    3. Make sure the Bus Comp property of the Business Object Components OBLE contains child definitions for the Contact and Opportunity business components.

      Although this step is not essential for this example, you want to perform it as practice for cases where you are using less common business component relationships. For more information, see About the Business Object and Business Component Relationship.

  3. Complete the procedure described in Creating Object Definitions for a Group Report with the following modifications:
    • Copy the object definitions for the Account Summary report rather than the Opportunity List - Current Query report.
    • In the Reports OBLE, change properties in the new report object definition as described in the following table.


      Account - Opty/Contact Detail

      Access Base DB Name


      Menu Text - String Override

      Account - Opportunity/Contact Detail

      Template Name


      Sort Specification

      (Leave this property empty.)

    • Perform the following before running the Generate Actuate Report utility:
      • In the Subreports OBLE, delete the subreport object definitions except those that have Contact or Opportunity in the Business Component property. To delete a subreport, click the Subreport object definition, choose Edit, and then the Delete Record menu item.

        For this example, a report that contains Contact and Opportunity subreports is sufficient.
      • Expand the Sub Report Field object type for the Opportunity subreport, and then add the City, Description, and Postal Code subreport fields.
    • Run the Generate Actuate Report utility on the parent Account - Opty/Contact Detail report.
    • Navigate to the Account List View rather than the Opportunity List View.
    • When adding the new view, pick Account - Opty/Contact Detail in the Report property.
    • After compiling your changes, unlock the Account (SSE) and the Report projects.

About the Business Object and Business Component Relationship

The parent-child relationships specified by the business object components and links in the business object are necessary for a parent-child datastream relationship to work correctly.

Since the hierarchy of reports and subreports must be in accordance with the business object and its business components and links, it is recommended that you examine object definitions in Siebel Tools to verify these relationships when building a report that includes a datastream that has a parent-child relationship.

It is recommended that you use only the driving business component in a view as the main datastream in the report.

Siebel Reports Administration Guide Copyright © 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices.