SAP XML Schema's - 2 questions

Hi All,
1. Difference between ifr.sap.com & XI
The schema's defined in ifr.sap.com and the schema's retrieved via the RFC adapter are different! The XSD's in ifr.sap.com use mixed case for the elements. The XSD/WSDL extracted contain element names that are all uppercase! Does seems like an error. Or am I missing something? Or is this on purpose?
2. elemenfFormDefault="unqualified"
The schema's defined in ifr.sap.com and used by SAP XI do not set elementFormDefault="qualified". This is not an error, but unusual. Non-global elements therefore do not belong to the target namespace but to an unnamed global namespace. What would be the reason for doing so?
Kind regards, Guy Crets (Apogado)

Hi Guy,
1. in ifr.sap.com you find three kinds of objects, namely IDocs, RFCs, and Business Objects.
XI has an IDoc-adapter (which uses the same XML as published at ifr.sap.com) and an RFC-adapter (which uses the same XML as published at ifr.sap.com).
As far as I know XI has no Business Object adapter. The reason might be, that for each method of a Business Object there is an RFC doing exactly the same work. So you can use the RFC adapter, but then clearly have to stick to the RFC-XML which differs from the Business Object XML. Normally, this RFC XML is not published at ifr.sap.com, because the Business Object is already published. Hence, you have to take the XSD from the Integration Repository in this case.
2. I think XML namespaces were introduced to avoid naming conflicts when XML documents are put together from different organizations. This purpose is served by both modelling styles.
So, in my opinion it remains a matter of taste.
I'm not so familiar with XSLT, but I cannot imagine that this is really a problem. In contrast to elements attributes most of the time are taken unqualified, and you can also deal with this, I think.
Moreover, 'unqualified' is the default according to the XSD spec. Hence, there are obviously several people, who believed this style to be the default.
Greetings
Stephan

Similar Messages

XML schema together with XHTML

Hi there,
I have the following situation:
I want to create an XML document that contains 2 parts:
a) a XHTML part (it can be either version 1.0 or 1.1 )
b) a non XHTML part that contains some information about the first part - like the location of that content or some other info on different constituents of the first part
The elements of the second part are defined by an XML schema.
My question is how to do this in an elegant manner?
Should I import somehow (I have no idea how) the XHTML schema on the part 2 schema? Or should I deal only on the instance XML file with this issue (if yes - how)?
Thanks a lot for the help.
Daniel

Download the newest version at http://xml.apache.org
and try again...Unfortunately I'm already using the latest version. It just doesn't seem to work.

How Does FrameMaker Support XML Schemas?

Hi All,
I'm wondering how FM supports XML Schemas. I need to validate the uniqnuess of the value of an element in my XML. Let's say I have an XML like this one:
<Param>
     <name>Parameter 1 name</name>
     <description>Parameter 1 description</description>
     <code>12345</code>
</Param>
<Param>
     <name>Parameter 2 name</name>
     <description>Parameter 2 description</description>
     <code>6789</code>
</Param>
The value of <code> must be unique throughout the XML file. As far as I know, I can add a validation of the uniqnuess of <code> into my XML schema. The question is whether this uniqnuess check will be supported by FM.
Any advice is appreciated.
Thank you very much!

It should (though I have not tested it myself). Framemaker 11 uses XercesC 2.7 for parsing the incoming/outgoing XML and it supports unique constrains. EDD cannot check the possible violation, however.
BR, Martti

Using xml schema problem (SAP MDM 7.1 Syndicator)

Good day !
I try to syndicate directory which correspond to some xml-schema and I have a problem.
I want to syndicate data from hierarchy table which have one field which have a type like lookup <Flat> (multivalued).
In XML-schema element "DEF_PRODUCT" and "DEF_PRODUCT_CODE" - attribute presents hierarchy table.
"CREDIT_PRODUCT" and childs presents linked flat table.
According idea and business rules I must get the result like this: each "DEF_PRODUCT" have N-"CREDIT_PRODUCT". One - to- many.
But when I set up all map completely and look to xml result file I start to be disappointed.
XML result file approximately must be like this:
<DEF_PRODUCT>
    <CREDIT_PRODUCT/>
    <CREDIT_PRODUCT/>
    <CREDIT_PRODUCT/>
