Convert XML to relational view

WE are retrieving data using Web Services, i.e. using SOAP protocol and receiving data in XML format.
We need to access this data using a normal relational view, but can not find a solution how to do this.
Example:
The returned XML is a invoice with 2 lines. We want to create 2 distinct views, one for the invoice header and one for the lines, i.e. it must return 2 rows.
How is this possible?

You can create a relational view using extract() and extractValue() SQL operators on the underlying XMLType data. Also, the XMLSequence() operator can be used to generate the view for lines.
See XML DB Developer's Guide for further details.

Similar Messages

Parse XML into relational view?

Hi All,
In the xml doc below, how can I extract value of lineNumber attribute of <item> tag? The query as it stands returns correct rows but it is missing line number.
Thanks!
select
extract(value(xml), '/Segment/@type').getStringval() att_name,
extract(value(xml), '/Segment/@id').getStringval() att_value,
extract(value(xml), '/item/@lineNumber').getNumberVal() att_line -- does not work!
from table(xmlsequence(
extract(xmltype('<?xml version="1.0" encoding="utf-8" ?>
<Header>
<item lineNumber = "1">
<Segment type="Action" id="Add" description="Action" />
<Segment type="Business Owner" id="John Doe" description="Business Owner" />
<Segment type="Catalog Item Ordered" id="20677765" description="Catalog Item Ordered" />
<Segment type="Asset Tag" id="0060123" description="Asset Tag" />
</item>
<item lineNumber = "2">
<Segment type="Action" id="Add" description="Action" />
<Segment type="Business Owner" id="Jane Doe" description="Business Owner" />
<Segment type="Catalog Item Ordered" id="20688865" description="Catalog Item Ordered" />
<Segment type="Asset Tag" id="0061444" description="Asset Tag" />
</item>
</Header>'), '/Header/item/Segment')
)) xml;
Message was edited by:
user521497

Here's you go
SQL> set pages 20 lines 150
SQL> --
SQL> var xmltext varchar2(4000)
SQL> --
SQL> begin
2    :xmltext :=
3 '<?xml version="1.0" encoding="utf-8" ?>
4 <Header>
5    <item lineNumber = "1">
6      <Segment type="Action" id="Add" description="Action" />
7      <Segment type="Business Owner" id="John Doe" description="Business Owner" />
8      <Segment type="Catalog Item Ordered" id="20677765" description="Catalog Item Ordered" />
9      <Segment type="Asset Tag" id="0060123" description="Asset Tag" />
10    </item>
11    <item lineNumber = "2">
12      <Segment type="Action" id="Add" description="Action" />
13      <Segment type="Business Owner" id="Jane Doe" description="Business Owner" />
14      <Segment type="Catalog Item Ordered" id="20688865" description="Catalog Item Ordered" />
15      <Segment type="Asset Tag" id="0061444" description="Asset Tag" />
16     </item>
17 </Header>';
18 end;
19 /
PL/SQL procedure successfully completed.
SQL> --
SQL> select extractValue(value(seg), '/Segment/@type') att_name,
2         extractValue(value(seg), '/Segment/@id') att_value,
3         extractValue(value(item), '/item/@lineNumber') att_line
4    from table(xmlsequence(extract(xmltype(:xmltext), '/Header/item'))) item,
5         table(xmlsequence(extract(value(item), '/item/Segment'))) seg
6 /
ATT_NAME
ATT_VALUE
ATT_LINE
Action
Add
1
Business Owner
John Doe
1
Catalog Item Ordered
20677765
1
Asset Tag
ATT_NAME
ATT_VALUE
ATT_LINE
0060123
1
Action
Add
2
Business Owner
Jane Doe
2
Catalog Item Ordered
20688865
ATT_NAME
ATT_VALUE
ATT_LINE
2
Asset Tag
0061444
2
8 rows selected.
SQL> select seg.ATT_NAME, seg.ATT_VALUE, item.ITEM_NUMBER
2    from xmltable
3         (
4           '/Header/item'
5           passing xmltype(:xmltext)
6           columns
7           ITEM_NUMBER number(2) path '@lineNumber',
8           SEGMENT_XML xmltype path 'Segment'
9         ) item,
10         xmltable
11         (
12           '/Segment'
13           passing item.SEGMENT_XML
14           columns
15           ATT_NAME varchar2(32) path '@type',
16           ATT_VALUE varchar2(32) path '@id'
17         ) seg
18 /
ATT_NAME                         ATT_VALUE                        ITEM_NUMBER
Action                           Add                                        1
Business Owner                   John Doe                                   1
Catalog Item Ordered             20677765                                   1
Asset Tag                        0060123                                    1
Action                           Add                                        2
Business Owner                   Jane Doe                                   2
Catalog Item Ordered             20688865                                   2
Asset Tag                        0061444                                    2
8 rows selected.
SQL>

How to create a relational view base on an xmltype table which included sev

Hi,
I am using oracle 11.2.0.1.0.
how to create a relational view base on an xmltype table which content several different .xml files?
Thanks.
for examle:
SQL> SELECT OBJECT_VALUE FROM document;
Edited by: Cow on Jan 6, 2011 7:57 PM

For example I already have these three xml files inserted into the document xmltype table.
These xml files have same schemas. I have attached below.
I want to show all elements/attribute values in xml files to relational view.
Is this possible to create one big relational view to show everything
or I have to create three separate relation views then use UNION to put together? Thanks a lot. Cow
<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet href="http://www.accessdata.fda.gov/spl/stylesheet/spl.xsl" type="text/xsl"?>
<document xmlns="urn:hl7-org:v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:hl7-org:v3 http://localhost:8080/home/DEV/xsd/spl.xsd">
<id root="5ca4e3cb-7298-4948-8cc2-58e71ad32694"/>
</component>
</document>
<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet href="http://www.accessdata.fda.gov/spl/stylesheet/spl.xsl" type="text/xsl"?>
<document xmlns="urn:hl7-org:v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:hl7-org:v3 http://localhost:8080/home/DEV/xsd/spl.xsd">
</component>
</document>
Edited by: Cow on Jan 4, 2011 9:51 AM

Converting from a Business View connection to a non-Business View connectio

I have a report on our Crystal Reports Server that I need to move to a machine with Crystal Reports XI installed and no connection to the Business Objects Server.
When I create an ODBC connection pointing to the same table and then try to use Set Datasource Location to Update the Data Source I get an errormessage:
Converting from a Business View connection to a non-Business View connection is not supported.
What can I do? It is a complex report that I don't want to take the time and energy to rewrite.
Thank You for any answers.
<a href="http://farm4.static.flickr.com/3234/2942702182_72365cc04f_o.jpg">Screen Shot</a>

Hello Brundibar,
I recommend to post this query to the [Universe Designer and Business Views Designer|Semantic Layer; forum.
This forum is dedicated to topics related to the universes and business views.
It is monitored by qualified technicians and you will get a faster response there.
Also, all Universe Designer and Business Views Designer queries remain in one place and thus can be easily searched in one place.
Best regards,
Falk

Getting error while converting xml to xsd

I am getting error"The table (citeinfo) cannot be the child table to itself in nested relations"
at "http://www.flame-ware.com/products/xml-2-xsd/Default.aspx", while converting
xml into xsd so i can register.
Wherever citeinfo is there it is giving error.
Please look at bold and suggest solution
thank you
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE metadata SYSTEM "http://www.fgdc.gov/metadata/fgdc-std-001-1998.dtd">
<metadata>
<idinfo>
<citation>
*<citeinfo>(1)*<origin>MRF</origin>
<pubdate>20040512</pubdate>
<pubtime>09000000</pubtime>
<title>BAS_EASEMENT</title>
<edition>1</edition>
<geoform>vector digital data</geoform>
<serinfo>
<sername>One</sername>
<issue>One</issue>
</serinfo>
<pubinfo>
<pubplace>San Jose</pubplace>
<publish>CITY</publish>
</pubinfo>
<othercit>None</othercit>
<onlink>www.mrf.com</onlink>
<lworkcit>
*<citeinfo>(2)*<pubdate>20040512</pubdate>
<pubtime>09000000</pubtime>
<edition>1</edition>
<geoform>vector digital data</geoform>
<serinfo>
<sername>One</sername>
<issue>One</issue>
</serinfo>
<pubinfo>
<pubplace>San Jose</pubplace>
<publish>CITY</publish>
</pubinfo>
<othercit>None</othercit>
<onlink>www.mrf.com</onlink>
*</citeinfo>(2)*</lworkcit>
*</citeinfo>(1)*</citation>
<descript>
<abstract>Easement</abstract>
<purpose>E911 System</purpose>
<supplinf>None</supplinf>
</descript>
<timeperd>
<timeinfo>
<sngdate>
<caldate>20040512</caldate>
<time>09000000</time>
</sngdate>
</timeinfo>
<current>publication date</current>
</timeperd>
<status>
<progress>Complete</progress>
<update>As needed</update>
</status>
<spdom>
<bounding>
<westbc>
-122.339</westbc>
<eastbc>
-121.0716</eastbc>
<northbc>
37.4900</northbc>
<southbc>
36.9086</southbc>
</bounding>
</spdom>
<keywords>
<theme>
<themekt>Easement</themekt>
<themekey>Easement</themekey>
</theme>
<place>
<placekt>San Jose</placekt>
<placekey>San Jose</placekey>
</place>
<stratum>
<stratkt>None</stratkt>
<stratkey>None</stratkey>
</stratum>
<temporal>
<tempkt>None</tempkt>
<tempkey>None</tempkey>
</temporal>
</keywords>
<accconst>None</accconst>
<useconst>None</useconst>
<ptcontac>
<cntinfo>
<cntperp>
<cntper>Earl Harris</cntper>
<cntorg>City of San Jose</cntorg>
</cntperp>
<cntpos>Project Manager</cntpos>
<cntaddr>
<addrtype>Actual Address</addrtype>
<address>801 N 1 ST</address>
<city>San Jose</city>
<state>CA</state>
<postal>90000</postal>
<country>USA</country>
</cntaddr>
<cntvoice>408.277.5626</cntvoice>
<cnttdd>408.277.5626</cnttdd>
<cntfax>408.298.8382</cntfax>
<cntemail>[email protected]</cntemail>
<hours>9-5</hours>
<cntinst>None</cntinst>
</cntinfo>
</ptcontac>
<browse>
<browsen>None</browsen>
<browsed>None</browsed>
<browset>None</browset>
</browse>
<datacred>Unknown</datacred>
<secinfo>
<secsys>FGDC</secsys>
<secclass>Confidential</secclass>
<sechandl>Confidential Information</sechandl>
</secinfo>
<native>Microsoft Windows NT Version 4.0 (Build 1381) Service Pack 6; ESRI ArcCatalog 8.3.0.800</native>
<crossref>
*<citeinfo>(3)*<origin>MRF</origin>
<pubdate>20040512</pubdate>
<pubtime>09000000</pubtime>
<title>BAS_EASEMENT</title>
<edition>1</edition>
<geoform>vector digital data</geoform>
<serinfo>
<sername>one</sername>
<issue>one</issue>
</serinfo>
<pubinfo>
<pubplace>San Jose</pubplace>
<publish>CITY</publish>
</pubinfo>
<othercit>None</othercit>
<onlink>www.mrf.com</onlink>
<lworkcit>
*<citeinfo>(*4)
<origin>MRF</origin>
<pubdate>20040512</pubdate>
<pubtime>09000000</pubtime>
<title>BAS_EASEMENT</title>
<edition>1</edition>
<geoform>vector digital data</geoform>
<serinfo>
<sername>one</sername>
<issue>one</issue>
</serinfo>
<pubinfo>
<pubplace>San Jose</pubplace>
<publish>CITY</publish>
</pubinfo>
<othercit>None</othercit>
<onlink>www.mrf.com</onlink>
*</citeinfo>(*3)
</lworkcit>
*</citeinfo*>(4)
</crossref>
</idinfo>
<dataqual>
<attracc>
<attraccr>All the related attributes are populated 100%.</attraccr>
<qattracc>
<attraccv>100%</attraccv>
<attracce>All the related attributes are populated 100%.</attracce>
</qattracc>
</attracc>
<logic>100% adjusted,modified and captured easements.</logic>
<complete>100%</complete>
<posacc>
<horizpa>
<horizpar>Easement accuracy is 2 ft for 3" pixel Orthophoto, 5 ft for 9" pixel Orthophoto.</horizpar>
<qhorizpa>
<horizpav>2 ft for 3" pixel Orthophoto, 5 ft for 9" pixel Orthophoto.</horizpav>
<horizpae>Easement accuracy is 2 ft for 3" pixel Orthophoto, 5 ft for 9" pixel Orthophoto.</horizpae>
</qhorizpa>
</horizpa>
<vertacc>
<vertaccr>Easement accuracy is 2 ft for 3" pixel Orthophoto, 5 ft for 9" pixel Orthophoto.</vertaccr>
<qvertpa>
<vertaccv>2 ft for 3" pixel Orthophoto, 5 ft for 9" pixel Orthophoto.</vertaccv>
<vertacce>Easement accuracy is 2 ft for 3" pixel Orthophoto, 5 ft for 9" pixel Orthophoto.</vertacce>
</qvertpa>
</vertacc>
</posacc>
<lineage>
<srcinfo>
<srccite>
<*citeinfo>(5)*<origin>MRF</origin>
<pubdate>20040512</pubdate>
<pubtime>09000000</pubtime>
<title>BAS_EASEMENT</title>
<edition>1</edition>
<geoform>vector digital data</geoform>
<serinfo>
<sername>one</sername>
<issue>one</issue>
</serinfo>
<pubinfo>
<pubplace>San Jose</pubplace>
<publish>CITY</publish>
</pubinfo>
<othercit>None</othercit>
<onlink>www.mrf.com</onlink>
<lworkcit>
*</citeinfo>(5*)*<citeinfo>(6)*
<origin>MRF</origin>
<pubdate>20040512</pubdate>
<pubtime>09000000</pubtime>
<title>BAS_EASEMENT</title>
<edition>1</edition>
<geoform>vector digital data</geoform>
<serinfo>
<sername>one</sername>
<issue>one</issue>
</serinfo>
<pubinfo>
<pubplace>San Jose</pubplace>
<publish>CITY</publish>
</pubinfo>
<othercit>None</othercit>
<onlink>www.mrf.com</onlink>
*</citeinfo>(5)*
</lworkcit>
*</citeinfo>(6)*
</srccite>
<srcscale>24000</srcscale>
<typesrc>FTP</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>20040512</caldate>
<time>09000000</time>
</sngdate>
</timeinfo>
<srccurr>publication date</srccurr>
</srctime>
<srccitea>Unknown</srccitea>
<srccontr>MGE dgn contains easement data.</srccontr>
</srcinfo>
<procstep>
<procdesc>Easement data is reprojected from NAD27 to NAD83.
Further it is adjusted as per the spatial alignment shown in MGE input dgn.</procdesc>
<srcused>Easement</srcused>
<procdate>20040512</procdate>
<proctime>09000000</proctime>
<srcprod>BAS_EASEMENT</srcprod>
<proccont>
<cntinfo>
<cntperp>
<cntper>Mahesh P Choudhury</cntper>
<cntorg>Rolta International Inc.</cntorg>
</cntperp>
<cntpos>Project Manager</cntpos>
<cntaddr>
<addrtype>mailing address</addrtype>
<address>5865 North Point Parkway</address>
<city>Alpharetta</city>
<state>GA</state>
<postal>30022</postal>
<country>USA</country>
</cntaddr>
<cntvoice>678.942.5015</cntvoice>
<cnttdd>678.942.5015</cnttdd>
<cntfax>678.942.5001</cntfax>
<cntemail>[email protected]</cntemail>
<hours>8-5</hours>
<cntinst>None</cntinst>
</cntinfo>
</proccont>
</procstep>
</lineage>
<cloud>Unknown</cloud>
</dataqual>
<spdoinfo>
<indspref>unknown</indspref>
<direct>Vector</direct>
<ptvctinf>
<sdtsterm>
<sdtstype>String</sdtstype>
<ptvctcnt>2203</ptvctcnt>
</sdtsterm>
</ptvctinf>
</spdoinfo>
<spref>
<horizsys>
<geograph>
<latres>5.5</latres>
<longres>5.5</longres>
<geogunit>Decimal degrees</geogunit>
</geograph>
<geodetic>
<horizdn>North American Datum of 1983</horizdn>
<ellips>Geodetic Reference System 80</ellips>
<semiaxis>1</semiaxis>
<denflat>2</denflat>
</geodetic>
</horizsys>
<vertdef>
<altsys>
<altdatum>North American Vertical Datum of 1988</altdatum>
<altres>0.002</altres>
<altunits>sf</altunits>
<altenc>Attribute values</altenc>
</altsys>
<depthsys>
</depthsys>
</vertdef>
</spref>
<eainfo>
<detailed>
<enttyp>
<enttypl>
BAS_EASEMENT</enttypl>
<enttypd>Contains geometry and attributes for easement segments</enttypd>
<enttypds>Data Model Dictionary</enttypds>
</enttyp>
<attr>
<attrlabl>BAS_EASEMENT_ID</attrlabl>
<attrdef>Migrated from STREET table ID column. After all the existing IDs have been migrated, assign ID #70,001 onwards for the new easement (or what ever # is available sequentially using, street centerline #) ID's.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
<begdatea>20040512</begdatea>
<enddatea>20040512</enddatea>
<attrvai>
<attrva>100</attrva>
<attrvae>Unknown</attrvae>
</attrvai>
<attrmfrq>As needed</attrmfrq>
</attr>
<attr>
<attrlabl>SURVEY_LENGTH</attrlabl>
<attrdef>Actual length of easement (international foot).This DOES take into account the State Plane Coordinate System.</attrdef>
<attrdefs>Data Model Dictionary</attrdefs>
<attrdomv>
<udom>Surveyed segment length</udom>
</attrdomv>
<begdatea>20040512</begdatea>
<enddatea>20040512</enddatea>
<attrvai>
<attrva>100</attrva>
<attrvae>Unknown</attrvae>
</attrvai>
<attrmfrq>As needed</attrmfrq>
</attr>
<attr>
<attrlabl>ROW_WIDTH</attrlabl>
<attrdef>Width of right-of-way (international feet)</attrdef>
<attrdefs>Data Model Dictionary</attrdefs>
<attrdomv>
<udom>Right-of-way width</udom>
</attrdomv>
<begdatea>20040512</begdatea>
<enddatea>20040512</enddatea>
<attrvai>
<attrva>100</attrva>
<attrvae>Updated from ROW files</attrvae>
</attrvai>
<attrmfrq>As needed</attrmfrq>
</attr>
<attr>
<attrlabl>FROM_EASEMENT_ID</attrlabl>
<attrdef>Self-referential key to BAS_EASEMENT table, that contains locational information about the easement that the easement is digitized from. "FROM" is the starting point of digitization</attrdef>
<attrdefs>Data Model Dictionary</attrdefs>
<attrdomv>
<udom>IDs of an easement to which FROM side of this easement is connected.</udom>
</attrdomv>
<begdatea>20040512</begdatea>
<enddatea>20040512</enddatea>
<attrvai>
<attrva>100</attrva>
<attrvae>Unknown</attrvae>
</attrvai>
<attrmfrq>As needed</attrmfrq>
</attr>
<attr>
<attrlabl>FROM_STREET_ID</attrlabl>
<attrdef>Foreign key to BAS_STREET_SEGMENT table, that contains locational information about street segment that the easement is digitized from. "FROM" is the starting point of digitization</attrdef>
<attrdefs>Data Model Dictionary</attrdefs>
<attrdomv>
<udom>IDs of an street segment to which FROM side of this easement is connected.</udom>
</attrdomv>
<begdatea>20040512</begdatea>
<enddatea>20040512</enddatea>
<attrvai>
<attrva>100</attrva>
<attrvae>Unknown</attrvae>
</attrvai>
<attrmfrq>As needed</attrmfrq>
</attr>
<attr>
<attrlabl>TO_EASEMENT_ID</attrlabl>
<attrdef>Self-referential key to BAS_EASEMENT table, that contains locational information about the easement that the easement is digitized to. "TO" is the ending point of digitization.</attrdef>
<attrdefs>Data Model Dictionary</attrdefs>
<attrdomv>
<udom>IDs of an easement to which TO side of this easement is closely located.</udom>
</attrdomv>
<begdatea>20040512</begdatea>
<enddatea>20040512</enddatea>
<attrvai>
<attrva>100</attrva>
<attrvae>Unknown</attrvae>
</attrvai>
<attrmfrq>As needed</attrmfrq>
</attr>
<attr>
<attrlabl>TO_STREET_ID</attrlabl>
<attrdef>Foreign key to BAS_STREET_SEGMENT table, that contains locational information about street segment that the easement is digitized to. "TO" is the ending point of digitization.</attrdef>
<attrdefs>Data Model Dictionary</attrdefs>
<attrdomv>
<udom>IDs of an street segment to which TO side of this easement is closely located.</udom>
</attrdomv>
<begdatea>20040512</begdatea>
<enddatea>20040512</enddatea>
<attrvai>
<attrva>100</attrva>
<attrvae>Unknown</attrvae>
</attrvai>
<attrmfrq>As needed</attrmfrq>
</attr>
<attr>
<attrlabl>OTH_PROCESSING_STATUS_ID</attrlabl>
<attrdef>ID of the status/result of last run batch job.</attrdef>
<attrdefs>Data Model Dictionary</attrdefs>
<attrdomv>
<udom>Migrated from PLAN_1 in MGE tables and GIS_TRACKING.MDB Access Database</udom>
</attrdomv>
<begdatea>20040512</begdatea>
<enddatea>20040512</enddatea>
<attrvai>
<attrva>100</attrva>
<attrvae>Unknown</attrvae>
</attrvai>
<attrmfrq>As needed</attrmfrq>
</attr>
<attr>
<attrlabl>MUNICIPALITY_NAME</attrlabl>
<attrdef>Name of municipality in which the easement primarily resides.</attrdef>
<attrdefs>Data Model Dictionary</attrdefs>
<attrdomv>
<codesetd>
<codesetn>MUNICIPALITY_NAME_DOMAIN</codesetn>
<codesets>Data Model Dictionary</codesets>
</codesetd>
</attrdomv>
<begdatea>20040512</begdatea>
<enddatea>20040512</enddatea>
<attrvai>
<attrva>100</attrva>
<attrvae>Updated using Municipal boundary source data.</attrvae>
</attrvai>
<attrmfrq>As needed</attrmfrq>
</attr>
<attr>
<attrlabl>RECORD_DRAWING_FLAG</attrlabl>
<attrdef>Engineering plan that has been accepted by the City of San Jose (Y or N).</attrdef>
<attrdefs>Data Model Dictionary</attrdefs>
<attrdomv>
<udom>USERNAME who last modified this record</udom>
</attrdomv>
<begdatea>20040512</begdatea>
<enddatea>20040512</enddatea>
<attrvai>
<attrva>100</attrva>
<attrvae>Updated using source data.</attrvae>
</attrvai>
<attrmfrq>As needed</attrmfrq>
</attr>
<attr>
<attrlabl>ACQUISITION_DATE</attrlabl>
<attrdef>Official date engineering plan accepted by the City of San Jose on this date</attrdef>
<attrdefs>Data Model Dictionary</attrdefs>
<attrdomv>
<udom>Date/Time stamp of last record modification</udom>
</attrdomv>
<begdatea>20040512</begdatea>
<enddatea>20040512</enddatea>
<attrvai>
<attrva>100</attrva>
<attrvae>Updated using source data.</attrvae>
</attrvai>
<attrmfrq>As needed</attrmfrq>
</attr>
<attr>
<attrlabl>GEO_MOD_DATE</attrlabl>
<attrdef>Time stamp when GEOMETRY column was last modified.</attrdef>
<attrdefs>Data Model Dictionary</attrdefs>
<attrdomv>
<udom>Time stamp when GEOMETRY column was last modified.</udom>
</attrdomv>
<begdatea>20040512</begdatea>
<enddatea>20040512</enddatea>
<attrvai>
<attrva>100</attrva>
<attrvae>Data modified date.</attrvae>
</attrvai>
<attrmfrq>As needed</attrmfrq>
</attr>
<attr>
<attrlabl>GDO_GEOMETRY</attrlabl>
<attrdef>Contains spatial data with true arc geometry.</attrdef>
<attrdefs>Data Model Dictionary</attrdefs>
<attrdomv>
<udom>Oracle Spatial Geometry Data - True Arcs</udom>
</attrdomv>
<begdatea>20040512</begdatea>
<enddatea>20040512</enddatea>
<attrvai>
<attrva>100</attrva>
<attrvae>Unknown</attrvae>
</attrvai>
<attrmfrq>As needed</attrmfrq>
</attr>
<attr>
<attrlabl>MAN_OVERRIDE</attrlabl>
<attrdef>This flag is 'N' by default. If this flag is set to 'Y' no unattended batch process will touch it ever again.</attrdef>
<attrdefs>Data Model Dictionary</attrdefs>
<attrdomv>
<udom>Flag set for batch process</udom>
</attrdomv>
<begdatea>20040512</begdatea>
<enddatea>20040512</enddatea>
<attrvai>
<attrva>100</attrva>
<attrvae>Unknown</attrvae>
</attrvai>
<attrmfrq>As needed</attrmfrq>
</attr>
<attr>
<attrlabl>MESSAGE</attrlabl>
<attrdef>Message from automated batch process to operator; can be "OK", or error message, or "to be checked", etc.</attrdef>
<attrdefs>data model dictionary</attrdefs>
<attrdomv>
<udom>GDO_GEOMETRY.LEN</udom>
</attrdomv>
<begdatea>20040512</begdatea>
<enddatea>20040512</enddatea>
<attrvai>
<attrva>100</attrva>
<attrvae>Unknown</attrvae>
</attrvai>
<attrmfrq>As needed</attrmfrq>
</attr>
<attr>
<attrlabl>OTH_PLAN_CREATED</attrlabl>
<attrdef>PLAN_1 in STREET table should be migrated to BAS_EASEMENT table OTH_PLAN_ID_CREATED column. This value should also be entered into the OTH_PLAN table PLAN_NAME column if not present.</attrdef>
<attrdefs>Data Dictionary</attrdefs>
<attrdomv>
<codesetd>
<codesetn>OTH_PLAN_DOMAIN</codesetn>
<codesets>data model dictionary</codesets>
</codesetd>
</attrdomv>
<begdatea>20040512</begdatea>
<enddatea>20040512</enddatea>
<attrvai>
<attrva>100</attrva>
<attrvae>Unknown</attrvae>
</attrvai>
<attrmfrq>As needed</attrmfrq>
</attr>
<attr>
<attrlabl>OTH_PLAN_MODIFIED</attrlabl>
<attrdef>PLAN_2 in STREET table should be migrated to BAS_EASEMENT table OTH_PLAN_ID_MODIFIED column. This value should also be entered into the OTH_PLAN table PLAN_NAME column if not present</attrdef>
<attrdefs>Data dictionary</attrdefs>
<attrdomv>
<codesetd>
<codesetn>OTH_PLAN_DOMAIN</codesetn>
<codesets>data model dictionary</codesets>
</codesetd>
</attrdomv>
<begdatea>20040512</begdatea>
<enddatea>20040512</enddatea>
<attrvai>
<attrva>100</attrva>
<attrvae>Unknown</attrvae>
</attrvai>
<attrmfrq>As needed</attrmfrq>
</attr>
<attr>
<attrlabl>LINEAGE_ID</attrlabl>
<attrdef>Artificial Numeric Identifier; Assigned to any graphical object; Unique throughout the system. Shared among tables. This column would also be used by EDL Administrator for lineage.</attrdef>
<attrdefs>Data dictionary</attrdefs>
<attrdomv>
<udom>Artificial Numeric Identifier</udom>
</attrdomv>
<begdatea>20040512</begdatea>
<enddatea>20040512</enddatea>
<attrvai>
<attrva>100</attrva>
<attrvae>Unknown</attrvae>
</attrvai>
<attrmfrq>As needed</attrmfrq>
</attr>
<attr>
<attrlabl>GDO_GEOMETRY.LEN</attrlabl>
<attrdef>Created default</attrdef>
<attrdefs>Data model</attrdefs>
<attrdomv>
<udom>unknown</udom>
</attrdomv>
<begdatea>20040512</begdatea>
<enddatea>20040512</enddatea>
<attrvai>
<attrva>100</attrva>
<attrvae>Unknown</attrvae>
</attrvai>
<attrmfrq>As needed</attrmfrq>
</attr>
</detailed>
<overview>
<eaover>Populated using MRF Tools</eaover>
<eadetcit>Various sources</eadetcit>
</overview>
</eainfo>
<distinfo>
<distrib>
<cntinfo>
<cntperp>
<cntper>Earl Harris</cntper>
<cntorg>City of San Jose</cntorg>
</cntperp>
<cntpos>Project Manager</cntpos>
<cntaddr>
<addrtype>Actual Address</addrtype>
<address>801 N 1 ST</address>
<city>San Jose</city>
<state>CA</state>
<postal>90000</postal>
<country>USA</country>
</cntaddr>
<cntvoice>408.277.5626</cntvoice>
<cnttdd>408.277.5626</cnttdd>
<cntfax>408.298.8382</cntfax>
<cntemail>[email protected]</cntemail>
<hours>9-5</hours>
<cntinst>None</cntinst>
</cntinfo>
</distrib>
<resdesc>Unknown</resdesc>
<distliab>Unknown</distliab>
<stdorder>
<digform>
<digtinfo>
<formname>GM Pro Access</formname>
<formvern>5.1</formvern>
<formspec>GM Pro 5.1</formspec>
<formcont>Easement data</formcont>
<filedec>no compression applied</filedec>
<transize>60</transize>
</digtinfo>
<digtopt>
<onlinopt>
<computer>
<networka>
<networkr>FTP</networkr>
</networka>
</computer>
<accinstr>FTP</accinstr>
<oncomp>FTP server</oncomp>
</onlinopt>
<offoptn>
<offmedia>None</offmedia>
<reccap>
<recden>1</recden>
<recdenu>None</recdenu>
</reccap>
<recfmt>None</recfmt>
<compat>None</compat>
</offoptn>
</digtopt>
</digform>
<fees>Unknown</fees>
<ordering>Unknown</ordering>
<turnarnd>Unknown</turnarnd>
</stdorder>
<custom>Unknown</custom>
<techpreq>Unknown</techpreq>
<availabl>
<timeinfo>
<sngdate>
<caldate>20040512</caldate>
<time>09000000</time>
</sngdate>
</timeinfo>
</availabl>
</distinfo>
<metainfo>
<metd>20040512</metd>
<metrd>20040512</metrd>
<metfrd>20040519</metfrd>
<metc>
<cntinfo>
<cntperp>
<cntper>Mahesh P Choudhury</cntper>
<cntorg>Rolta International Inc</cntorg>
</cntperp>
<cntpos>Project Manager</cntpos>
<cntaddr>
<addrtype>mailing address</addrtype>
<address>5865 North Point Parkway</address>
<city>Alpharetta</city>
<state>GA</state>
<postal>30022</postal>
<country>USA</country>
</cntaddr>
<cntvoice>678.942.5015</cntvoice>
<cnttdd>678.942.5015</cnttdd>
<cntfax>678.942.5001</cntfax>
<cntemail>[email protected]</cntemail>
<hours>8-5</hours>
<cntinst>None</cntinst>
</cntinfo>
</metc>
<metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn>
<metstdv>FGDC-STD-001-1998</metstdv>
<mettc>local time</mettc>
<metac>Unknown</metac>
<metuc>Unknown</metuc>
<metsi>
<metscs>Unknown</metscs>
<metsc>Confidential</metsc>
<metshd>Unknown</metshd>
</metsi>
<metextns>
<onlink>http://www.esri.com/metadata/esriprof80.html</onlink>
<metprof>ESRI Metadata Profile</metprof>
</metextns>
</metainfo>
</metadata>

I am having error while registering as undefined element for citeinfo, timeinfo and cntinfo as shown below
Please could you help me solve.
thanks
</xs:appinfo>
          </xs:annotation>
</xs:element>
<xs:complexType name="citationType">
<xs:sequence>
*<xs:element ref="citeinfo"/>*
</xs:sequence>
</xs:complexType>
SQL> BEGIN
2 DBMS_XMLSCHEMA.registerSchema(
3 SCHEMAURL => 'fgdc-std-001-1998-sect011.xsd',
4 SCHEMADOC => bfilename('XMLDIR','fgdc-std-001-1998-sect011.xsd'),
5 CSID => nls_charset_id('UTF8'));
6 END;
7 /
BEGIN
ERROR at line 1:
ORA-31154: invalid XML document
ORA-19202: Error occurred in XML processing
LSX-00021: undefined element "citeinfo"
ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 37
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 61
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 126
ORA-06512: at line 2
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:complexType name="timeperdType">
<xs:sequence>
*<xs:element ref="timeinfo"/>     *
<xs:element ref="current"/>
</xs:sequence>
</xs:complexType>
<xs:element name="current" type="currentType">
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:complexType name="ptcontacType">
<xs:sequence>
*<xs:element ref="cntinfo"/>     *
</xs:sequence>
     </xs:complexType>
<xs:element name="browse" type="browseType">
<xs:annotation>

Simple transformation error in converting XML to internal table

Hi Team,
I have an issue, its working in Dev, QA, and Prod in PI 7.0, once we upgrade it to PI 7.1 I'm getting the below mention error,
Unknown Simple transformation error in converting XML to internal table
Application error in mapping program ZF_INT006_FILE_TO_SAP_FILE, error code: , error text: Unknown Simple transformation error in converting XML to internal table An exception has occurred.
Can any one suggest related notes are suggestion.
appericate in advance for the solutions which you all provide me
Thank you
Venkat Anil

Check the flag "use SAP XML toolkit" for the operation mapping and try, if that works then.
Check the flag for all XSLT and Java mappings which is migrated from PI 7.0

Problems with relational view

I'm a newbie at this so any help is greatly appreciated!
I have an xml document which contains many rows:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<echoems:ECHOMetrics xmlns:echoems="http://myURL/myFilename.xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://myURL/myFilename.xsd
http://myURL/myFilename.xsd">
<OrderMetrics>
<OrderItemMetric>
<submissionDateTime>2007-12-10T15:08:10.000</submissionDateTime>
<requestor>user1</requestor>
<product>123</product>
</OrderItemMetric>
<OrderItemMetric>
<submissionDateTime>2007-12-10T15:09:15.000</submissionDateTime>
<requestor>0.0.0.0</requestor>
<product>ABC</product>
</OrderItemMetric>
<OrderItemMetric>
<submissionDateTime>2007-12-17T13:41:41.000</submissionDateTime>
<requestor>user3</requestor>
<product>XYZ</product>
</OrderItemMetric>
</OrderMetrics>
</echoems:ECHOMetrics>
I've registered the schema, created the corresponding xmltype table based on the schema, and loaded the data with no problem.
I am trying to create a relational view of the data:
CREATE OR REPLACE view myView
(submissionDateTime, requestor, product)
AS
SELECT
extractvalue
(object_value,
'echoems:ECHOMetrics/OrderMetrics/OrderItemMetric/submissionDateTime',
'xmlns:echoems="http://myURL/myFilename.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"'
) as submissionDateTime,
extractvalue
(object_value,
'echoems:ECHOMetrics/OrderMetrics/OrderItemMetric/requestor',
'xmlns:echoems="http://myURL/myFilename.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"'
) as requestor,
extractvalue
(object_value,
'echoems:ECHOMetrics/OrderMetrics/OrderItemMetric/product',
'xmlns:echoems="http://myURL/myFilename.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"'
) as product
FROM myXMLTypeTable;
However, I believe I must be querying the data for creation of the view incorrectly. My query:
select count(*) from myXMLTypeTable;
returns 1 record, I was hoping for 3 based on the 3 records contained in the file.
Likewise, when I try to query the view, I get the following error:
select product from myXMLTypeTable;
ERROR at line 1:
ORA-01427: single-row subquery returns more than one row
Am I loading the xml data wrong or querying from the view wrong or both?
Thank you in advance for any help.

Thank you for your help. I've been doing some research on the XMLTable syntax but am having a difficult time getting it right. I've tried a couple of different things but not working.
Here's what I'm trying:
CREATE OR REPLACE view myView
(submissionDateTime, requestor, product)
AS
select xtab.column_value from echoXML3,
XMLTable(xmlnamespaces('http://myURL/myFilename.xsd' as e),
'for $i in echoems:ECHOMetrics/OrderMetrics/OrderItemMetric
return $i/e:submissionDateTime,
$i/e:requestor,
$i/e:product'
PASSING OBJECT_VALUE) xtab;
getting this error:
ERROR at line 4:
ORA-19228: XP0008 - undeclared identifier: prefix 'echoems' local-name
'echoems:ECHOMetrics'
Not sure what I'm doing wrong. I appreciate any further guidance.

Create Relational View got error: ORA-19276: XPST0005 - XPath step specifie

Hi expert,
I am using Oracle 11.2.0.1.0 XML DB.
I am successfully registered schema and generated a table DOCUMENT.
I have succfully inserted 12 .xml files to this table.
SQL> SELECT OBJECT_VALUE FROM document;
OBJECT_VALUE
<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet href="http://www.accessdata.fda.gov/spl/stylesheet/spl.xsl" type="text/xsl"?>
<document xmlns="urn:hl7-org:v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:hl7-org:v3 http://localhost:8080/home/DEV/xsd/spl.xsd">
<id root="03d6a2cd-fdda-4fe1-865d-da0db9212f34"/>
<code code="51725-0" codeSystem="2.16.840.1.113883.6.1" displayName="ESTABLISHMENT REGISTRATION"/>
</component>
</document>
then I tried to create a create Relational View base on one inserted .xml file I got error:
ERROR at line 3:
ORA-19276: XPST0005 - XPath step specifies an invalid element/attribute name: (document)
is there anyone know what was wrong?
Thanks a lot!
Cow
Edited by: Cow on Feb 15, 2011 8:58 PM
Edited by: Cow on Feb 21, 2011 6:59 AM

These kinds of issues, you will have to solve by joining multiple resultsets or passing fragments to the next XMLTABLE statement and building redundancy via the ORDINALITY clause (which results a NUMBER datatype)
For example
A "transaction" can have multiple "status"ses which can have multiple "reason"s
WITH XTABLE
AS
(SELECT xmltype('<TRANSACTION>
                    <PFL_ID>123456789</PFL_ID>
                    <PMI_ID>1</PMI_ID><PII_ID>1</PII_ID>
                    <ID>1</ID>
                    <INSTR_ID>MARCO_003</INSTR_ID>
                    <E_TO_E_ID>MARCO_004</E_TO_E_ID>
                    <INSTD_AMT>10</INSTD_AMT>
                    <INSTD_AMT_CCY>EUR</INSTD_AMT_CCY>
                    <STATUS>
                        <PFL_ID>123456789</PFL_ID>
                        <PMI_ID>1</PMI_ID><PII_ID>1</PII_ID>
                        <TXI_ID>1</TXI_ID>
                        <ID>1</ID>
                        <PMT_TX_STS_UTC_DT>2011-02-15</PMT_TX_STS_UTC_DT>
                           <REASON>
                              <ID>1000</ID>
                              <STS_RSN_PRTRY>MG001</STS_RSN_PRTRY>
                           </REASON>
                           <REASON>
                              <ID>2000</ID>
                              <STS_RSN_PRTRY>IS000</STS_RSN_PRTRY>
                           </REASON>
                     </STATUS>
                  </TRANSACTION>') as XMLCOLUMN
FROM DUAL
SELECT STS_ID             as STATUS_ID,
       STS_PFL_ID,
       STS_PMI_ID,
       STS_TXI_ID,
       RSN_ID             as REASON_ID,
       RSN_STS_RSN_PRTRY,
       RSN_XML_POS        as POSITION
FROM XTABLE
,     XMLTABLE ('/TRANSACTION/STATUS'
                PASSING XMLCOLUMN
                COLUMNS
                    STS_PFL_ID         NUMBER(10)    path 'PFL_ID'
                  , STS_PMI_ID         NUMBER(10)    path 'PMI_ID'
                  , STS_TXI_ID         NUMBER(10)    path 'TXI_ID'
                  , STS_ID             VARCHAR2(10) path 'ID'
                  , XML_REASONS        XMLTYPE       path 'REASON'
                  ) sts
,     XMLTABLE ('/REASON'
                PASSING sts.XML_REASONS
                COLUMNS
                    RSN_XML_POS        FOR ORDINALITY
                  , RSN_ID             VARCHAR2(10) path 'ID'
                  , RSN_STS_RSN_PRTRY VARCHAR2(10) path 'STS_RSN_PRTRY'
                  ) rsnWill give you the following output (in your case DON"T forget to buildin the namespace references)
SQL> WITH XTABLE
2 AS
3   (SELECT xmltype('<TRANSACTION>
4             <PFL_ID>123456789</PFL_ID>
5             <PMI_ID>1</PMI_ID><PII_ID>1</PII_ID>
6             <ID>1</ID>
7             <INSTR_ID>MARCO_003</INSTR_ID>
8             <E_TO_E_ID>MARCO_004</E_TO_E_ID>
9             <INSTD_AMT>10</INSTD_AMT>
10             <INSTD_AMT_CCY>EUR</INSTD_AMT_CCY>
11            <STATUS>
12              <PFL_ID>123456789</PFL_ID>
13              <PMI_ID>1</PMI_ID><PII_ID>1</PII_ID>
14              <TXI_ID>1</TXI_ID>
15              <ID>1</ID>
16              <PMT_TX_STS_UTC_DT>2011-02-15</PMT_TX_STS_UTC_DT>
17                <REASON>
18                  <ID>1000</ID>
19                  <STS_RSN_PRTRY>MG001</STS_RSN_PRTRY>
20                </REASON>
21                <REASON>
22                   <ID>2000</ID>
23                   <STS_RSN_PRTRY>IS000</STS_RSN_PRTRY>
24                </REASON>
25              </STATUS>
26           </TRANSACTION>') as XMLCOLUMN
27   FROM DUAL
28   )
29 SELECT STS_ID             as STATUS_ID,
30         STS_PFL_ID,
31         STS_PMI_ID,
32         STS_TXI_ID,
33         RSN_ID             as REASON_ID,
34         RSN_STS_RSN_PRTRY,
35         RSN_XML_POS        as POSITION
36 FROM XTABLE
37 ,     XMLTABLE ('/TRANSACTION/STATUS'
38                  PASSING XMLCOLUMN
39              COLUMNS
40                  STS_PFL_ID         NUMBER(10)    path 'PFL_ID'
41                , STS_PMI_ID         NUMBER(10)    path 'PMI_ID'
42                , STS_TXI_ID         NUMBER(10)    path 'TXI_ID'
43                , STS_ID             VARCHAR2(10) path 'ID'
44                , XML_REASONS        XMLTYPE       path 'REASON'
45            ) sts
46 ,     XMLTABLE ('/REASON'
47                  PASSING sts.XML_REASONS
48              COLUMNS
49                  RSN_XML_POS        FOR ORDINALITY
50                , RSN_ID             VARCHAR2(10) path 'ID'
51                , RSN_STS_RSN_PRTRY VARCHAR2(10) path 'STS_RSN_PRTRY'
52            ) rsn
53 ;
STATUS_ID STS_PFL_ID STS_PMI_ID STS_TXI_ID REASON_ID RSN_STS_RS   POSITION
1           123456789          1          1 1000       MG001               1
1           123456789          1          1 2000       IS000               2
2 rows selected.If I wouldn't have done that then I would have got your result which fails with your error:
- ORA-19279 - XQuery dynamic type mismatch: expected singleton sequence - got multi-item sequence
SQL> WITH XTABLE
2 AS
3   (SELECT xmltype('<TRANSACTION>
4             <PFL_ID>123456789</PFL_ID>
5             <PMI_ID>1</PMI_ID><PII_ID>1</PII_ID>
6             <ID>1</ID>
7             <INSTR_ID>MARCO_003</INSTR_ID>
8             <E_TO_E_ID>MARCO_004</E_TO_E_ID>
9             <INSTD_AMT>10</INSTD_AMT>
10             <INSTD_AMT_CCY>EUR</INSTD_AMT_CCY>
11            <STATUS>
12              <PFL_ID>123456789</PFL_ID>
13              <PMI_ID>1</PMI_ID><PII_ID>1</PII_ID>
14              <TXI_ID>1</TXI_ID>
15              <ID>1</ID>
16              <PMT_TX_STS_UTC_DT>2011-02-15</PMT_TX_STS_UTC_DT>
17                <REASON>
18                  <ID>1000</ID>
19                  <STS_RSN_PRTRY>MG001</STS_RSN_PRTRY>
20                </REASON>
21                <REASON>
22                   <ID>2000</ID>
23                   <STS_RSN_PRTRY>IS000</STS_RSN_PRTRY>
24                </REASON>
25              </STATUS>
26           </TRANSACTION>') as XMLCOLUMN
27   FROM DUAL
28   )
29 SELECT STS_ID             as STATUS_ID,
30         STS_PFL_ID,
31         STS_PMI_ID,
32         STS_TXI_ID,
33         RSN_ID             as REASON_ID,
34         RSN_STS_RSN_PRTRY
35 FROM XTABLE
36 ,     XMLTABLE ('/TRANSACTION/STATUS'
37                  PASSING XMLCOLUMN
38              COLUMNS
39                  STS_PFL_ID         NUMBER(10)    path 'PFL_ID'
40                , STS_PMI_ID         NUMBER(10)    path 'PMI_ID'
41                , STS_TXI_ID         NUMBER(10)    path 'TXI_ID'
42                , STS_ID             VARCHAR2(10) path 'ID'
43                , RSN_ID             VARCHAR2(10) path 'REASON/ID'
44                , RSN_STS_RSN_PRTRY VARCHAR2(10) path 'REASON/STS_RSN_PRTRY'
45           ) rsn;
              </REASON>
ERROR at line 24:
ORA-19279: XQuery dynamic type mismatch: expected singleton sequence - got
multi-item sequenceHTH
Edited by: Marco Gralike on Feb 16, 2011 12:12 PM

Help! - XSU, object-relational views and chaching

I'm working with Oracle's SQL utility XSU using the PL/SQL API (xmlgen package) to generate XML from object-relational views in Oracle 8.1.7.
Sometimes when I change the definition of the view or the objects the view is based on the changes seem not be be reflected in the generated output. I'm getting errors for datatypes I've changed (Java still wants the "old" datatype) or the XML tag generated still reflects the old column name of the object. I get the new definition when I restart the database but that's not really a workable option.
I suppose the objects/view or something else must be cached somewhere.
Does anyone know what is going on?
Where is this stuff cached?
Can I somehow flush the cache?
Can I turn the cache off ? (might be useful for a development environment)
Any help'd be appreciated!
null

Peter,
Glad to see you took my advice and posted your question over here. Although I am a frequent user of the Oracle usenet groups, I have found that this is a much better place to get help with Spatial. My experiences suggest that the population of people using spatial is small--and of them the ones that really know alot are few and far between. I can only claim to be in the former group.
As far as your problem goes--this is probably something you've already considered--is there a way to model the data such that you don't have to replicate the geometry components? Another option would be to handle the replication without using snapshots. Examples would be to export the data and then ftp/copy it to the target machines and import it. If you need real-time replication you could experiment with triggers that execute INSERTs/UPDATEs/DELETEs on the remote databases. This of course has its own issues--but you're going to end up with some sort of compromise no matter how you slice this.
Of course you could use the relational model. I have never used it so I'm hard pressed to give any advice on it. As I posted on the usenet board, it is heading for desupport in 9i Release 2 according to the documentation available. So if you go relational you'll eventually have to migrate to object/relational. I'm not sure how automatic (or non-automatic) that process is. Hopefully someone on here will have some more concrete advice on that.
Good luck.
Matt.

Is it possible to create relational view on Analytic Workspace in Oracle 9i Release1

Hi All,
We are in the initial stages of Oracle 9i OLAP prototype. Since the current version of BIBeans 2.5 does not work with Release 2 of Oracle 9i OLAP, we are planning to use Oracle 9i OLAP Release 1. So can you please answer the following questions.
1. Is it possible to create relational view on Analytic Workspace(like in Release 2) and populate the OLAP catalog, if so can you give me guidance to get the appropriate user guide. The OLAP DML guide in Release 1 talks about creating OLAP catalog metadata for Analytic Workspace using a metadata locator object.
2, Is it advisable to use Oralce 9i OLAP Release 1? Does the Analytic Workspace and the corresponding BIBeans work in Release 1?
Thank you,
Senthil

Analytic Workspaces (Express/multidimensional data objects and procedures written in
the OLAP DML) are new to Oracle9i OLAP Release 2, you cannot find them in Release 1.
BI Beans will soon (within a week) introduce a version on OTN that will work with Oracle9i OLAP Release 2.

Converting from a Business View connection to a non-Business View Error

I have CR 2008 report with SP1. The report has a sub report. The main report is based off of a BV but the sub report is using an ODBC connection. When I try to update the ODBC connection I recieve an error message telling me that:
Quote:
"Converting from a Business View connection to a non-Business View connection is not supported."
I am do not want to update the BusinessView just the ODBC connection for the subreport.

Hi Michael,
When you try to update both the Business views and ODBC connection you will be prompted for those errors.
You need to break the link in the report and update the connections individually.
Thanks,
Naveen.

How to convert XML file to an internal table ?

Hi All,
I want to do a batch input program. The source data would be given as an excel file . I would like to know how to convert XML file to internal table properly. Please help me out..
Thanking you in advance ..
Shankara Narayanan T.V

Hi Shankar,
use 'ALSM_EXCEL_TO_INTERNAL_TABLE' FM.
CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
         EXPORTING
              filename                = p_file1
              i_begin_col             = '1'
              i_begin_row             = '5'
              i_end_col               = '40'
              i_end_row               = '16'
         TABLES
              intern                  = it_intern
         EXCEPTIONS
              inconsistent_parameters = 1
              upload_ole              = 2
              OTHERS                  = 3.
    IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
LOOP AT it_intern.
      AT NEW row.
        CLEAR it_intern.
      ENDAT.
        CASE lv_flag.
    Production Version
          WHEN 1.
            it_master-matnr      =   it_intern-value.
          WHEN 2.
            it_master-werks      = it_intern-value.
          WHEN 3.
            it_master-verid      = it_intern-value.
          WHEN 4.
            it_master-text1      = it_intern-value.
          WHEN 5.
            it_master-fdate     = it_intern-value.
      AT END OF row.
        APPEND it_master.
      ENDAT.
    ENDLOOP.
-Anu
Message was edited by:
        Anupama Reddy

Convert XML file to sap

Dear friends
              For converting XML file to SAP, I used TEXT_CONVERT_XML_TO_SAP function module. In this I have some doubt. Pls clarify this.
1. I am getting run time error with type h.
2 I_FIELD_SEPERATOR          = ';'
   I_LINE_HEADER              =
   I_TAB_RAW_DATA             =
   I_FILENAME                 =
   I_TOTALSIZE                =
for the above parameter what are the value has to passed.
Thanks.

Hi,
Take a look in this code:
*& Report z_xit_xml_check
REPORT z_xit_xml_check.
TYPE-POOLS: ixml.
DATA: BEGIN OF t_cabec OCCURS 0.
          INCLUDE STRUCTURE zmmt2010.
DATA END OF t_cabec.
DATA: BEGIN OF t_item OCCURS 0.
          INCLUDE STRUCTURE zmmt2011.
DATA END OF t_item.
DATA: BEGIN OF t_itemt OCCURS 0.
          INCLUDE STRUCTURE zmmt2012.
DATA END OF t_itemt.
TYPES: BEGIN OF t_xml_line,
          data(256) TYPE x,
        END OF t_xml_line.
DATA check_item(1).
DATA check_itemt(1).
DATA: l_ixml            TYPE REF TO if_ixml,
        l_streamfactory   TYPE REF TO if_ixml_stream_factory,
        l_parser          TYPE REF TO if_ixml_parser,
        l_istream         TYPE REF TO if_ixml_istream,
        l_document        TYPE REF TO if_ixml_document,
        l_node            TYPE REF TO if_ixml_node,
        l_xmldata         TYPE string.
DATA: l_elem            TYPE REF TO if_ixml_element,
        l_root_node       TYPE REF TO if_ixml_node,
        l_next_node       TYPE REF TO if_ixml_node,
        l_name            TYPE string,
        l_iterator        TYPE REF TO if_ixml_node_iterator.
DATA: l_xml_table       TYPE TABLE OF t_xml_line,
        l_xml_line        TYPE t_xml_line,
        l_xml_table_size TYPE i.
DATA: l_filename        TYPE string.
PARAMETERS: pa_file TYPE char1024 DEFAULT 'c:\xml.xml'.
START-OF-SELECTION.
    PERFORM busca_xml.
    PERFORM carrega_tabela.
*&      Form get_xml_table
FORM get_xml_table CHANGING l_xml_table_size TYPE i
                              l_xml_table      TYPE STANDARD TABLE.
Local variable declaration
    DATA: l_len      TYPE i,
          l_len2     TYPE i,
          l_tab      TYPE tsfixml,
          l_content TYPE string,
          l_str1     TYPE string,
          c_conv     TYPE REF TO cl_abap_conv_in_ce,
          l_itab     TYPE TABLE OF string.
    l_filename = pa_file.
upload a file from the client's workstation
    CALL METHOD cl_gui_frontend_services=>gui_upload
      EXPORTING
        filename   = l_filename
        filetype   = 'BIN'
      IMPORTING
        filelength = l_xml_table_size
      CHANGING
        data_tab   = l_xml_table
      EXCEPTIONS
        OTHERS     = 19.
    IF sy-subrc <> 0.
      MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
ENDFORM.                    "get_xml_table
*&      Form process_dom
FORM process_dom USING document TYPE REF TO if_ixml_document.
    DATA: node      TYPE REF TO if_ixml_node,
          iterator TYPE REF TO if_ixml_node_iterator,
          nodemap   TYPE REF TO if_ixml_named_node_map,
          attr      TYPE REF TO if_ixml_node,
          name      TYPE string,
          prefix    TYPE string,
          value     TYPE string,
          indent    TYPE i,
          count     TYPE i,
          index     TYPE i.
    DATA v_codcat TYPE zmmt2011-codcat.
    DATA v_master_for TYPE zmmt2011-master_for.
    node ?= document.
    CHECK NOT node IS INITIAL.
    IF node IS INITIAL. EXIT. ENDIF.
create a node iterator
    iterator = node->create_iterator( ).
get current node
    node = iterator->get_next( ).
loop over all nodes
    WHILE NOT node IS INITIAL.
      indent = node->get_height( ) * 2.
      indent = indent + 20.
      CASE node->get_type( ).
        WHEN if_ixml_node=>co_node_element.
        element node
          name    = node->get_name( ).
          TRANSLATE name TO LOWER CASE.
          IF name = 'iten'.
            MOVE 'I' TO check_item.
          ENDIF.
          IF name = 'cabec'.
            MOVE 'C' TO check_item.
          ENDIF.
          IF name = 'iten_texto'.
            MOVE 'T' TO check_item.
          ENDIF.
          nodemap = node->get_attributes( ).
          IF NOT nodemap IS INITIAL.
          attributes
            count = nodemap->get_length( ).
            DO count TIMES.
              index = sy-index - 1.
              attr   = nodemap->get_item( index ).
              name   = attr->get_name( ).
              prefix = attr->get_namespace_prefix( ).
              value = attr->get_value( ).
            ENDDO.
          ENDIF.
        WHEN if_ixml_node=>co_node_text OR
             if_ixml_node=>co_node_cdata_section.
        text node
          value = node->get_value( ).
          IF check_item = 'C'.
            TRANSLATE name TO LOWER CASE.
            CASE name.
              WHEN 'lifnr'.     MOVE value TO t_cabec-lifnr.
              WHEN 'codcat'.
                MOVE value TO t_cabec-codcat.
                MOVE value TO v_codcat.
              WHEN 'bukrs'.     MOVE value TO t_cabec-bukrs.
              WHEN 'zterm'.     MOVE value TO t_cabec-zterm.
              WHEN 'waers'.     MOVE value TO t_cabec-waers.
              WHEN 'inco1'.     MOVE value TO t_cabec-inco1.
              WHEN 'inco2'.     MOVE value TO t_cabec-inco2.
              WHEN 'telf1'.     MOVE value TO t_cabec-telf1.
              WHEN 'verkf'.     MOVE value TO t_cabec-verkf.
              WHEN 'datav'.
                MOVE value TO t_cabec-datav.
                APPEND t_cabec.
            ENDCASE.
          ENDIF.
          IF check_item = 'I'.
            TRANSLATE name TO LOWER CASE.
            CASE name.
              WHEN 'master_for'.
                MOVE value TO t_item-master_for.
                MOVE value TO v_master_for.
              WHEN 'werks'.      MOVE value TO t_item-werks.
              WHEN 'versao'.     MOVE value TO t_item-versao.
              WHEN 'matkl'.      MOVE value TO t_item-matkl.
              WHEN 'j_1bindus3'. MOVE value TO t_item-j_1bindus3.
              WHEN 'j_1bmatuse'. MOVE value TO t_item-j_1bmatuse.
              WHEN 'j_1bmatorg'. MOVE value TO t_item-j_1bmatorg.
              WHEN 'j_1bnbmco1'. MOVE value TO t_item-j_1bnbmco1.
              WHEN 'bsgru'.      MOVE value TO t_item-bsgru.
              WHEN 'ekgrp'.      MOVE value TO t_item-ekgrp.
              WHEN 'txz01'.      MOVE value TO t_item-txz01.
              WHEN 'epstp'.      MOVE value TO t_item-epstp.
              WHEN 'netpr'.      MOVE value TO t_item-netpr.
              WHEN 'peinh'.      MOVE value TO t_item-peinh.
              WHEN 'meins'.      MOVE value TO t_item-meins.
              WHEN 'plifz'.      MOVE value TO t_item-plifz.
              WHEN 'mwskz'.      MOVE value TO t_item-mwskz.
              WHEN 'steuc'.
                MOVE value TO t_item-steuc.
                MOVE v_codcat TO t_item-codcat.
                APPEND t_item.
            ENDCASE.
          ENDIF.
          IF check_item = 'T'.
            TRANSLATE name TO LOWER CASE.
            CASE name.
              WHEN 'linha'.     MOVE value TO t_itemt-linha.
              WHEN 'txlng'.     MOVE value TO t_itemt-txlng.
                MOVE v_master_for TO t_itemt-master_for.
                MOVE v_codcat     TO t_itemt-codcat.
                append t_itemt.
            ENDCASE.
          ENDIF.
      ENDCASE.
    advance to next node
      node = iterator->get_next( ).
    ENDWHILE.
ENDFORM.                    "process_dom
*&      Form Busca_XML
      text
--> p1        text
<-- p2        text
FORM busca_xml .
    DATA: lc_mess(70) TYPE c,lv_tab.
    TYPES: BEGIN OF ty_zvmsgorgtr.
            INCLUDE STRUCTURE zmmt2011.
    TYPES   END OF ty_zvmsgorgtr.
Creating the main iXML factory
    l_ixml = cl_ixml=>create( ).
Creating a stream factory
    l_streamfactory = l_ixml->create_stream_factory( ).
    PERFORM get_xml_table CHANGING l_xml_table_size l_xml_table.
wrap the table containing the file into a stream
    l_istream = l_streamfactory->create_istream_itable( table =
    l_xml_table size = l_xml_table_size ).
Creating a document
    l_document = l_ixml->create_document( ).
Create a Parser
    l_parser = l_ixml->create_parser( stream_factory = l_streamfactory
                                      istream        = l_istream
                                      document       = l_document ).
Parse the stream
    IF l_parser->parse( ) NE 0.
      IF l_parser->num_errors( ) NE 0.
        DATA: parseerror TYPE REF TO if_ixml_parse_error,
              str        TYPE string,
              i          TYPE i,
              count      TYPE i,
              index      TYPE i.
        count = l_parser->num_errors( ).
        WRITE: count, ' parse errors have occured:'.
        index = 0.
        WHILE index < count.
          parseerror = l_parser->get_error( index = index ).
          i = parseerror->get_line( ).
          WRITE: 'line: ', i.
          i = parseerror->get_column( ).
          WRITE: 'column: ', i.
          str = parseerror->get_reason( ).
          WRITE: str.
          index = index + 1.
        ENDWHILE.
      ENDIF.
    ENDIF.
ENDFORM.                    " Busca_XML
*&      Form Carrega_Tabela
      text
--> p1        text
<-- p2        text
FORM carrega_tabela .
Process the document
    IF l_parser->is_dom_generating( ) EQ 'X'.
      PERFORM process_dom USING l_document.
    ENDIF.
ENDFORM.                    " Carrega_Tabela

Converted XML not showing multiple data entries correctly

Hello
I am creating a PDF Form from a xsd scheme but when I have data that could require multiple entries the converted xml is a mess. I am curently trying to create a way to add fields for multiple children. I created an expanding table and the fields are automatically copied when I click on „+“ or are deleted when I click on „-“ . If I have multiple rows for children then the converted xml looks like this :
The correct xml for multiple data entries should look like this (this is from a xml scheme not made in LiveCycle) :
Even if I copy the fields without creating a table, the converted xml is still a mess just like on the first image. Is there a way to show the xml from the PDF from correctly. I linked the xsd scheme that I am using for the PDF form: https://drive.google.com/file/d/0B30LkLSwYgB4SFN5bTkyLW1fOVU/edit?usp=sharing
Best regards
Ivica

Hello
I am creating a PDF Form from a xsd scheme but when I have data that could require multiple entries the converted xml is a mess. I am curently trying to create a way to add fields for multiple children. I created an expanding table and the fields are automatically copied when I click on „+“ or are deleted when I click on „-“ . If I have multiple rows for children then the converted xml looks like this :
The correct xml for multiple data entries should look like this (this is from a xml scheme not made in LiveCycle) :
Even if I copy the fields without creating a table, the converted xml is still a mess just like on the first image. Is there a way to show the xml from the PDF from correctly. I linked the xsd scheme that I am using for the PDF form: https://drive.google.com/file/d/0B30LkLSwYgB4SFN5bTkyLW1fOVU/edit?usp=sharing
Best regards
Ivica

Problem in converting XML to XML file

Hi,
I am trying to convert xml file to another xml through command-line interface but failed.
java oracle.xml.parser.v2.oraxsl data.xml data.xsl data_new.xml
My xml and xsl files are:
1. XML file
<employee_data>
<employee_row>
<employee_number>7950</employee_number>
<employee_name>ABC</employee_name>
<employee_title>PRESIDENT</employee_title>
<manager>1111</manager>
<date_of_hire>20-JAN-93</date_of_hire>
<salary>65000</salary>
<commission>1000</commission>
<department_number>10</department_number>
</employee_row>
</employee_data>
2-1 XSL file
<?xml version="1.0" ?>
<xsl:stylesheet xsl:version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml"/>
<xsl:template match="*">
<xsl:copy>
<xsl:apply-templates>
<xsl:sort select=".//employee_name"/>
</xsl:apply-templates>
</xsl:copy>
</xsl:template>
</xsl:stylesheet>
2-2 XSL file
<?xml version = "1.0"?>
<ROWSET xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:for-each select="employee_data/employee_row">
<ROW>
<EMPNO><xsl:value-of select="employee_number"/></EMPNO>
<ENAME><xsl:value-of select="employee_name"/></ENAME>
<JOB><xsl:value-of select="employee_title"/></JOB>
<MGR><xsl:value-of select="manager"/></MGR>
<HIREDATE><xsl:value-of select="date_of_hire"/></HIREDATE>
<SAL><xsl:value-of select="salary"/></SAL>
<COMM><xsl:value-of select="commission"/></COMM>
<DEPTNO><xsl:value-of select="department_number"/></DEPTNO>
</ROW>
</xsl:for-each>
</ROWSET>
I used two xsl file to test but received same error message:
Error occurred while processing data.xsl: Error in expression: '*|/'.
Does anyone know how to fix the problem? I'll appreciate it very much for your help.
Thanks.
Yi

Hi,
I have only tried it out with XML Spy, but anyway:
there seems to be an error in your 2-1 XSl file in line 2:
the correct stylesheet declaration is:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
You had an empty namespace and a wrong version attribute...
HTH,
Bernhard

Convert XML to relational view

Similar Messages

Maybe you are looking for