Can't specify XML Schema root in MDM Syndicator

Hello: I am using MDM 5.5 SP3, and I am trying to use Syndicator to output multilingual XML product descriptions. The XSD I am attempting to use is pasted below.
When I attempt to specify the Destination Properties and select the XSD file I have loaded into the repository via the Console, I am unable to select the "Root" (it is grayed out). I am unable to use the XSD in any way within Syndicator because the "OK" button is grayed out...I assume because Root has not been specified.
Any suggestions?
Thank you - Matt
<?xml version="1.0"?>
<xs:schema xmlns:xs="http://www.w3.org/2000/10/XMLSchema">
<xs:element name="ProdDescription" maxOccurs="unbounded">
<xs:complexType>
 <xs:sequence>
 <xs:element name="ProdCatalogNum" type="xs:string"/>
 <xs:element name="Description" type="xs:string" maxOccurs="unbounded">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="Language" type="xs:string"/>
 <xs:element name="Value" type="xs:string"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 </xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
I also tried this variant with no success. Changes are in bold and notes are underlined.
<?xml version="1.0"?>
<xs:schema xmlns:xs="http://www.w3.org/2000/10/XMLSchema">
<xs:element name="root">
<xs:complexType>
 <xs:choice maxOccurs="unbounded">
 <xs:element ref="ProdDescription" />
 </xs:choice>
</xs:complexType>
</xs:element>
<xs:element name="ProdDescription"> previously: maxOccurs="unbounded"
<xs:complexType>
 <xs:sequence>
 <xs:element name="ProdCatalogNum" type="xs:string"/>
 <xs:element name="Description" type="xs:string" maxOccurs="unbounded">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="Language" type="xs:string"/>
 <xs:element name="Value" type="xs:string"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 </xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>

I solved my problem: here is the updated XSD:
I believe it was mostly due to the bolded line:
<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <xsd:element name="ProdDescription" type="ProdDescType"/>
 <xsd:complexType name="ProdDescType">
 <xsd:sequence>
 <xsd:element name="ProdCatalogNum" type="xsd:string"/>
 <xsd:element name="Description" type="DescriptionType" maxOccurs="unbounded"/>
 </xsd:sequence>
 </xsd:complexType>
 <xsd:complexType name="DescriptionType">
 <xsd:sequence>
 <xsd:element name="Language" type="xsd:string"/>
 <xsd:element name="Value" type="xsd:string"/>
 </xsd:sequence>
 </xsd:complexType>
</xsd:schema>

Similar Messages

Problem with XML import MDM 7.1 - Can't generate Xml Schema

Hi All,
When I try to open an XML file using Import manager, I'm getting some errors, as detailed below. I mention that I'm using MDM 7.1.
The first error I received was the following:
"Can't open C:/Program files/SAP MDM 7.1/Import Manager/XSD.exe". I copied the file xsd.exe in the Import Manager folder, as suggest here:
Re: Import Manager Error.
Afterwards, I received a new error:
"Can't generate Xml Schema for: C:/Program files/SAP MDM 7.1/Import Manager/filename.xml"
If anyone has faced the same problem - and solved it -, could you please help me find the reason for this behaviour?
Regards,
Laura

Hi Laura,
The error message "Can't generate Xml Schema" might be related to DTD. the XML file has a directive for loading DTD.
MDM doesnot support DTDs.
Remove the DTD line and make sure there is only one root element in the XML file and try again.
Hope this helps,
Bes t Regards,
Silpa Chillakuru

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 ?

Can't import XML schema with ref to external namespace

In TopLink 10.1.3 Dev Preview 3 (build 041116), I have 2 simple schema files. One defines an element as a ref to an element in the other schema, so the ref points to an element in an external namespace. TopLink won't import this schema.
First schema, imports fine:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
 xmlns:xs="http://www.w3.org/2001/XMLSchema"
 targetNamespace="http://www.oracle.com/employee"
 xmlns="http://www.oracle.com/employee"
 elementFormDefault="qualified"
 attributeFormDefault="unqualified">
 <xs:element name="employee">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="name" type="xs:string"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
</xs:schema>
Second schema, fails import with "ERROR: null. Please check to ensure the document conforms to the XML Schema specification and try again":
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
 xmlns:xs="http://www.w3.org/2001/XMLSchema"
 targetNamespace="http://www.oracle.com/department"
 xmlns="http://www.oracle.com/department"
 xmlns:employee="http://www.oracle.com/employee"
 elementFormDefault="qualified"
 attributeFormDefault="unqualified">
 <xs:import
 namespace="http://www.oracle.com/employee"
 schemaLocation="employee.xsd"/>
 <xs:element name="department">
 <xs:complexType>
 <xs:sequence>
 <xs:element ref="employee:employee" maxOccurs="unbounded"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
