Problem Importing OAG v9 BOD XML to IS

Hello Every One ,

We are using IS 6.5 and developer 6.5. We have to import Standard OAG BOD v9 Xmls (not xsd) into IS. We dont want to apply any constraint on the data. When we imported one of the OAG BOD XML v9, …for all the fields, the “Required Constraints” Property has been set to true by default. This is a big problem for us , now we are manually changing this Property ( Required = False), There are more than 1000 fields in one imported document. Do we have some way by which we can set required = false ??

Any help would be highly appreciated.

You could edit the XSD and do a change-all on the string minoccurs=1 to change it to minoccurs=0

Note: When you do this would be able to create documents that do not conform to the OAG BOD v9 schema and that would not be valid if validated against that schema.

Mark

Hi Mark,

Thanks for replying. We are not referring xsd at all. we are just importing the OAG BOD XML for its structure. We have also REMOVED all URIs mentioned below) from all the OAGBOD XMLs before importing them in IS –


xmlns=“http://www.openapplications.org/oagis/9” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance” xsi:schemaLocation=“http://www.openapplications.org/oagis/9 …/…/BODs/Developer/ShowItemMaster.xsd”


Also, I’m pasting a ShowitemMaster.xsd here . “minoccur” is nowhere in the xsd.


[highlight=xml] <?xml version="1.0" encoding="utf-8"?>

<xsd:schema xmlns:xsd=“http://www.w3.org/2001/XMLSchema” xmlns=“http://www.openapplications.org/oagis/9” targetNamespace=“http://www.openapplications.org/oagis/9” elementFormDefault=“qualified” attributeFormDefault=“unqualified”>
<xsd:include schemaLocation="…/…/Resources/Nouns/ItemMaster.xsd"/>
<xsd:element name=“ShowItemMaster” type=“ShowItemMasterType”>
xsd:annotation
<xsd:documentation source=“http://www.openapplications.org/oagis/9”>The purpose of the ShowItemMaster is to supply ITEM Information to another business application module. This request may be used as a response to a GetItemMaster request or as the result of some other business event. This BOD does not usually cause updates to occur.

There are many possible business applications in several environments that may use this capability. For example, an MRP, Inventory, or Manufacturing business application could use this to request item information.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name=“ShowItemMasterType”>
xsd:complexContent
<xsd:extension base=“BusinessObjectDocumentType”>
xsd:sequence
<xsd:element name=“DataArea” type=“ShowItemMasterDataAreaType”>
xsd:annotation
<xsd:documentation source=“http://www.openapplications.org/oagis/9”>Is where the information that the BOD message carries is provided, in this case ShowItemMaster. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (ItemMaster).</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name=“ShowItemMasterDataAreaType”>
xsd:sequence
<xsd:element ref=“Show”/>
<xsd:element ref=“ItemMaster” maxOccurs=“unbounded”/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>[/highlight] *****************************

Creating Integration Server document types from XML instance documents is a bad idea. If the instance document does not contain values in optional elements, those elements will be omitted from the document type. Also, none of the data content constraints will be added to the document type.

The ShowItemMasterType.xsd uses an xs:include statement to reference the ItemMaster.xsd schema. If you drill down far enough, you’ll find the underlying definitions for this schema.

My strong recommendation is to create your IS document types and IS schemas from the XML schemas and not from XML instance documents. See the “webMethods Integration Server Schema Reference Version 6.5” for good information on how IS represents XML schemas. This document can be found in your webm_home\Developer\doc\guides folder.

Mark