Siebel Reports Administration Guide > Creating a Simple List Report > Process of Creating a Custom Report With Actuate e.Report Designer Professional >

Creating Object Definitions for a Custom Report

Each report design, whether custom or standard, normally has its own report object definition in Siebel Tools and a corresponding data supply library file. Report (and child) object definitions and exported datastream libraries are explained in Actuate Report Data Definitions.

In this example, you create a report object definition and children from scratch. An alternative approach is discussed in Copying a Report Object Definition.

This task is a step in Process of Creating a Custom Report With Actuate e.Report Designer Professional.

To create object definitions for a custom report

  1. Open Siebel Tools, click the Project object type in the Object Explorer, and then lock the Report object definition in the Projects OBLE.
  2. Navigate to the Report object type in the Object Explorer.

    If necessary, expose the Report object type. From the application-level menu, choose View, Options, click the Object Explorer tab making sure the Report tree has a white checkbox, and then click OK.

  3. From the application-level menu, choose Edit, and then the New Record menu item.

    A new object definition appears in the Reports Object List Editor (OBLE) with the cursor placed in the Name property.

  4. Define properties for the new report object definition by using values from the following table.


    Test Report

    The name used to refer to the report structure in Siebel Tools. For example, when you add the report to the Reports menu for a view.



    The Report project is standard for Siebel Sales. Report (SSV) is typically used for Siebel Service. Report projects are usually tied to specific Siebel Business Applications.

    Access Base DB Name


    Specifies that Testrept.rox will be the name of the report executable invoked when this report object definition is invoked from the Reports menu in a view.

    Capitalization is not required, although this value for standard reports is capitalized.

    Business Component


    The business component specified provides business component records for the main report. Subreports in more advanced reports have their own business components.



    Specifies that the report is an Actuate report.

    Menu Text - String Override

    Test Report

    Specifies text that will appear in the Menu Text property field and in the Reports menu for a view when this report is included in the view through the use of a view report object definition.

    Template Name


    Specifies the name to be used for the generated data supply library file when the Generate Actuate Report option is invoked for this report object definition.

    Capitalization is not required, although the values of this property for standard reports are capitalized.

  5. Expand the Report object type in the Object Explorer, and then click the Report Field child object.
  6. From the application-level menu, choose Edit, and then the New Record menu item.
  7. In the Field property, pick Name in the Field pick applet.

    Fields in the Field pick list are context-sensitive based on the value specified in the Business Component property for the parent report object definition. For this example, fields from the Opportunity business component are displayed. Each Report Field object definition you add as a child of the report defines a field that will be exported in the data supply library.

    NOTE:  A business component must be active before you can query a field in that business component. If the business component is not active, the field will not appear in the Reports Field dialog box.

  8. Repeat Step 7 for the Account, Revenue, and Close Date fields.

    TIP:   You can type directly in the Name property rather than looking it up in the pick applet. Make sure you match the spelling exactly.

  9. In the Reports OBLE, click the Test Report object definition, choose Tools, Utilities, and then the Generate Actuate Report menu item.

    This generates a data supply ROL file in the $\Siebel\RPTSRC\ENU\LIB folder. The ROL file is named according to the value in the Template Name property.

    If you receive the message, '\ActuateX\eRDPro\AFC\afc.rol' file not found, click OK. Search for the file in the Actuate release folder in the Program Files directory, or the equivalent on your system.

    For more information, see Siebel Reports Directory Structure.

  10. Choose the View object type in the Object Explorer.
  11. In the OBLE, query the Name property for Opportunity List View.
  12. From the application-level menu, choose Tools, and then the Lock Project menu item to lock the Oppty (SSE) project.
  13. In the Object Explorer, expand the View object type, and then choose the View Report child object.

    The View Reports OBLE lists the My Opportunities views that are displayed in the Opportunities screen. In this procedure, you add the new report to the Reports menu for this view.

  14. Click the View object type in the Object explorer, and then add an object definition in the Views OBLE using values described in the following table.


    Test Report

    Identifies the report object definition that defines the report, including menu text to display and the report executable to invoke.

    The value you enter must match exactly the spelling and spacing used in the Name property for the report object definition you specified in Step 4. To make sure you assign the correct report, choose Test Report from the Report property picklist.


    [1 + highest value displayed in the Sequence property.]

    Specifies the report's position in the menu relative to other reports.

    Enter a value that is higher than the Sequence value for any other view report currently displayed in the View Reports OBLE.

  15. Compile the objects you just modified in Siebel Tools.
Siebel Reports Administration Guide Copyright © 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices.