Publishing Reports to the Web - Downloads - Oracle

Creating XML Customizations
2. Store the XML customization in a location that is accessible to OracleAS Reports
Services.
3. Apply the XML customization to another report with the CUSTOMIZE command
line keyword or the SRW.APPLY_DEFINITION built-in procedure, or run the XML
customization by itself (if it contains a complete report definition) with the
REPORT (or MODULE) command line keyword.
16.2 Creating XML Customizations
This section provides examples of various report customizations. It includes examples
of:
■ Required XML Tags
■ Changing Styles
■ Changing a Format Mask
■ Adding Formatting Exceptions
■ Adding Program Units and Hyperlinks
■ Adding a New Query and Using the Result in a New Header Section
■ Encoding the URL
16.2.1 Required XML Tags
See Also: Command Line Options
For information on using the command line keywords.
Every XML customization must contain the following required tag pair:
For example, the following is the most minimal XML customization possible:
This XML customization would have a null effect if applied to a report because it
contains nothing. It can be parsed because it has the needed tags, but it is useful only
as an example of the required tags.
The tag indicates the beginning of the report customization, its name, and
the version of the Data Type Dictionary (DTD) file that is being used with this XML
customization. The tag indicates the end of the report customization.
The report tag's name attribute can be any name you wish, either the name of the
report the XML file will customize, or any other name.
This example represents a minimal use of the tag. The tag also
has many attributes, most of which are implied and need not be specified. The only
required attribute is DTDVersion.
A full report definition requires both a data model and a layout and therefore also
requires the following tags and their contents:
■
■
Customizing Reports with XML 16-3