XSD Schema Generation
XSD Schema Generation
User Guide
XSD Schema Generation
Overview .................................................................................................................................................. 3
Architecture/Design ................................................................................................................................. 3
XSD Schemas ...................................................................................................................................... 3
Repeating Groups ................................................................................................................................ 6
Repeating Subgroups .......................................................................................................................... 6
White Space ......................................................................................................................................... 7
Setup ....................................................................................................................................................... 8
T24 Schema Generation ...................................................................................................................... 8
T24 F.SCHEMA table .......................................................................................................................... 8
T24 Standard Selection ....................................................................................................................... 8
Schema Override Options ................................................................................................................... 8
T24_XSD_MAX_NOINPUTLEN ....................................................................................................... 8
T24_XSD_MOD_LEN_PERCENT ................................................................................................... 9
T24_XSD_MAINTAIN_DOM ............................................................................................................ 9
T24_XSD_TEST............................................................................................................................... 9
EBS.CREATE.FILE............................................................................................................................ 10
XSD Schema Registration ................................................................................................................. 11
EB.CONVERT.TABLE Utility ............................................................................................................. 12
Manual Operation .............................................................................................................................. 13
Appendix ................................................................................................................................................ 14
Appendix A- CUSTOMER XML Schema ........................................................................................... 14
Appendix B - CUSTOMER Record Example ..................................................................................... 50
Appendix C – Oracle Structured Storage Description ....................................................................... 52
Description of Controlling Group........................................................................................................ 53
Description of Standalone Group....................................................................................................... 54
Nested Tables .................................................................................................................................... 55
No part of this document may be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without the express written permission of TEMENOS Holdings NV.
Overview
This document provides a guide for the generation and utilisation of the T24 XML Schema Definition
(XSD) documents. These T24 XML Schema Definitions are used to describe the structure of the T24
XML documents, which are used when storing T24 data in an XML column type.
The XML storage model includes several properties, which enable T24 to leverage the many benefits
of deployment on a Relational Database Management System (RDBMS).
The XSD document provides T24 with the capability to provide a precise description of the XML data
content and relationships in a universal format which conforms to standards specified be the W3C
world independent standards organisation.
The XML Schema provides the following definitions:
rd
These definitions can be used by 3 parties to either extract data content from an XML document or
query several XML documents using industry recognised standards tools such as XML Query, XPATH
expressions or SQL XML extensions.
The majority of T24 tables have a layout as defined by the T24 program modules. This layout is
interrogated to produce the initial description of each of the fields in the table along with
interdependencies such as controlling fields, etc. This information is then used to programmatically
generate the XML Schema Definition for the specified table.
The XML Schema definition can be used in conjunction with RDBMS processes, such as Oracle
Structured Storage (XML DB) to interpret XML documents and shred the documents into RDBMS
tables.
Architecture/Design
XSD Schemas
The T24 XML Schema Definitions conform to the W3C Standards regarding Schema Definitions. In
addition to the required schema element definition the T24 XML Schema Definitions also contain
information specific to the T24. These fields are contained within application information elements
<appinfo></appinfo> and have special significance to T24 utilities only.
In the top level element three properties and there values are specified. These properties are used to
determine the current status of the XML Schema Definition.
e.g
<xsd:appinfo>
<xsd:hasProperty name="locked" value="no" />
<xsd:hasProperty name="useschema" value="no" />
<xsd:hasProperty name="register" value="no" />
</xsd:appinfo>
The ‘locked’ property is used to determine whether or not the current XML Schema Definition in the
F.SCHEMA table can be overwritten.
The ‘useschema’ property is used by the T24 EBS.CREATE.FILE module and RDBMS Conversion
process to determine if the XML Schema Definition should be used when creating tables associated
with the Schema.
The ‘register’ property is used by the T24 EBS.CREATE.FILE module and RDBMS Conversion
process to determine if the XML Schema Definition should be registered (i.e. Use Structured Storage
in the case of Oracle) when creating tables associated with the Schema.
The above properties can be modified prior to an RDBMS Conversion or by the EB.CONVERT.TABLE
utility when converting tables to XML Schema based tables (i.e. Oracle Structured Storage ).
The <appinfo> elements are also used to contain cross reference information to the T24 legacy
dictionary information.
e.g.
<xsd:appinfo>
<xsd:hasProperty name="fieldtag" value="Mnemonic" />
<xsd:hasProperty name="fieldnumber" value="1" />
<xsd:hasProperty name="fielddatatype" value="string" />
<xsd:hasProperty name="fieldfmt" value="" />
<xsd:hasProperty name="fieldlen" value="10" />
<xsd:hasProperty name="fieldinputlen" value="10" />
<xsd:hasProperty name="fieldgroupnumber" value="0" />
<xsd:hasProperty name="fieldmvgroupnumber" value="0" />
<xsd:hasProperty name="fieldshortname" value="c1" />
<xsd:hasProperty name="fieldname" value="MNEMONIC" />
<xsd:hasProperty name="fieldcolumnname" value="MNEMONIC" />
<xsd:hasProperty name="fieldgroupname" value="" />
<xsd:hasProperty name="fieldmvgroupname" value="" />
<xsd:hasProperty name="fieldjustification" value="L" />
<xsd:hasProperty name="fieldtype" value="D" />
</xsd:appinfo>
The “fieldtag” property specifies the captialised element name for the field, this is the element tag used
for the XML Schema Definition.
The “fieldnumber” property is a cross references to the element field of the internal record structure.
The “fieldatatype” property defines the element data type used for the internal record structure. These
type can be “string” or “numeric”. Currently this data type is internal to T24 only and the XML Schema
Definition data type is always specified as type “string”.
The “fieldfmt” property defines the format of the data element, currently the internal formatting types
are “date” and “decimal” for the “numeric” data type and only internal to T24.
The “fieldlen” property defines the length of the field specified for the internal record structure, this is
the defined length internal to T24.
The “fieldinputlen” property defines the field length for the internal record structure, this is the length
used for the XML Schema Definition. This value will either be the fieldlen value (modified by the
MOD_LEN_PERCENT override) or in the case of a noinput field a value of 60 (or the value specified
by the MAX_NOINPUTLEN override)
The “fieldgroupnumber” defines the controlling field for the group of values. (See later)
The “fieldmvgroupnumber” defines the controlling field for the subgroup of values. (See later)
The “fieldshortname” is a reference to the short tag element name that would be used for non schema
based table definitions.
The “fieldname” property cross references the legacy dictionary field name. These field names may
contain metadata characters.
The “fieldcolumname” is a reference to the SQL columnname for the field, whereby metadata
characters would be changed to underscore.
The “fieldgroupname” is a cross reference to the tag name of the controlling field for the group of
values.
The “fieldmvgroupname” is a cross reference to the tag name of the controlling field for the subgroup
of values.
The “fieldjustfication” property is a cross reference to the expect format of the internal record structure
and implies how the field should be sorted. i.e. Right Justified for numeric sort else Left Justified.
The “fieldtype” property is a cross reference to the data type and can be “D” for data, “N” for numeric
or “S” for string. Currently this field is only for internal reference and not used in the XML Schema
Definition when describing element data types.
The data type for each of the elements in the T24 XML Schema definition is an XML “simpleType” of
generic XML type “string”. The element is given a maximum length as specified by the noinput field
length.
e.g.
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
Repeating Groups
Repeating fields within the internal T24 record are translated into two types of groups.
The first type is defined in the T24 XML Schema Definition by the single occurrence of a Group
Element or ‘g’ type specified as an xsd complexType, which in turn contains the element for the single
repeating value. This element can occur many times and hence is specified as
maxOccurs=”unbounded”.
This type of element would be represented in the Oracle Structured Storage as a nested array of
single values within the group element array specified in the parent table.
The second type is defined in the T24 XML Schema Definition again by the single occurrence of a
Group element specified as an xsd complexType, but this time the ‘g’ type element contains a ‘m’ type
element which is also specified as a complexType. This element in turn contains the multiple set of
related elements. In this case it is the ‘m’ type element that can occur many times and hence is
specified as maxOccurs=”unbounded”. Each element within the ‘m’ type element can occur only once
and hence is set with maxOccurs=”1”.
This type of element would be represented in the Oracle Structured Storage as a nested table with
multiple columns within the group element array specified in the parent table.
Repeating Subgroups
In addition to repeating groups it is also possible for each element in the repeating set to also contain
repeating values. Similarly to the repeating groups these repeating values can either be a single set of
values or a multiple set of values.
In the case of a single set of values, these would be contained with a Subgroup ‘sg’ element type and
have the maximum occurrences set to unbounded. In the case of a repeating set of multiple values
then these would be further defined within an sub element ‘s’ type, which in turn would contain the
related values. In this case the ‘s’ type element could repeat multiple times for each set of multiple
values and hence is set with maximum occurrences to unbounded. Each element within the ‘s’ type
element can only occur once and hence is defined as maxOccurs=”1”.
White Space
The T24 XML Schema Definition defines the requirement to preserve white space within the XML
document as leading or trailing spaces can have meaning within certain fields.
As such the top level element is assigned with an attribute to preserve white space.
e.g.
Setup
T24 Schema Generation
T24 will ignore all XML Schema generation requests until the T24 Schema table has been created.
SS, I ACCOUNT
Set Field 28 to Y
Then Validate Request
The XML Schema Definition “ACCOUNT.xsd” will be created as a record in the F.SCHEMA table.
Note: In cases whereby the PGM reference contains dots or other metadata these characters will be
converted to dots.
An additional record XMLREF will also be created in the F.SCHEMA table. The @XMLREF record is
an internal cross reference record for driver translation of the XML documents and should not be
modified.
Note: If an existing schema already exists then the “locked” property in the <appinfo> element of the
schema is checked. If the value is “yes” then the schema will NOT be updated, as the schema is
deemed to be locked, this ensures a Standard Selection rebuild does not overwrite the current
schema definition.
T24_XSD_MOD_LEN_PERCENT
Some T24 tables can also contain fields whereby the field definition does not take account of decimal
points. For example a decimal field with a field length of 3 may also contain a decimal point taking the
actual field length to 4. In addition other fields within T24 can also contain metadata characters, which
will be expanded when ‘escaped’ in XML. For example an ampersand ‘&’ is expanded to the string
“&” to escape the ampersand. As such this environment variable can be used to increase the
specified field length by a per cent value to avoid insertion problems. A value of 20 per cent should
prove sufficient for most occurrences.
T24_XSD_MAINTAIN_DOM
This environment variable can be set to “true” to force the use of the Document Object Model (DOM)
and cause schema verification of each XML Document. The default value is ‘false’ .
T24_XSD_TEST
This environment variable can be used to produce test data and query statements which can then be
executed against the table to ensure that the table has been created correctly and that data can be
inserted into all of the fields without error. The queries produced can also be used to determine that
the query is translated and executed correctly according to the driver query translation rules.
EBS.CREATE.FILE
The T24 EBS.CREATE.FILE module will check for the existence of a related XML Schema Definition
when creating new tables. I
If the associated .xsd record is found in the F.SCHEMA, then the create file process will determine if
the XSD Schema should be used (i.e. The XSD schema <appinfo> properties are set as
“useschema=yes”) and also registered (i.e. The XSD schema <appinfo> properties are set as
“registerschema=yes”).
If the use schema property is set then the XSDSCHEMA qualifier will be provided to the CREATE-
FILE utility.
If the register schema property is set then the XSDSCHEMAREG qualifier will also be provided to the
CREATE-FILE utility.
This enables creation of additional companies to be based on existing registered schemas. For
example creating an ACCOUNT table for company FCO2 could use the existing ACCOUNT.xsd when
creating table FCO2.ACCOUNT.
For Example:
CREATE-FILE DATA FBNK.ACCOUNT TYPE=XMLORACLE XSDSCHEMA=ACCOUNT
The above command will automatically register the XML Schema Definition “ACCOUNT.xsd” if not
already registered and then proceed to issue the create table request with the XSD reference. The
parent table type will be of Structured Storage and contain reference to nested tables as specified by
the XML Schema Definition.
To force schema registration for MSSQL and DB2 an additional qualifier must be specified.
XSDSCHEMAREG=YES
To create a table in ORACLE which conforms to the XML Schema Definition but does not use
Structured Storage the above additional qualifier must be specified with the value equal to NO.
Note: There is a performance cost (schema translation) and network cost (additional traffic) to using
XSD schema translation and a database server CPU cost to invoking schema validation.
EB.CONVERT.TABLE Utility
An automated utility is provided with T24 to convert existing tables using short tag elements into long
tag element tables that use the XML Schema Definition.
This utility is a standalone program and must only be executed when the database is not in use by
other users.
The utility first verifies that the specified XML Schema Definition exists in the F.SCHEMA table and is
enabled. The schema will then be copied from the F.SCHEMA table into the driver Schema directory
such that the driver can find the schema and register it with the database when creating the new table.
The utility then creates a temporary table into which it will then copy the existing table rows. Once
copied then the current table is dropped and a new table created using the associated schema. The
original data rows are then copied into the new schema based table. Once complete then the schema
properties, (”locked”, “useschema” and “registerschema”) are modified to reflect the new status of the
schema.
Manual Operation
If the EB.CONVERT.TABLE is not yet available, the table conversion can be executed manually using
the following steps. This operation should only be performed when no other users are using the
database.
Copy required XML Schema Definition reference to driver ‘schema’ directory specified using the
relevant driver configuration tool. (config-XMLORACLE, config-XMLDB2 or config-XMLMSQL )
Note: The copy operations could be optimised by using a program and including transaction
boundaries such that a transaction commit is executed every 1000 inserts.
Appendix
Appendix A- CUSTOMER XML Schema
<xsd:documentation>NAME.2</xsd:documentation>
<xsd:appinfo>
<xsd:hasProperty name="fieldtag" value="Name2" />
<xsd:hasProperty name="fieldnumber" value="4" />
<xsd:hasProperty name="fielddatatype" value="string" />
<xsd:hasProperty name="fieldfmt" value="" />
<xsd:hasProperty name="fieldlen" value="35" />
<xsd:hasProperty name="fieldinputlen" value="35" />
<xsd:hasProperty name="fieldgroupnumber" value="4" />
<xsd:hasProperty name="fieldmvgroupnumber" value="0" />
<xsd:hasProperty name="fieldshortname" value="c4" />
<xsd:hasProperty name="fieldname" value="NAME.2" />
<xsd:hasProperty name="fieldcolumnname" value="NAME_2" />
<xsd:hasProperty name="fieldgroupname" value="NAME.2" />
<xsd:hasProperty name="fieldmvgroupname" value="" />
<xsd:hasProperty name="fieldjustification" value="L" />
<xsd:hasProperty name="fieldtype" value="D" />
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="35" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="g" type="xsd:positiveInteger" use="optional" />
</xsd:complexType>
</xsd:element>
<xsd:element name="gStreet" minOccurs="0">
<xsd:complexType xdb:SQLType="gCUSTOMERStreet" xdb:maintainDOM="false">
<xsd:sequence minOccurs="0">
<xsd:element name="Street" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="STREET"
xdb:SQLCollType="T24CUSTOMER35_COLL_COLL">
<xsd:annotation>
<xsd:documentation>STREET</xsd:documentation>
<xsd:appinfo>
<xsd:hasProperty name="fieldtag" value="Street" />
<xsd:hasProperty name="fieldnumber" value="5" />
<xsd:hasProperty name="fielddatatype" value="string" />
<xsd:hasProperty name="fieldfmt" value="" />
<xsd:hasProperty name="fieldlen" value="35" />
<xsd:hasProperty name="fieldinputlen" value="35" />
<xsd:hasProperty name="fieldgroupnumber" value="5" />
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="35" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="g" type="xsd:positiveInteger" use="optional" />
</xsd:complexType>
</xsd:element>
<xsd:element name="gRelationCode" minOccurs="0">
<xsd:complexType xdb:SQLType="gCUSTOMERRelationCode" xdb:maintainDOM="false">
<xsd:sequence minOccurs="0">
<xsd:element name="mRelationCode" minOccurs="0" maxOccurs="unbounded"
xdb:SQLCollType="mCUSTOMERRelationCode_COLL">
<xsd:complexType xdb:SQLType="mCUSTOMERRelationCode" xdb:maintainDOM="false">
<xsd:sequence minOccurs="0">
<xsd:element name="RelationCode" minOccurs="0" xdb:SQLName="RELATION_CODE"
xdb:SQLCollType="T24CUSTOMER3_COLL_COLL">
<xsd:annotation>
<xsd:documentation>RELATION.CODE</xsd:documentation>
<xsd:appinfo>
<xsd:hasProperty name="fieldtag" value="RelationCode" />
<xsd:hasProperty name="fieldnumber" value="7" />
<xsd:hasProperty name="fielddatatype" value="string" />
<xsd:hasProperty name="fieldfmt" value="" />
<xsd:hasProperty name="fieldlen" value="3" />
<xsd:hasProperty name="fieldinputlen" value="3" />
<xsd:hasProperty name="fieldgroupnumber" value="7" />
<xsd:hasProperty name="fieldmvgroupnumber" value="0" />
<xsd:hasProperty name="fieldshortname" value="c7" />
<xsd:hasProperty name="fieldname" value="RELATION.CODE" />
<xsd:hasProperty name="fieldcolumnname" value="RELATION_CODE" />
<xsd:hasProperty name="fieldgroupname" value="RELATION.CODE" />
<xsd:hasProperty name="fieldmvgroupname" value="" />
<xsd:hasProperty name="fieldjustification" value="R" />
<xsd:hasProperty name="fieldtype" value="D" />
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="3" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="RelCustomer" minOccurs="0" xdb:SQLName="REL_CUSTOMER"
xdb:SQLCollType="T24CUSTOMER10_COLL_COLL">
<xsd:annotation>
<xsd:documentation>REL.CUSTOMER</xsd:documentation>
<xsd:appinfo>
<xsd:hasProperty name="fieldtag" value="RelCustomer" />
<xsd:hasProperty name="fieldnumber" value="8" />
<xsd:hasProperty name="fielddatatype" value="numeric" />
<xsd:hasProperty name="fieldfmt" value="decimal" />
<xsd:hasProperty name="fieldlen" value="10" />
<xsd:hasProperty name="fieldinputlen" value="10" />
<xsd:hasProperty name="fieldgroupnumber" value="7" />
<xsd:hasProperty name="fieldmvgroupnumber" value="0" />
<xsd:hasProperty name="fieldshortname" value="c8" />
<xsd:hasProperty name="fieldname" value="REL.CUSTOMER" />
<xsd:hasProperty name="fieldcolumnname" value="REL_CUSTOMER" />
<xsd:hasProperty name="fieldgroupname" value="RELATION.CODE" />
<xsd:hasProperty name="fieldmvgroupname" value="" />
<xsd:hasProperty name="fieldjustification" value="R" />
<xsd:hasProperty name="fieldtype" value="D" />
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ReversRelCode" minOccurs="0" xdb:SQLName="REVERS_REL_CODE"
xdb:SQLCollType="T24CUSTOMER60_COLL_COLL">
<xsd:annotation>
<xsd:documentation>REVERS.REL.CODE</xsd:documentation>
<xsd:appinfo>
<xsd:hasProperty name="fieldtag" value="ReversRelCode" />
<xsd:hasProperty name="fieldnumber" value="9" />
<xsd:hasProperty name="fielddatatype" value="string" />
<xsd:hasProperty name="fieldfmt" value="" />
<xsd:hasProperty name="fieldlen" value="60" />
<xsd:hasProperty name="fieldinputlen" value="3" />
<xsd:hasProperty name="fieldgroupnumber" value="7" />
<xsd:hasProperty name="fieldmvgroupnumber" value="0" />
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="AccountOfficer" minOccurs="0" xdb:SQLName="ACCOUNT_OFFICER"
xdb:SQLCollType="T24CUSTOMER4_COLL_COLL">
<xsd:annotation>
<xsd:documentation>ôCCOUNT.OFFICER</xsd:documentation>
<xsd:appinfo>
<xsd:hasProperty name="fieldtag" value="AccountOfficer" />
<xsd:hasProperty name="fieldnumber" value="11" />
<xsd:hasProperty name="fielddatatype" value="string" />
<xsd:hasProperty name="fieldfmt" value="" />
<xsd:hasProperty name="fieldlen" value="4" />
<xsd:hasProperty name="fieldinputlen" value="4" />
<xsd:hasProperty name="fieldgroupnumber" value="0" />
<xsd:hasProperty name="fieldmvgroupnumber" value="0" />
<xsd:hasProperty name="fieldshortname" value="c11" />
<xsd:hasProperty name="fieldname" value="ACCOUNT.OFFICER" />
<xsd:hasProperty name="fieldcolumnname" value="ACCOUNT_OFFICER" />
<xsd:hasProperty name="fieldgroupname" value="" />
<xsd:hasProperty name="fieldmvgroupname" value="" />
<xsd:hasProperty name="fieldjustification" value="R" />
<xsd:hasProperty name="fieldtype" value="D" />
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="gOtherOfficer" minOccurs="0">
<xsd:complexType xdb:SQLType="gCUSTOMEROtherOfficer" xdb:maintainDOM="false">
<xsd:sequence minOccurs="0">
<xsd:element name="OtherOfficer" minOccurs="0" maxOccurs="unbounded"
xdb:SQLName="OTHER_OFFICER"
xdb:SQLCollType="T24CUSTOMER4_COLL_COLL">
<xsd:annotation>
<xsd:documentation>OTHER.OFFICER</xsd:documentation>
<xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Residence" minOccurs="0" xdb:SQLName="RESIDENCE"
xdb:SQLCollType="T24CUSTOMER2_COLL_COLL">
<xsd:annotation>
<xsd:documentation>RESIDENCE</xsd:documentation>
<xsd:appinfo>
<xsd:hasProperty name="fieldtag" value="Residence" />
<xsd:hasProperty name="fieldnumber" value="17" />
<xsd:hasProperty name="fielddatatype" value="string" />
<xsd:hasProperty name="fieldfmt" value="" />
<xsd:hasProperty name="fieldlen" value="2" />
<xsd:hasProperty name="fieldinputlen" value="2" />
<xsd:hasProperty name="fieldgroupnumber" value="0" />
<xsd:hasProperty name="fieldmvgroupnumber" value="0" />
<xsd:hasProperty name="fieldshortname" value="c17" />
<xsd:hasProperty name="fieldname" value="RESIDENCE" />
<xsd:hasProperty name="fieldcolumnname" value="RESIDENCE" />
<xsd:hasProperty name="fieldgroupname" value="" />
<xsd:hasProperty name="fieldmvgroupname" value="" />
<xsd:hasProperty name="fieldjustification" value="L" />
<xsd:hasProperty name="fieldtype" value="D" />
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="2" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ContactDate" minOccurs="0" xdb:SQLName="CONTACT_DATE"
xdb:SQLCollType="T24CUSTOMER11_COLL_COLL">
<xsd:annotation>
<xsd:documentation>CONTACT.DATE</xsd:documentation>
<xsd:appinfo>
<xsd:hasProperty name="fieldtag" value="ContactDate" />
<xsd:hasProperty name="fieldnumber" value="18" />
<xsd:hasProperty name="fielddatatype" value="numeric" />
<xsd:hasProperty name="fieldfmt" value="date" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="gText" minOccurs="0">
<xsd:complexType xdb:SQLType="gCUSTOMERText" xdb:maintainDOM="false">
<xsd:sequence minOccurs="0">
<xsd:element name="Text" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="TEXT"
xdb:SQLCollType="T24CUSTOMER35_COLL_COLL">
<xsd:annotation>
<xsd:documentation>TEXT</xsd:documentation>
<xsd:appinfo>
<xsd:hasProperty name="fieldtag" value="Text" />
<xsd:hasProperty name="fieldnumber" value="20" />
<xsd:hasProperty name="fielddatatype" value="string" />
<xsd:hasProperty name="fieldfmt" value="" />
<xsd:hasProperty name="fieldlen" value="35" />
<xsd:hasProperty name="fieldinputlen" value="35" />
<xsd:hasProperty name="fieldgroupnumber" value="20" />
<xsd:hasProperty name="fieldmvgroupnumber" value="0" />
<xsd:hasProperty name="fieldshortname" value="c20" />
<xsd:hasProperty name="fieldname" value="TEXT" />
<xsd:hasProperty name="fieldcolumnname" value="TEXT" />
<xsd:hasProperty name="fieldgroupname" value="TEXT" />
<xsd:hasProperty name="fieldmvgroupname" value="" />
<xsd:hasProperty name="fieldjustification" value="L" />
<xsd:hasProperty name="fieldtype" value="D" />
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="35" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="g" type="xsd:positiveInteger" use="optional" />
</xsd:complexType>
</xsd:element>
<xsd:element name="LegalId" minOccurs="0" xdb:SQLName="LEGAL_ID"
xdb:SQLCollType="T24CUSTOMER20_COLL_COLL">
<xsd:annotation>
<xsd:documentation>LEGAL.ID</xsd:documentation>
<xsd:appinfo>
<xsd:hasProperty name="fieldtag" value="LegalId" />
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="17" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="BirthIncorpDate" minOccurs="0" xdb:SQLName="BIRTH_INCORP_DATE"
xdb:SQLCollType="T24CUSTOMER11_COLL_COLL">
<xsd:annotation>
<xsd:documentation>BIRTH.INCORP.DATE</xsd:documentation>
<xsd:appinfo>
<xsd:hasProperty name="fieldtag" value="BirthIncorpDate" />
<xsd:hasProperty name="fieldnumber" value="23" />
<xsd:hasProperty name="fielddatatype" value="numeric" />
<xsd:hasProperty name="fieldfmt" value="date" />
<xsd:hasProperty name="fieldlen" value="11" />
<xsd:hasProperty name="fieldinputlen" value="11" />
<xsd:hasProperty name="fieldgroupnumber" value="0" />
<xsd:hasProperty name="fieldmvgroupnumber" value="0" />
<xsd:hasProperty name="fieldshortname" value="c23" />
<xsd:hasProperty name="fieldname" value="BIRTH.INCORP.DATE" />
<xsd:hasProperty name="fieldcolumnname" value="BIRTH_INCORP_DATE" />
<xsd:hasProperty name="fieldgroupname" value="" />
<xsd:hasProperty name="fieldmvgroupname" value="" />
<xsd:hasProperty name="fieldjustification" value="R" />
<xsd:hasProperty name="fieldtype" value="D" />
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="11" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="GlobalCustomer" minOccurs="0" xdb:SQLName="GLOBAL_CUSTOMER"
xdb:SQLCollType="T24CUSTOMER10_COLL_COLL">
<xsd:annotation>
<xsd:documentation>GLOBAL.CUSTOMER</xsd:documentation>
<xsd:appinfo>
<xsd:hasProperty name="fieldtag" value="GlobalCustomer" />
<xsd:hasProperty name="fieldnumber" value="24" />
<xsd:hasProperty name="fielddatatype" value="string" />
<xsd:hasProperty name="fieldfmt" value="" />
<xsd:hasProperty name="fieldlen" value="10" />
</xsd:simpleType>
</xsd:element>
<xsd:element name="Language" minOccurs="0" xdb:SQLName="LANGUAGE"
xdb:SQLCollType="T24CUSTOMER2_COLL_COLL">
<xsd:annotation>
<xsd:documentation>LANGUAGE</xsd:documentation>
<xsd:appinfo>
<xsd:hasProperty name="fieldtag" value="Language" />
<xsd:hasProperty name="fieldnumber" value="26" />
<xsd:hasProperty name="fielddatatype" value="string" />
<xsd:hasProperty name="fieldfmt" value="" />
<xsd:hasProperty name="fieldlen" value="2" />
<xsd:hasProperty name="fieldinputlen" value="2" />
<xsd:hasProperty name="fieldgroupnumber" value="0" />
<xsd:hasProperty name="fieldmvgroupnumber" value="0" />
<xsd:hasProperty name="fieldshortname" value="c26" />
<xsd:hasProperty name="fieldname" value="LANGUAGE" />
<xsd:hasProperty name="fieldcolumnname" value="LANGUAGE" />
<xsd:hasProperty name="fieldgroupname" value="" />
<xsd:hasProperty name="fieldmvgroupname" value="" />
<xsd:hasProperty name="fieldjustification" value="R" />
<xsd:hasProperty name="fieldtype" value="D" />
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="2" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="PostingRestrict" minOccurs="0" xdb:SQLName="POSTING_RESTRICT"
xdb:SQLCollType="T24CUSTOMER2_COLL_COLL">
<xsd:annotation>
<xsd:documentation>POSTING.RESTRICT</xsd:documentation>
<xsd:appinfo>
<xsd:hasProperty name="fieldtag" value="PostingRestrict" />
<xsd:hasProperty name="fieldnumber" value="27" />
<xsd:hasProperty name="fielddatatype" value="string" />
<xsd:hasProperty name="fieldfmt" value="" />
<xsd:hasProperty name="fieldlen" value="2" />
<xsd:hasProperty name="fieldinputlen" value="2" />
<xsd:hasProperty name="fieldgroupnumber" value="0" />
<xsd:hasProperty name="fieldmvgroupnumber" value="0" />
<xsd:hasProperty name="fieldshortname" value="c27" />
<xsd:sequence minOccurs="0">
<xsd:element name="PostCode" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="POST_CODE"
xdb:SQLCollType="T24CUSTOMER35_COLL_COLL">
<xsd:annotation>
<xsd:documentation>POST.CODE</xsd:documentation>
<xsd:appinfo>
<xsd:hasProperty name="fieldtag" value="PostCode" />
<xsd:hasProperty name="fieldnumber" value="29" />
<xsd:hasProperty name="fielddatatype" value="string" />
<xsd:hasProperty name="fieldfmt" value="" />
<xsd:hasProperty name="fieldlen" value="35" />
<xsd:hasProperty name="fieldinputlen" value="35" />
<xsd:hasProperty name="fieldgroupnumber" value="29" />
<xsd:hasProperty name="fieldmvgroupnumber" value="0" />
<xsd:hasProperty name="fieldshortname" value="c29" />
<xsd:hasProperty name="fieldname" value="POST.CODE" />
<xsd:hasProperty name="fieldcolumnname" value="POST_CODE" />
<xsd:hasProperty name="fieldgroupname" value="POST.CODE" />
<xsd:hasProperty name="fieldmvgroupname" value="" />
<xsd:hasProperty name="fieldjustification" value="L" />
<xsd:hasProperty name="fieldtype" value="D" />
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="35" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="g" type="xsd:positiveInteger" use="optional" />
</xsd:complexType>
</xsd:element>
<xsd:element name="gCountry" minOccurs="0">
<xsd:complexType xdb:SQLType="gCUSTOMERCountry" xdb:maintainDOM="false">
<xsd:sequence minOccurs="0">
<xsd:element name="Country" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="COUNTRY"
xdb:SQLCollType="T24CUSTOMER35_COLL_COLL">
<xsd:annotation>
<xsd:documentation>COUNTRY</xsd:documentation>
<xsd:appinfo>
<xsd:hasProperty name="fieldtag" value="Country" />
<xsd:hasProperty name="fieldnumber" value="30" />
<xsd:hasProperty name="fielddatatype" value="string" />
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="11" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ConfidTxt" minOccurs="0" xdb:SQLName="CONFID_TXT"
xdb:SQLCollType="T24CUSTOMER3_COLL_COLL">
<xsd:annotation>
<xsd:documentation>CONFID.TXT</xsd:documentation>
<xsd:appinfo>
<xsd:hasProperty name="fieldtag" value="ConfidTxt" />
<xsd:hasProperty name="fieldnumber" value="32" />
<xsd:hasProperty name="fielddatatype" value="string" />
<xsd:hasProperty name="fieldfmt" value="" />
<xsd:hasProperty name="fieldlen" value="3" />
<xsd:hasProperty name="fieldinputlen" value="3" />
<xsd:hasProperty name="fieldgroupnumber" value="0" />
<xsd:hasProperty name="fieldmvgroupnumber" value="0" />
<xsd:hasProperty name="fieldshortname" value="c32" />
<xsd:hasProperty name="fieldname" value="CONFID.TXT" />
<xsd:hasProperty name="fieldcolumnname" value="CONFID_TXT" />
<xsd:hasProperty name="fieldgroupname" value="" />
<xsd:hasProperty name="fieldmvgroupname" value="" />
<xsd:hasProperty name="fieldjustification" value="R" />
<xsd:hasProperty name="fieldtype" value="D" />
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="3" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="DispoExempt" minOccurs="0" xdb:SQLName="DISPO_EXEMPT"
xdb:SQLCollType="T24CUSTOMER3_COLL_COLL">
<xsd:annotation>
<xsd:documentation>DISPO.EXEMPT</xsd:documentation>
<xsd:appinfo>
<xsd:hasProperty name="fieldtag" value="DispoExempt" />
<xsd:hasProperty name="fieldnumber" value="33" />
<xsd:hasProperty name="fielddatatype" value="string" />
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="35" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="g" type="xsd:positiveInteger" use="optional" />
</xsd:complexType>
</xsd:element>
<xsd:element name="gOverride" minOccurs="0">
<xsd:complexType xdb:SQLType="gCUSTOMEROverride" xdb:maintainDOM="false">
<xsd:sequence minOccurs="0">
<xsd:element name="Override" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="OVERRIDE"
xdb:SQLCollType="T24CUSTOMER60_COLL_COLL">
<xsd:annotation>
<xsd:documentation>OVERRIDE</xsd:documentation>
<xsd:appinfo>
<xsd:hasProperty name="fieldtag" value="Override" />
<xsd:hasProperty name="fieldnumber" value="41" />
<xsd:hasProperty name="fielddatatype" value="string" />
<xsd:hasProperty name="fieldfmt" value="" />
<xsd:hasProperty name="fieldlen" value="60" />
<xsd:hasProperty name="fieldinputlen" value="35" />
<xsd:hasProperty name="fieldgroupnumber" value="41" />
<xsd:hasProperty name="fieldmvgroupnumber" value="0" />
<xsd:hasProperty name="fieldshortname" value="c41" />
<xsd:hasProperty name="fieldname" value="OVERRIDE" />
<xsd:hasProperty name="fieldcolumnname" value="OVERRIDE" />
<xsd:hasProperty name="fieldgroupname" value="OVERRIDE" />
<xsd:hasProperty name="fieldmvgroupname" value="" />
<xsd:hasProperty name="fieldjustification" value="L" />
<xsd:hasProperty name="fieldtype" value="D" />
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="60" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="g" type="xsd:positiveInteger" use="optional" />
</xsd:complexType>
</xsd:element>
<xsd:element name="RecordStatus" minOccurs="0" xdb:SQLName="RECORD_STATUS"
xdb:SQLCollType="T24CUSTOMER4_COLL_COLL">
<xsd:annotation>
<xsd:documentation>RECORD.STATUS</xsd:documentation>
<xsd:appinfo>
<xsd:hasProperty name="fieldtag" value="RecordStatus" />
<xsd:hasProperty name="fieldnumber" value="42" />
<xsd:hasProperty name="fielddatatype" value="string" />
<xsd:hasProperty name="fieldfmt" value="" />
<xsd:hasProperty name="fieldlen" value="4" />
<xsd:hasProperty name="fieldinputlen" value="4" />
<xsd:hasProperty name="fieldgroupnumber" value="0" />
<xsd:hasProperty name="fieldmvgroupnumber" value="0" />
<xsd:hasProperty name="fieldshortname" value="c42" />
<xsd:hasProperty name="fieldname" value="RECORD.STATUS" />
<xsd:hasProperty name="fieldcolumnname" value="RECORD_STATUS" />
<xsd:hasProperty name="fieldgroupname" value="" />
<xsd:hasProperty name="fieldmvgroupname" value="" />
<xsd:hasProperty name="fieldjustification" value="L" />
<xsd:hasProperty name="fieldtype" value="D" />
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CurrNo" minOccurs="0" xdb:SQLName="CURR_NO"
xdb:SQLCollType="T24CUSTOMER4_COLL_COLL">
<xsd:annotation>
<xsd:documentation>CURR.NO</xsd:documentation>
<xsd:appinfo>
<xsd:hasProperty name="fieldtag" value="CurrNo" />
<xsd:hasProperty name="fieldnumber" value="43" />
<xsd:hasProperty name="fielddatatype" value="string" />
<xsd:hasProperty name="fieldfmt" value="" />
<xsd:hasProperty name="fieldlen" value="4" />
<xsd:hasProperty name="fieldinputlen" value="4" />
<xsd:hasProperty name="fieldgroupnumber" value="0" />
<xsd:hasProperty name="fieldmvgroupnumber" value="0" />
<xsd:hasProperty name="fieldshortname" value="c43" />
</xsd:element>
</xsd:sequence>
<xsd:attribute name="g" type="xsd:positiveInteger" use="optional" />
</xsd:complexType>
</xsd:element>
<xsd:element name="gDateTime" minOccurs="0">
<xsd:complexType xdb:SQLType="gCUSTOMERDateTime" xdb:maintainDOM="false">
<xsd:sequence minOccurs="0">
<xsd:element name="DateTime" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="DATE_TIME"
xdb:SQLCollType="T24CUSTOMER15_COLL_COLL">
<xsd:annotation>
<xsd:documentation>DATE.TIME</xsd:documentation>
<xsd:appinfo>
<xsd:hasProperty name="fieldtag" value="DateTime" />
<xsd:hasProperty name="fieldnumber" value="45" />
<xsd:hasProperty name="fielddatatype" value="string" />
<xsd:hasProperty name="fieldfmt" value="" />
<xsd:hasProperty name="fieldlen" value="15" />
<xsd:hasProperty name="fieldinputlen" value="15" />
<xsd:hasProperty name="fieldgroupnumber" value="45" />
<xsd:hasProperty name="fieldmvgroupnumber" value="0" />
<xsd:hasProperty name="fieldshortname" value="c45" />
<xsd:hasProperty name="fieldname" value="DATE.TIME" />
<xsd:hasProperty name="fieldcolumnname" value="DATE_TIME" />
<xsd:hasProperty name="fieldgroupname" value="DATE.TIME" />
<xsd:hasProperty name="fieldmvgroupname" value="" />
<xsd:hasProperty name="fieldjustification" value="R" />
<xsd:hasProperty name="fieldtype" value="D" />
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="15" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="g" type="xsd:positiveInteger" use="optional" />
</xsd:complexType>
</xsd:element>
<xsd:element name="Authoriser" minOccurs="0" xdb:SQLName="AUTHORISER"
xdb:SQLCollType="T24CUSTOMER20_COLL_COLL">
<xsd:annotation>
<xsd:documentation>AUTHORISER</xsd:documentation>
<xsd:appinfo>
<xsd:hasProperty name="fieldtag" value="Authoriser" />
<xsd:hasProperty name="fieldnumber" value="46" />
<xsd:hasProperty name="fielddatatype" value="string" />
<xsd:hasProperty name="fieldfmt" value="" />
<xsd:hasProperty name="fieldlen" value="20" />
<xsd:hasProperty name="fieldinputlen" value="20" />
<xsd:hasProperty name="fieldgroupnumber" value="0" />
<xsd:hasProperty name="fieldmvgroupnumber" value="0" />
<xsd:hasProperty name="fieldshortname" value="c46" />
<xsd:hasProperty name="fieldname" value="AUTHORISER" />
<xsd:hasProperty name="fieldcolumnname" value="AUTHORISER" />
<xsd:hasProperty name="fieldgroupname" value="" />
<xsd:hasProperty name="fieldmvgroupname" value="" />
<xsd:hasProperty name="fieldjustification" value="L" />
<xsd:hasProperty name="fieldtype" value="D" />
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CoCode" minOccurs="0" xdb:SQLName="CO_CODE"
xdb:SQLCollType="T24CUSTOMER11_COLL_COLL">
<xsd:annotation>
<xsd:documentation>CO.CODE</xsd:documentation>
<xsd:appinfo>
<xsd:hasProperty name="fieldtag" value="CoCode" />
<xsd:hasProperty name="fieldnumber" value="47" />
<xsd:hasProperty name="fielddatatype" value="string" />
<xsd:hasProperty name="fieldfmt" value="" />
<xsd:hasProperty name="fieldlen" value="11" />
<xsd:hasProperty name="fieldinputlen" value="11" />
<xsd:hasProperty name="fieldgroupnumber" value="0" />
<xsd:hasProperty name="fieldmvgroupnumber" value="0" />
<xsd:hasProperty name="fieldshortname" value="c47" />
<xsd:hasProperty name="fieldname" value="CO.CODE" />
<xsd:hasProperty name="fieldcolumnname" value="CO_CODE" />
<xsd:hasProperty name="fieldgroupname" value="" />
<xsd:hasProperty name="fieldmvgroupname" value="" />
<xsd:hasProperty name="fieldjustification" value="L" />
<xsd:hasProperty name="fieldtype" value="D" />
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="11" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="DeptCode" minOccurs="0" xdb:SQLName="DEPT_CODE"
xdb:SQLCollType="T24CUSTOMER4_COLL_COLL">
<xsd:annotation>
<xsd:documentation>DEPT.CODE</xsd:documentation>
<xsd:appinfo>
<xsd:hasProperty name="fieldtag" value="DeptCode" />
<xsd:hasProperty name="fieldnumber" value="48" />
<xsd:hasProperty name="fielddatatype" value="string" />
<xsd:hasProperty name="fieldfmt" value="" />
<xsd:hasProperty name="fieldlen" value="4" />
<xsd:hasProperty name="fieldinputlen" value="4" />
<xsd:hasProperty name="fieldgroupnumber" value="0" />
<xsd:hasProperty name="fieldmvgroupnumber" value="0" />
<xsd:hasProperty name="fieldshortname" value="c48" />
<xsd:hasProperty name="fieldname" value="DEPT.CODE" />
<xsd:hasProperty name="fieldcolumnname" value="DEPT_CODE" />
<xsd:hasProperty name="fieldgroupname" value="" />
<xsd:hasProperty name="fieldmvgroupname" value="" />
<xsd:hasProperty name="fieldjustification" value="L" />
<xsd:hasProperty name="fieldtype" value="D" />
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="AuditorCode" minOccurs="0" xdb:SQLName="AUDITOR_CODE"
xdb:SQLCollType="T24CUSTOMER16_COLL_COLL">
<xsd:annotation>
<xsd:documentation>AUDITOR.CODE</xsd:documentation>
<xsd:appinfo>
<xsd:hasProperty name="fieldtag" value="AuditorCode" />
<xsd:hasProperty name="fieldnumber" value="49" />
<xsd:hasProperty name="fielddatatype" value="string" />
XMLRECORD
----------------------------------------------------------------------------------------------
--------------------------------------
<OtherOfficer>1</OtherOfficer>
</gOtherOfficer>
<Industry>8100</Industry>
<Target>999</Target>
<Nationality>UK</Nationality>
<CustomerStatus>4</CustomerStatus>
<Residence>GB</Residence>
<ContactDate>20000101</ContactDate>
<gText>
<Text>text1</Text>
<Text>text2</Text>
</gText>
<BirthIncorpDate>20000101</BirthIncorpDate>
<Language>1</Language>
<gPostCode>
<PostCode>EC3M 4TD</PostCode>
<PostCode>HP2 4NW</PostCode>
</gPostCode>
<gCountry>
<Country>UK</Country>
<Country>GB</Country>
</gCountry>
<ClsCparty>NO</ClsCparty>
<gLocalRef>
<LocalRef>100</LocalRef>
<LocalRef>200</LocalRef>
<LocalRef>300</LocalRef>
</gLocalRef>
<CurrNo>1</CurrNo>
<gInputter>
<Inputter>28_INPUTTER</Inputter>
</gInputter>
<gDateTime>
<DateTime>0006121122</DateTime>
</gDateTime>
<Authoriser>28_SANTHOSH.1</Authoriser>
<CoCode>US0010001</CoCode>
<DeptCode>1</DeptCode>
</row>
m NUMBER(38)
RELATION_CODE VARCHAR2(3 CHAR)
REL_CUSTOMER VARCHAR2(10 CHAR)
REVERS_REL_CODE VARCHAR2(60 CHAR)
Nested Tables
To display nested table allocations and their related parent table columns
TABLE_NAME PARENT_TABLE_COLUMN
------------------ ------------------------------------------------------------
XDBCUSTOMER_2 "SYS_NC00006$"."gShortName"."SHORT_NAME"
XDBCUSTOMER_3 "SYS_NC00006$"."gName1"."NAME_1"
XDBCUSTOMER_4 "SYS_NC00006$"."gName2"."NAME_2"
XDBCUSTOMER_5 "SYS_NC00006$"."gStreet"."STREET"
XDBCUSTOMER_6 "SYS_NC00006$"."gTownCountry"."TOWN_COUNTRY"
XDBCUSTOMER_7 "SYS_NC00006$"."gRelationCode"."mRelationCode"
XDBCUSTOMER_12 "SYS_NC00006$"."gOtherOfficer"."OTHER_OFFICER"
XDBCUSTOMER_20 "SYS_NC00006$"."gText"."TEXT"
XDBCUSTOMER_29 "SYS_NC00006$"."gPostCode"."POST_CODE"
XDBCUSTOMER_30 "SYS_NC00006$"."gCountry"."COUNTRY"
XDBCUSTOMER_39 "SYS_NC00006$"."gCustomerRating"."CUSTOMER_RATING"
XDBCUSTOMER_40 "SYS_NC00006$"."gLocalRef"."LOCAL_REF"
XDBCUSTOMER_41 "SYS_NC00006$"."gOverride"."OVERRIDE"
XDBCUSTOMER_44 "SYS_NC00006$"."gInputter"."INPUTTER"
XDBCUSTOMER_45 "SYS_NC00006$"."gDateTime"."DATE_TIME"
2 1 499061 10
Name_1
-----------------------------------
TEMENOS LONDON
TEMENOS HEMEL