</DEF_PRODUCT>
but in result I have all <CREDIT_PRODUCT> in one node and child attributes.
I attach 3 pics which explain my situation.
xml-schema :[http://xmages.net/storage/10/1/0/6/3/upload/42ca6ca8.jpg]
field mapping: [http://xmages.net/storage/10/1/0/6/a/upload/bbbc09f2.jpg]
example: [http://xmages.net/storage/10/1/0/c/c/upload/817b0e23.jpg]
Anybody can help me?
About software : SAP MDM 7.1 (7.1.04.139)
P.S: My problem can be resolved succesfully if I will use 1 <main> table and 1 <qualified flat> table.
       But in my case I must use hierarchy - structure because it most usable for business - users

>
Christian Heuer wrote:
> Hi,
>
> now I understood and you really have got a point here. But the question is whether you need key mapping then on the remote key level with a tuple anymore. If yes, you won
>
> Best regards
> Christian
If SAP MDM will present many opportunities to me I will be very glad.
I repeat I must get output xml which have the pair like "RemoteKey"="RemoteSystem" in tuple subnode.
In tuple, after your advices.
Ideally, Syndicator must present to each user ability to choose pair "RemoteKey" = "RemoteSystem" in each subnode like <LookUp> table in root (look at my example pic).
Imagine you have one root table and N-linked <lookup> tables.
Tree like this :
<main tbl>
<subtbl1/>
<subtbl2/>
<subtbl3>
     <childtbl1/>
     <childtbl2/>
</subtbl3>
</main tbl>
It's dangerous to deprive SAP MDM user to select pair "RemoteKey" = "RemoteSystem" from ROOT to ALL and LAST LEAF in abstract hierarchy. How do you think ?
Now, I haven't abilities to solve my problem using standard resources. Really ?

XMLType column based on XML Schema: several questions

Hi,
I've a table on an oracle db version 10.1.0.4 where I stage the xml files containing orders created on a third party's system using BizTalk.
Although the storage I opted for is based on an XML Schema, defined by this third-party, I am facing big perfomance issues with files bigger than a few hundreds of kBs.
For instance, a 32Mb file takes more than 2 hours to be processed.
Now, after reading other threads in this forum and the documentation, my understanding of the problem is that the whole issue is with the correct indexing of the nested tables.
Here is my current XML Schema definition:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
               xmlns:xs="http://www.w3.org/2001/XMLSchema"
               xmlns:xdb="http://xmlns.oracle.com/xdb"
               elementFormDefault="qualified"
               attributeFormDefault="unqualified"
               xdb:storeVarrayAsTable="true">
     <xs:include schemaLocation="private/Types.xsd"/>
     <xs:element name="PickData">
          <xs:complexType xdb:maintainDOM="false">
               <xs:sequence>
                    <xs:element name="ProdRun">
                         <xs:complexType xdb:maintainDOM="false">
                              <xs:sequence>
                                   <xs:element name="Nr" type="xs:int"/>
                                   <xs:element name="Date" type="string8"/>
                                   <xs:element name="Final" type="xs:int"/>
                                   <xs:element name="PickWave" maxOccurs="unbounded">
                                        <xs:complexType xdb:maintainDOM="false">
                                             <xs:sequence>
                                                  <xs:element name="Nr" type="string10"/>
                                                  <xs:element name="ProdLine" type="string2"/>
                                                  <xs:element name="TourSeq" type="xs:int"/>
                                                  <xs:element name="Tour" type="string20"/>
                                                  <xs:element name="Customer" maxOccurs="unbounded">
                                                       <xs:complexType xdb:maintainDOM="false">
                                                            <xs:sequence>
                                                                 <xs:element name="Seq" type="string20"/>
                                                                 <xs:element name="Cust" type="string10"/>
                                                                 <xs:element name="Mod" type="string30"/>
                                                                 <xs:element name="Tod" type="string30"/>
                                                                 <xs:element name="InvOrder" maxOccurs="unbounded">
                                                                      <xs:complexType xdb:maintainDOM="false">
                                                                           <xs:sequence>
                                                                                <xs:element name="Nr" type="string20"/>
                                                                                <xs:element name="Item" type="string20"/>
                                                                                <xs:element name="Qty" type="xs:int"/>
                                                                                <xs:element name="Priority" type="xs:int"/>
                                                                                <xs:element name="Reordering" type="xs:int"/>
                                                                                <xs:element name="DelDate" type="string8"/>
                                                                                <xs:element name="HlOrder" type="string20"/>
                                                                           </xs:sequence>
                                                                      </xs:complexType>
                                                                      <xs:unique name="InvOrderKey">
                                                                           <xs:selector xpath="InvOrder"/>
                                                                           <xs:field xpath="Nr"/>
                                                                      </xs:unique>
                                                                 </xs:element>
                                                            </xs:sequence>
                                                       </xs:complexType>
                                                       <xs:unique name="CustomerKey">
                                                            <xs:selector xpath="Customer"/>
                                                            <xs:field xpath="Seq"/>
                                                       </xs:unique>
                                                  </xs:element>
                                             </xs:sequence>
                                        </xs:complexType>
                                        <xs:unique name="PickWaveKey">
                                             <xs:selector xpath="PickWave"/>
                                             <xs:field xpath="Nr"/>
                                        </xs:unique>
                                   </xs:element>
                              </xs:sequence>
                         </xs:complexType>
                         <xs:unique name="ProdRunKey">
                              <xs:selector xpath="ProdRun"/>
                              <xs:field xpath="Nr"/>
                         </xs:unique>
                    </xs:element>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
</xs:schema>
Here is the included sub-schema:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
          <xsd:simpleType name="string2">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="2"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="string5">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="5"/>
</xsd:restriction>
</xsd:simpleType>
          <xsd:simpleType name="string6">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="6"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="string8">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="8"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="string10">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="string15">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="15"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="string20">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="string30">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="30"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="string40">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="string50">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="string250">
               <xsd:restriction base="xsd:string">
                    <xsd:maxLength value="250"/>
               </xsd:restriction>
          </xsd:simpleType>
     </xsd:schema>
The statement for creating my table is
CREATE TABLE "XML_ORDERS"
("ID" NUMBER(7,0) NOT NULL ENABLE,
"XMLFILE" "SYS"."XMLTYPE" ,
"INSERTED" DATE DEFAULT sysdate,
CONSTRAINT "XML_ORDERS_PK" PRIMARY KEY ("ID") USING INDEX ENABLE
) XMLTYPE COLUMN XMLFILE STORE AS OBJECT RELATIONAL
XMLSCHEMA "private/PickData.xsd" ELEMENT "PickData"
Here is a simple instance document:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<PickData xsi:noNamespaceSchemaLocation="private/PickData.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ProdRun>
<Nr>5</Nr>
<Date>15112005</Date>
<Final>1</Final>
<PickWave>
<Nr>IPW0000017</Nr>
<ProdLine>01</ProdLine>
<TourSeq>1</TourSeq>
<Tour>00000043_078</Tour>
<Customer>
<Seq>5</Seq>
<Cust>100000006</Cust>
<Mod>FO</Mod>
<Tod>DDU</Tod>
<InvOrder>
<Nr>IIO0000457</Nr>
<Item>100000036</Item>
<Qty>20</Qty>
<Priority>1</Priority>
<Reordering>0</Reordering>
<DelDate>15112005</DelDate>
<HlOrder>CSO000742</HlOrder>
</InvOrder>
<InvOrder>
<Nr>IIO0000459</Nr>
<Item>100000045</Item>
<Qty>20</Qty>
<Priority>1</Priority>
<Reordering>0</Reordering>
<DelDate>15112005</DelDate>
<HlOrder>CSO000742</HlOrder>
</InvOrder>
</Customer>
<Customer>
<Seq>6</Seq>
<Cust>100000013</Cust>
<Mod>FO</Mod>
<Tod>DDU</Tod>
<InvOrder>
<Nr>IIO0000461</Nr>
<Item>100000036</Item>
<Qty>20</Qty>
<Priority>1</Priority>
<Reordering>0</Reordering>
<DelDate>15112005</DelDate>
<HlOrder>CSO000743</HlOrder>
</InvOrder>
<InvOrder>
<Nr>IIO0000463</Nr>
<Item>100000045</Item>
<Qty>20</Qty>
<Priority>1</Priority>
<Reordering>0</Reordering>
<DelDate>15112005</DelDate>
<HlOrder>CSO000743</HlOrder>
</InvOrder>
</Customer>
<Customer>
<Seq>2</Seq>
<Cust>100000114</Cust>
<Mod>FO</Mod>
<Tod>DDU</Tod>
<InvOrder>
<Nr>IIO0000465</Nr>
<Item>100000036</Item>
<Qty>20</Qty>
<Priority>1</Priority>
<Reordering>0</Reordering>
<DelDate>15112005</DelDate>
<HlOrder>CSO000744</HlOrder>
</InvOrder>
<InvOrder>
<Nr>IIO0000467</Nr>
<Item>100000045</Item>
<Qty>20</Qty>
<Priority>1</Priority>
<Reordering>0</Reordering>
<DelDate>15112005</DelDate>
<HlOrder>CSO000744</HlOrder>
</InvOrder>
</Customer>
<Customer>
<Seq>3</Seq>
<Cust>100000140</Cust>
<Mod>FO</Mod>
<Tod>DDU</Tod>
<InvOrder>
<Nr>IIO0000469</Nr>
<Item>100000036</Item>
<Qty>20</Qty>
<Priority>1</Priority>
<Reordering>0</Reordering>
<DelDate>15112005</DelDate>
<HlOrder>CSO000745</HlOrder>
</InvOrder>
<InvOrder>
<Nr>IIO0000471</Nr>
<Item>100000045</Item>
<Qty>20</Qty>
<Priority>1</Priority>
<Reordering>0</Reordering>
<DelDate>15112005</DelDate>
<HlOrder>CSO000745</HlOrder>
</InvOrder>
</Customer>
<Customer>
<Seq>7</Seq>
<Cust>100000143</Cust>
<Mod>FO</Mod>
<Tod>DDU</Tod>
<InvOrder>
<Nr>IIO0000473</Nr>
<Item>100000036</Item>
<Qty>20</Qty>
<Priority>1</Priority>
<Reordering>0</Reordering>
<DelDate>15112005</DelDate>
<HlOrder>CSO000746</HlOrder>
</InvOrder>
<InvOrder>
<Nr>IIO0000475</Nr>
<Item>100000045</Item>
<Qty>20</Qty>
<Priority>1</Priority>
<Reordering>0</Reordering>
<DelDate>15112005</DelDate>
<HlOrder>CSO000746</HlOrder>
</InvOrder>
</Customer>
<Customer>
<Seq>8</Seq>
<Cust>100000145</Cust>
<Mod>FO</Mod>
<Tod>DDU</Tod>
<InvOrder>
<Nr>IIO0000477</Nr>
<Item>100000036</Item>
<Qty>20</Qty>
<Priority>1</Priority>
<Reordering>0</Reordering>
<DelDate>15112005</DelDate>
<HlOrder>CSO000747</HlOrder>
</InvOrder>
<InvOrder>
<Nr>IIO0000479</Nr>
<Item>100000045</Item>
<Qty>20</Qty>
<Priority>1</Priority>
<Reordering>0</Reordering>
<DelDate>15112005</DelDate>
<HlOrder>CSO000747</HlOrder>
</InvOrder>
</Customer>
<Customer>
<Seq>9</Seq>
<Cust>100000146</Cust>
<Mod>FO</Mod>
<Tod>DDU</Tod>
<InvOrder>
<Nr>IIO0000481</Nr>
<Item>100000036</Item>
<Qty>20</Qty>
<Priority>0</Priority>
<Reordering>0</Reordering>
<DelDate>15112005</DelDate>
<HlOrder>CSO000748</HlOrder>
</InvOrder>
<InvOrder>
<Nr>IIO0000483</Nr>
<Item>100000045</Item>
<Qty>20</Qty>
<Priority>1</Priority>
<Reordering>0</Reordering>
<DelDate>15112005</DelDate>
<HlOrder>CSO000748</HlOrder>
</InvOrder>
</Customer>
<Customer>
<Seq>4</Seq>
<Cust>100000147</Cust>
<Mod>FO</Mod>
<Tod>DDU</Tod>
<InvOrder>
<Nr>IIO0000485</Nr>
<Item>100000036</Item>
<Qty>20</Qty>
<Priority>0</Priority>
<Reordering>0</Reordering>
<DelDate>15112005</DelDate>
<HlOrder>CSO000750</HlOrder>
</InvOrder>
<InvOrder>
<Nr>IIO0000487</Nr>
<Item>100000045</Item>
<Qty>20</Qty>
<Priority>1</Priority>
<Reordering>0</Reordering>
<DelDate>15112005</DelDate>
<HlOrder>CSO000750</HlOrder>
</InvOrder>
</Customer>
<Customer>
<Seq>10</Seq>
<Cust>100000148</Cust>
<Mod>FO</Mod>
<Tod>DDU</Tod>
<InvOrder>
<Nr>IIO0000489</Nr>
<Item>100000036</Item>
<Qty>20</Qty>
<Priority>0</Priority>
<Reordering>0</Reordering>
<DelDate>15112005</DelDate>
<HlOrder>CSO000751</HlOrder>
</InvOrder>
<InvOrder>
<Nr>IIO0000491</Nr>
<Item>100000045</Item>
<Qty>20</Qty>
<Priority>1</Priority>
<Reordering>0</Reordering>
<DelDate>15112005</DelDate>
<HlOrder>CSO000751</HlOrder>
</InvOrder>
</Customer>
</PickWave>
</ProdRun>
</PickData>
When I registered the XMLSchema, the following types and tables were automatically created and you can see the hierarchy below:
(by the way, I could not find any xdb_utilities.printNestedTables mentioned elsewhere)
XML_ORDERS
|_PickData381_T
|___ProdRun382_T
|_____PickWave388_COLL
|_______PickWave383_T
|_________Customer387_COLL
|___________Customer384_T
|_____________InvOrder386_COLL
These objects are then used in the following nested tables:
TABLE_NAME     TABLE_TYPE_NAME     PARENT_TABLE_NAME     PARENT_TABLE_COLUMN
SYS_NTaK/5zar5S0WitSsgu6OKPQ==     PickWave388_COLL     PickData389_TAB     "XMLDATA"."ProdRun"."PickWave"
SYS_NTf6QvwVm8SFKz+K/YYWq+WQ==     Item408_COLL     ProdData409_TAB     "XMLDATA"."Item"
SYS_NTtu05ilrRQqmuEN4k+07VDA==     Customer402_COLL     OutboundParty403_TAB     "XMLDATA"."Customer"
SYS_NTK6fhWq5uTJ+vKcgBpNm1Fg==     InvOrder386_COLL     SYS_NTIIzv7bkXQSSS43igtfi5eg==     InvOrder
SYS_NTIIzv7bkXQSSS43igtfi5eg==     Customer387_COLL     SYS_NTaK/5zar5S0WitSsgu6OKPQ==     Customer
I enabled sql tracing and I got the following TKPROF output
INSERT INTO IMP_ORDERS (PICK_INVORDERNR, PICK_ITEM, PICK_QTY, PICK_PRIORITY,
PICK_REORDERING, PICK_HLORDER, PICK_DELDATE, PICK_CUST, PICK_MOD, PICK_TOD,
PICK_SEQ, PICK_PICKWAVENR, PICK_PICKWAVEPRODLINE, PICK_PICKWAVETOUR,
PICK_PICKWAVETOURSEQ, PICK_ORDKEY, PICK_RUNKEY) SELECT INVORDERNR, ITEM,
QTY, PRIORITY, REORDERING, HLORDER, DELDATE, CUST, MOD, TOD, SEQ,
PICKWAVENR, PICKWAVEPRODLINE, PICKWAVETOUR, PICKWAVETOURSEQ, ROWNUM AS
PICK_ORDKEY, PRODRUNID FROM (SELECT /*+ cardinality(g 15)*/
EXTRACTVALUE(VALUE(G), '/InvOrder/Nr') AS INVORDERNR, EXTRACTVALUE(VALUE(G),
'/InvOrder/Item') AS ITEM, EXTRACTVALUE(VALUE(G), '/InvOrder/Qty') AS QTY,
EXTRACTVALUE(VALUE(G), '/InvOrder/Priority') AS PRIORITY,
EXTRACTVALUE(VALUE(G), '/InvOrder/Reordering') AS REORDERING,
EXTRACTVALUE(VALUE(G), '/InvOrder/HlOrder') AS HLORDER,
TO_DATE(EXTRACTVALUE(VALUE(G), '/InvOrder/DelDate'),'DDMMYYYY') AS DELDATE,
F.CUST, F.MOD, F.TOD, F.SEQ, F.PICKWAVENR, F.PICKWAVEPRODLINE,
F.PICKWAVETOUR, F.PICKWAVETOURSEQ, F.PRODRUNNR, F.PRODRUNDATE,
F.PRODRUNFINAL, F.PRODRUNID FROM (SELECT /*+ cardinality(e 60)*/VALUE(E) AS
CUSTOMERNODE, EXTRACTVALUE(VALUE(E), '/Customer/Cust') AS CUST,
EXTRACTVALUE(VALUE(E), '/Customer/Mod') AS MOD, EXTRACTVALUE(VALUE(E),
'/Customer/Tod') AS TOD, TO_NUMBER(EXTRACTVALUE(VALUE(E), '/Customer/Seq'))
AS SEQ, D.PICKWAVENR, D.PICKWAVEPRODLINE, D.PICKWAVETOUR, D.PICKWAVETOURSEQ,
D.PRODRUNNR, D.PRODRUNDATE, D.PRODRUNFINAL, D.PRODRUNID FROM (SELECT /*+
cardinality(c 100)*/VALUE(C) AS PICKWAVENODE, EXTRACTVALUE(VALUE(C),
'/PickWave/Nr') AS PICKWAVENR, TO_NUMBER(EXTRACTVALUE(VALUE(C),
'/PickWave/ProdLine')) AS PICKWAVEPRODLINE, EXTRACTVALUE(VALUE(C),
'/PickWave/Tour') AS PICKWAVETOUR, TO_NUMBER(EXTRACTVALUE(VALUE(C),
'/PickWave/TourSeq')) AS PICKWAVETOURSEQ, A.PRODRUNNR, A.PRODRUNDATE,
A.PRODRUNFINAL, A.PRODRUNID FROM (SELECT /*+ cardinality(b 1)*/VALUE(B) AS
PRODRUNNODE, EXTRACTVALUE(VALUE(B), '/ProdRun/Nr') AS PRODRUNNR,
TO_DATE(EXTRACTVALUE(VALUE(B), '/ProdRun/Date'),'DDMMYYYY') AS PRODRUNDATE,
EXTRACTVALUE(VALUE(B), '/ProdRun/Final') AS PRODRUNFINAL, X.ID PRODRUNID
FROM XML_ORDERS X, TABLE(XMLSEQUENCE(EXTRACT(X.XMLFILE,'/PickData/ProdRun'))
) B WHERE X.ID = :B1 ) A, TABLE(XMLSEQUENCE(EXTRACT(A.PRODRUNNODE,
'/ProdRun/PickWave'))) C ) D, TABLE(XMLSEQUENCE(EXTRACT(D.PICKWAVENODE,
'/PickWave/Customer'))) E ) F, TABLE(XMLSEQUENCE(EXTRACT(F.CUSTOMERNODE,
'/Customer/InvOrder'))) G ORDER BY PICKWAVEPRODLINE, PICKWAVETOURSEQ,
PICKWAVENR, SEQ )
call count cpu elapsed disk query current rows
Parse 1 0.00 0.00 0 0 0 0
Execute 1 4324.09 9994.65 0 57193 0 0
Fetch 0 0.00 0.00 0 0 0 0
total 2 4324.09 9994.65 0 57193 0 0
Misses in library cache during parse: 1
Misses in library cache during execute: 1
Optimizer mode: ALL_ROWS
Parsing user id: 68 (recursive depth: 1)
Rows Row Source Operation
0 COUNT (cr=0 pr=0 pw=0 time=180 us)
0 VIEW (cr=0 pr=0 pw=0 time=166 us)
0 SORT ORDER BY (cr=0 pr=0 pw=0 time=152 us)
40866 NESTED LOOPS (cr=54973 pr=0 pw=0 time=31065606 us)
1363 NESTED LOOPS (cr=54937 pr=0 pw=0 time=11037183 us)
1 NESTED LOOPS (cr=54889 pr=0 pw=0 time=10145883 us)
1 NESTED LOOPS (cr=54841 pr=0 pw=0 time=9799012 us)
1 TABLE ACCESS BY INDEX ROWID XML_ORDERS (cr=2 pr=0 pw=0 time=222 us)
1 INDEX UNIQUE SCAN XML_ORDERS_PK (cr=1 pr=0 pw=0 time=126 us)(object id 58551)
1 COLLECTION ITERATOR PICKLER FETCH (cr=54839 pr=0 pw=0 time=9798748 us)
1 COLLECTION ITERATOR PICKLER FETCH (cr=48 pr=0 pw=0 time=346818 us)
1363 COLLECTION ITERATOR PICKLER FETCH (cr=48 pr=0 pw=0 time=870830 us)
40866 COLLECTION ITERATOR PICKLER FETCH (cr=36 pr=0 pw=0 time=18739302 us)
Note that I cancelled this operation before it was over so I imagine that these figures refer to the statistics as of the time when the operation was interrupted.
So, here are finally my questions.
In order to create the constraints on the nested tables as shown in other threads, do I need to drop the existing xml_orders table and ancillary object types and recreate them or is there a way to add such constraints using the existing system generated object names?
Secondly, the xml_orders table may contain severale documents, not just one and his current primary key is the column ID. So, in order to uniquely identify the deepest element in the xml document, I need first to select the relevant document by means of the id column.
Would it be better to create the indexes containing this id column together with the nested_table_id and array_index?
Thanks for you help.
Flavio
PS: I wrote a 10 lines xsl transformation that I passed on to Saxon together with the 32Mb file. It took less than 1 minute to produce a flat file that was loaded almost instantly by SQL*Loader. So, what I am looking for is a procedure loading this stuff in less than 2 minutes or possibly less.

Does the following help
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Dec 27 21:44:53 2005
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> spool registerSchema_&4..log
SQL> set trimspool on
SQL> connect &1/&2
Connected.
SQL> --
SQL> declare
2    result boolean;
3 begin
4    result := dbms_xdb.createResource('/home/&1/xsd/&4',
5                                      bfilename(USER,'&4'),nls_charset_id('AL32UTF8'));
6 end;
7 /
old   4:   result := dbms_xdb.createResource('/home/&1/xsd/&4',
new   4:   result := dbms_xdb.createResource('/home/OTNTEST/xsd/GetaxTypes.xsd',
old   5:                                    bfilename(USER,'&4'),nls_charset_id('AL32UTF8'));
new   5:                                    bfilename(USER,'GetaxTypes.xsd'),nls_charset_id('AL32UTF8'));
PL/SQL procedure successfully completed.
SQL> commit
2 /
Commit complete.
SQL> alter session set events='31098 trace name context forever'
2 /
Session altered.
SQL> begin
2    dbms_xmlschema.registerSchema
3    (
4      schemaURL => '&3',
5      schemaDoc => xdbURIType('/home/&1/xsd/&4').getClob(),
6      local     => TRUE,
7      genTypes => TRUE,
8      genBean   => FALSE,
9      genTables => &5
10    );
11 end;
12 /
old   4:     schemaURL => '&3',
new   4:     schemaURL => 'private/GetaxTypes.xsd',
old   5:     schemaDoc => xdbURIType('/home/&1/xsd/&4').getClob(),
new   5:     schemaDoc => xdbURIType('/home/OTNTEST/xsd/GetaxTypes.xsd').getClob(),
old   9:     genTables => &5
new   9:     genTables => TRUE
PL/SQL procedure successfully completed.
SQL> quit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Dec 27 21:44:55 2005
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> spool registerSchema_&4..log
SQL> set trimspool on
SQL> connect &1/&2
Connected.
SQL> --
SQL> declare
2    result boolean;
3 begin
4    result := dbms_xdb.createResource('/home/&1/xsd/&4',
5                                      bfilename(USER,'&4'),nls_charset_id('AL32UTF8'));
6 end;
7 /
old   4:   result := dbms_xdb.createResource('/home/&1/xsd/&4',
new   4:   result := dbms_xdb.createResource('/home/OTNTEST/xsd/PickData.xsd',
old   5:                                    bfilename(USER,'&4'),nls_charset_id('AL32UTF8'));
new   5:                                    bfilename(USER,'PickData.xsd'),nls_charset_id('AL32UTF8'));
PL/SQL procedure successfully completed.
SQL> commit
2 /
Commit complete.
SQL> alter session set events='31098 trace name context forever'
2 /
Session altered.
SQL> begin
2    dbms_xmlschema.registerSchema
3    (
4      schemaURL => '&3',
5      schemaDoc => xdbURIType('/home/&1/xsd/&4').getClob(),
6      local     => TRUE,
7      genTypes => TRUE,
8      genBean   => FALSE,
9      genTables => &5
10    );
11 end;
12 /
old   4:     schemaURL => '&3',
new   4:     schemaURL => 'private/PickData.xsd',
old   5:     schemaDoc => xdbURIType('/home/&1/xsd/&4').getClob(),
new   5:     schemaDoc => xdbURIType('/home/OTNTEST/xsd/PickData.xsd').getClob(),
old   9:     genTables => &5
new   9:     genTables => TRUE
PL/SQL procedure successfully completed.
SQL> quit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Dec 27 21:44:58 2005
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> spool createTable.log
SQL> --
SQL> connect &1/&2
Connected.
SQL> --
SQL> CREATE TABLE "XML_ORDERS"
2     ("ID" NUMBER(7,0) NOT NULL ENABLE,
3      "XMLFILE" "SYS"."XMLTYPE" ,
4      "INSERTED" DATE DEFAULT sysdate,
5       CONSTRAINT "XML_ORDERS_PK" PRIMARY KEY ("ID") USING INDEX ENABLE
6     ) XMLTYPE COLUMN XMLFILE STORE AS OBJECT RELATIONAL
7       XMLSCHEMA "private/PickData.xsd"
8       ELEMENT "PickData"
9           VARRAY XMLFILE."XMLDATA"."ProdRun"."PickWave" STORE AS TABLE PickWave_TAB
10             (
11                ( primary key (nested_table_id, array_index)
12                ) organization index overflow
13                VARRAY "Customer" STORE AS TABLE Customer_TAB
14                  (
15                    (primary key (nested_table_id, array_index)
16                    ) organization index overflow
17                    VARRAY "InvOrder" STORE AS TABLE InvOrder_TAB
18                      (
19                        (primary key (nested_table_id, array_index)
20                        ) organization index overflow
21                      )
22                  )
23            )
24 /
Table created.
SQL> quit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Dec 27 21:44:59 2005
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> spool insertFile_&3..log
SQL> set trimspool on
SQL> connect &1/&2
Connected.
SQL> --
SQL> set timing on
SQL> set long 10000
SQL> --
SQL> insert into XML_ORDERS (ID, XMLFILE) values (&4, xmltype(bfilename(USER,'&3'),nls_charset_id('AL32UTF8')))
2 /
old   1: insert into XML_ORDERS (ID, XMLFILE) values (&4, xmltype(bfilename(USER,'&3'),nls_charset_id('AL32UTF8')))
new   1: insert into XML_ORDERS (ID, XMLFILE) values (10, xmltype(bfilename(USER,'testcase.xml'),nls_charset_id('AL32UT
8')))
1 row created.
Elapsed: 00:00:00.11
SQL> commit
2 /
Commit complete.
Elapsed: 00:00:00.01
SQL> quit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Dec 27 21:44:59 2005
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> spool testcase.log
SQL> set trimspool on
SQL> connect &1/&2
Connected.
SQL> --
SQL> set timing on
SQL> set long 10000
SQL> set pages 0 lines 140
SQL> --
SQL> -- Testcase code here
SQL> --
SQL> set autotrace on explain
SQL> --
SQL> create or replace view PROD_RUN_VIEW
2 (
3    PRODRUNNODE,
4    PRODRUNNR,
5    PRODRUNDATE,
6    PRODRUNID,
7    PRODRUNFINAL
8 )
9 as
10 select EXTRACT(XMLFILE,'/PickData/ProdRun'),
11         EXTRACTVALUE(XMLFILE , '/PickData/ProdRun/Nr'),
12         TO_DATE(EXTRACTVALUE(XMLFILE, '/PickData/ProdRun/Date'),'DDMMYYYY'),
13         ID,
14         EXTRACTVALUE(XMLFILE,'/PickData/ProdRun/Final')
15    from XML_ORDERS
16 /
View created.
Elapsed: 00:00:00.09
SQL> create or replace view PICK_WAVE_VIEW
2 (
3    PICKWAVENODE,
4    PICKWAVENR,
5    PICKWAVEPRODLINE,
6    PICKWAVETOUR,
7    PICKWAVETOURSEQ,
8    PRODRUNNR,
9    PRODRUNDATE,
10    PRODRUNID,
11    PRODRUNFINAL
12 )
13 as
14 select value(PW),
15         extractValue(value(PW),'/PickWave/Nr'),
16         TO_NUMBER(EXTRACTVALUE(value(PW),'/PickWave/ProdLine')),
17         extractValue(value(PW),'/PickWave/Tour'),
18         TO_NUMBER(extractValue(value(PW),'/PickWave/TourSeq')),
19         PRODRUNNR,
20         PRODRUNDATE,
21         PRODRUNID,
22         PRODRUNFINAL
23    FROM PROD_RUN_VIEW, table(xmlsequence(extract(PRODRUNNODE,'/ProdRun/PickWave'))) PW
24 /
View created.
Elapsed: 00:00:00.09
SQL> create or replace view CUSTOMER_VIEW
2 (
3    CUSTOMERNODE,
4    CUST,
5    MOD,
6    TOD,
7    SEQ,
8    PICKWAVENR,
9    PICKWAVEPRODLINE,
10    PICKWAVETOUR,
11    PICKWAVETOURSEQ,
12    PRODRUNNR,
13    PRODRUNDATE,
14    PRODRUNFINAL,
15    PRODRUNID
16 )
17 as
18 select value(CUST),
19         EXTRACTVALUE(VALUE(CUST), '/Customer/Cust'),
20         EXTRACTVALUE(VALUE(CUST), '/Customer/Mod'),
21         EXTRACTVALUE(VALUE(CUST), '/Customer/Tod'),
22         TO_NUMBER(EXTRACTVALUE(VALUE(CUST), '/Customer/Seq')),
23         PICKWAVENR,
24         PICKWAVEPRODLINE,
25         PICKWAVETOUR,
26         PICKWAVETOURSEQ,
27         PRODRUNNR,
28         PRODRUNDATE,
29         PRODRUNFINAL,
30         PRODRUNID
31    from PICK_WAVE_VIEW, table(xmlsequence(extract(PICKWAVENODE,'/PickWave/Customer'))) CUST
32 /
View created.
Elapsed: 00:00:00.10
SQL>
SQL> create or replace view INVOICE_ORDER_VIEW
2 (
3    INVORDERNR,
4    ITEM,
5    QTY,
6    PRIORITY,
7    REORDERING,
8    HLORDER,
9    DELDATE,
10    CUST,
11    MOD,
12    TOD,
13    SEQ,
14    PICKWAVENR,
15    PICKWAVEPRODLINE,
16    PICKWAVETOUR,
17    PICKWAVETOURSEQ,
18    PRODRUNNR,
19    PRODRUNDATE,
20    PRODRUNFINAL,
21    PRODRUNID
22 )
23 as
24 SELECT EXTRACTVALUE(VALUE(INV), '/InvOrder/Nr'),
25         EXTRACTVALUE(VALUE(INV), '/InvOrder/Item'),
26         EXTRACTVALUE(VALUE(INV), '/InvOrder/Qty'),
27         EXTRACTVALUE(VALUE(INV), '/InvOrder/Priority'),
28         EXTRACTVALUE(VALUE(INV), '/InvOrder/Reordering'),
29         EXTRACTVALUE(VALUE(INV), '/InvOrder/HlOrder'),
30         TO_DATE(EXTRACTVALUE(VALUE(INV), '/InvOrder/DelDate'),'DDMMYYYY'),
31         CUST,
32         MOD,
33         TOD,
34         SEQ,
35         PICKWAVENR,
36         PICKWAVEPRODLINE,
37         PICKWAVETOUR,
38         PICKWAVETOURSEQ,
39         PRODRUNNR,
40         PRODRUNDATE,
41         PRODRUNFINAL,
42         PRODRUNID
43   FROM CUSTOMER_VIEW, table(xmlsequence(extract(CUSTOMERNODE,'Customer/InvOrder'))) INV
44 /
View created.
Elapsed: 00:00:00.13
SQL> select * from INVOICE_ORDER_VIEW
2 /
IIO0000461           100000036                    20          1          0 CSO000743            15-NOV-05 100000013
FO                             DDU                                     6 IPW0000017                1 00000043_078
                1
         5 15-NOV-05            1         10
IIO0000463           100000045                    20          1          0 CSO000743            15-NOV-05 100000013
FO                             DDU                                     6 IPW0000017                1 00000043_078
                1
         5 15-NOV-05            1         10
IIO0000473           100000036                    20          1          0 CSO000746            15-NOV-05 100000143
FO                             DDU                                     7 IPW0000017                1 00000043_078
                1
         5 15-NOV-05            1         10
IIO0000475           100000045                    20          1          0 CSO000746            15-NOV-05 100000143
FO                             DDU                                     7 IPW0000017                1 00000043_078
                1
         5 15-NOV-05            1         10
IIO0000469           100000036                    20          1          0 CSO000745            15-NOV-05 100000140
FO                             DDU                                     3 IPW0000017                1 00000043_078
                1
         5 15-NOV-05            1         10
IIO0000471           100000045                    20          1          0 CSO000745            15-NOV-05 100000140
FO                             DDU                                     3 IPW0000017                1 00000043_078
                1
         5 15-NOV-05            1         10
IIO0000489           100000036                    20          0          0 CSO000751            15-NOV-05 100000148
FO                             DDU                                    10 IPW0000017                1 00000043_078
                1
         5 15-NOV-05            1         10
IIO0000491           100000045                    20          1          0 CSO000751            15-NOV-05 100000148
FO                             DDU                                    10 IPW0000017                1 00000043_078
                1
         5 15-NOV-05            1         10
IIO0000481           100000036                    20          0          0 CSO000748            15-NOV-05 100000146
FO                             DDU                                     9 IPW0000017                1 00000043_078
                1
         5 15-NOV-05            1         10
IIO0000483           100000045                    20          1          0 CSO000748            15-NOV-05 100000146
FO                             DDU                                     9 IPW0000017                1 00000043_078
                1
         5 15-NOV-05            1         10
IIO0000485           100000036                    20          0          0 CSO000750            15-NOV-05 100000147
FO                             DDU                                     4 IPW0000017                1 00000043_078
                1
         5 15-NOV-05            1         10
IIO0000487           100000045                    20          1          0 CSO000750            15-NOV-05 100000147
FO                             DDU                                     4 IPW0000017                1 00000043_078
                1
         5 15-NOV-05            1         10
IIO0000457           100000036                    20          1          0 CSO000742            15-NOV-05 100000006
FO                             DDU                                     5 IPW0000017                1 00000043_078
                1
         5 15-NOV-05            1         10
IIO0000459           100000045                    20          1          0 CSO000742            15-NOV-05 100000006
FO                             DDU                                     5 IPW0000017                1 00000043_078
                1
         5 15-NOV-05            1         10
IIO0000477           100000036                    20          1          0 CSO000747            15-NOV-05 100000145
FO                             DDU                                     8 IPW0000017                1 00000043_078
                1
         5 15-NOV-05            1         10
IIO0000479           100000045                    20          1          0 CSO000747            15-NOV-05 100000145
FO                             DDU                                     8 IPW0000017                1 00000043_078
                1
         5 15-NOV-05            1         10
IIO0000465           100000036                    20          1          0 CSO000744            15-NOV-05 100000114
FO                             DDU                                     2 IPW0000017                1 00000043_078
                1
         5 15-NOV-05            1         10
IIO0000467           100000045                    20          1          0 CSO000744            15-NOV-05 100000114
FO                             DDU                                     2 IPW0000017                1 00000043_078
                1
         5 15-NOV-05            1         10
18 rows selected.
Elapsed: 00:00:00.22
Execution Plan
Plan hash value: 1730223965
| Id | Operation                | Name              | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT         |                   |    18 | 10278 |   877   (0)| 00:00:11 |
|   1 | NESTED LOOPS            |                   |    18 | 10278 |   877   (0)| 00:00:11 |
|   2 |   NESTED LOOPS           |                   |    18 | 8424 |   841   (0)| 00:00:11 |
|   3 |    MERGE JOIN CARTESIAN |                   |    18 | 4680 |   805   (0)| 00:00:10 |
|   4 |     TABLE ACCESS FULL    | XML_ORDERS        |     1 |    67 |     3   (0)| 00:00:01 |
|   5 |     BUFFER SORT          |                   |    18 | 3474 |   802   (0)| 00:00:10 |
|   6 |      INDEX FAST FULL SCAN| SYS_IOT_TOP_64187 |    18 | 3474 |   802   (0)| 00:00:10 |
|* 7 |    INDEX UNIQUE SCAN     | SYS_IOT_TOP_64185 |     1 |   208 |     2   (0)| 00:00:01 |
|* 8 |     INDEX RANGE SCAN     | SYS_C008783       |     1 |       |     0   (0)| 00:00:01 |
|* 9 |   INDEX UNIQUE SCAN      | SYS_IOT_TOP_64183 |     1 |   103 |     2   (0)| 00:00:01 |
|* 10 |    INDEX RANGE SCAN      | SYS_C008785       |     1 |       |     0   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   7 - access("NESTED_TABLE_ID"="CUSTOMER_TAB"."SYS_NC0000800009$")
   8 - access("NESTED_TABLE_ID"="CUSTOMER_TAB"."SYS_NC0000800009$")
   9 - access("NESTED_TABLE_ID"="PICKWAVE_TAB"."SYS_NC0000800009$")
       filter("NESTED_TABLE_ID"="XML_ORDERS"."SYS_NC0001000011$")
10 - access("NESTED_TABLE_ID"="PICKWAVE_TAB"."SYS_NC0000800009$")
Note
   - dynamic sampling used for this statement
SQL> quit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
C:\oracle\xdb\otn\347125>You were sequencing the ProdRun node, which is a mistake. Only nodes which occur multiple times should be sequenced...

OInvoice Business Object XML Schema question

I am trying to produce an xml file based on the oInvoices business object to use in an EDI translation. I am running Sap Business One 2005 A SP:01 PL:03. I used one of the sample programs in the SDK Samples folder to produce an XML schema of the oInvoices object. The sample program is in the COM DI folder, program #06. ObjectSchemas. When I run this program is produces an xml file that is really a schema for oInvoices, and it uses the GetBusinessObjectXmlSchema function for the oInvoices BoObjectType. If I use the SaveXML function on the SAPbobsCOM.BoObjectTypes.oInvoices, I get a different xml file that does not use the same table or fields names. (See sample below - schema uses the table name, OINV, SaveXml uses 'Documents' in place of the OINV name, schema has a QueryParams tag set, SaveXml does not, SaveXml has a Version defined within the AdminInfo, the Schema does not have this). Why doesn't the oInvoices xml schema match the xml file produced using the SaveXML function. Which example below is the correct xml representation of an Invoice? I have copied parts of each file below.
oInvoices file produced using GetBusinessObjectXmlSchema for oInvoices:
- <element name="BOM">
- <complexType>
- <all>
- <element maxOccurs="1" minOccurs="0" name="BO">
- <complexType>
- <sequence>
- <element maxOccurs="1" minOccurs="0" name="AdmInfo">
- <complexType>
- <all>
<element maxOccurs="1" minOccurs="0" name="Object" type="long" />
</all>
</complexType>
</element>
- <element maxOccurs="1" minOccurs="0" name="QueryParams">
- <complexType>
- <all>
<element maxOccurs="1" minOccurs="0" name="DocEntry" type="string" />
</all>
</complexType>
</element>
- <element maxOccurs="1" minOccurs="0" name="OINV">
- <complexType>
- <sequence>
- <element maxOccurs="unbounded" minOccurs="0" name="row">
- <complexType>
- <all>
<element maxOccurs="1" minOccurs="0" name="DocNum" type="long" />
<element maxOccurs="1" minOccurs="0" name="DocType" type="string" />
<element maxOccurs="1" minOccurs="0" name="Handwrtten" type="string" />
<element maxOccurs="1" minOccurs="0" name="DocDate" type="string" />
<element maxOccurs="1" minOccurs="0" name="DocDueDate" type="string" />
<element maxOccurs="1" minOccurs="0" name="CardCode" type="string" />
<element maxOccurs="1" minOccurs="0" ......
OInvoices xml file produced using SaveXml
- <BOM>
- <BO>
- <AdmInfo>
<Object>13</Object>
<Version>2</Version>
</AdmInfo>
- <Documents>
- <row>
<DocNum>5</DocNum>
<DocType>dDocument_Items</DocType>
<HandWritten>tNO</HandWritten>
<Printed>tNO</Printed>
<DocDate>20050116</DocDate>
<DocDueDate>20050215</DocDueDate>
<CardCode>C20000</CardCode>.....
I did not copy all of the xml for each file as it would be too lengthy.
Thanks,
Nancy Walk
[email protected]

Hi Nancy,
I can´t find it right now, but I do remember reading that there were different XML definition versions for SBO objects. In the version 1, table names where used. In the version 2, object names where used. Looks like the schema defines version 2, but SBO is using version 2.
I will check if I can found where I did read that. Try speaking with someone in SAP and about XML versions, perhaps they could help you with this info.
Hope helps,
Ibai Peñ

Standard XML schema for Vendor data exchange between SAP and other system

Is there a SAP standard way of XML schema that we exchange between SAP and other system? Please let me know.
Thanks.

See SAP Interface Repository (http://ifr.sap.com).
My proposal is to leave old SAP connectors staff and use SAP Exchange Infrastructure. There is a support of industry XML standards in XI 3.0 like xCBL.

XML SCHEMA validation question

i'm using jdk 1.4.2 and am trying to validate an xml document against an xml schema. i don't have any packages like xerces or apache and am trying to avoid having to use them. i've had a look at the jdk 1.5 api documentation, and it seems to have some new classes dedicated to xml validation using schemas that 1.4.2 does not have (e.g. the Schema class). my question is, is it possible to do xml validation against a schema only using jdk 1.4.2 and without the likes of the xerces and apache parser packages?
any help much appreciated, thanks

The tutorial on Schema Validation parses/validates with the SAXParserFactory. J2sdk 1.4.2 JAXP has an error in the implementation of the SAXParserFactory. Parse/validate with the DocumentBuilderFactory instead of the SAXParserFactory.
http://java.sun.com/j2ee/1.4/docs/tutorial/doc/JAXPSAX9.html

XML generation with SAP data using XML schema - Reg

Hello experts,
My requirement is , SAP( ztable data ) data has to be transferred to third party software folder.Third party using XML so they requires output from SAP in XML format.
For that third party software guys told me that they will give their own XML schema to me.I have to generate XML file with SAP data using their XML schema.
Generating XML file with their Schema should be underlined.
I studied that call transformation statement helps for this.
Even then i don't have clear idea about this topic.
Please brief me about how to use their XML schema to generate XML with my own sap data.
Thanks in advance experts.
Kumar

please try this same program    and see it ....
*& Report z_xit_xml_check
REPORT z_xit_xml_check.
TYPE-POOLS: ixml.
TYPES: BEGIN OF t_xml_line,
          data(256) TYPE x,
        END OF t_xml_line.
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:temporders_dtd.xml'.
* Validation of XML file: Only DTD included in xml document is supported
PARAMETERS: pa_val TYPE char1 AS CHECKBOX.
START-OF-SELECTION.
*   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 ).
*   Validate a document
    IF pa_val EQ 'X'.
      l_parser->set_validating( mode = if_ixml_parser=>co_validate ).
    ENDIF.
*   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.
*   Process the document
    IF l_parser->is_dom_generating( ) EQ 'X'.
      PERFORM process_dom USING l_document.
    ENDIF.
*&      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.
*   Writing the XML document to the screen
    CLEAR l_str1.
    LOOP AT l_xml_table INTO l_xml_line.
      c_conv = cl_abap_conv_in_ce=>create( input = l_xml_line-data replacement = space ).
      c_conv->read( IMPORTING data = l_content len = l_len ).
      CONCATENATE l_str1 l_content INTO l_str1.
    ENDLOOP.
    l_str1 = l_str1+0(l_xml_table_size).
    SPLIT l_str1 AT cl_abap_char_utilities=>cr_lf INTO TABLE l_itab.
    WRITE: /.
    WRITE: /' XML File'.
    WRITE: /.
    LOOP AT l_itab INTO l_str1.
      REPLACE ALL OCCURRENCES OF cl_abap_char_utilities=>horizontal_tab IN
        l_str1 WITH space.
      WRITE: / l_str1.
    ENDLOOP.
    WRITE: /.
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.
    node ?= document.
    CHECK NOT node IS INITIAL.
    ULINE.
    WRITE: /.
    WRITE: /' DOM-TREE'.
    WRITE: /.
    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( ).
          nodemap = node->get_attributes( ).
          WRITE: / 'ELEMENT :'.
          WRITE: AT indent name COLOR COL_POSITIVE INVERSE.
          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( ).
              WRITE: / 'ATTRIBUTE:'.
              WRITE: AT indent name COLOR COL_HEADING INVERSE, '=',
                               value COLOR COL_TOTAL   INVERSE.
            ENDDO.
          ENDIF.
        WHEN if_ixml_node=>co_node_text OR
             if_ixml_node=>co_node_cdata_section.
*         text node
          value = node->get_value( ).
          WRITE: / 'VALUE     :'.
          WRITE: AT indent value COLOR COL_GROUP INVERSE.
      ENDCASE.
*     advance to next node
      node = iterator->get_next( ).
    ENDWHILE.
ENDFORM.                    "process_dom
reward points if it is use fulll ....
Girish

XML Schema - Two Questions

1. Can a validation requirement such as the one in the following
example be specified in the XML 1.0 schema:
The identification information for a student must include either a
social security number (SSN) or a student id. It is also valid to
specify both.
We were able to specify an exclusive or, that is either A or B, using
the choice group element. A choice group element allows only one of its
children to appear in an instance and thus works for the case of either
SSN or student id.
Can the choice feature be extended to accommodate the inclusive or
case, that is either A or B or both, as stated in the validation
requirement?
If choice cannot be used, is there another schema feature that can be
used to accommodate this case?
2. Is there any way to allow child elements of a group to have a
maxOccurs greater than 1 while at the same time allowing the elements to
occur in any order. The default, sequence, indicates that the
sequence of elements within a group must follow the order indicated in
the schema. The all group allows for flexibility in the order, but
restricts maxOccurs to 0 or 1. Looking at the following example:
<complexType name=description>
<element name=tattoos minOccurs=0 maxOccurs=100>
<element name= birthdate minOccurs=0 maxOccurs=1>
<element name=nicknames minOccurs=0 maxOccurs=10>
</complexType>
We would like to allow multiple occurrences of tattoos and nicknames and
also allow the three elements (tattoos, birthdate, nicknames) to be
specified in any order.
Is it possible to do this in XML Schema 1.0 and, if so, what is the
correct syntax?

1. You may use somewhat cumbersome syntax like:
choice
A
B
all
A
B
/all
/choice
to implement inclusive or.
2. They (W3 Schema WG) were talking about
this but decided not to allow it (at least for now). A workaround you may use:
all
group ref = group1
group ref = group2
/all
group name=group1
elem ... maxOccurs = 10
/group
Something like that.
null

Question about Java API for XML schema?

Hello, everyone!
I am looking for a java api for XML schema. I hope the API is capable for parsing the structure of element
or complextype declarations in XML schema. So for example, if I specify a name of an element or
complextype defined in a schema, the name, dataype and other constraints of contained child elements can be returned.
Does anyone know if there exists such a paser?
Thanks very much!

An implementation of DOM Level 3.

XML Schema Design question

Hello all,
I am a new to XML Schema design and struggling with designing my first XML Schema. Here is my problem.
I have almost 200 elements in my database which I have to use to design XSDs, I have customer name ( last name, first name, dob etc) and customer address ( office address, home address etc) and at the same time I have other player such as Patient name ( last name, first name, dob etc) and patient address( home address, office address).
And then we have some dollor related data such as patient insurance amount, copay amount , total amount and many more $.
What I wanted to know is that what would be best approach to design a XML schema for such kind of system, should I create one schema (xsd) for all the 200 attributes or I should create seperate schema for customers ( including names and addresses along with other dollor amount data ) and a similar xsd for Patient data. Some of the XML documents which I will create from these schemas would be based on customers and patient information both .
Thank you.
Regards
Suhail Ahmad

It's hard to tell what is the best design. But in order to simplify access to these data through other program APIs such as JAXB, you may start from defining objects such as the schema types/elements for customer, patient and the addresses
Then you can assoicate the related data to these object.

XML Schema Question

Hi everyone,
I'm constructing two complex data types in my xml schema: Base and Extended. The two types look like this (or this is how I want them to look):
<xs:complexType type="baseType">
     <xs:attribute name="name" type="xs:string" use="required" />
<xs:attribute name="stuff" type="xs:string" use="required" />
<xs:all>
</xs:all>
</xs:complexType>
<xs:complexType type="extendedType">
     <xs:complexContent>
          <xs:extension base="baseType">
               <xs:attribute name="stuff" type="xs:string" use="optional" />
<xs:all>
</xs:all>
</xs:extension>
</xs:complexContent>
</xs:complexType>
What I'm trying to do is overwrite the use attribute for the attribute stuff. Is this possible? Can this be done?
Thanks,
Brandon

Could you provide a little more information about the code bit you posted. More info about what class/package it is from and how you want to get the schema vs. how the method wants you to do it.
I have worked with Dtds and Schemas, but not too much through the way you are doing it (We use them mainly as printouts on paper to give to people), so I will help with what I can.
A little more info might also help someone remember something similar they did.

Unable to find root element in XML Schema when Syndicating (SAP MDM)

Hi experts,
We are having a problem with our Syndication.
We have created an XML Schema using XML Spy. We need a namespace, and this is 70 characters long (in other words, far shorter than maximum at 255 characters).
<xs:schema xmlns:ns="http://schemas.xxxxx.com/ServiceManagement/ServiceMasterDataFromMDM/0.3" xmlns:xs="http://www.xxxxx.org/2001/XMLSchema" targetNamespace="http://schemas.xxxxxx.com/ServiceManagement/ServiceMasterDataFromMDM/0.3" elementFormDefault="unqualified" attributeFormDefault="unqualified">
When opening the xml schema file in Syndicator, the root field is disabled.
If we remove namespace in heading of xml schema, the root field is enabled, and the root element is correct.
How can we make use of the XML schema when we need namespace?
We have tried to add namespace annotation ns: to all type definitions:
<xs:element name="ServiceCategory" type="ns:ServiceCategoryType">
This did not help.
Please advice.
KR,
Thomas
Edited by: Thomas on Mar 2, 2011 2:12 PM

>>We need a namespace, and this is 70 characters long
If you want namespace to appear in XML and your XSD has it too. please add the namespace under "URI" attribute in XML schema in Console.
You need to import the XSD in Console first, specify namespace under URI and then use this to build syndication map.
Thanks
Aamir

How to handle tables data in XML schema based adobe form

Hi all,
I am working on the CRM business partner creation by using Interactive adobe form with following steps:
1) Uploaded the offline Interactive adobe form to online interactive adobe form via WebDynpro ABAP;
2) Capture XML data into corresponding BAPI structures;
3) Save all the changes to database via BAPI.
The adobe form contains customer information as well as several table views which are bind with the context created in WebDynpro: Node NEW_BP_NODE cardinality 1:1 with single attributes and table type attributes (1:n): COLOUR_COMP, MEN_COMP etc.
While converting the xml format data to SAP context format, It is fine to use following routine to find the single attribute and map to the BAPI structure to do the database update.
NODE = DOCUMENT->FIND_FROM_NAME( NAME = 'XYZu2019).
XYZ = NODE->GET_VALUE( ).
Question: how to convert the xml table data to SAP context format in WebDynpro ABAP?
The XML table data looks like below.
<?xml version="1.0" encoding="UTF-8" ?>
<NEW_BP_NODE>
<COLOUR_COMP>
<DATA>
<ZZTFLD0W2AQW />
<ZZTFLDRZ2AQX>000</ZZTFLDRZ2AQX>
<ZZTFLDVD2TQW />
<ZZTFLDQK2HQX />
<ZZTFLDEL2XQX />
<ZZTFLDTC2DQX>000</ZZTFLDTC2DQX>
<ZZTFLDOR2UQX />
</DATA>
<DATA>
<ZZTFLD0W2AQW />
<ZZTFLDRZ2AQX />
<ZZTFLDVD2TQW />
<ZZTFLDQK2HQX />
<ZZTFLDEL2XQX />
<ZZTFLDTC2DQX />
<ZZTFLDOR2UQX />
</DATA>
<DATA>
<ZZTFLD0W2AQW />
<ZZTFLDRZ2AQX />
<ZZTFLDVD2TQW />
<ZZTFLDQK2HQX />
<ZZTFLDEL2XQX />
<ZZTFLDTC2DQX />
<ZZTFLDOR2UQX />
</DATA>
</COLOUR_COMP>
<MEN_COMP>
<DATA>
<ZZTFLD4V2V7V />
<ZZTFLDYD2N7W>000</ZZTFLDYD2N7W>
<ZZTFLDX32I7W />
<ZZTFLD2D2W7W />
<ZZTFLDGD2A7W />
</DATA>
<DATA>
<ZZTFLD4V2V7V />
<ZZTFLDYD2N7W>000</ZZTFLDYD2N7W>
<ZZTFLDX32I7W />
<ZZTFLD2D2W7W />
<ZZTFLDGD2A7W />
</DATA>
</MEN_COMP>
Thanks in advance for your help.
Michelle

Hi,
Just follow these steps:
1. Create interactive form UI element in your view.
2. Now provide Datasource and PDFSOURCE to it in form properties.
3. Now give a template name prefix with 'Z' or 'Y'.
4. Double click on it. It will prompt for interface name.
5. Provide interface name prefixed with 'Z' or 'Y'.
6. Click on Context button in the Pop up window and provide the node you have selected as DATASOURCE.
7. Click ok and it will open the form designer.
8. In this way you can create a XML Schema based Form.
9. Activate the interface and design the form providing layout type and other details.
Hope it will help.
Regards,
Vaibhav

SAP XML Schema's - 2 questions

Similar Messages

Maybe you are looking for