XML Schema any element

I have a list of schema files and they a number of elements in them. But for my data extraction i use only close to 300 tags. When i register the schema I get an error that a table cannot of have more than 1000 columns. My work mate is working on Annotations and I am planning to build a new schema to make extract only these 300 tag names and also make sure the XML file can be validated like it did earlier. Explaining this i came across a complex type element called *<any>* which can be used to allow elements to be available which are not declared within the schema file.
My Original schema file looks something like below,
<xsd:complexType name="WfInformation">
<xsd:all minOccurs="0">
<xsd:element name="Company" type="WfCompany" minOccurs="0" />
<xsd:element name="HeadOffice" type="WfOffice" minOccurs="0" />
<xsd:element name="IndependentOffice" type="WfIOffice" minOccurs="0" />
<xsd:element name="AffiliateCompany" type ="WfIAOffice" minOccurs="0" />
<xsd:element name="Number" type="xsd:string" minOccurs="0" />
<xsd:element name="ReferenceID" type="xsd:string" minOccurs="0" />
</xsd:all>
</xsd:complexType>
of the above list of items i use only elements Company, HeadOffice, Number. After reading through some documentation I wanted to <any> tag like below,
<xsd:complexType name="WfInformation">
*<xsd:sequence>*
<xsd:element name="Company" type="WfCompany" minOccurs="0" />
<xsd:element name="HeadOffice" type="WfOffice" minOccurs="0" />
*<xsd:any processContents="lax"/>*
*<xsd:any processContents="lax"/>*
<xsd:element name="Number" type="xsd:string" minOccurs="0" />
*<xsd:any processContents="lax"/>*
*</xsd:sequence>*
</xsd:complexType>
My question is if I am correcting the lines as i mentioned above will be Register schema again fail with same reason that i have 1000 columns. As i understand every element inside an Complex element is stored as a column value. In that case will this redesign work. Or is there any other way to approach re-desgin the XML Schema.

Thanks. I think that leaves out my option to create a totally new Schema to suit my XML files.
Only other option we have is to use Annotations.
I think my colleague - eoin62 would have shared the XML Schema files earlier through your oracle email address.
Please refer thread - How to register multiple XSD files
But we received a reply and we knew very little on how to make changes to Admin.xsd and how would that solve our problem. Please correct me if i am incorrect. Because the biggest Schema was estimate.xsd that has close to 800+ elements. I am not sure if my colleague sent you the necessary tag names we use within the Schema. We have close to around 300 tags we use. But our combined XML Schema has close to 1600+ If we have to annotate, i thought it would be better we tell Oracle which tagswe need, which inturn should should help better create XMLtype table against a Schema and work on performance.
Your earlier reply was,
Basically in XML Schema Admin.xsd element AdminCompin WorkfileTypeneeds to be stored Out of line..
Add the annotations xdb:SQLInline=”false” and xdb:defaultTable=”ADMIN_COMP_XML”. to the element..
if you can share with our XML Schema on how to annotate or if you can share a location that shows how an annotated or non-annotated Schema works that would help us correcting our Schema files.
Thanks for all your support. We have gone a long way in XML Parsing in the last 6 weeks.
Edited by: beta32c on Feb 19, 2013 12:09 AM

Similar Messages

Data Insertion, XML Schema Specifying Element minOccurs="1

An XML schema having an element with attribute minOccurs="1" has been successfully registered. A table was created based on that schema. Inserting data both with and without that element works successfully. Why is this?

The only thing right now, I can think of, is that the database doesn't recognize it as being controlled via / depends on a registered XML Schema. See the FAQ on this forum for examples (See here: How does XML DB handle XML Schema Validation ?

XML Schema for elements names varying with number

HI ,
I have an xml document where the no of tags are unlimited ,but having same name +tag number
ex:-<name1>String</name1>
<name2>String</name2>
<name3>String</name3>
<name4>String</name4>
<name5>String</name5>
I need to design a schema for this xml,where the name tag can go up to any number,i am not able to use attributes,as the system recieving this xml is demanding this format.
can any one give me a schema for this,so that i will be able to generate jaxb objects to generate xml from the schema,in my webservice

