|
Siebel Reports Administration Guide > Master-Detail Reports > Example—Creating a Report with Multiple Hierarchies >
Creating a New Report Object Definition in Siebel Tools
Only Step 1 from Example—Creating a Report with Multiple Hierarchies is described in detail. All the other steps for developing a Master-Detail report are identical to those explained in Creating a New Report Object Definition in Siebel Tools. To create a new report object definition in Siebel Tools by copying
- Open Siebel Tools. Verify that the Account business object has Opportunity, Contact, and Competitor detail business components relative to the Account (master) business component. Also verify under Account business object that a link is defined for the Competitor business component between Opportunity and Competitor business components.
This confirms the hierarchical relationship among the business components under Account business object.
In this example, the Opportunity and Contact business components are at the child level, and the Competitor business component is at the grandchild level relative to Account business object.
- Make sure that all the business components to be used in the master detail report are active in the associated business object.
A master detail report can be created with multiple hierarchy levels with as many business components as the user needs, as long as all of these business components belong in the same business object and are active. Further, each business component below the parent level should have a link defined with a parent level business component.
In this example, make sure that the competitor business component (which will appear at the grandchild level in the report) has a link defined with the Opportunity business component.
- Navigate to the Report object type in the Object Explorer and lock the Report project (choose Tools > Lock Project) before proceeding to the next step. See Project in Step 7 for more information.
- Expand the Report object type to reveal the child Sub Report object type.
- Locate and select the Account Summary object definition in the Reports Object List Editor window.
Notice that this report has seven subreport components, including Opportunity, Contact, and Competitor. Any account report object definition with these latter three subreports would have sufficed. You will copy this report object definition and delete the unwanted subreport components.
- With the Account Summary object definition selected in Reports and choose Edit > Copy Record.
A new report object definition is created with an empty Name property and a set of children and properties otherwise matching the original.
- Change the following property settings in the new report object definition (the other property settings do not need to be changed):
- Name. Multiple Hierarchy Report
This is the name used to refer to the report structure in Siebel Tools, for instance when you add the report to the Reports menu for a view.
- Project. Report
The Report project is standard for Siebel Sales. Report (SSV) is typically used for Siebel Service. Report projects are usually tied to specific Siebel applications.
- Access Base DB Name. mulhier
This specifies that mulhier.rox will be the name of the report executable invoked when this report object definition is invoked from the Reports menu in a view.
- Menu Text - String Override. Multiple Hierarchy Report
This is the 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. mulhier
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.
- Sort Specification. (blank)
By default, do not sort the account records into account name order, which is necessary for the group breaks to work correctly. Alternatively, you could specify a value of Account.
- Navigate to the Sub Report list in the Objects List Editor for the new report object definition.
The same set of children and properties otherwise matching the original Account Summary object definition is also here.
- Delete all the subreport object definitions (using Edit > Delete Record) except Opportunity, Contacts, and Competitor.
Notice that the position field indicated for Opportunity and Contacts is 1 and 2 respectively, while for Competitor it is 1.1. This indicates that Opportunity and Contacts are at hierarchical level 2 and Competitor is at level 3 under Opportunity.
The position is indicated relative to the main business component. Each hierarchy level is separated by a period, and the number indicates the relative position with respect to the associated parent. For example, position 2.3 indicates that the subreport is two levels below the main business component, and that it is a child, 3, of the business component designated with position 2.
- Expand the Sub Report Field object definition for the Opportunity subreport and add the following subreport fields if they are not already present: City, Close Date, Description, Name, Postal Code, Rep%, Revenue, Sales Rep, and Sales Stage.
- Expand the Sub Report Field object definition for the Competitor subreport. Add the subreport fields Threat Value and Vendor if they are not already present.
- Click the parent object definition (Multiple Hierarchy Report in Report) in the Object List Editor window. Choose Tools > Utilities > Generate Actuate Report.
NOTE: 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).
This generates a data supply ROL file, named according to the value in the Template Name property, in the \Siebdev\RPTSRC\ENU\LIB folder (or the equivalent on your system).
If your installation uses a non-English version of Siebel eBusiness Applications, you do not have an \ENU folder. Instead, you have a folder in the appropriate language code for your installation, such as \DEU for Germany.
See Global Deployment Guide for a list of three-letter International Standards Organization (ISO) language extensions.
- Navigate to the View object type in the Object Explorer.
- Locate Account List View and lock (Tools > Lock Project) the project associated with this view.
In this example, the project being locked is Account (SSE).
- In the Object Explorer, expand View and click View Report.
This is the My Accounts view in the Accounts screen. You will add the new report to the Reports menu for this view.
- Add a view report object definition in the Object List Editor. Enter the name Multiple Hierarchy Report (match spelling and spacing exactly) and a sequence number that is greater by 1 than any other sequence number in the list.
The name that you specify identifies the report object definition that defines the report, including the menu text to display and the report executable to invoke. The sequence number specifies the report's position in the menu relative to other reports.
- Choose Tools > Compile Project and recompile the repository. Move the resulting SRF file to the \OBJECTS\ENU directory of your Siebel Dedicated or Mobile Web Client; for example \Siebdev\OBJECTS\ENU\siebel.srf.
If your installation uses a non-English version of Siebel eBusiness Applications, you do not have an \ENU folder. Instead, you have a folder in the appropriate language code for your installation, such as \DEU for Germany.
See Global Deployment Guide for a list of three-letter International Standards Organization (ISO) language extensions.
This last step is necessary for this new report to appear as a selection on the Reports button on the Accounts List view. Repository compilation is not necessary for generating the data supply ROL file.
- From the Account List View, unlock the project (Tools > Unlock Project) associated with this view.
- Unlock the Report project.
|