</xs:schema>
Both schemas are valid according to the W3C schema validation checker at http://www.w3.org/2001/03/webdata/xsv.
I can work around the issue by putting the employee definitions into the department schema file so that all elements are in the same namespace. But I would like the schemas to be in separate files for better modularity and maintainability.
Am I doing something wrong? I would really like to be able to use references to external namespaces in my element definitions.
Thanks,
Dave

Hello David,
Apologies, but this is a bug in DP3 with respect to references to elements in imported namespaces. This has been fixed in current code, but until you get that, there are a couple ways to work around it:
==========================================================
1) Use an include rather than an import.
department.xsd
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
 targetNamespace="http://www.oracle.com/department"
 xmlns="http://www.oracle.com/department"
 xmlns:xs="http://www.w3.org/2001/XMLSchema"
 elementFormDefault="qualified"
 attributeFormDefault="unqualified">
 <xs:include schemaLocation="employee.xsd"/>
 <xs:element name="department">
 <xs:complexType>
 <xs:sequence>
 <xs:element ref="employee" maxOccurs="unbounded"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
</xs:schema>employee.xsd
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
 xmlns:xs="http://www.w3.org/2001/XMLSchema"
 targetNamespace="http://www.oracle.com/department"
 xmlns="http://www.oracle.com/department"
 elementFormDefault="qualified"
 attributeFormDefault="unqualified">
 <xs:element name="employee">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="name" type="xs:string"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
</xs:schema>You should only have to import the parent schema (i.e. department.xsd), as the included document will automatically be built in. Note that this works for imports as well, provided that there aren't nasty bugs blocking the process.
==========================================================
2. Build everything into the same document
department.xsd
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
 targetNamespace="http://www.oracle.com/department"
 xmlns="http://www.oracle.com/department"
 xmlns:xs="http://www.w3.org/2001/XMLSchema"
 elementFormDefault="qualified"
 attributeFormDefault="unqualified">
 <xs:element name="department">
 <xs:complexType>
 <xs:sequence>
 <xs:element ref="employee" maxOccurs="unbounded"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="employee">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="name" type="xs:string"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
</xs:schema>Obviously, this one won't work quite as well in some cases.
==========================================================
Until you can get to the latest code, I hope this helps some.
- Paul

Can you generate XML schema from XMLDB?

I have not used XMLDB and donÂ´t read the entire doc about the product(sorry for that).
I got the following question, is it possible to generate a XML schema from relational data through XMLDB? Or is this best done via a third party software like XMLSpy or alike?

3rd Party Software...
We can generate a schema for an object Hierarchy but our considered opinion is that there is no sensible way to generate an XML Schema representation of a purely relational data structure. It requires a tool which allows you to make decisions on how to organize the heirarchy.

How I can binding specified xml node to datagridview?

hello
please, i am new in c#;
I have xml file, i displayed the first node within form in c#, this node have attribute is called 'id', now i want to display all nodes that have attribute is called 'father' its value equal to id value of the displayed node.
xml file:
<?xml version="1.0" encoding="UTF-8"?>
<tree>
<grand name="aaa" id="1" sex="m" status="d" child="2" father=""></grand>
<grand name="ddd" id="12" sex="m" status="d" child="" father="1"></grand>
<grand name="bbb" id="11" sex="m" status="d" child="1" father="1"></grand>
<grand name="ccc" id="111" sex="m" status="d" child="1" father="11"></grand>
<grand name="ddd" id="1111" sex="m" status="d" child="3" father="111"></grand>
<grand name="eee" id="11111" sex="f" status="d" child="" father="1111"></grand>
<grand name="fff" id="11112" sex="m" status="d"child="" father="1111"></grand>
</tree>
c# code that display the first node is:
InitializeComponent();
XDocument xdoc = XDocument.Load(" http://domaim.net/tree/index.xml");
var name = xdoc.Descendants("grand").First().Attribute("name").Value;
var sex = xdoc.Descendants("grand").First().Attribute("sex").Value;
var alive = xdoc.Descendants("grand").First().Attribute("status").Value;
var child = xdoc.Descendants("grand").First().Attribute("child").Value;
var id = xdoc.Descendants("grand").First().Attribute("id").Value;
var father = xdoc.Descendants("grand").First().Attribute("father").Value;
textBox1.Text = name;
if (sex == "m") textBox2.Text = "male"; else textBox2.Text = "female";
if (child == "") textBox4.Text = "no child"; else textBox4.Text = child;
if (alive == "d") textBox3.Text = "dead"; else textBox3.Text = "alive";
here I displayed the node its id="1", now i want to display all nodes that its "father" attribute is equal 1. i want to display thier attributes of these nodes within datagridview,(bbb & ddd).
thank you for all.