Hi Abhishek,
Thanks for your reply
In our project
The remaining part of the code we are dealing with schema and jaxb objects..i am having only this xml which is pending....
as of now i was creating this xml in a dynamic passion only using DOM.
my plan is to atleast do like below
expected result
<doc>
<tag1></tag1>
<tag2></tag2>
<tag3></tag3>
<tag4></tag4>
<tag5></tag5>
</doc>
I am able to generate the below xml
Actual
<doc>
<tag></tag>
<tag></tag>
<tag></tag>
<tag></tag>
<tag></tag>
</doc>
I am trying to write an XSL and transform above result to the expected result. But still not be able to write the xsl to match mmy expected result
Edited by: Aditya on Aug 3, 2011 7:26 AM

MDIS ValueX XML Structure, element TEXT not found in xml schema

When you extract ECC Contract through MECCM using port ERP Contract Data Transmission, if your mapping isn't correct 2 exception types are created: StructuralX or ValueX (and ImportX but I haven't seen this type of exception yet).
Anyone noticed that the structure of the XML messages are actually different? The XSD for structuralX files are the same as the files placed in the "ready" folder, where as the XSD for the valueX files are DIFFERENT, and contain a tag called <TEXT>.
This raises an issue when we're trying to handle exceptions in Import Manager using the type Port. We get error "Logon Error: Source file does not conform to XML Schema. Element <TEXT> not found in xml schema".
We can process exceptions in the structuralX folder, but not in the valuex folder because the xml file structure in the valuex folder is different.
Just wondering if anyone else has had this issue or has resolved it. We will open message with SAP.
Thanks.

Hello
What is your MDM version ?
this issue happened in old MDM 7.1 versions but was fixed in SP-2 unless you mapped Clone fields and in this case the fix is a bit later.
In MDM 7.1 the latest builds of SP-2 and SP-3 should have the fix for all issues. But if you use MDM 5.5 then some issues regarding XSD conversion for exception where not addressed due to technical issues.
The workaround for MDM 5.5 (If you use a late build of SP-6 Patch-4 or SP-6 Patch-5) is to use the original file to fix the exception and not the file in the exception folder.
Please notice that when you have Structural exception then all the Source XML file will go to the Exception folder.
But in case of Value Exception - The source XML file will be dropped in the archive folder and another XML file containing VXR's (Virtual Extended Records) will be dropped in the exception folder, Therefore will have a different structure.
Hope it helps.
Thanks.
Best Regards.
Yaron.

Obtain name into name element (XML schema)

Hello abappers,
I need obtain the next code XML schema
<xs:element name='AuditFile'>
 <xs:complexType>
 <xs:sequence>
 <xs:element ref='Header' />
 <xs:element ref='MasterFiles' />
 <xs:element name='GeneralLedgerEntries' />
 <xs:element name='SourceDocuments' />
 </xs:sequence>
 </xs:complexType>
</xs:element>
The code:
l_element_Audito TYPE REF TO if_ixml_element,
l_document TYPE REF TO if_ixml_document.
l_element_AuditFile TYPE REF TO if_ixml_element,
l_element_GeneralLedgerEntries TYPE REF TO if_ixml_element,
l_element_SourceDocuments TYPE REF TO if_ixml_element,
l_element_Header TYPE REF TO if_ixml_element,
l_element_MasterFiles TYPE REF TO if_ixml_element,
Fill root node with value AuditFile
 l_element_AuditFile = l_document->create_simple_element(
 name = 'AuditFile'
 parent = l_element_Audito ).
Create element 'Header' as child of 'AuditFile'
 l_element_Header = l_document->create_simple_element(
 name = 'Header'
 parent = l_element_AuditFile ).
