Namespaces when Composing XML from Reational Tables

Hi,
I am trying to create XML documents from Oracle tables that look like this (this is a very abbreviated version):
<?xml version="1.0" encoding="UTF-8" ?>
<Document xmlns="urn:iso:std:etc:etc" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:iso:std:etc:etc.03 ZZZZZ6A.xsd">
<Cstmr>
<GrpHdr>
<MsgId>1006</MsgId>
<CreDtTm>2011-07-12T11:49:07.0Z</CreDtTm>
<NbOfTxs>4624</NbOfTxs>
<CtrlSum>1133772055</CtrlSum>
</GrpHdr>
</Cstmr>
</Document>
I have a SELECT statement that works successfully as follows:
SELECT XMLElement(NOENTITYESCAPING "Document"
,XMLAttributes('urn:iso:std:iso:etc:etc' AS "xmlns"
,'http://www.w3.org/2001/XMLSchema-instance' AS "xmlns:xsi"
,'urn:iso:std:iso:etc:etc.03 ZZZZZ6A.xsd' AS "xsi:schemaLocation"
,XMLElement(NOENTITYESCAPING "Cstmr"
,XMLElement(NOENTITYESCAPING "GrpHdr"
,XMLForest(spi1.msg_id AS "MsgId"
,TO_CHAR(SYSDATE,'YYYY-MM-DD') || 'T' || TO_CHAR(SYSDATE,'HH24:MI:SS') || '.0Z'
AS "CreDtTm"
,COUNT(*) AS "NbOfTxs"
,SUM(spi1.payment_pence_amt) / 100
AS "CtrlSum"
) AS xml_doc
FROM t_std18_payment_item_test spi1
GROUP BY spi1.msg_id;
This succesffully produces the desired output:
XML_DOC
<Document xmlns="urn:iso:std:iso:etc:etc" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:
schemaLocation="urn:iso:std:iso:etc:etc.03 ZZZZZ6A.xsd"><Cstmr><GrpHdr><MsgId>1006</MsgId><CreDtTm>2
011-07-12T13:20:19.0Z</CreDtTm><NbOfTxs>4624</NbOfTxs><CtrlSum>1133772055</CtrlSum></GrpHdr></Cstmr>
</Document>
I can then successfully create a VIEW for this:
CREATE OR REPLACE VIEW payment_xml of XMLType
WITH OBJECT ID (XMLCast(XMLQuery('/Document/CstmrCdtTrfInitn' Passing OBJECT_VALUE RETURNING CONTENT) AS BINARY_DOUBLE))
AS
SELECT XMLElement(NOENTITYESCAPING "Document"
,XMLAttributes('urn:iso:std:iso:etc:etc' AS "xmlns"
,'http://www.w3.org/2001/XMLSchema-instance' AS "xmlns:xsi"
,'urn:iso:std:iso:etc:etc.03 ZZZZZ6A.xsd' AS "xsi:schemaLocation"
,XMLElement(NOENTITYESCAPING "Cstmr"
,XMLElement(NOENTITYESCAPING "GrpHdr"
,XMLForest(spi1.msg_id AS "MsgId"
,TO_CHAR(SYSDATE,'YYYY-MM-DD') || 'T' || TO_CHAR(SYSDATE,'HH24:MI:SS') || '.0Z'
AS "CreDtTm"
,COUNT(*) AS "NbOfTxs"
,SUM(spi1.payment_pence_amt) / 100
AS "CtrlSum"
FROM t_std18_payment_item_test spi1
GROUP BY spi1.msg_id;
But when I select from it using:
SELECT XMLSerialize(Content OBJECT_VALUE AS CLOB indent) AS "Payments"
FROM payment_xml;
I get this:
FROM payment_xml
ERROR at line 2:
ORA-19276: XPST0005 - XPath step specifies an invalid element/attribute name: (Document)
I guess this is to do with my namespace declarations as I can successfully select from the view without the <Document> tag. However, I cannot fathom out quite what I have done wrong or how to fix it.
Any help gratefully received.
Thanks you,
Graham

That said, have you already looked into the FAQ on this forum. You could have found stuff like
SQL> begin
2    dbms_xmlschema.registerSchema
3    (
4      :schemaURL,
5      xdbURIType(:schemaPath).getClob(),
6      TRUE,TRUE,FALSE,FALSE
7    );
8 end;
9 /
PL/SQL procedure successfully completed.
SQL> create or replace view PURCHASEORDER_XML
2 of xmltype
3 xmlSCHEMA "http://xfiles:8080/home/SCOTT/poSource/xsd/purchaseOrder.xsd" Element "PurchaseOrder"
4 with object id
5 (
6    substr(extractValue(object_value,'/PurchaseOrder/Reference'),1,32)
7 )
8 as
9    select xmlElement
10           (
11             "PurchaseOrder",
12             xmlAttributes
13             (
14               'http://xfiles:8080/home/SCOTT/poSource/xsd/purchaseOrder.xsd' as "xsi:noNamespaceSchemaLocation",
15               'http://www.w3.org/2001/XMLSchema-instance' as "xmlns:xsi"
16             ),
17             xmlElement("Reference",p.REFERENCE),
18             xmlElement
19             (
20               "Actions",
21               ( select xmlAgg
22                        (
23                          xmlElement
24                          (
25                            "Action",
26                            xmlElement("User",ACTIONEDBY),
27                            case
28                              when DATEACTIONED is not null
29                              then xmlElement("Date",DATEACTIONED)
30                            end
31                          )
32                        )
33                   from PURCHASEORDER_ACTION a
34                  where a.REFERENCE = p.REFERENCE
35               )
36             ),
37             xmlElement
38             (
39               "Reject",
40                  xmlForest
41                  (
42                    REJECTEDBY as "User",
43                 DATEREJECTED as "Date",
44                    COMMENTS as "Comments"
45                  )
46             ),
47             xmlElement("Requestor",REQUESTER),
48             xmlElement("User",USERID),
49             xmlElement("CostCenter",COSTCENTER),
50             xmlElement
51             (
52               "ShippingInstructions",
53               xmlElement("name",SHIPTONAME),
54               xmlElement("address",ADDRESS),
55               xmlElement("telephone",PHONE)
56             ),
57             xmlElement("SpecialInstructions",SPECIALINSTRUCTIONS),
58             xmlElement
59             (
60               "LineItems",
61               ( select xmlAgg
62                        (
63                          xmlElement
64                          (
65                            "LineItem",
66                            xmlAttributes(LINENO as "ItemNumber"),
67                            xmlElement("Description",DESCRIPTION),
68                            xmlElement
69                            (
70                              "Part",
71                              xmlAttributes
72                              (
73                                UPC       as "Id",
74                                QUANTITY as "Quantity",
75                                UNITPRICE as "UnitPrice"
76                              )
77                            )
78                          )
79                        )
80                    from PURCHASEORDER_LINEITEM l
81                   where l.REFERENCE = p.REFERENCE
82               )
83             )
84           )
85      from PURCHASEORDER_TABLE p, PURCHASEORDER_REJECTION r, PURCHASEORDER_SHIPPING s
86     where r.REFERENCE = p.REFERENCE
87       and s.REFERENCE = p.REFERENCE
88 /
View created.
and how to do this based on relational content...

Similar Messages

Generating xml from diff tables in a db

hi,
i need to write a oracle procedure, which when called generates xml doc (building xml from different tables in database.). i got the DTDs . but i still dont understand how can the data be pulled from diff tables and put in the one xml? can anyone give me rough idea.. i know that i have to use xmlquery and xml_save packages... but still not much clear..
i m working on oracle 8i database. any help is appreciated.. thanks.

Any feedback to the above questions would be greatly appreciated!

Suppress default namespace when extracting XML

How can I avoid that Oracle includes the target namespace of my schema as the default namespace when using the EXTRACT function?
E.g., select xmlelement("XmlData",
xmlagg(extract(tx.transmission, '/Transmission/Item')))
from transmissions tx
returns something like
<XmlData>
<Item xmlns="http://myschematargetnamespace" N="1">abcdef</Item>
<Item xmlns="http://myschematargetnamespace" N="2">abcdef</Item>
</XmlData>
Any ideas will be appreciated very much!
P.S. Can anybody tell me how I configure sqlplus to display the complete XML instead of only two lines?

Well not sure about your XML issue yet but as for SQLplus, you need to set certain session parameters.
type
SQL> show all
for a list of possible options but for your case I think something like
SQL> set long 10000
will help (this means limit to 10000 chars).
'set linesize' and 'set pagesize' could help too, eg:
SQL> set linesize 500 (if your terminal will accept 500 cols)
SQL> set pagesize 90
etc...
Voila.
Sam.

Remove spaces when generating xml from data mapped on object types

My problem is kind of complex so I'll try to reduce it to a more manageable example:
drop type msm force;
drop type list_msm force;
create type msm as object(
     nume char(20)
create type list_msm as table of msm;
select xmlserialize (document xmlelement("values",
     cast(multiset(
          select trim(p.den) from produse p) as list_msm
     ) as clob indent size=2
     ) as "xml"
     from dual;
This is where it gets tricky.
p.den is a field that contains spaces. I use trim(p.den) to remove them but because I cast this to list_msm, the values are then again mapped into msm objects, which have the "nume" field of char(20). So.. when generating the XML, the output still contains spaces.
This is an excerpt of the result:
<values>
<LIST_MSM>
<MSM>
<NUME>Prod.1 </NUME>
</MSM>
<MSM>
<NUME>Prod.2 </NUME>
</MSM>
<MSM>
<NUME>Prod.3 </NUME>
</MSM>
<Later.. I see that the forum removes the extra spaces but I ensure you that after eg. "Prod.1" there are a lot of spaces, as the original field from the "produse" table is defined as char(20))
So.. Is there a way to generate the XML without those extra spaces? Basically, I want to be able to trim them before I send them to the xml serializer, but the problem is that i have no control over the whole casting thing ( oracle magic happening that automatically creates all the xmlelements needed, etc.)
Somehow, when the xml engine steps over the collection and accesses the fields, somehow, i need a trim there. Maybe some kind of accesor for the fields in the type can be declared so that the xml engine uses it instead of the field itself directly. The accesor would then return trim(field). Sorry for this mumbo jumbo gibberish but I want to be as clear as possible.
Edited by: user9229988 on May 10, 2012 9:24 AM
Edited by: user9229988 on May 10, 2012 9:25 AM
Edited by: user9229988 on May 10, 2012 9:38 AM

Hi.
Check this:
drop type msm force;
drop type list_msm force;
create type msm as object(
nume VARchar2(20)     --VARCHAR2 NOT CHAR
create type list_msm as table of msm;
create table produse
den char(20)
INSERT INTO produse VALUES('Prod.1');
INSERT INTO produse VALUES('Prod.2');
INSERT INTO produse VALUES('Prod.3');
COMMIT;
select xmlserialize (document xmlelement("values",
cast(multiset(
select trim(p.den) from produse p) as list_msm
) as clob indent size=2
) as "xml"
from dual;
<values>
<LIST_MSM>
    <MSM>
      <NUME>Prod.1</NUME>
    </MSM>
    <MSM>
      <NUME>Prod.2</NUME>
    </MSM>
    <MSM>
      <NUME>Prod.3</NUME>
    </MSM>
</LIST_MSM>
</values>Hope this helps.

Images not displaying when selecting it from real table

Case is, I have some HTML in a table, help texts for that matter. It has some images in it defined like that:
... <img src="&COMPANY_IMAGES.picture.gif"> ...
But the &COMPANY_IMAGES. substitution does not take place. When testing, I found out that
select '&COMPANY_IMAGES.<br><br>#COMPANY_IMAGES#' as working
, col as not_working
from TEST_TABLE where ID = 1
working column had both strings replaced, while not_working had not. Now the question is, whether this is an intended behaviour or not? I got my report working with the workaround of
select replace(col, '&'||'COMPANY_IMAGES.', :COMPANY_IMAGES) as col
from TEST_TABLE where ID=1
but I would like to know the exact limitations to know while planning ahead not discover afterwards... Or is there a better way to get them substituted from db columns (without the replace)?

Kaja,
Looks like intended behavior to me. There is no reason for the engine to do substitutions on data you select from a table. Your method should be fine.
Scott

Maximum Open cursor Exceeded error when deleting records from a table

I have a strange problem.
I have a table EMP_MASTER . Whenever I am trying to delete a record from this table, I am getting Maximum no. of open cursor exceeded error. But this error doesnot come when i delete from any other tables. And no. of open cursor is much lesser than OPEN_CURSOR parameter.
All other tables (around 700) has foreign key constraint to this EMP_MASTER table for created_user paramater.
Is it some thing like, when I am trying to delete a record from EMP_master, implicit cursor opens up and checks all referenced tables. and that limit gets exceeded ?
Please help.
Thanks,
Raj

Raji03 wrote:
There is no trigger defined for this table.
Is there a limit on which no.of references made to a column ? Because one column in this field, Emp no is being referenced in almost every other table. around 700 tables. Will it have any adverse effect ?That should have nothing to do with your problem directly. Again, those tables could have triggers defined on them and you are leaking cursors in one of those triggers (wild guess).
An example of a table with many many others foreign key'd to it.
create table parent_of_everything
   column1 number primary key
insert into parent_of_everything select level from dual connect by level <= 1000;
commit;
--create 1000 tables all with foreign keys to the parent_of_everything
begin
   for i in 1 .. 1000
   loop
      execute immediate 'create table child_' || i || ' (column1 number, column2 number, constraint child_' || i || '_fk foreign key (column1) references parent_of_everything (column1) on delete cascade)';
      execute immediate 'insert into child_' || i || ' select level, mod(level, ' || i || ') from dual connect by level <= 1000';
      commit;
   end loop;
end;
TUBBY_TUBBZ?delete parent_of_everything;
1000 rows deleted.
Elapsed: 00:02:53.03No problems were had (none were expected).
Cleanup script.
--remove the 1000 child tables
begin
   for i in 1 .. 1000
   loop
      begin
         execute immediate 'drop table child_' || i || ' purge';
      exception when others
         then
            null;
      end;
   end loop;
end;
/

XDK Export in XML from multiple tables

Hello everybody,
I have to export data from an Oracle database to a XML file and then generate the Java classes.
1)
I used XSU successfully with one table. My problem is to retrieve data not from a unique table but from multiple tables linked by relations.
I wanted to do this using XSU to retrieve data from the database and create the corresponding XML schema.
That seems to be possible but I need help for database relations.
Can someone help me to explain if it is possible to export from multiple tables (and if yes how)?
2)
Having my XML schema then I will have to generate Java objects. How is it possible with the XML Class Generator for Java?
Does anybody have experience and samples?
Many Thanks in advance!

Hi Elodie,
Please refer the Product Order sample on OTN that describes the usage of XML Class Generator for Java.
The URL for it is:
http://otn.oracle.com/tech/xml/xdk_sample/ProductOrdersSample.html
Hope it helps
Shefali

Generate xml from a table and insert the xml into another table

I want to generate an xml file from a table and insert it into another table all in one tsql
insert into table B(xmlfile)
select * from tableA
FOR
XML
PATH('ac'),TYPE,ELEMENTS
XSINIL,ROOT('Accum')
Is not working any help

I have solved my issue all I did was to change my column datatype to xml

Generate XML from Oracle Table Data

Hi All,
I am new to this network. I am also new to oracle XML package. I want a help for the below query.
CREATE TABLE EMP(ID NUMBER PRIMARY KEY, NAME VARCHAR2(10), PHONE NUMBER);
INSERT INTO EMP(ID,NAME,PHONE) VALUES (11,'Joy',1234);
INSERT INTO EMP(ID,NAME,PHONE) VALUES (22,'Mike',5678);
INSERT INTO EMP(ID,NAME,PHONE) VALUES (33,'Jason',NULL);
COMMIT;
I want to export the EMP table data in a XML file with the below format.
Required Output:
<?xml version="1.0" encoding="UTF-8"?><STATICDATA><EMP><ID>11</ID><NAME>Joy</NAME></EMP></STATICDATA>
<?xml version="1.0" encoding="UTF-8"?><STATICDATA><EMP><ID>22</ID><NAME>Mike</NAME></EMP></STATICDATA>
<?xml version="1.0" encoding="UTF-8"?><STATICDATA><EMP><ID>33</ID><NAME>Jason</NAME></EMP></STATICDATA>
I have used some XML functions and have written the below query.
select XMLROOT(XMLELEMENT(staticdata,XMLELEMENT(EMP,XMLELEMENT(ID,ID),XMLELEMENT(NAME,NAME))), version '1.0" encoding="UTF-8') xml FROM EMP;
output of my query:
<?xml version="1.0" encoding="UTF-8"?>
<STATICDATA>
<EMP>
<ID>11</ID>
<NAME>Joy</NAME>
</EMP>
</STATICDATA>
<?xml version="1.0" encoding="UTF-8"?>
<STATICDATA>
<EMP>
<ID>22</ID>
<NAME>Mike</NAME>
</EMP>
</STATICDATA>
<?xml version="1.0" encoding="UTF-8"?>
<STATICDATA>
<EMP>
<ID>33</ID>
<NAME>Jason</NAME>
</EMP>
</STATICDATA>
But i want the out as the required output above. every record in a single line. can any one help me in achieving the required output. also can i export all the columns of the table by some thing like select * from the table in XML file ?
Thanks,
Sartaj

user13683418 wrote:
Hi All,
I am new to this network. I am also new to oracle XML package. I want a help for the below query.
CREATE TABLE EMP(ID NUMBER PRIMARY KEY, NAME VARCHAR2(10), PHONE NUMBER);
INSERT INTO EMP(ID,NAME,PHONE) VALUES (11,'Joy',1234);
INSERT INTO EMP(ID,NAME,PHONE) VALUES (22,'Mike',5678);
INSERT INTO EMP(ID,NAME,PHONE) VALUES (33,'Jason',NULL);
COMMIT;
I want to export the EMP table data in a XML file with the below format.
Required Output:
<?xml version="1.0" encoding="UTF-8"?><STATICDATA><EMP><ID>11</ID><NAME>Joy</NAME></EMP></STATICDATA>
<?xml version="1.0" encoding="UTF-8"?><STATICDATA><EMP><ID>22</ID><NAME>Mike</NAME></EMP></STATICDATA>
<?xml version="1.0" encoding="UTF-8"?><STATICDATA><EMP><ID>33</ID><NAME>Jason</NAME></EMP></STATICDATA>
I have used some XML functions and have written the below query.
select XMLROOT(XMLELEMENT(staticdata,XMLELEMENT(EMP,XMLELEMENT(ID,ID),XMLELEMENT(NAME,NAME))), version '1.0" encoding="UTF-8') xml FROM EMP;
output of my query:
<?xml version="1.0" encoding="UTF-8"?>
<STATICDATA>
<EMP>
<ID>11</ID>
<NAME>Joy</NAME>
</EMP>
</STATICDATA>
<?xml version="1.0" encoding="UTF-8"?>
<STATICDATA>
<EMP>
<ID>22</ID>
<NAME>Mike</NAME>
</EMP>
</STATICDATA>
<?xml version="1.0" encoding="UTF-8"?>
<STATICDATA>
<EMP>
<ID>33</ID>
<NAME>Jason</NAME>
</EMP>
</STATICDATA>
But i want the out as the required output above. every record in a single line.Why?
Some things output XML all as one stream, some things naturally display it structured. It doesn't matter as the XML is still the same because by it's very nature it is a structured data definition. Anything that reads XML will be able to read it whether it's on one line (streamed) or structured.
also can i export all the columns of the table by some thing like select * from the table in XML file ?A couple of ways of exporting XML to a file...
-- DBMS_XSLPROCESSOR.clob2file
-- outputs a clob to a file
DECLARE
   ctx   DBMS_XMLGEN.ctxtype;
BEGIN
   ctx := DBMS_XMLGEN.newcontext ('select * from emp');
   DBMS_XSLPROCESSOR.clob2file (DBMS_XMLGEN.getxml (ctx), 'TEMP', 'emp.xml');
   DBMS_XMLGEN.closecontext (ctx);
END;
PL/SQL procedure successfully completed.or
..snip..
v_xml                 XMLTYPE;
v_doc                 XMLDOM.DOMDocument;
v_dir                 VARCHAR2(2000);
v_file                VARCHAR2(2000);
BEGIN
v_xml := ... populate with XML ...;
v_dir := 'TEST_DIR'; -- directory object name (in UPPER CASE)
v_file := 'myfile.xml';
v_doc := DBMS_XMLDOM.NEWDOMDOCUMENT(v_xml);
DBMS_XMLDOM.WRITETOFILE(v_doc, v_dir||'\'||v_file, 'UTF-8');
DBMS_XMLDOM.FREEDOCUMENT(v_doc);
..snip..

How to add doctype when generating XML from an arbitrary data structure

I was reading SUN's tutorial "Working with XML - PART IV: Using XSLT". Inside this tutorial, in 3, it talks about how to generate XML from an arbitrary data structure making use of a XMLReader and a Transformer. The example only shows adding elements. Is there a way to add DTD information in the XML generated, i.e. <!DOCTYPE ... >? What APIs can I use?
Thanks,
Alex

The simplest way seems to me is to use a XSL file for that. The <xsl:output> attributes doctype-system and doctype-public generate the DTD declaration <!DOCTYPE YOUR_ROOT SYSTEM "yourDTDfile.dtd"> and <!DOCTYPE YOUR_ROOT PUBLIC "yourDTDfile.dtd">, respectively.
When calling transformerInstance.transform() the XSLT processor performs the identity transformation - it just copies elements, attributes, content, processing instructions and comments to the result stream.
If you're using an xsl file for your transformation already, simply add <xsl:output doctype-system="yourDTDfile.dtd"/> to your existing XSL file.
If you're only using the identity transformation you'd need to change the line of code where you obtain the transformer instance from the TransformerFactory to:
t_factory.newTransformer(new StreamSource("test.xsl"));
and use this as test.xsl:
<?xml version="1.0"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
   <xsl:output doctype-system="yourDTDfile.dtd"/>
   
   <xsl:template match="*|@*|comment()|processing-instruction()|text()">
      <xsl:copy>
         <xsl:apply-templates select="*|@*|comment()|processing-instruction()|text()"/>
      </xsl:copy>
   </xsl:template>
</xsl:stylesheet>Good luck.

Creating XML from Oracle Tables

Would it be possible to post me a snapshot of the ODI Flow diagram for an Oracle to XML conversion? Does the staging area have to be on the Target (XML)? What KMs & CM should be used? Can the XML be written straight back to an .xml file? What should the XML Schema look like?
These are the KMs I use: LKM-SQL to SQL; IKM-SQL Incremental Update; CKM-SQL.
My flow is straight from source (oracle) to target (xml), with staging area on target (doesn't feel right).
My Oracle Dataserver & Schema work fine. Not sure about the XML dataserver setup though - I think this is where the problem lies. These are my JDBC settings:
- com.sunopsis.jdbc.driver.xml.SnpsXmlDriver
- jdbc:snps:xml?f=E:\Oracle ODI\Member.xsd
I am evaluating ODI for a client and I wanted to throw together a quick demo showing how easily ODI can generate XML from any source. I know this is the case as I understand the concept of ODI's components - just haven't had time to read manuals thoroughly.
Many thanks for your help,
Steve

Hello,
1. Try to test the connection to the XML dataserver.
2. Create a model and reverse-engineer this dataserver. You'll see what the XML structure is mapped to immediately.
3. Integrate data to this model (using standard KM targeting "SQL").
You can put the staging area on the Oracle source or in the XML driver if you want. Both solutions will work.
just haven't had time to read manuals thoroughly.I think you should quickly read the "Sunopsis ODI with... XML" section in the manual.
It is not very long and very helpful. Have also a quick look at the XML driver documentation.
Regards,
-FX

How to create XML from relational tables based on an XML Schema ?

There is no automated way in Oracle XML DB to define an automatic mapping between a set of columns in some existing relational tables and the elements and attributres defined by an XML Schema.
However it is easy solve this problem by using the SQL/XML operators (XMLAGG, XMLELEMENT, XMLFOREST, XMLATTRIBUTES, etc) to generate XML documents that are compliant with an XML Schema directly from a SQL statement.
If the XML Schema is registered with Oracle XML DB and the appropraite Schema Location information is added into the generated document using XMLAttributes then it becomes very easy to ensure that the generated documents are valid.
The following example show an easy way to do this by creating an XML View that contains the documents to be validated.
SQL> drop table PURCHASEORDER_LINEITEM
2 /
Table dropped.
SQL> drop table PURCHASEORDER_REJECTION
2 /
Table dropped.
SQL> drop table PURCHASEORDER_SHIPPING
2 /
Table dropped.
SQL> drop TABLE PURCHASEORDER_ACTION
2 /
Table dropped.
SQL> drop TABLE PURCHASEORDER_TABLE
2 /
Table dropped.
SQL> create table PURCHASEORDER_TABLE
2 (
3   REFERENCE                                          VARCHAR2(28),
4   PRIMARY KEY ("REFERENCE"),
5   REQUESTER                                          VARCHAR2(48),
6   USERID                                             VARCHAR2(32),
7   COSTCENTER                                         VARCHAR2(3),
8   SPECIALINSTRUCTIONS                                VARCHAR2(2048)
9 )
10 /
Table created.
SQL> create table PURCHASEORDER_ACTION
2 (
3   REFERENCE,
4   FOREIGN KEY ("REFERENCE")                          REFERENCES "PURCHASEORDER_TABLE" ("REFERENCE") ON DELETE CASCADE,
5   ACTIONEDBY                                         VARCHAR2(32),
6   DATEACTIONED                                       DATE
7 )
8 /
Table created.
SQL> create table PURCHASEORDER_SHIPPING
2 (
3   REFERENCE,
4   FOREIGN KEY ("REFERENCE")                          REFERENCES "PURCHASEORDER_TABLE" ("REFERENCE") ON DELETE CASCADE,
5   PRIMARY KEY ("REFERENCE"),
6   SHIPTONAME                                         VARCHAR2(48),
7   ADDRESS                                            VARCHAR2(512),
8   PHONE                                              VARCHAR2(32)
9 )
10 /
Table created.
SQL> create table PURCHASEORDER_REJECTION
2 (
3   REFERENCE,
4   FOREIGN KEY ("REFERENCE")                          REFERENCES "PURCHASEORDER_TABLE" ("REFERENCE") ON DELETE CASCADE,
5   PRIMARY KEY ("REFERENCE"),
6   REJECTEDBY                                         VARCHAR2(32),
7   DATEREJECTED                                       DATE,
8   COMMENTS                                           VARCHAR2(2048)
9 )
10 /
Table created.
SQL> create table PURCHASEORDER_LINEITEM
2 (
3   REFERENCE,
4   FOREIGN KEY ("REFERENCE")                          REFERENCES "PURCHASEORDER_TABLE" ("REFERENCE") ON DELETE CASCADE,
5   LINENO                                             NUMBER(10),
6   PRIMARY KEY ("REFERENCE","LINENO"),
7   UPC                                                   VARCHAR2(14),
8   DESCRIPTION                                        VARCHAR2(128),
9   QUANTITY                                           NUMBER(10),
10   UNITPRICE                                          NUMBER(12,2)
11 )
12 /
Table created.
SQL> insert into PURCHASEORDER_TABLE values ('SMCCAIN-20030109123335470PDT','Samuel B. McCain','SMCCAIN','A10','Courier')
2 /
1 row created.
SQL> insert into PURCHASEORDER_ACTION values ('SMCCAIN-20030109123335470PDT','SVOLLMAN',NULL)
2 /
1 row created.
SQL> insert into PURCHASEORDER_SHIPPING values ('SMCCAIN-20030109123335470PDT','Samuel B. McCain','800 Bridge Parkway,Redwood Shores,CA,9406
5,USA','650 506 7800')
2 /
1 row created.
SQL> insert into PURCHASEORDER_REJECTION values ('SMCCAIN-20030109123335470PDT',null,null,null)
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','1','715515010320','Life of Brian - Monty Python''s','2','39.
95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','2','37429145227','The Night Porter','2','29.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','3','37429128121','Oliver Twist','1','39.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','4','715515012720','Notorious','4','39.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','5','715515012928','In the Mood for Love','3','39.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','6','37429130926','Alphaville','2','29.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','7','37429166529','General Idi Amin Dada','4','29.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','8','715515012928','In the Mood for Love','3','39.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','9','715515009423','Flesh for Frankenstein','3','39.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','10','715515008976','The Killer','1','39.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','11','37429167922','Ballad of a Soldier','2','29.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','12','37429158623','Ordet','2','0')
2 /
1 row created.
SQL> var schemaPath varchar2(256)
SQL> --
SQL> begin
2    :schemaURL := 'http://xfiles:8080/home/SCOTT/poSource/xsd/purchaseOrder.xsd';
3    :schemaPath := '/public/purchaseOrder.xsd';
4 end;
5 /
PL/SQL procedure successfully completed.
SQL> call dbms_xmlSchema.deleteSchema(:schemaURL,4)
2 /
Call completed.
SQL> declare
2    res boolean;
3    xmlSchema xmlType := xmlType(
4 '
5 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" version="1.0" xdb:storeVarrayAsTable="tr
ue">
6          <xs:element name="PurchaseOrder" type="PurchaseOrderType" xdb:defaultTable="PURCHASEORDER"/>
7          <xs:complexType name="PurchaseOrderType" xdb:SQLType="PURCHASEORDER_T" xdb:maintainDOM="false">
8                  <xs:sequence>
9                          <xs:element name="Reference" type="ReferenceType" xdb:SQLName="REFERENCE"/>
10                          <xs:element name="Actions" type="ActionsType" xdb:SQLName="ACTIONS"/>
11                          <xs:element name="Reject" type="RejectionType" minOccurs="0" xdb:SQLName="REJECTION"/>
12                          <xs:element name="Requestor" type="RequestorType" xdb:SQLName="REQUESTOR"/>
13                          <xs:element name="User" type="UserType" xdb:SQLName="USERID"/>
14                          <xs:element name="CostCenter" type="CostCenterType" xdb:SQLName="COST_CENTER"/>
15                          <xs:element name="ShippingInstructions" type="ShippingInstructionsType" xdb:SQLName="SHIPPING_INSTRUCTIONS"/>
16                          <xs:element name="SpecialInstructions" type="SpecialInstructionsType" xdb:SQLName="SPECIAL_INSTRUCTIONS"/>
17                          <xs:element name="LineItems" type="LineItemsType" xdb:SQLName="LINEITEMS"/>
18                  </xs:sequence>
19          </xs:complexType>
20          <xs:complexType name="LineItemsType" xdb:SQLType="LINEITEMS_T" xdb:maintainDOM="false">
21                  <xs:sequence>
22                          <xs:element name="LineItem" type="LineItemType" maxOccurs="unbounded" xdb:SQLName="LINEITEM" xdb:SQLCollType="L
INEITEM_V"/>
23                  </xs:sequence>
24          </xs:complexType>
25          <xs:complexType name="LineItemType" xdb:SQLType="LINEITEM_T" xdb:maintainDOM="false">
26                  <xs:sequence>
27                          <xs:element name="Description" type="DescriptionType" xdb:SQLName="DESRIPTION"/>
28                          <xs:element name="Part" type="PartType" xdb:SQLName="PART"/>
29                  </xs:sequence>
30                  <xs:attribute name="ItemNumber" type="xs:integer" xdb:SQLName="ITEMNUMBER" xdb:SQLType="NUMBER"/>
31          </xs:complexType>
32          <xs:complexType name="PartType" xdb:SQLType="PART_T" xdb:maintainDOM="false">
33                  <xs:attribute name="Id" xdb:SQLName="PART_NUMBER" xdb:SQLType="VARCHAR2">
34                          <xs:simpleType>
35                                  <xs:restriction base="xs:string">
36                                          <xs:minLength value="10"/>
37                                          <xs:maxLength value="14"/>
38                                  </xs:restriction>
39                          </xs:simpleType>
40                  </xs:attribute>
41                  <xs:attribute name="Quantity" type="moneyType" xdb:SQLName="QUANTITY"/>
42                  <xs:attribute name="UnitPrice" type="quantityType" xdb:SQLName="UNITPRICE"/>
43          </xs:complexType>
44          <xs:simpleType name="ReferenceType">
45                  <xs:restriction base="xs:string">
46                          <xs:minLength value="18"/>
47                          <xs:maxLength value="30"/>
48                  </xs:restriction>
49          </xs:simpleType>
50          <xs:complexType name="ActionsType" xdb:SQLType="ACTIONS_T" xdb:maintainDOM="false">
51                  <xs:sequence>
52                          <xs:element name="Action" maxOccurs="4" xdb:SQLName="ACTION" xdb:SQLCollType="ACTION_V">
53                                  <xs:complexType xdb:SQLType="ACTION_T" xdb:maintainDOM="false">
54                                          <xs:sequence>
55                                                  <xs:element name="User" type="UserType" xdb:SQLName="ACTIONED_BY"/>
56                                                  <xs:element name="Date" type="DateType" minOccurs="0" xdb:SQLName="DATE_ACTIONED"/>
57                                          </xs:sequence>
58                                  </xs:complexType>
59                          </xs:element>
60                  </xs:sequence>
61          </xs:complexType>
62          <xs:complexType name="RejectionType" xdb:SQLType="REJECTION_T" xdb:maintainDOM="false">
63                  <xs:all>
64                          <xs:element name="User" type="UserType" minOccurs="0" xdb:SQLName="REJECTED_BY"/>
65                          <xs:element name="Date" type="DateType" minOccurs="0" xdb:SQLName="DATE_REJECTED"/>
66                          <xs:element name="Comments" type="CommentsType" minOccurs="0" xdb:SQLName="REASON_REJECTED"/>
67                  </xs:all>
68          </xs:complexType>
69          <xs:complexType name="ShippingInstructionsType" xdb:SQLType="SHIPPING_INSTRUCTIONS_T" xdb:maintainDOM="false">
70                  <xs:sequence>
71                          <xs:element name="name" type="NameType" minOccurs="0" xdb:SQLName="SHIP_TO_NAME"/>
72                          <xs:element name="address" type="AddressType" minOccurs="0" xdb:SQLName="SHIP_TO_ADDRESS"/>
73                          <xs:element name="telephone" type="TelephoneType" minOccurs="0" xdb:SQLName="SHIP_TO_PHONE"/>
74                  </xs:sequence>
75          </xs:complexType>
76          <xs:simpleType name="moneyType">
77                  <xs:restriction base="xs:decimal">
78                          <xs:fractionDigits value="2"/>
79                          <xs:totalDigits value="12"/>
80                  </xs:restriction>
81          </xs:simpleType>
82          <xs:simpleType name="quantityType">
83                  <xs:restriction base="xs:decimal">
84                          <xs:fractionDigits value="4"/>
85                          <xs:totalDigits value="8"/>
86                  </xs:restriction>
87          </xs:simpleType>
88          <xs:simpleType name="UserType">
89                  <xs:restriction base="xs:string">
90                          <xs:minLength value="1"/>
91                          <xs:maxLength value="10"/>
92                  </xs:restriction>
93          </xs:simpleType>
94          <xs:simpleType name="RequestorType">
95                  <xs:restriction base="xs:string">
96                          <xs:minLength value="0"/>
97                          <xs:maxLength value="128"/>
98                  </xs:restriction>
99          </xs:simpleType>
100          <xs:simpleType name="CostCenterType">
101                  <xs:restriction base="xs:string">
102                          <xs:minLength value="1"/>
103                          <xs:maxLength value="4"/>
104                  </xs:restriction>
105          </xs:simpleType>
106          <xs:simpleType name="VendorType">
107                  <xs:restriction base="xs:string">
108                          <xs:minLength value="0"/>
109                          <xs:maxLength value="20"/>
110                  </xs:restriction>
111          </xs:simpleType>
112          <xs:simpleType name="PurchaseOrderNumberType">
113                  <xs:restriction base="xs:integer"/>
114          </xs:simpleType>
115          <xs:simpleType name="SpecialInstructionsType">
116                  <xs:restriction base="xs:string">
117                          <xs:minLength value="0"/>
118                          <xs:maxLength value="2048"/>
119                  </xs:restriction>
120          </xs:simpleType>
121          <xs:simpleType name="NameType">
122                  <xs:restriction base="xs:string">
123                          <xs:minLength value="1"/>
124                          <xs:maxLength value="20"/>
125                  </xs:restriction>
126          </xs:simpleType>
127          <xs:simpleType name="AddressType">
128                  <xs:restriction base="xs:string">
129                          <xs:minLength value="1"/>
130                          <xs:maxLength value="256"/>
131                  </xs:restriction>
132          </xs:simpleType>
133          <xs:simpleType name="TelephoneType">
134                  <xs:restriction base="xs:string">
135                          <xs:minLength value="1"/>
136                          <xs:maxLength value="24"/>
137                  </xs:restriction>
138          </xs:simpleType>
139          <xs:simpleType name="DateType">
140                  <xs:restriction base="xs:date"/>
141          </xs:simpleType>
142          <xs:simpleType name="CommentsType">
143                  <xs:restriction base="xs:string">
144                          <xs:minLength value="1"/>
145                          <xs:maxLength value="2048"/>
146                  </xs:restriction>
147          </xs:simpleType>
148          <xs:simpleType name="DescriptionType">
149                  <xs:restriction base="xs:string">
150                          <xs:minLength value="1"/>
151                          <xs:maxLength value="256"/>
152                  </xs:restriction>
153          </xs:simpleType>
154 </xs:schema>
155 ');
156 begin
157    if (dbms_xdb.existsResource(:schemaPath)) then
158      dbms_xdb.deleteResource(:schemaPath);
159    end if;
160    res := dbms_xdb.createResource(:schemaPath,xmlSchema);
161 end;
162 /
PL/SQL procedure successfully completed.
SQL> begin
2    dbms_xmlschema.registerSchema
3    (
4      :schemaURL,
5      xdbURIType(:schemaPath).getClob(),
6      TRUE,TRUE,FALSE,FALSE
7    );
8 end;
9 /
PL/SQL procedure successfully completed.
SQL> create or replace view PURCHASEORDER_XML
2 of xmltype
3 xmlSCHEMA "http://xfiles:8080/home/SCOTT/poSource/xsd/purchaseOrder.xsd" Element "PurchaseOrder"
4 with object id
5 (
6    substr(extractValue(object_value,'/PurchaseOrder/Reference'),1,32)
7 )
8 as
9    select xmlElement
10           (
11             "PurchaseOrder",
12             xmlAttributes
13             (
14               'http://xfiles:8080/home/SCOTT/poSource/xsd/purchaseOrder.xsd' as "xsi:noNamespaceSchemaLocation",
15               'http://www.w3.org/2001/XMLSchema-instance' as "xmlns:xsi"
16             ),
17             xmlElement("Reference",p.REFERENCE),
18             xmlElement
19             (
20               "Actions",
21               ( select xmlAgg
22                        (
23                          xmlElement
24                          (
25                            "Action",
26                            xmlElement("User",ACTIONEDBY),
27                            case
28                              when DATEACTIONED is not null
29                              then xmlElement("Date",DATEACTIONED)
30                            end
31                          )
32                        )
33                   from PURCHASEORDER_ACTION a
34                  where a.REFERENCE = p.REFERENCE
35               )
36             ),
37             xmlElement
38             (
39               "Reject",
40                  xmlForest
41                  (
42                    REJECTEDBY as "User",
43                 DATEREJECTED as "Date",
44                    COMMENTS as "Comments"
45                  )
46             ),
47             xmlElement("Requestor",REQUESTER),
48             xmlElement("User",USERID),
49             xmlElement("CostCenter",COSTCENTER),
50             xmlElement
51             (
52               "ShippingInstructions",
53               xmlElement("name",SHIPTONAME),
54               xmlElement("address",ADDRESS),
55               xmlElement("telephone",PHONE)
56             ),
57             xmlElement("SpecialInstructions",SPECIALINSTRUCTIONS),
58             xmlElement
59             (
60               "LineItems",
61               ( select xmlAgg
62                        (
63                          xmlElement
64                          (
65                            "LineItem",
66                            xmlAttributes(LINENO as "ItemNumber"),
67                            xmlElement("Description",DESCRIPTION),
68                            xmlElement
69                            (
70                              "Part",
71                              xmlAttributes
72                              (
73                                UPC       as "Id",
74                                QUANTITY as "Quantity",
75                                UNITPRICE as "UnitPrice"
76                              )
77                            )
78                          )
79                        )
80                    from PURCHASEORDER_LINEITEM l
81                   where l.REFERENCE = p.REFERENCE
82               )
83             )
84           )
85      from PURCHASEORDER_TABLE p, PURCHASEORDER_REJECTION r, PURCHASEORDER_SHIPPING s
86     where r.REFERENCE = p.REFERENCE
87       and s.REFERENCE = p.REFERENCE
88 /
View created.
SQL> set long 10000 pages 0 lines 140
SQL> --
SQL> select x.object_value.extract('/*')
2    from PURCHASEORDER_XML x
3 /
<PurchaseOrder xsi:noNamespaceSchemaLocation="http://xfiles:8080/home/SCOTT/poSource/xsd/purchaseOrder.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Reference>SMCCAIN-20030109123335470PDT</Reference>
<Actions>
    <Action>
      <User>SVOLLMAN</User>
    </Action>
</Actions>
<Reject/>
<Requestor>Samuel B. McCain</Requestor>
<User>SMCCAIN</User>
<CostCenter>A10</CostCenter>
<ShippingInstructions>
    <name>Samuel B. McCain</name>
    <address>800 Bridge Parkway,Redwood Shores,CA,94065,USA</address>
    <telephone>650 506 7800</telephone>
</ShippingInstructions>
<SpecialInstructions>Courier</SpecialInstructions>
<LineItems>
    <LineItem ItemNumber="1">
      <Description>Life of Brian - Monty Python's</Description>
      <Part Id="715515010320" Quantity="2" UnitPrice="39.95"/>
    </LineItem>
    <LineItem ItemNumber="2">
      <Description>The Night Porter</Description>
      <Part Id="37429145227" Quantity="2" UnitPrice="29.95"/>
    </LineItem>
    <LineItem ItemNumber="3">
      <Description>Oliver Twist</Description>
      <Part Id="37429128121" Quantity="1" UnitPrice="39.95"/>
    </LineItem>
    <LineItem ItemNumber="4">
      <Description>Notorious</Description>
      <Part Id="715515012720" Quantity="4" UnitPrice="39.95"/>
    </LineItem>
    <LineItem ItemNumber="5">
      <Description>In the Mood for Love</Description>
      <Part Id="715515012928" Quantity="3" UnitPrice="39.95"/>
    </LineItem>
    <LineItem ItemNumber="6">
      <Description>Alphaville</Description>
      <Part Id="37429130926" Quantity="2" UnitPrice="29.95"/>
    </LineItem>
    <LineItem ItemNumber="7">
      <Description>General Idi Amin Dada</Description>
      <Part Id="37429166529" Quantity="4" UnitPrice="29.95"/>
    </LineItem>
    <LineItem ItemNumber="8">
      <Description>In the Mood for Love</Description>
      <Part Id="715515012928" Quantity="3" UnitPrice="39.95"/>
    </LineItem>
    <LineItem ItemNumber="9">
      <Description>Flesh for Frankenstein</Description>
      <Part Id="715515009423" Quantity="3" UnitPrice="39.95"/>
    </LineItem>
    <LineItem ItemNumber="10">
      <Description>The Killer</Description>
      <Part Id="715515008976" Quantity="1" UnitPrice="39.95"/>
    </LineItem>
    <LineItem ItemNumber="11">
      <Description>Ballad of a Soldier</Description>
      <Part Id="37429167922" Quantity="2" UnitPrice="29.95"/>
    </LineItem>
    <LineItem ItemNumber="12">
      <Description>Ordet</Description>
      <Part Id="37429158623" Quantity="2" UnitPrice="0"/>
    </LineItem>
</LineItems>
</PurchaseOrder>
SQL> begin
2    for x in (select object_value from PURCHASEORDER_XML) loop
3      x.object_value.schemaValidate();
4    end loop;
5 end;
6 /
PL/SQL procedure successfully completed.
SQL>

There is no automated way in Oracle XML DB to define an automatic mapping between a set of columns in some existing relational tables and the elements and attributres defined by an XML Schema.
However it is easy solve this problem by using the SQL/XML operators (XMLAGG, XMLELEMENT, XMLFOREST, XMLATTRIBUTES, etc) to generate XML documents that are compliant with an XML Schema directly from a SQL statement.
If the XML Schema is registered with Oracle XML DB and the appropraite Schema Location information is added into the generated document using XMLAttributes then it becomes very easy to ensure that the generated documents are valid.
The following example show an easy way to do this by creating an XML View that contains the documents to be validated.
SQL> drop table PURCHASEORDER_LINEITEM
2 /
Table dropped.
SQL> drop table PURCHASEORDER_REJECTION
2 /
Table dropped.
SQL> drop table PURCHASEORDER_SHIPPING
2 /
Table dropped.
SQL> drop TABLE PURCHASEORDER_ACTION
2 /
Table dropped.
SQL> drop TABLE PURCHASEORDER_TABLE
2 /
Table dropped.
SQL> create table PURCHASEORDER_TABLE
2 (
3   REFERENCE                                          VARCHAR2(28),
4   PRIMARY KEY ("REFERENCE"),
5   REQUESTER                                          VARCHAR2(48),
6   USERID                                             VARCHAR2(32),
7   COSTCENTER                                         VARCHAR2(3),
8   SPECIALINSTRUCTIONS                                VARCHAR2(2048)
9 )
10 /
Table created.
SQL> create table PURCHASEORDER_ACTION
2 (
3   REFERENCE,
4   FOREIGN KEY ("REFERENCE")                          REFERENCES "PURCHASEORDER_TABLE" ("REFERENCE") ON DELETE CASCADE,
5   ACTIONEDBY                                         VARCHAR2(32),
6   DATEACTIONED                                       DATE
7 )
8 /
Table created.
SQL> create table PURCHASEORDER_SHIPPING
2 (
3   REFERENCE,
4   FOREIGN KEY ("REFERENCE")                          REFERENCES "PURCHASEORDER_TABLE" ("REFERENCE") ON DELETE CASCADE,
5   PRIMARY KEY ("REFERENCE"),
6   SHIPTONAME                                         VARCHAR2(48),
7   ADDRESS                                            VARCHAR2(512),
8   PHONE                                              VARCHAR2(32)
9 )
10 /
Table created.
SQL> create table PURCHASEORDER_REJECTION
2 (
3   REFERENCE,
4   FOREIGN KEY ("REFERENCE")                          REFERENCES "PURCHASEORDER_TABLE" ("REFERENCE") ON DELETE CASCADE,
5   PRIMARY KEY ("REFERENCE"),
6   REJECTEDBY                                         VARCHAR2(32),
7   DATEREJECTED                                       DATE,
8   COMMENTS                                           VARCHAR2(2048)
9 )
10 /
Table created.
SQL> create table PURCHASEORDER_LINEITEM
2 (
3   REFERENCE,
4   FOREIGN KEY ("REFERENCE")                          REFERENCES "PURCHASEORDER_TABLE" ("REFERENCE") ON DELETE CASCADE,
5   LINENO                                             NUMBER(10),
6   PRIMARY KEY ("REFERENCE","LINENO"),
7   UPC                                                   VARCHAR2(14),
8   DESCRIPTION                                        VARCHAR2(128),
9   QUANTITY                                           NUMBER(10),
10   UNITPRICE                                          NUMBER(12,2)
11 )
12 /
Table created.
SQL> insert into PURCHASEORDER_TABLE values ('SMCCAIN-20030109123335470PDT','Samuel B. McCain','SMCCAIN','A10','Courier')
2 /
1 row created.
SQL> insert into PURCHASEORDER_ACTION values ('SMCCAIN-20030109123335470PDT','SVOLLMAN',NULL)
2 /
1 row created.
SQL> insert into PURCHASEORDER_SHIPPING values ('SMCCAIN-20030109123335470PDT','Samuel B. McCain','800 Bridge Parkway,Redwood Shores,CA,9406
5,USA','650 506 7800')
2 /
1 row created.
SQL> insert into PURCHASEORDER_REJECTION values ('SMCCAIN-20030109123335470PDT',null,null,null)
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','1','715515010320','Life of Brian - Monty Python''s','2','39.
95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','2','37429145227','The Night Porter','2','29.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','3','37429128121','Oliver Twist','1','39.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','4','715515012720','Notorious','4','39.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','5','715515012928','In the Mood for Love','3','39.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','6','37429130926','Alphaville','2','29.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','7','37429166529','General Idi Amin Dada','4','29.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','8','715515012928','In the Mood for Love','3','39.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','9','715515009423','Flesh for Frankenstein','3','39.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','10','715515008976','The Killer','1','39.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','11','37429167922','Ballad of a Soldier','2','29.95')
2 /
1 row created.
SQL> insert into PURCHASEORDER_LINEITEM values ('SMCCAIN-20030109123335470PDT','12','37429158623','Ordet','2','0')
2 /
1 row created.
SQL> var schemaPath varchar2(256)
SQL> --
SQL> begin
2    :schemaURL := 'http://xfiles:8080/home/SCOTT/poSource/xsd/purchaseOrder.xsd';
3    :schemaPath := '/public/purchaseOrder.xsd';
4 end;
5 /
PL/SQL procedure successfully completed.
SQL> call dbms_xmlSchema.deleteSchema(:schemaURL,4)
2 /
Call completed.
SQL> declare
2    res boolean;
3    xmlSchema xmlType := xmlType(
4 '
5 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" version="1.0" xdb:storeVarrayAsTable="tr
ue">
6          <xs:element name="PurchaseOrder" type="PurchaseOrderType" xdb:defaultTable="PURCHASEORDER"/>
7          <xs:complexType name="PurchaseOrderType" xdb:SQLType="PURCHASEORDER_T" xdb:maintainDOM="false">
8                  <xs:sequence>
9                          <xs:element name="Reference" type="ReferenceType" xdb:SQLName="REFERENCE"/>
10                          <xs:element name="Actions" type="ActionsType" xdb:SQLName="ACTIONS"/>
11                          <xs:element name="Reject" type="RejectionType" minOccurs="0" xdb:SQLName="REJECTION"/>
12                          <xs:element name="Requestor" type="RequestorType" xdb:SQLName="REQUESTOR"/>
13                          <xs:element name="User" type="UserType" xdb:SQLName="USERID"/>
14                          <xs:element name="CostCenter" type="CostCenterType" xdb:SQLName="COST_CENTER"/>
15                          <xs:element name="ShippingInstructions" type="ShippingInstructionsType" xdb:SQLName="SHIPPING_INSTRUCTIONS"/>
16                          <xs:element name="SpecialInstructions" type="SpecialInstructionsType" xdb:SQLName="SPECIAL_INSTRUCTIONS"/>
17                          <xs:element name="LineItems" type="LineItemsType" xdb:SQLName="LINEITEMS"/>
18                  </xs:sequence>
19          </xs:complexType>
20          <xs:complexType name="LineItemsType" xdb:SQLType="LINEITEMS_T" xdb:maintainDOM="false">
21                  <xs:sequence>
22                          <xs:element name="LineItem" type="LineItemType" maxOccurs="unbounded" xdb:SQLName="LINEITEM" xdb:SQLCollType="L
INEITEM_V"/>
23                  </xs:sequence>
24          </xs:complexType>
25          <xs:complexType name="LineItemType" xdb:SQLType="LINEITEM_T" xdb:maintainDOM="false">
26                  <xs:sequence>
27                          <xs:element name="Description" type="DescriptionType" xdb:SQLName="DESRIPTION"/>
28                          <xs:element name="Part" type="PartType" xdb:SQLName="PART"/>
29                  </xs:sequence>
30                  <xs:attribute name="ItemNumber" type="xs:integer" xdb:SQLName="ITEMNUMBER" xdb:SQLType="NUMBER"/>
31          </xs:complexType>
32          <xs:complexType name="PartType" xdb:SQLType="PART_T" xdb:maintainDOM="false">
33                  <xs:attribute name="Id" xdb:SQLName="PART_NUMBER" xdb:SQLType="VARCHAR2">
34                          <xs:simpleType>
35                                  <xs:restriction base="xs:string">
36                                          <xs:minLength value="10"/>
37                                          <xs:maxLength value="14"/>
38                                  </xs:restriction>
39                          </xs:simpleType>
40                  </xs:attribute>
41                  <xs:attribute name="Quantity" type="moneyType" xdb:SQLName="QUANTITY"/>
42                  <xs:attribute name="UnitPrice" type="quantityType" xdb:SQLName="UNITPRICE"/>
43          </xs:complexType>
44          <xs:simpleType name="ReferenceType">
45                  <xs:restriction base="xs:string">
46                          <xs:minLength value="18"/>
47                          <xs:maxLength value="30"/>
48                  </xs:restriction>
49          </xs:simpleType>
50          <xs:complexType name="ActionsType" xdb:SQLType="ACTIONS_T" xdb:maintainDOM="false">
51                  <xs:sequence>
52                          <xs:element name="Action" maxOccurs="4" xdb:SQLName="ACTION" xdb:SQLCollType="ACTION_V">
53                                  <xs:complexType xdb:SQLType="ACTION_T" xdb:maintainDOM="false">
54                                          <xs:sequence>
55                                                  <xs:element name="User" type="UserType" xdb:SQLName="ACTIONED_BY"/>
56                                                  <xs:element name="Date" type="DateType" minOccurs="0" xdb:SQLName="DATE_ACTIONED"/>
57                                          </xs:sequence>
58                                  </xs:complexType>
59                          </xs:element>
60                  </xs:sequence>
61          </xs:complexType>
62          <xs:complexType name="RejectionType" xdb:SQLType="REJECTION_T" xdb:maintainDOM="false">
63                  <xs:all>
64                          <xs:element name="User" type="UserType" minOccurs="0" xdb:SQLName="REJECTED_BY"/>
65                          <xs:element name="Date" type="DateType" minOccurs="0" xdb:SQLName="DATE_REJECTED"/>
66                          <xs:element name="Comments" type="CommentsType" minOccurs="0" xdb:SQLName="REASON_REJECTED"/>
67                  </xs:all>
68          </xs:complexType>
69          <xs:complexType name="ShippingInstructionsType" xdb:SQLType="SHIPPING_INSTRUCTIONS_T" xdb:maintainDOM="false">
70                  <xs:sequence>
71                          <xs:element name="name" type="NameType" minOccurs="0" xdb:SQLName="SHIP_TO_NAME"/>
72                          <xs:element name="address" type="AddressType" minOccurs="0" xdb:SQLName="SHIP_TO_ADDRESS"/>
73                          <xs:element name="telephone" type="TelephoneType" minOccurs="0" xdb:SQLName="SHIP_TO_PHONE"/>
74                  </xs:sequence>
75          </xs:complexType>
76          <xs:simpleType name="moneyType">
77                  <xs:restriction base="xs:decimal">
78                          <xs:fractionDigits value="2"/>
79                          <xs:totalDigits value="12"/>
80                  </xs:restriction>
81          </xs:simpleType>
82          <xs:simpleType name="quantityType">
83                  <xs:restriction base="xs:decimal">
84                          <xs:fractionDigits value="4"/>
85                          <xs:totalDigits value="8"/>
86                  </xs:restriction>
87          </xs:simpleType>
88          <xs:simpleType name="UserType">
89                  <xs:restriction base="xs:string">
90                          <xs:minLength value="1"/>
91                          <xs:maxLength value="10"/>
92                  </xs:restriction>
93          </xs:simpleType>
94          <xs:simpleType name="RequestorType">
95                  <xs:restriction base="xs:string">
96                          <xs:minLength value="0"/>
97                          <xs:maxLength value="128"/>
98                  </xs:restriction>
99          </xs:simpleType>
100          <xs:simpleType name="CostCenterType">
101                  <xs:restriction base="xs:string">
102                          <xs:minLength value="1"/>
103                          <xs:maxLength value="4"/>
104                  </xs:restriction>
105          </xs:simpleType>
106          <xs:simpleType name="VendorType">
107                  <xs:restriction base="xs:string">
108                          <xs:minLength value="0"/>
109                          <xs:maxLength value="20"/>
110                  </xs:restriction>
111          </xs:simpleType>
112          <xs:simpleType name="PurchaseOrderNumberType">
113                  <xs:restriction base="xs:integer"/>
114          </xs:simpleType>
115          <xs:simpleType name="SpecialInstructionsType">
116                  <xs:restriction base="xs:string">
117                          <xs:minLength value="0"/>
118                          <xs:maxLength value="2048"/>
119                  </xs:restriction>
120          </xs:simpleType>
121          <xs:simpleType name="NameType">
122                  <xs:restriction base="xs:string">
123                          <xs:minLength value="1"/>
124                          <xs:maxLength value="20"/>
125                  </xs:restriction>
126          </xs:simpleType>
127          <xs:simpleType name="AddressType">
128                  <xs:restriction base="xs:string">
129                          <xs:minLength value="1"/>
130                          <xs:maxLength value="256"/>
131                  </xs:restriction>
132          </xs:simpleType>
133          <xs:simpleType name="TelephoneType">
134                  <xs:restriction base="xs:string">
135                          <xs:minLength value="1"/>
136                          <xs:maxLength value="24"/>
137                  </xs:restriction>
138          </xs:simpleType>
139          <xs:simpleType name="DateType">
140                  <xs:restriction base="xs:date"/>
141          </xs:simpleType>
142          <xs:simpleType name="CommentsType">
143                  <xs:restriction base="xs:string">
144                          <xs:minLength value="1"/>
145                          <xs:maxLength value="2048"/>
146                  </xs:restriction>
147          </xs:simpleType>
148          <xs:simpleType name="DescriptionType">
149                  <xs:restriction base="xs:string">
150                          <xs:minLength value="1"/>
151                          <xs:maxLength value="256"/>
152                  </xs:restriction>
153          </xs:simpleType>
154 </xs:schema>
155 ');
156 begin
157    if (dbms_xdb.existsResource(:schemaPath)) then
158      dbms_xdb.deleteResource(:schemaPath);
159    end if;
160    res := dbms_xdb.createResource(:schemaPath,xmlSchema);
161 end;
162 /
PL/SQL procedure successfully completed.
SQL> begin
2    dbms_xmlschema.registerSchema
3    (
4      :schemaURL,
5      xdbURIType(:schemaPath).getClob(),
6      TRUE,TRUE,FALSE,FALSE
7    );
8 end;
9 /
PL/SQL procedure successfully completed.
SQL> create or replace view PURCHASEORDER_XML
2 of xmltype
3 xmlSCHEMA "http://xfiles:8080/home/SCOTT/poSource/xsd/purchaseOrder.xsd" Element "PurchaseOrder"
4 with object id
5 (
6    substr(extractValue(object_value,'/PurchaseOrder/Reference'),1,32)
7 )
8 as
9    select xmlElement
10           (
11             "PurchaseOrder",
12             xmlAttributes
13             (
14               'http://xfiles:8080/home/SCOTT/poSource/xsd/purchaseOrder.xsd' as "xsi:noNamespaceSchemaLocation",
15               'http://www.w3.org/2001/XMLSchema-instance' as "xmlns:xsi"
16             ),
17             xmlElement("Reference",p.REFERENCE),
18             xmlElement
19             (
20               "Actions",
21               ( select xmlAgg
22                        (
23                          xmlElement
24                          (
25                            "Action",
26                            xmlElement("User",ACTIONEDBY),
27                            case
28                              when DATEACTIONED is not null
29                              then xmlElement("Date",DATEACTIONED)
30                            end
31                          )
32                        )
33                   from PURCHASEORDER_ACTION a
34                  where a.REFERENCE = p.REFERENCE
35               )
36             ),
37             xmlElement
38             (
39               "Reject",
40                  xmlForest
41                  (
42                    REJECTEDBY as "User",
43                 DATEREJECTED as "Date",
44                    COMMENTS as "Comments"
45                  )
46             ),
47             xmlElement("Requestor",REQUESTER),
48             xmlElement("User",USERID),
49             xmlElement("CostCenter",COSTCENTER),
50             xmlElement
51             (
52               "ShippingInstructions",
53               xmlElement("name",SHIPTONAME),
54               xmlElement("address",ADDRESS),
55               xmlElement("telephone",PHONE)
56             ),
57             xmlElement("SpecialInstructions",SPECIALINSTRUCTIONS),
58             xmlElement
59             (
60               "LineItems",
61               ( select xmlAgg
62                        (
63                          xmlElement
64                          (
65                            "LineItem",
66                            xmlAttributes(LINENO as "ItemNumber"),
67                            xmlElement("Description",DESCRIPTION),
68                            xmlElement
69                            (
70                              "Part",
71                              xmlAttributes
72                              (
73                                UPC       as "Id",
74                                QUANTITY as "Quantity",
75                                UNITPRICE as "UnitPrice"
76                              )
77                            )
78                          )
79                        )
80                    from PURCHASEORDER_LINEITEM l
81                   where l.REFERENCE = p.REFERENCE
82               )
83             )
84           )
85      from PURCHASEORDER_TABLE p, PURCHASEORDER_REJECTION r, PURCHASEORDER_SHIPPING s
86     where r.REFERENCE = p.REFERENCE
87       and s.REFERENCE = p.REFERENCE
88 /
View created.
SQL> set long 10000 pages 0 lines 140
SQL> --
SQL> select x.object_value.extract('/*')
2    from PURCHASEORDER_XML x
3 /
<PurchaseOrder xsi:noNamespaceSchemaLocation="http://xfiles:8080/home/SCOTT/poSource/xsd/purchaseOrder.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Reference>SMCCAIN-20030109123335470PDT</Reference>
<Actions>
    <Action>
      <User>SVOLLMAN</User>
    </Action>
</Actions>
<Reject/>
<Requestor>Samuel B. McCain</Requestor>
<User>SMCCAIN</User>
<CostCenter>A10</CostCenter>
<ShippingInstructions>
    <name>Samuel B. McCain</name>
    <address>800 Bridge Parkway,Redwood Shores,CA,94065,USA</address>
    <telephone>650 506 7800</telephone>
</ShippingInstructions>
<SpecialInstructions>Courier</SpecialInstructions>
<LineItems>
    <LineItem ItemNumber="1">
      <Description>Life of Brian - Monty Python's</Description>
      <Part Id="715515010320" Quantity="2" UnitPrice="39.95"/>
    </LineItem>
    <LineItem ItemNumber="2">
      <Description>The Night Porter</Description>
      <Part Id="37429145227" Quantity="2" UnitPrice="29.95"/>
    </LineItem>
    <LineItem ItemNumber="3">
      <Description>Oliver Twist</Description>
      <Part Id="37429128121" Quantity="1" UnitPrice="39.95"/>
    </LineItem>
    <LineItem ItemNumber="4">
      <Description>Notorious</Description>
      <Part Id="715515012720" Quantity="4" UnitPrice="39.95"/>
    </LineItem>
    <LineItem ItemNumber="5">
      <Description>In the Mood for Love</Description>
      <Part Id="715515012928" Quantity="3" UnitPrice="39.95"/>
    </LineItem>
    <LineItem ItemNumber="6">
      <Description>Alphaville</Description>
      <Part Id="37429130926" Quantity="2" UnitPrice="29.95"/>
    </LineItem>
    <LineItem ItemNumber="7">
      <Description>General Idi Amin Dada</Description>
      <Part Id="37429166529" Quantity="4" UnitPrice="29.95"/>
    </LineItem>
    <LineItem ItemNumber="8">
      <Description>In the Mood for Love</Description>
      <Part Id="715515012928" Quantity="3" UnitPrice="39.95"/>
    </LineItem>
    <LineItem ItemNumber="9">
      <Description>Flesh for Frankenstein</Description>
      <Part Id="715515009423" Quantity="3" UnitPrice="39.95"/>
    </LineItem>
    <LineItem ItemNumber="10">
      <Description>The Killer</Description>
      <Part Id="715515008976" Quantity="1" UnitPrice="39.95"/>
    </LineItem>
    <LineItem ItemNumber="11">
      <Description>Ballad of a Soldier</Description>
      <Part Id="37429167922" Quantity="2" UnitPrice="29.95"/>
    </LineItem>
    <LineItem ItemNumber="12">
      <Description>Ordet</Description>
      <Part Id="37429158623" Quantity="2" UnitPrice="0"/>
    </LineItem>
</LineItems>
</PurchaseOrder>
SQL> begin
2    for x in (select object_value from PURCHASEORDER_XML) loop
3      x.object_value.schemaValidate();
4    end loop;
5 end;
6 /
PL/SQL procedure successfully completed.
SQL>

Query to read XML from CLOB table column

Hi
I want an SQL to get the following information extract from a CLOB table column.
MasterReport/sg:RptDef/sg:RptCell@RealDesc MasterReport/sg:RptDef/sg:RptCell@RealNum
credits                              100
debits                              100
Sample XML data from table column is:
<?xml version="1.0" encoding="UTF-8" ?>
<MasterReport xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:sg="http://www.oracle.com/fsg/2002-03-20/" xsi:schemaLocation="http://www.oracle.com/2002-03-20/fsg.xsd">
<sg:LDGName>Vision Portugal</sg:LDGName>
<sg:SOBName>Vision Portugal</sg:SOBName>
<sg:DataAccessSetName>Vision Portugal</sg:DataAccessSetName>
<sg:InternalReportName>Model 30 Report</sg:InternalReportName>
<sg:CustomParam10 />
<sg:RowContext RowId="r100001">
<sg:RowName />
<sg:RowLineItem>Litigation Credits- Total amount from previous period</sg:RowLineItem>
<sg:RowDispUnit>1</sg:RowDispUnit>
<sg:RowDispFormat />
<sg:RowUnitOfMeasure>EUR</sg:RowUnitOfMeasure>
<sg:RowLedgerCurrency>ANY</sg:RowLedgerCurrency>
<sg:RowCurrencyType>T</sg:RowCurrencyType>
<sg:RowChangeSign>0</sg:RowChangeSign>
<sg:RowSeq>1.0000000000000</sg:RowSeq>
</sg:RowContext>
<sg:RowContext RowId="r100002">
<sg:RowName />
<sg:RowLineItem>Litigation credits- Taxed amounts from column2 for Previous period</sg:RowLineItem>
<sg:RowDispUnit>1</sg:RowDispUnit>
<sg:RowDispFormat />
<sg:RowUnitOfMeasure>EUR</sg:RowUnitOfMeasure>
<sg:RowLedgerCurrency>ANY</sg:RowLedgerCurrency>
<sg:RowCurrencyType>T</sg:RowCurrencyType>
<sg:RowChangeSign>0</sg:RowChangeSign>
<sg:RowSeq>2.0000000000000</sg:RowSeq>
</sg:RowContext>
<sg:ColContext ColId="c1000">
<sg:ColAmountType />
<sg:ColPeriod />
<sg:ColPerOffset />
<sg:ColChangeSign />
<sg:ColPosition />
<sg:ColSeq />
<sg:ColWidth>100</sg:ColWidth>
</sg:ColContext>
<sg:ColContext ColId="c1001">
<sg:ColName>Total</sg:ColName>
<sg:ColDescr />
<sg:ColDispUnit>1</sg:ColDispUnit>
<sg:ColUnitOfMeasure>EUR</sg:ColUnitOfMeasure>
<sg:ColLedgerCurrency>ANY</sg:ColLedgerCurrency>
<sg:ColCurrencyType>T</sg:ColCurrencyType>
<sg:ColDispFormat>999999999.99</sg:ColDispFormat>
<sg:ColAmountType>YTD-Actual</sg:ColAmountType>
<sg:ColPerOffset>0</sg:ColPerOffset>
<sg:ColAmntId>14</sg:ColAmntId>
<sg:ColParamId>-1</sg:ColParamId>
<sg:ColType>A</sg:ColType>
<sg:ColStyle>B</sg:ColStyle>
<sg:ColPeriod>10-08</sg:ColPeriod>
<sg:ColPeriodYear>2008</sg:ColPeriodYear>
<sg:ColPeriodNum>11</sg:ColPeriodNum>
<sg:ColPeriodStart>2008-10-01T00:00:00</sg:ColPeriodStart>
<sg:ColPeriodEnd>2008-10-31T00:00:00</sg:ColPeriodEnd>
<sg:ColChangeSign>0</sg:ColChangeSign>
<sg:ColHeadLine1>Totals</sg:ColHeadLine1>
<sg:ColHeadLine2 />
<sg:ColHeadLine3 />
<sg:ColHeadLine4 />
<sg:ColHeadLine5 />
<sg:ColHeadLine6 />
<sg:ColHeadLine7 />
<sg:ColHeadLine8 />
<sg:ColHeadLine9 />
<sg:ColPosition>99</sg:ColPosition>
<sg:ColSeq>1.0000000000000</sg:ColSeq>
<sg:ColWidth>14</sg:ColWidth>
</sg:ColContext>
<sg:RptDef RptId="p1001" RptDetName="Ledger=Vision PT (Vision Portugal)" RptPESegm="" RptPEVal="" RptTabLabel="Output 1 (Vision PT)">
<sg:RptLine RptCnt="p1001" RowCnt="r100001" LineRowSeq="1.0000000000000" LinCnt="l100001">
<sg:RptCell ColCnt="c1000" RealDesc="debits">debits</sg:RptCell>
<sg:RptCell ColCnt="c1001" RealNum="100.000000">100.00</sg:RptCell>
</sg:RptLine>
<sg:RptLine RptCnt="p1001" RowCnt="r100002" LineRowSeq="2.0000000000000" LinCnt="l100002">
<sg:RptCell ColCnt="c1000" RealDesc="creditsd">credits</sg:RptCell>
<sg:RptCell ColCnt="c1001" RealNum="100.000000">100.00</sg:RptCell>
</sg:RptLine>
</sg:RptDef>
<sg:TabCount>1</sg:TabCount>
</MasterReport>
Please help me.
Regards
Giri
Edited by: user576087 on Mar 18, 2012 11:54 PM

I'm not sure if you want the values from the attribute or the element, but this should give you a good start :
SQL> alter session set nls_numeric_characters = ".,";
Session altered
SQL>
SQL> select x.*
2 from my_table t
3     , xmltable(
4         xmlnamespaces('http://www.oracle.com/fsg/2002-03-20/' as "sg")
5       , '/MasterReport/sg:RptDef/sg:RptLine'
6         passing xmltype(t.xmldoc)
7         columns type    varchar2(30) path 'sg:RptCell[1]'
8               , amount number       path 'sg:RptCell[2]'
9       ) x
10 ;
TYPE                               AMOUNT
debits                                100
credits                               100

Error when copying items from one table to another

I am trying to copy data from 2 archive tables within an
Access database to their twin production tables. The first table
copies perfectly with the code:
<CFQUERY NAME="moveArchAttach" datasource="faaco2">
INSERT INTO tbl_Attachment ( PostID, Attachment, AttachNote,
AttachName )
SELECT tbl_Attachment_Archived.PostID,
tbl_Attachment_Archived.Attachment,
tbl_Attachment_Archived.AttachNote,
tbl_Attachment_Archived.AttachName
FROM tbl_Attachment_Archived
</CFQUERY>
However, when trying to use similar code on the other table:
<CFQUERY NAME="moveArchPost" datasource="faaco2">
INSERT INTO tbl_Posting ( Title, FirstName, LastName,
PhoneNumber, RoutingSymbol, Email, IniDate, ComDate, SOLNBR,
PhaseCode, ProcCode, Posting, Password, RegionCode )
SELECT tbl_Posting_Archived.Title,
tbl_Posting_Archived.FirstName, tbl_Posting_Archived.LastName,
tbl_Posting_Archived.PhoneNumber,
tbl_Posting_Archived.RoutingSymbol, tbl_Posting.Email,
tbl_Posting.IniDate, tbl_Posting.ComDate, tbl_Posting.SOLNBR,
tbl_Posting.PhaseCode, tbl_Posting.ProcCode, tbl_Posting.Posting,
tbl_Posting.Password, tbl_Posting.RegionCode
FROM tbl_Posting_Archived
</CFQUERY>
I receive the error:
[Microsoft][ODBC Microsoft Access Driver] Too few parameters.
Expected 9.
Any help would be greatly appreciated, I am at a loss and
I've tried everything. Thank you.

I realized my error immediately after posting this topic and
subsequently have resolved this error. On 9 of the values, I have
listed the wrong table in the SELECT statement. This is why one
needs to take breaks instead of staring at a screen forever :).
Thank you anyway!

Error in Abap code when combining data from two tables

Hi,
I got error in my code when i try to select data based on two tables
error message Unknown column name "(" field list. field list. field list. field list.
select ( WLK1~ARTNR )
          into ZOXE1D0041-ZZPROMO
          from WLK1 INNER JOIN T001W
          ON WLK1FILIA = T001WKUNNR.
          where WLK1-PFLKN NE 'P' AND
          WLK1-QUELL NE '2'.
Table 1 WLK1
ARTNR   FILIA       PFLKN                  QUELL
001         C001        P                           2
002         C001        A                          1
Table 2 T001W
KUNNR                WERKS
C001                    P001
My requirement is to extract from article number from table WLK1 where the customer number (FILIA) matches with Customer number from (T001W) and plant (WERKS).
In conclusion I like to have this only this row
ARTNR   FILIA       PFLKN                  QUELL
002         C001        A                          1

Hi
You need to append every article number after each select is performed
is this an intermal table ZOXE1D0041 with header line ? if yes
then do this way
select WLK1~ARTNR
into ZZARTICLE
from WLK1 INNER JOIN T001W
ON WLK1FILIA = T001WKUNNR
where WLK1~PFLKN NE 'P' AND
WLK1~PFLKN NE 'S' AND
WLK1~QUELL NE '2'.
ZOXE1D0041-ZZLISTARTICLE = ZZARTICLE.
Append ZOXE1D0041. " <edited>
endselect.
then ZOXE1D0041 will have all article numbers.
Edited by: Sonal Patel on Sep 5, 2009 10:27 AM

Namespaces when Composing XML from Reational Tables

Similar Messages

Maybe you are looking for