© 2009 Oracle Financial Services. All rights reserved.

1
The following is intended to outline our general
product direction. It is intended for information
purposes only, and may not be incorporated into any
contract. It is not a commitment to deliver any
material, code, or functionality, and should not be
relied upon in making purchasing decisions.
The development, release, and timing of any
features or functionality described for Oracle’s
products remains at the sole discretion of Oracle.

© 2009 Oracle Financial Services. All rights reserved. 2

Tips – Creating Reports in BI Publisher
-Shalini Goel

© 2009 Oracle Financial Services. All rights reserved. 3

 Tip # 1 - Cache Properties
 Cache option is available for queries of type SQL, HTTP Dataset,
MDX Query etc.
 It should be used only when there is the requirement of viewing
reports online with different templates or formats(as there is no
such requirement in FCPB so it can be avoided)

 Cache Expiration: Sets the time in minutes up to which dataset

need to be in cache (Default :30)
 Cache Size Limit: No of datasets to be maintained in the cache.
Default is 1000
 Maximum cached reports: Maximum no. of reports maintained
in the cache. Default is 50.

General Properties
 Debug level
 Report Viewer Height (Default 600 pixels)
 Report Scalable Threshold (Default is 10000000 or10 megabytes) - use
only if doing caching(can enter in kilobytes)

© 2009 Oracle Financial Services. All rights reserved. 4

 Tip # 1 - Cache Properties..Contd..
All the properties mentioned in previous slide can be changed using
link in BI Publisher UI.

© 2009 Oracle Financial Services. All rights reserved. 5

 Tip # 2 –RTF Templates
Use Form Fields.

Form Fields are also supported by Template Builder ‘Field Browser’

© 2009 Oracle Financial Services. All rights reserved. 6

 Tip # 2 –RTF Templates ..Contd..

• Don't overcomplicate you template.

• The template is easier to understand, debug and maintain

• In general it is better to have different business documents in

different templates

• Try to limit the logic in templates to simple if or loop

statements (It is advisable to avoid their usage in templates.)

• Use sub templates to simplify documents if necessary(e.g.

Reuse common layouts as in the form of Header.rtf or
Footer.rtf)

• Some calculations are easier performed in the data template

© 2009 Oracle Financial Services. All rights reserved. 7

 Tip # 2 –RTF Templates..Contd..

If you don't want the "Data to be resorted", mark checkbox

"Data already sorted" while using grouping. It will not resort
the data while grouping.

It is advisable to sort the data in the query itself.

© 2009 Oracle Financial Services. All rights reserved. 8

 Tip # 3 –DataTemplate
• Use short element names to reduce XML file size containing Data.
e.g. use SHIP_ADDR instead of SHIPPING_ADDRESS.

• Avoid re-using the same name for element names e.g CITY under
element SHIPPING_ADDRESS and BILLING_ADDRESS can
cause ambiguity and may lead to wrong output.

• If you know it is going to be a large dataset then set scalable

mode= on in data template properties. It is advisable to use it for
all dataTemplate based reports.

• Avoid generating empty tags in the XML. Missing fields do not

cause any problem but summation over fields that contain empty
tags [e.g. sum(<null>) ] will result in a “not a number” exception.
Also such fields unnecessarily increase the size of XML. Property
can be set in dataTemplate.

© 2009 Oracle Financial Services. All rights reserved. 9

 Tip # 3 –DataTemplate..Contd..

Always enclose the query in <![CDATA]]> section when you are

using relational operators.

Correct Wrong
Text inside <![CDATA]]> section is ignored by XML parser.

© 2009 Oracle Financial Services. All rights reserved. 10

 Thank You

© 2009 Oracle Financial Services. All rights reserved. 11

© 2009 Oracle Financial Services. All rights reserved. 12