How to convert Oracle reports to XML

Publisher Report.
1> During the conversion process, the source reports must eventually be in Oracle
Reports XML format. Oracle Reports XML format is supported in Oracle Reports 9i and
above.
Open the .rdf file and convert it into report xml file
The process of conversion is given with screenshots:a>

b>

c> Source : Browse the .rdf file to be converted. and click on OK.
A file with name <filename>.xml will be created.
2> Move the <filename>.xml file to unix box home directory.
3> Run the following command :
java oracle.apps.xdo.rdfparser.BIPBatchConversion <filename>.xml -source<source
path of report.xml file> -target<path were the code should be generated after
conversion> debug
e.g
java oracle.apps.xdo.rdfparser.BIPBatchConversion <filename>.xml -source
/home/Bomma600 -target /home/Bomma600 debug
Note : You have to check whether BIPBatchConversion.class file is present at
location cd JAVA_TOP/oracle/apps/xdo/rdfparser/ BIPBatchConversion

Output Files
The conversion utility will generate the following output files for each report:

Report definition file that includes the Data Model (for example: pfoa181p.xdo)
(Note: This file is not needed for E-Business Suite users; see the following note
under DataTemplate.)

DataTemplate (for example: pfoa181p_template.xml)

(Note: this is not required for Oracle BI Publisher Enterprise users because the
data template is embedded in pfoa181p.xdo.)

Default PL/SQL package specification (for example: pfoa181pS.pls)

Default PL/SQL package body (for example: pfoa181pB.pls)
RTF Layout Template (for example: pfoa181p.rtf)
Log file (for example: pfoa181p.log)

Most converted reports will run exactly as expected without further modification. More
complex reports may require some additional modification to work as desired. Following
are some common issues with converted reports.

Data Template and PL/SQL Files

Occasionally when converting a more complex Oracle Reports report, the Data Template
or PL/SQL may contain minor errors and require manual correction.
The conversion utility will move all formula columns to the select clause of the SQL
query in the data model. In most cases this will not cause a problem. However, if any of
the arguments to the formula is a summary column, this will not work because the
summary column will not be calculated at the time the query is executed.
To correct this problem you will need to remove this formula from the select clause and
implement the formula as XSL in your layout template. Most of these formulas are used
either for simple addition or summation or currency conversion, formatting, and
rounding.

RTF Layout Template File

The majority of Oracle Reports reports use simple 'if' formatting logic that is
automatically converted to equivalent XSL-FO and inserted into form fields in the RTF
layout template. However, there is no support for PL/SQL in RTF layout templates. The
conversion utility does not convert any PL/SQL format trigger logic present in the report.
Instead the conversion utility writes all the format trigger code to a log file. You will
need to implement any corresponding PL/SQL logic as XSL code.
To aid in this process, the resulting RTF template will contain form fields that hold the
format trigger names that are called; these fields will be highlighted in red. You can then
refer to the log to find the actual PL/SQL code used in the original Oracle Report. You
will need to rewrite these PL/SQL triggers as XSL-FO.