In any Oracle Reports-generated XML file, your output mimics the data model; that is, it is structured by groups and columns. Follow the steps below to do any of the following:
Generate an XML output file from your current report.
Preview the contents of an XML file in a Web browser in conjunction with command line invocation.
Change the XML properties that control XML output for the entire report.
Change the XML properties that control XML output for a column or group.
To generate an XML output file from your current report in Reports Builder:
(Optional) In the Object Navigator, select or open the report, then click
in the toolbar to
run the report. Currently, any report style can be generated to XML output,
but with limited support for matrix-style reports.
(Optional) In the Paper Design
view, choose FilePreview
Format
XML to preview
XML data in your default XML viewer (for example, your Web browser).
Tip: An .XML extension is required by XML-supporting
browsers to recognize the format as XML and display it accordingly.
To generate an XML output file from the command line, then preview the contents of the XML file in a Web browser:
On the command line, run your report with the arguments DESFORMAT=XML
,
DESTYPE=FILE
, and DESNAME=filename.XML
.
Open an XML-supporting Web browser.
Choose FileOpen to navigate
to the XML file that you just generated, and display it in the browser window.
To change the XML properties of the entire report:
In the Object Navigator, double-click next to the report
name to display the Property Inspector.
Under XML Settings, set the XML properties as required for this report.
To change the XML properties of a column or group:
In the Data Model view, double-click the column or the title bar of the group to display the Property Inspector.
Under XML Settings, set the XML properties as required.
Reports Builder creates "well-formed" XML output. This means that there is an XML Declaration present in the prolog of the XML document, but not necessarily a DTD (document type definition). If you wish to create "valid" XML, you must add the DTD in the XML Prolog Value property field at the report level.
For a report developed in a release prior to Oracle Reports 10g Release 2 (10.1.2) patch 2, you may encounter the following issue when saving the report in XML format: if the report defines a PL/SQL package, the package specification, and sometimes the body, is not saved in the XML report. To resolve this issue, perform either of the following steps:
If the RDF exists, regenerate the XML output file using Oracle Reports 10g Release 2 (10.1.2) patch 2 or later.
If the RDF does not exist, edit the XML to manually to add type="packageSpec"
and/or type="packageBody"
to the function
element, as shown in the following example:
<programUnits>
<function name="a" type="packageSpec">
<textSource>
<![CDATA[
PACKAGE a IS
function lire return date;
END a;
]]>
</textSource>
</function>
<function name="a" type="packageBody">
<textSource>
<![CDATA[
PACKAGE BODY a IS
function lire return date is
c2 date;
begin
c2 :=sysdate;
return c2;
end;
END;
]]>
</textSource>
</function>
<function name="cf_1formula" returnType="date">
<textSource>
<![CDATA[
function CF_1Formula return Date is
aa date;
begin
--aa :=a.lire;
end;
]]>
</textSource>
</function>
</programUnits>
If your report includes a graph, the graph information will not be saved
in the XML file (XML is text-based output, which means images are not included).
The chapters "Creating Advanced Distributions" and "Customizing
Reports with XML" in the OracleAS Reports Services Publishing Reports
to the Web manual, available on the Oracle
Technology Network Oracle Reports Documentation page (http://www.oracle.com/technology/documentation/reports.html
).
Running and dispatching a report from the user interface
Running a report from the command line
Running a report using a command file
Running a report to a remote Reports Server
Generating HTML or HTMLCSS output
Distributing a report to multiple destinations
Copyright © 1984, 2005, Oracle. All rights reserved.