Create element 'MasterFiles' as child of 'AuditFile'
 l_element_MasterFiles = l_document->create_simple_element(
 name = 'MasterFiles'
 parent = l_element_AuditFile ).
Create element 'GeneralLedgerEntries' as child of 'AuditFile'
 l_element_GeneralLedgerEntries = l_document->create_simple_element(
 name = 'GeneralLedgerEntries'
 parent = l_element_AuditFile ).
Create element 'SourceDocuments' as child of 'AuditFile'
 l_element_SourceDocuments = l_document->create_simple_element(
 name = 'SourceDocuments'
 parent = l_element_AuditFile ).
and with the this code obtain:
<xs:element name="AuditFile">
<xs:complexType>
<xs:sequence>
<xs:element ref="Header" />
<xs:element ref="MasterFiles" />
<xs:element ref="GeneralLedgerEntries" />
<xs:element ref="SourceDocuments" />
</xs:sequence>
</xs:complexType>
</xs:element>
Can you help me, please?
Cordial greetings.

Hello abappers,
I need obtain the next code XML schema
<xs:element name='AuditFile'>
 <xs:complexType>
 <xs:sequence>
 <xs:element ref='Header' />
 <xs:element ref='MasterFiles' />
 <xs:element name='GeneralLedgerEntries' />
 <xs:element name='SourceDocuments' />
 </xs:sequence>
 </xs:complexType>
</xs:element>
The code:
l_element_Audito TYPE REF TO if_ixml_element,
l_document TYPE REF TO if_ixml_document.
l_element_AuditFile TYPE REF TO if_ixml_element,
l_element_GeneralLedgerEntries TYPE REF TO if_ixml_element,
l_element_SourceDocuments TYPE REF TO if_ixml_element,
l_element_Header TYPE REF TO if_ixml_element,
l_element_MasterFiles TYPE REF TO if_ixml_element,
Fill root node with value AuditFile
 l_element_AuditFile = l_document->create_simple_element(
 name = 'AuditFile'
 parent = l_element_Audito ).
Create element 'Header' as child of 'AuditFile'
 l_element_Header = l_document->create_simple_element(
 name = 'Header'
 parent = l_element_AuditFile ).
Create element 'MasterFiles' as child of 'AuditFile'
 l_element_MasterFiles = l_document->create_simple_element(
 name = 'MasterFiles'
 parent = l_element_AuditFile ).
Create element 'GeneralLedgerEntries' as child of 'AuditFile'
 l_element_GeneralLedgerEntries = l_document->create_simple_element(
 name = 'GeneralLedgerEntries'
 parent = l_element_AuditFile ).
Create element 'SourceDocuments' as child of 'AuditFile'
 l_element_SourceDocuments = l_document->create_simple_element(
 name = 'SourceDocuments'
 parent = l_element_AuditFile ).
and with the this code obtain:
<xs:element name="AuditFile">
<xs:complexType>
<xs:sequence>
<xs:element ref="Header" />
<xs:element ref="MasterFiles" />
<xs:element ref="GeneralLedgerEntries" />
<xs:element ref="SourceDocuments" />
</xs:sequence>
</xs:complexType>
</xs:element>
Can you help me, please?
Cordial greetings.

How to enhance the fields into xml schema?

Hi Expert,
We are at SRM-MDM Catalog 3.0 SP02, we enhanced two fields in the contract data which were transfered from the SRM via xml. But when the MDM import manage do the mapping between the xml file and MDM catalog items automatically, it will bring a exception with the mapping error. The error message is "Logon Error: Source file dose not conform to XML schema. Element <field name> not found in the xml schema."
How could I add these fields to xml schema?
The problem is resolved.
Edited by: Wendrin Duan on Nov 5, 2009 5:01 AM

Hi
Did changing the Name of the Schema in the console to be the same as the Name of the Schema file solve the problem.
I take it you used the output file with the custime fields to create the Schema file so as to have a consistent structure.
REegards,
Iggy

XML Schema Element any

