XSD generated using EAI XML XSD Generator doesn't define string lengths.

(Doc ID 1926710.1)

Last updated on AUGUST 16, 2016

Applies to:

Siebel Life Sciences CRM - Version [IP2013] and later
Information in this document applies to any platform.


Product Type: Siebel Life Sciences CRM
Version: [IP2013]
OS platform: Microsoft Windows (32-bit)
DB: Oracle Database - Enterprise Edition
Env type: All

Statement of Issue:
In Tools, a XSD is being generated for an IO using the EAI XML XSD Generator. In 8.0, the XSD included a definition of the length of fields of type string. String lengths aren’t defined in

For example, a XSD was generated for the standard IO Sample Account.

The 8.0 XSD includes:

<xsd:complexType name="Account">

<xsd:element name="Name" type="xsdLocal:string100" minOccurs="0" maxOccurs="1">
<xsd:simpleType name="string100">
<xsd:restriction base="xsd:string">
<xsd:maxLength value="100" />

The 8.1 XSD includes:

<xsd:complexType name="Account">

<xsd:element name="Name" type="xsd:string" minOccurs="0" maxOccurs="1">

The same behavior is mentioned in relation to WSDL generation in [Field sizes not included in XSD schema of WSDL Generated Siebel Client] (Doc ID 1515661.1). In this case, string lengths weren’t included in the XSD after the user property EnableSimpleTypeLength = Y was added to the IO.

Expected Behavior:
String lengths are defined in the XSD.

Actual Behavior:
String lengths aren’t defined in the XSD.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms