Table 8 provides details of the Oracle BI Publisher syntax and description for the fields defined in the example template.
Table 8. Oracle BI Publisher Syntax and Field Definitions for the Service Request Activity (All) Report Template
Syntax Oracle BI Publisher Code Description
If <?if://ssServiceRequest?> An IF condition that checks for service request records. If there are no service request records, no records are displayed.
for-eachgroup: ssServiceRequest
<?for-each-
group:ssServiceRequest; position()?>
The start of a group section which iterates for each record in the Service Request data set. ssSrNumber ssAccount ssStatus <?ssSrNumber?> <?ssAccount?> <?ssStatus? Field mappings
If <?if://ssCreated?> If condition that does not display the ssCreated field if null.
ssCreated <?format- date:psfn:totext(ssCreated, "yyyy-MM-dd'T'HH:mm:ss", "MM/dd/yyyy hh:mm:ss"); 'SHORT_TIME'?> Field formatting
End <?end if?> End of if condition
ssSeverity ssDescription
<?ssSeverity?> <?ssDescription?>
Field mappings
If <?if://ssClosedDate?> If condition that does not display the ssClosedDate field if null.
ssClosedDate <?format- date:psfn:totext(ssClosedDa te,"yyyy-MM-dd'T'HH:mm:ss", "MM/dd/yyyy hh:mm:ss"); 'SHORT_TIME'?> Field formatting
End <?end if?> End of if condition
ssPriority ssCustomerRefNumber ssOwner <?ssPriority?> <?ssCustomerRefNumber?> <?ssOwner?> Field mappings for-each:current-group() <?for-each:current- group()?>
Start of a group section, iterating for each record in the current group (for example, Service Request).
You can view additional information about the integration object definition (and related integration components) in Siebel Tools. For information about viewing integration object definitions in Siebel Tools, see Using Siebel Tools.
If <?if:current-group()//
ssAction?>
Condition to check for Action records. If there are no records, do not display the section.
for-each:ssAction <?for-each:ssAction?> Beginning of the repeating element group for Action.
If <?if://ssCreated?> If condition that does not display the ssCreated field if null.
ssCreated <?format- date:psfn:totext(ssCreated, "yyyy-MM-dd'T'HH:mm:ss", "MM/dd/yyyy hh:mm:ss"); 'SHORT_TIME'?> Field formatting
End <?end if?> End of if condition
ssCreatedByN ssOwnedBy sssStatussType ssDescription <?ssCreatedByName?> <?ssOwnedBy?> <?ssType?> <?ssStatus?> <?ssDescription?> Field mappings
end for-each:ssAction <?end for-each?> End of the repeating element group for Action.
End if <?end if?> The end of the if condition
end for-each <?end for-each?> End of current-group() repeating group section.
page break <?split-by-page-break:?> Page break after the end of the group section.
end for-each-group: ssServiceRequest
<?end for-each-group?> End of Service Request group section
End <?end if?> End if statement for conditional
check on Service Request records
If <?if:not(//
ssServiceRequest)?>
If condition that prints "No Data Found" at the bottom of the report if there are no records.
End <?end if?> End if statement for above
condition.
Table 8. Oracle BI Publisher Syntax and Field Definitions for the Service Request Activity (All) Report Template
For more information about Oracle BI Publisher syntax, see Oracle Business Intelligence Publisher Report Designer's Guide, Release 10.1.3.4 available on Oracle Technology Network (OTN). For more information about creating master-detail templates, see “Example of Comparing the Service Request Activity (All) Report with its Corresponding Layout Template” on page 132 and “Creating a Master-Detail Layout Template in Microsoft Word” on page 136.
Creating a Master-Detail Layout
Template in Microsoft Word
Creating a master-detail report follows the same process as creating a simple report. However, consider the following important points when creating master-detail reports:
■ Make sure that all child integration components in the integration object have the appropriate value in the Parent Integration Component property.
■ In the RTF template, make sure that the correct for-each-group and for-each:current-group elements are placed in the template, see “Example of Comparing the Service Request Activity (All) Report with its Corresponding Layout Template” on page 132.
■ When creating custom integration objects for Siebel Reports, make sure that the fields used for dynamic queries in the applet of the master component are also contained in the integration component. Dynamic queries are specific, customized queries that you create.
To create a master-detail layout template in Microsoft Word 1 Open Microsoft Word, and create a new document.
2 Using the Oracle BI Publisher Desktop menu, select Data, and then Load XML Data. 3 Select the XML file containing the sample data, and then save the template in RTF format. 4 Add the relevant titles, formatting, page header and footer, and so on to the document. 5 Add the Master data section by doing the following:
a Insert a master data section manually, or by using the Insert menu option from the Oracle BI Publisher Desktop menu.
b Select the master data section, and add a for-each-group section: ❏ Click Insert, Repeating Group, and then the Advanced tab.
NOTE: This process embeds the for loop within the table and does not replicate the location of the controls in the preconfigured examples.
❏ Change the expression:
<?for-each-group:ssServiceRequest;position()?>
c (Optional) If you want to view descriptive text for the inserted sections, click Tools, Options, Build, and then Descriptive.
b From the Oracle BI Publisher menu, click Insert, and then Repeating Group. c Select the defaults, and then click OK.
7 Insert a page break after the final detail section by doing the following: a Select the Oracle BI Publisher properties of the entire group.
b Navigate to Create, Group, and then Properties. c Select a page break option.
8 Add the additional formatting features and conditions.
For more information on adding features, see “Example of Comparing the Service Request Activity (All) Report with its Corresponding Layout Template” on page 132.
9 After testing the report, register the report layout template in the usual manner.
For information about registering report layout templates, see “Registering Report Layout Templates” on page 114.