Try this. You have an error in the XML that you need to put a space before child in the last row.
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Windows.Forms;
namespace WindowsFormsApplication1
public partial class Form1 : Form
public Form1()
InitializeComponent();
DataSet ds = new DataSet();
ds.ReadXml(@"c:\temp\index.xml");
dataGridView1.DataSource = ds.Tables["grand"];
DataTable fatherRows = ds.Tables["grand"].AsEnumerable()
.Where(x => x.Field<string>("father") == "1").CopyToDataTable();
dataGridView2.DataSource = fatherRows;

"Source file does not conform to XML Schema!" error at Import Server

Dear SDN,
When I run Import Server the import job stopped with the error "Source file does not conform to XML Schema!" in Log file. I used MDM SP05 Patch01 and HF1.
Both of 2 Import Server have same problems. Of course it works in Import Manager.
What do I have to check?
Regards,
Eric

Hi Eric
Just confirm this...
One needs to load XML schema file in MDM and can be done by specifying this file in Port .
Refer this link.
http://help.sap.com/saphelp_mdm550/helpdata/en/fa/69b20ae0ae4b158a3f6d025b3d3847/content.htm
Just make sure that corresponding XSD file is specified in the port
Regards

Problems importing an XML Schema

Hello,
I am trying to import an XML schema using the MDM Console.
In the Console Hierarchy tree I right-click on the MDM repository into
which I want to import the XML schema and choose Import
Repository Schema from the context menu and finally I choose a simple XML file.
Then an message appears: "MDS Version mismaths. Upgrade the source repository to the latest version and import the original schema again"
I use the SAP MDM Console for Windows, version 5.5 SP4. There is another way to import an schema in my repository? This Console version really doesn't support it?
Thank you.
Could I import my Schema of my repository using MDM Import manager?

Hi Marta,
MDM Console will not update the schema.If you select an xml schema in the import manager and try to specify an xml file with different structure,Then it will give you error and will not allow you to import.
You define xml schema into MDM console so that u can import data into MDM repository from the xml file or files having same structure as defined into xml schema table of repository.
The XML Schema drop-down list in Import manager includes an entry for each XML schema you define in the MDM Console. For each XML Schema defined in the console, you can select multiple XML source files, each having the same structure.
Hope it will help you.Let me know the result and further queries if any.

Please remark if it helped you.
Thanks,
Shiv Prashant Dixit

Need to add a new field to the Schema for MDM Syndicator

We are running MDM 5.5 SP6.
We have a requirement to add a new field and syndicate the new field to the our Procurement System.
I was able to add the new field to the repository and schema in SAP MDM Console. However, when I went into the Syndicator to map the new field (which I do see) to the new Schema field, I don't see the new field to map in the Schema.
How can I change the existing syndication jobs (11 of them) to use the new Schema? Or do I have to recreate all of them?
Thank you in advance!!!

Hi Janynne,
I hope you have modify the Syndication XSD(add new field) and then load it in XML Schema table of MDM Console, right ?
If you have done it, now open MDM Syndicator>Go to File>Open, select the required Remote system and Available map.
Now your existing map will be loaded which has not the required added field, Now again, go to file-->Export.
Give file name and save this syndication map on your Desktop. Once you have done this.
Go to File>New>Select respective remote system and Type as XML Schema if you have loaded this XSD in Console else select Type as XML Schema file and select the modified XSD (added new field XSD) from Desktop. Once it is loaded, import the existing syndication map(which you have exported as said above) which should have all the fields mapped, now in target side you will have here new added field too, map it with required source field in Item Mapping and then go to file>Save as>select the required Remote system and give new map name. Use this map for exporting files for future reference.
Also, if your are using Port Concept, you need to change the Properties Map and XML Schema in Port of MDM Console.
Regards,
Mandeep Saini

Can you generate a Schem Collection from an SQL Query

Is there an Option that allows you to generate and XML Schema Collection in a Select Statement that will be loaded either to a table or an application.
An example
SELECT Column1, Column2, Column3
FROM table
FOR XML PATH('');
An easy way to generate a template or a start without having to type from scratch?
Antonio

Hi Antonio,
The FOR XML clause
can generate the XML schema, you can reference the optional XMLSCHEMA.
XMLSCHEMA [ ('TargetNameSpaceURI') ]
Returns inline XSD schema. You can optionally specify a target namespace URI when you specify this directive, which returns the specified namespace in the schema. For more information, see
Generate an Inline XSD Schema.
If you have any question, feel free to let me know.
Best regards,
Eric Zhang
TechNet Community Support

Xml schema of ordrsp

Hi,
How can i get the xml schema of idoc ordrsp in sap.And also how to build xml in java using Sapjco3.0 and sapidoc3.0.
Regards
Sri