Is there any workaround or planned support for the XML any tag in future for PI 7.1?

We have a situation where a sending system is sending a message which conforms to a schema which includes an <xs:any minOccurs="0"/> element. I have access this XSD so could (in theory) create a PI message type. However, the message type can't handle the <any> element - when designing the mapping you don't have access to the elements which could be replaced into the <any> element.
Does any one have ideas, work arounds, to handle source messages whose XSD contains an <any> element?

How to bind data from script created variable to embed element of XML schema (xsd) in "Data View"

Hi, i have got another problem with livecycle designer scripting.
I have got script line which is defining of string variable:
var aaa = "this is my string";
and i have got embed XML schema like this (it`s only short part of whole file):
... xs:element name="bbb" type="xs:string"/ ...
After saving data to XML i would like to get "this is my string" as a value of my "bbb" XML element.
To save this data i`m using submit button which is connect with submit.php file on my server.
How to connect script created variable and embed XML schema element which is present on my "Data View" tab.
Please help me a bit becouse i don`t know even where to search answer of it...
Of course i know possibilities to create fake unvisible text field object and bind it with 'bbb' and than put "this.rawValue = aaa" to connect those two variables but i think that is not a good idea to solve it in that way. It`s too primitive

i solve it, i should write this:
xfa.datasets.data.bbb.value = aaa;

Specifying Case-Insensitive Element Names in XML Schema

Hope someone knows this!
Is it possible to define an an XML Schema Definition so that Element names in the target XML File can be case insensitive.
At the moment my Parser throws an error if the element names in the XML file do not have the exact same case as the definition in the XML schema.
E.g
In Schema i have:
<xsd:element name="HOSTINVENTORYLINE" type="HostInventoryLineType" maxOccurs="unbounded" minOccurs="0"/>
but in xml file i have
<HostInventoryLine field=""/>
or
<hostinventoryline field=""/>
Does anyone know anyway to get around this, so that the parser accepts the HostInventoryLine element in the xml as an instance of the HOSTINVENTORYLINE element defined in the schema.
Thanks in Advance
JJ
Message was edited by:
[email protected]

You could use substitution groups to handle this. You would need an entry in the schema for each valid capitalization. This won't scale well if you want to be completely case insensitive, but if you only support lower case, upper case, and camel case it should do the trick.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
 <xs:complexType name="HostInventoryLineType">
 <xs:sequence>
 <xs:element name="an-element" type="xs:string"/>
 </xs:sequence>
 </xs:complexType>
 <xs:element name="HostInventoryLine" type="HostInventoryLineType"/>
 <xs:element name="HOSTINVENTORYLINE" type="HostInventoryLineType" substitutionGroup="HostInventoryLine"/>
 <xs:element name="hostinventoryline" type="HostInventoryLineType" substitutionGroup="HostInventoryLine"/>
</xs:schema>-Blaise

Specifying nested element with two different XML Schema

Hello,
I am trying to convert one xml file to another file. I figure data services would be great for this.
My problem relates to how to have a source xml file with a certain xml schema be transformed to one of a different xml schema. I cannot build the nested elements of the target schema.
From the source xml I only need four fields. But they need to be nested three levels in the target xml.
Source
<DRUG_PRODUCT_LST xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <DRUG_ITEM>
 <DRUG_PRODUCT_ID>113083</DRUG_PRODUCT_ID>
 <DIN_PDIN>2317559</DIN_PDIN>
 <HC_BRAND_NAME>PMS-SILDENAFIL</HC_BRAND_NAME>
 <HC_ATC_CODE>G04BE03</HC_ATC_CODE>
 </DRUG_ITEM>
<DRUG_PRODUCT_LST
Target
<?xml version="1.0" encoding="ISO-8859-1"?>
<CODES>
 <CODE_TYPES>
 <CODE_TYPE>
 <COD_CODE>113083</COD_CODE>
 <COD_DESCR>PMS-SILDENAFIL</COD_DESCR>
 <COD_SOURCE>G04BE03</COD_SOURCE>
 <COD_NPSA>2317559</COD_NPSA>
 </CODE_TYPE>
 </CODE_TYPES>
</CODES>
I have tried using an xml pipline to unnest the source, then use a query transform to re-nest for the target. But I do not know how to specify the input schemas.

Hello,
I am trying to convert one xml file to another file. I figure data services would be great for this.
My problem relates to how to have a source xml file with a certain xml schema be transformed to one of a different xml schema. I cannot build the nested elements of the target schema.
From the source xml I only need four fields. But they need to be nested three levels in the target xml.
Source
<DRUG_PRODUCT_LST xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <DRUG_ITEM>
 <DRUG_PRODUCT_ID>113083</DRUG_PRODUCT_ID>
 <DIN_PDIN>2317559</DIN_PDIN>
 <HC_BRAND_NAME>PMS-SILDENAFIL</HC_BRAND_NAME>
 <HC_ATC_CODE>G04BE03</HC_ATC_CODE>
 </DRUG_ITEM>
<DRUG_PRODUCT_LST
Target
<?xml version="1.0" encoding="ISO-8859-1"?>
<CODES>
 <CODE_TYPES>
 <CODE_TYPE>
 <COD_CODE>113083</COD_CODE>
 <COD_DESCR>PMS-SILDENAFIL</COD_DESCR>
 <COD_SOURCE>G04BE03</COD_SOURCE>
 <COD_NPSA>2317559</COD_NPSA>
 </CODE_TYPE>
 </CODE_TYPES>
</CODES>
I have tried using an xml pipline to unnest the source, then use a query transform to re-nest for the target. But I do not know how to specify the input schemas.

Xml Schema xs:choice element in dynamic forms

Hi all,
I'm developing an xml schema for creating the data model of a form. I connect LC Designer-8.2ES to this schema.
In the schema I do have mutually exclusive elements implemented with a <xs:choice> element. A very comparable situation was described in this thread : http://www.acrobatusers.com/forums/aucbb/viewtopic.php?id=123 in 2007.
The problem, as related in this thread, is that only the very first element of the choice is displayed in the generated pdf and I don't know how to display all parts as a real choice. So what's the best way to let user fill in one part or the other of the choice?
Does it need to be implemented with scripting (xfa...myform.presence = visible | hidden)?
I want that only the filled element of the choice be exported from the form, the resulting xml being valid according the schema. I seems to work, but as of now, only for the first element...
BTW, what's the best document describing what parts of xml schema are usable in dynamic XFA forms? Is it 100% compatible? I've observed that the constraints in my schema are not validated in the forms. Shouldn't xml schema generate validating script in LCD? Does it apply for a subset of xml schema?
Thanks in advance,
jgrd

Hi all,
finally, I understand that we cannot use "anonymous" sequences neither in LiveCycle (like this following example where person might have many email)
 <xs:element name="person">
 <xs:complexType>
 <xs:sequence maxOccurs="unbounded">
 <xs:element name="email" type="xs:string"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
valid instance with 3 emails :
<person xsi:noNamespaceSchemaLocation="Untitled39.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <email>String</email>
 <email>String</email>
 <email>String</email>
</person>
In LC Designer, element with same name (<email>) are not used AFAK. Maybe I'm wrong?
The same hands with <xs:choice> where only first choice appears in pdf although being present in LC Designer.
As for sequences, my idea is to produce <email1>, <email2>, etc. in a static schema, before connecting schema's data to LCD.
Hope someone can show up and tell it's the right way or not.
Regards
jgrd

Insert XHTML elements inside XML schema

Hi,
My oracle version is 10.2.0.2.0. Following this suggest :
http://forums.oracle.com/forums/thread.jspa?messageID=835251&#835251
I tried to create a schema in this way:
<?xml version="1.0"?>
<xs:schema
 xmlns:xs="http://www.w3.org/2001/XMLSchema"
 xmlns:xdb="http://xmlns.oracle.com/xdb"
 targetNamespace="http://test.example.it/test"
 xmlns="http://test.example.it/test"
 elementFormDefault="qualified"
 attributeFormDefault="unqualified">
 
 <xs:element name="Project">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="AnnoBando" type="xs:string" xdb:SQLType="CLOB"/>
 <xs:element name="AnnoBando2" type="xs:string"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
</xs:schema>In this schema only element "AnnoBando" contains XHTML elements, my question is, when I upload my xml document, can I pass directly XHTML elements in this way?
insert into TESTSQLTYPE values ('codice', xmltype('
<Project
 xmlns = "http://test.example.it/test"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:xml="http://www.w3.org/XML/1998/namespace"
 xsi:schemaLocation = "http://test.example.it/test http://test.example.it/test2.xsd">
 <AnnoBando> text bolded text text</AnnoBando>
<AnnoBando2>empty text</AnnoBando2>
</Project>
'))or I should insert html entities of "<" and ">" of the element?
If i try to insert the xml example specified here I get this error:
ORA-31187: Cannot Add Node 'b' (type='element') to Simple Type Node '/Project/Annobando'Thanks for your help.
Stefano

Try these two:
1.
======
<AnnoBando>![CDATA[text bolded text text]]</AnnoBando>
=======
2.
======
<AnnoBando> text &lt;b&gt;bolded text&lt;/b&gt; text</AnnoBando>
=======
Basically, because '<' and '>' are used for element declarations in XML, you cannot include them 'nude' in the element content. The above are two methods of escaping those characters.

Leigh.

Any function module/program to write-xml schema of a idoctype

Hi experts,
I need to write the xml format into an internal table.
input---idoc type.
output--xml schema file in an internal table/or in some file.
Through we60 we can get the xml schema.but through some program i want to get it .how to go for it.
Any function module do you suggest which fits to this requirement and do the work for me.
For ex: idoc type--orders05
Message was edited by:
dasr r

Hello Dasr
There are several function modules available. Please check yourself if any of them matches your demands.
EDIN                           IDoc: Eingangsverarbeitung
IDOC_INBOUND_XML_VIA_HTTP      eingang über http
IDOC_XML_FROM_FILE             IDoc: Eingangsverarbeitung vom XML über Dateischnittstelle
IDOC_ADAPTER_MB                Message Broker IDoc Adapter
IDX_IDOC_TO_XML                Konvertierung IDoc nach IDoc XML im XMB
IDOC_XML1                      erweiterte Tabellenpflege (generiert)
IDOC_XML_DISPLAY               Anzeigen eines IDocs in XML-Format mit XSL
IDOC_XML_TRANSFORM             Anzeigen eines IDocs in XML-Format mit XSL
Regards
Uwe

Any workarounds for not supported features of XML Schema

Hi,
We are trying to generate JAVA source code by providing a xsd.
This XML Schema file has all sorts of Identity constraints & attribute wildcards.
Due to the above reasons I am unable to generate the code.
Are there any workarounds? If so Please share those.
Thanks & Regards,
Priti Ranka

I am sorry I did not mention the tech. being used.
I am using JAXB for the above task.

Any tools for converting java class to xml schema ?

Hi,
Are there any tools out there that can convert my java class to xml schema. How such tools take care of java collections like HashTable, ArrayList etc. in my class structure. I am not interested in writing any configuration files(like jaxb configuration files, jibx binding xml files etc.) for serving this purpose and the can be able to give me xml schema from the java classes. Please suggest ...
I am not sure even JAXB 2.0 allows me to do this without writing any jaxb configuration files or annotations in my java class which is not there in JDK 1.4.2
Thanks & Regards,
Kr.

Hi,
You can convert the EDI file to XML in any of the ways
1) Using third party seeburger adapters
2) Conversion agent
3) Stylus studio.
I think using java code it will be very difficult.
Thnx
Chirag

XML Schema any element

Similar Messages

Maybe you are looking for