Change exported XML from a report

Question

Hello,
I need to export a XML from a report button with this structure:
<LOTE CONTABLE>
<CONFIG />
<LOTE>LOTE</LOTE>
<LINEAS>
<LINEA>
<FAC_CODI>1</FAC_CODI>
<EFDESC>F/pruebass N 1</EFDESC>
<EFTYPENT>P</EFTYPENT>
<EFCOMPTE>960</EFCOMPTE>
</LINEA>
</LINEAS>
I have a report with all the columns that I need. I have created a Report Queries (from Shared Components) to generate a XML with the same sql as the report but the XML that APEX generates by default has this structure:
<ROWSET>
<ROW>
<FAC_CODI>1</FAC_CODI>
<EFDESC>F/pruebass N 1</EFDESC>
<EFTYPENT>P</EFTYPENT>
<EFCOMPTE>960</EFCOMPTE>
</ROW>
</ROWSET>
How can I change this structure? I want to add a header and replace "rowset" and "row" to "lineas" and "linea". Is it possible?
Thank you very much in advance.
Kind regards,
Amparo

Answer 1

>
The issue is that in the following code, I've replaced this line:
qryCtx := dbms_xmlgen.newContext('select hash_value from hash');
with this line:
qryCtx := dbms_xmlgen.newContext(V_Return);
I did this because the value that I want to be in XML is in the variable V_Return and not in a table. I get a compilation error:
PLS-00382: expression is of wrong typeCompilation failed
Is there a way to use newContext with a variable value rather than a select statement from a table?
>
It seems unlikely. The DBMS_XMLGEN documentation says:
>
The DBMS_XMLGEN package converts the results of a SQL query to a canonical XML format. The package takes an arbitrary SQL query as input, converts it to XML format, and returns the result as a CLOB.
>
http://download.oracle.com/docs/cd/E11882_01/appdev.112/e10577/d_xmlgen.htm#i1012053
If <tt>VReturn</tt> is not a SQL query then you will need to use one of the (many) other ways of generating XML. This question has nothing to do with APEX and would be better addressed to the XML DB.
Additionally, the recommended methods for XML generation, encryption and hashing are heavily version-dependent and you should always quote the relevant DB version/edition information to ensure an appropriate answer. For example, DBMS_OBFUSCATION_TOOLKIT is deprecated as of Oracle 10g and replaced by DBMS_CRYPTO.