Hey Sri,
You can get the XML schema of an IDoc in SAP via transaction WE60. There you can choose menu entry Documentation -> XML schema assuming that you're on a high enough release (I think 4.70 and higher is sufficient, in 4.6c you can only generate DTD's, but no schemas). Otherwise an XI system is always handy, because there you can easily generate schemas for any IDocs.
I'm not quite sure I understand the question about building XML. Do you want to create an XML IDoc and then use an IDocXMLProcessor class to parse it? Maybe you can elaborate a bit what you want to achieve.
Cheers, harald
p.s.: When creating an IDoc via JCo3 IDoc library you might not need any XML processing. I.e. you could create your IDoc via the IDocFactory (which you get from JCoIDoc) and then get the root segment from your IDocDocument via method getRootSegment(). Once you have the IDocSegment class you can add additional segments via methods addChild or addSibling, depending on your IDoc hierarchy.

WE60 - Error while generating the xml schema

Hi
Using the transaction WE60 I am trying to generate an XML schema for the BASIC type : DEBMDM06, Segment release - 7 and record type version - 3. Following error message is displayed. "Structure of segment E1T023W is unknown". Kindly let me know how to generate an XML schema successfully and what is the reason for this error to come up
Regards
Aruna

Hi Aruna,
It seems a dictionary error but it doesn't occurs to me. I can download the XML schema without problems in SAP ECC 6.0.
If you let me know your email I can send it zipped to you.
Reward points if helps.
Roger

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

Can't place XML into defaultTable using WinExplorier

Hi,
Oracle 9.2.0.1
My sequence of operations:
1. Register schema - successfully - can see it using WinExplorier; defaultTable and types were created;
2. Using SQLPLUS can place any XML corresponding registered schema into repository and can see it into
defaultTable.
3. BUT CANT PLACE THE SAME XML USING WinExplorier (WEBDAV) !! Using drag-and-drop operation xml just
can be inserted into repository, but doesn't appear
inti defaultTable.
It looks like XMLDB can't see xml schema in registered path.
Has anybody run into the same problem ?
Thanks in advance
Viacheslav

Hi,
Upgrade to 9.2.0.3, until I upgrade I could not get the web-dav upload to work at all.
The only problems I've had with this is if I logged on to web-dav as a different user from that which I registered the schema with. One thing I have noticed, is that the file size is shown as being 0 when the xml has been shredded successfully.
And the previous answer is right, if you use FTP you might see better error messages.
Hope it helps,
John

How to identify objects created by registering xml schema

Hi Everyone,
We are using Oracle 9i Rel2. I have registered an XML schema and I saw that there were several objects created for it table ,some types and a trigger . For some build purposes I want to exclude all of these objects which are associated with xml schema and should be able to drop and recreate the whole of oracle schema.
I see the user_types table does not have any parameter to indicate that these are autogenerated or are different. In user_types they look like any other type that a user would have created. Do any of you know how to differentiate these types created by registering XML schemas from the normal types.
Thanks for your help

There is no way I know of to differentiate between a type created by Schema Registration and another Type. You can query the XML Schema itslef to get the Typenames it relies on.
SQL> --
SQL> SQL> select nvl(extractvalue
2 (
3 value(ct),
4 '/xs:complexType/@name',
5 'xmlns:xs="http://www.w3.org/2001/XMLSchema"
6 xmlns:xdb="http://xmlns.oracle.com/xdb"'
7 ),'Local Complex Type') COMPLEX_TYPE,
8 extractvalue
9 (
10 value(ct),
11 '/xs:complexType/@xdb:SQLType',
12 'xmlns:xs="http://www.w3.org/2001/XMLSchema"
13 xmlns:xdb="http://xmlns.oracle.com/xdb"'
14 ) SQL_TYPE
15 from user_xml_schemas,
16 table
17 (
18 xmlsequence
19 (
20 extract
21 (
22 schema,
23 '//xs:complexType',
24 'xmlns:xs="http://www.w3.org/2001/XMLSchema"
25 xmlns:xdb="http://xmlns.oracle.com/xdb"'
26 )
27 )
28 ) ct
29 /
COMPLEX_TYPE
SQL_TYPE
PurchaseOrderType
PURCHASEORDER_T
LineItemsType
LINEITEMS_T
LineItemType
LINEITEM_T
COMPLEX_TYPE
SQL_TYPE
PartType
PART_T
ActionsType
ACTIONS_T
Local Complex Type
ACTION_T
COMPLEX_TYPE
SQL_TYPE
RejectionType
REJECTION_T
ShippingInstructionsType
SHIPPING_INSTRUCTIONS_T
Local Complex Type
ROOT_T
COMPLEX_TYPE
SQL_TYPE
Local Complex Type
P222_T
10 rows selected.
SQL>

Can't specify XML Schema root in MDM Syndicator

Similar Messages

Maybe you are looking for