JAXB: Abstract Types and Substitution Group Errors

I am using several schemas as defined below:
Schema 1 defines an abstract type
Schema 2 extends abstract type
Schema 3 makes reference to abstract type in 1 and is using substitution groups on the abstarct type
The error only occurs when the element is Abstract and what extends
the abstract element specify a substitution group (which I believe is
correct according to
http://www.w3.org/TR/2001/REC-xmlschema-0-20010502/#abstract). I can't
remove the substitution group because declaring the element as abstract
requires this. Is there a way to fix this?
code that generates error:
When attempting to do a JAXBContext jaxbContext = JAXBContext.newInstance(Schema3.class) I get the following error
Exception in thread "main" com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts of IllegalAnnotationExceptions
There's no ObjectFactory with an @XmlElementDecl for the element {[http://test.com/FeatureBase.xsd|http://seams.csp.com/FeatureBase.xsd]}FeatureBase.
     this problem is related to the following location:
          at com.test.blah
     at com.sun.xml.bind.v2.runtime.IllegalAnnotationsException$Builder.check(IllegalAnnotationsException.java:102)
     at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:448)
     at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:297)
     at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139)
     at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:117)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:214)
     at javax.xml.bind.ContextFinder.find(ContextFinder.java:375)
     at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:574)
     at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:522)

Hi all,
This seems to be a bug unless someone of you have a solution.
Also I ma new to xml/xsd world, so could someone please give the differences between xsi:type vs substitution groups with both element and complex type being abstract. Can this scenario be accomplished by usuage of choice groups.
Also can anyone suggest any other good xml forums.
Please let me know.
Thanks in advance.

Similar Messages

Problem with abstract complex type in substitution group.

Hi all,
I have three xsds, A, B, C.XSD respectively. A.xsd:There is a substitution group and its complex type declared as abstract and element that uses them. B.xsd has the same structure as A except that it has complex type derived from complex type from A. C.xsd is same as B.xsd.
The xml files of A and B validate but not of C.
It gives the following error:
This file is not valid. Unexpected element'signatureString' in element author. Expected signatureString,signatureText.
Any help at the earliest is greatly appreciated.
the code of each xsds is as follows:
A.XSD:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:PARTICIPATION="Participation" targetNamespace="Participation">
     
     
     
     
     
     
     <xs:element name="signatureString" type="PARTICIPATION:SignatureString" substitutionGroup="PARTICIPATION:signatureText"/>
     <xs:complexType name="SignatureString">
          <xs:complexContent>
               <xs:extension base="PARTICIPATION:SignatureText">
                    <xs:attribute name="value" type="xs:string" use="required"/>
               </xs:extension>
          </xs:complexContent>
     </xs:complexType>
     
     
     
     <xs:element name="signatureText" type="PARTICIPATION:SignatureText" abstract="true"/>
     <xs:complexType name="SignatureText" abstract="true"/>
</xs:schema>
B.xsd:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:CM3202="Common3202" xmlns:PARTICIPATION="Participation" targetNamespace="Common3202">
     <xs:import namespace="Participation" schemaLocation="Datatypes3203/RDT/Participation.xsd"/>
     
     
     
     <xs:element name="practitionerParticipation" type="CM3202:PractitionerParticipation" abstract="true"/>
     <xs:complexType name="PractitionerParticipation" abstract="true">
          <xs:sequence>
               
               <xs:element ref="PARTICIPATION:signatureText"/>
               </xs:sequence>
     </xs:complexType>
     
     
     
     <xs:element name="author" type="CM3202:Author" substitutionGroup="CM3202:practitionerParticipation"/>
     <xs:complexType name="Author">
          <xs:complexContent>
               <xs:extension base="CM3202:PractitionerParticipation"/>
          </xs:complexContent>
     </xs:complexType>
</xs:schema>
C.xsd
<?xml version="1.0" encoding="ISO-8859-1"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:VS3203="VitalSigns3203" xmlns:CM3202="Common3202" targetNamespace="VitalSigns3203">
     <xs:import namespace="Common3202" schemaLocation="Common3202.xsd"/>
     
     
     
     <xs:element name="vitalSignsObservationEvent" type="VS3203:VitalSignsObservationEvent"/>
     <xs:complexType name="VitalSignsObservationEvent">
          <xs:sequence>
               <xs:element name="author" type="CM3202:Author" minOccurs="0">
               </xs:element>
          </xs:sequence>
     </xs:complexType>
</xs:schema>

Hi all,
This seems to be a bug unless someone of you have a solution.
Also I ma new to xml/xsd world, so could someone please give the differences between xsi:type vs substitution groups with both element and complex type being abstract. Can this scenario be accomplished by usuage of choice groups.
Also can anyone suggest any other good xml forums.
Please let me know.
Thanks in advance.

What is the relation between req type and checking group

Could any1 please explain me the link between requirement type and checking group?
Also please throw some light on the other terms in ATP like requirement class and checking rule.
Thanks in advance

Dear VGR,
The requirement type refers to the origin type, for example, goods receipt for purchase order (Type B) or goods issue to cost centers (Type K).
The criterion that groups together all checking rules for all application areas for a material.
In conjunction with the checking rule, the checking group defines the scope of the availability check for each business event, that is, which stocks, goods receipts, and goods issues are taken into account in the availability check, and whether replenishment lead time is checked.
Checking rule
A rule that defines how the availability check is performed.
The checking rule, in conjunction with the checking group, determines the scope of the availability check for every business operation; that is, which stocks, receipts, and issues are included in the availability check and whether the check is performed with or without the replenishment lead time.
I hope this will help you,
Regards,
Murali.

Xmlbeans and substitution groups

I am working with the new GoogleEarth .xsd files and I have compiled them using xmlbeans. There are a number of elements that make use of substitutiongroups. for example:
<element name="Placemark" type="kml:PlacemarkType"
    substitutionGroup="kml:AbstractFeatureGroup"/>
<complexType name="PlacemarkType" final="#all">
    <complexContent>
      <extension base="kml:AbstractFeatureType">
        <sequence>
          <element ref="kml:AbstractGeometryGroup" minOccurs="0"/>
        </sequence>
      </extension>
    </complexContent>
</complexType>how do I "replace" the substitution group with the actual element so that instead of:
<AbstractGeometryGroup>
          <Point>
            <extrude>true</extrude>
            <altitudeModeGroup>
              <altitudeMode>relativeToGround</altitudeMode>
            </altitudeModeGroup>
            <coordinates>32.18582907768492, -107.85250271267361, 50</coordinates>
          </Point>
        </AbstractGeometryGroup>I would get just           <Point>
            <extrude>true</extrude>
            <altitudeModeGroup>
              <altitudeMode>relativeToGround</altitudeMode>
            </altitudeModeGroup>
            <coordinates>32.18582907768492, -107.85250271267361, 50</coordinates>
          </Point>I have tried casting, the substitute method, and the replace method to no avail. I think casting is the right way to go, but I throw a class cast exception when I try to cast. Here is my code
PointType point = (PointType)placemark.addNewAbstractGeometryGroup();
     AltitudeModeDocument altModeDoc = AltitudeModeDocument.Factory.newInstance();
     AltitudeModeEnumType.Enum altModeEnum = AltitudeModeEnumType.Enum.forString("relativeToGround");
     altModeDoc.setAltitudeMode(altModeEnum);
     point.setAltitudeModeGroup(altModeDoc);
     point.setExtrude(true);
     Vector<String> coordinates = new Vector<String>(3);
     coordinates.add("32.18582907768492,");
     coordinates.add("-107.85250271267361,");
     coordinates.add("50");
     point.setCoordinates(coordinates);With the cast exception thrown on the first line. Which I would understand, but I can call
placemark.setNewAbstractGeometryGroup(), which takes a AbstractGeometryType as an argument and will accept a PointType as an argument which I assume means PointType isa AbstractGeometryType. Is the issue that that I am casting the wrong direction? Any help is greatly appreciated. I would much prefer to build the xml messages using the beans rather then hacking together a StringBuffer.

Hi Pon -
Do you mean groups of users or group of pages?
If you mean groups of users, you can create your sub-groups as a regular groups, and then when assigning users to your Main Finance group ... add the 2 groups which are your subGroups.
If you are talking about the Portal Page Group structure, you cannot nest page groups, but you can create pages and subpages.
Hope this helps,
Candace

Port, Message type and Function Group

Hai,
Iam working on an inbound process for four different Partners.
Is there any need of Port for Inbound?
Shall i use the same message type and Idoc type?
And what about the function Group?
Thanks
Avi

Hello,
<b> If the functionality is same , you can use the same function Group.
If functionality is different , you want to use different Function Group.
Obvisouly, it is suggested to use different Message types .
If you are using same fields ,you can use the same idoc type.
depends on the scenior , the process code is needed. Generally no need.</b>
Thanks
Manju

I need a sample about how substitution groups are rewrited

Hi
As mentioned in a documentation, substitution groups in 10g are rewritten:
The XML Schema constructs for the XPath expression are rewritable.
XML Schema constructs such as complex types, enumerated values, lists, inherited (derived) types, and substitution groups are rewritten.
Can anybody give me a link to a topic or a blog where this subject is discussed?
I'm very need to.
Thanks
Dmitry

Hi
As mentioned in a documentation, substitution groups in 10g are rewritten:
The XML Schema constructs for the XPath expression are rewritable.
XML Schema constructs such as complex types, enumerated values, lists, inherited (derived) types, and substitution groups are rewritten.
Can anybody give me a link to a topic or a blog where this subject is discussed?
I'm very need to.
Thanks
Dmitry

Material type and account assignment group relation

Hi,
Getting an error while creating material master save. Account assignment Zx can't be with Material Type Zxxxx.
Please advise where is the link maintained between material account assignment group and material type.
My material is Z service material.
As I no for plant,industry, material type valuation class quanity update tick required but that is for stockable materials which is not the case above.
Thanks

HI,
You can make the field Account Assignment Group of Material Master as inactive.
But it depends up on Plant, Industry Sector Type and Material Type.
You can do this in IMG --> Logistic General --> Material Master --> Field Selection
Or
use SHD0.. give T-code MM01. and you can deactivate the field.
Hope this helps you.
TC
BR
AKS

QS41 and QS51- code group error

Hi,
I am trying to create new code groups in QM. i have maintained the defect classes and the catalog types. then in QS41 I have maintained the code groups for the catalogs along with the codes. All the code groups are in released status. In the next step in QS 51 I am trying to edit the selected sets but when I enter the catalog, plant and the set the error message qs204 comes which says 'Selected sets are not defined for these catalog types'. and the performance assistant recommends maintaining the table TQ15so that selected sets are allowed for the catalog type.
Why is this error coming? after I have maintained all the required catalogs. Kindly help me with the solution as soon as possible as it is quite critical.
Thanks,
Ariel.

Hi,
This is the correct community regarding your subject. please let me know what is the type of catalog your creating selected for. SAP allows you in standard for creating selected sets only for some of the catalogs namely Usage decision, Character attributes
If you need to maintain selected for other catalogs you have to do the customisation
SPRO > QM > Quality Planning > Basic Data > Catalog > define Catalog Type> choose the catalog > maintian Selected sets allowed
Hope this helps
Regards
Gajesh

Handling substitution groups and Tables generation

Hi
This is concerning the generation of tables from xml schema containing "substitutionGroup" attributes and "extension" elements for
deriving from abstract types.
I want to know how the tables are generated when schema has subsitution groups.
I went through the generated tables and observed that it creates a table for each extension...but also generates a table for the head of the subsitution group.
This table would have columns for each of the members in the derivatives of the abstract type.This is resulting in more than 1000 columns in my case
Any suggestions?
Thanks
Devashish

When a subsitution group is used each of the type of each of the elements in the substition group must be an extension of the type of the head element. In the case where the head type is based on an abstract empty complexType this makes no sense. Since the type inheritiance system implies that anywhere a parent type can appear it is legal for the chlild type to appear in it's place we have to create a storage structure for the head element which can handle any of the possible child types. This means that at the storage level we have to generate a table with a column for each possible descendant of the head element. This means that we are effectively restricting the number of direct elements and attributes that can be defined by members of the substition group to a number that is a little less than 1000.
This can be be seen in the first example below.
However in the case where the substition group contains no common element we can model this as choice. as is shown in the second XML Schema. Since every member of the choice is independant of the other members of the choice there is no need for the inheritance hierarchy in the type definitions. This means that each member of the choice can now be mapped to a seperate table. This structure allows for a choice with approxamately a 1000 entries and no practicle limits on the number of decendant elements and attributes for each member of the choice..
This can be seen in the second example bleow;
The key point is the number of columns in ROOT_TABLE. In the First Example it is 17, the fixed overhead plus the number of columns required to persist headType, member1Type and member2Type. In the Second example it is 12, the fixed overhead plus a REF XMLType to point at instances of member1Type and REF XMLType to point at instnaces of member2Type.
I hope this answers your question
SQL> var schemaURL varchar2(256)
SQL> var schemaPath varchar2(256)
SQL> --
SQL> column qualified_col_name format A64
SQL> column data_type format A40
SQL> --
SQL> set lines 150 pages 25 long 10000
SQL> --
SQL> begin
2    :schemaURL := 'testcase.xsd';
3    :schemaPath := '/public/testcase.xsd';
4 end;
5 /
PL/SQL procedure successfully completed.
SQL> call dbms_xmlSchema.deleteSchema(:schemaURL,4)
2 /
Call completed.
SQL> declare
2    res boolean;
3    xmlSchema xmlType := xmlType(
4 '<?xml version="1.0" encoding="UTF-8"?>
5 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" elementFormDefault="qualified" attribute
FormDefault="unqualified" xdb:storeVarrayAsTable="true">
6     <xs:element name="root" type="rootType" xdb:defaultTable="ROOT_TABLE"/>
7     <xs:complexType name="rootType" xdb:SQLType="ROOT_T">
8             <xs:sequence>
9                     <xs:element ref="head"/>
10             </xs:sequence>
11     </xs:complexType>
12     <xs:complexType name="headType" xdb:SQLType="HEAD_T" abstract="true"/>
13     <xs:complexType name="member1Type" xdb:SQLType="MEMBER1_T">
14             <xs:complexContent>
15                     <xs:extension base="headType">
16                             <xs:sequence>
17                                     <xs:element name="Member1.Child1" type="xs:string"/>
18                                     <xs:element name="Member1.Child2" type="xs:string"/>
19                             </xs:sequence>
20                     </xs:extension>
21             </xs:complexContent>
22     </xs:complexType>
23     <xs:complexType name="member2Type" xdb:SQLType="MEMBER2_T">
24             <xs:complexContent>
25                     <xs:extension base="headType">
26                             <xs:sequence>
27                                     <xs:element name="Member2.Child1" type="xs:string"/>
28                                     <xs:element name="Member2.Child2" type="xs:string"/>
29                             </xs:sequence>
30                     </xs:extension>
31             </xs:complexContent>
32     </xs:complexType>
33     <xs:element name="head" type="headType" xdb:defaultTable="GLOBAL_HEAD_TABLE"/>
34     <xs:element name="member1" type="member1Type" substitutionGroup="head" xdb:defaultTable="GLOBAL_MEMBER1_TABLE"/>
35     <xs:element name="member2" type="member2Type" substitutionGroup="head" xdb:defaultTable="GLOBAL_MEMBER2_TABLE"/>
36 </xs:schema>');
37 begin
38    if (dbms_xdb.existsResource(:schemaPath)) then
39      dbms_xdb.deleteResource(:schemaPath);
40    end if;
41    res := dbms_xdb.createResource(:schemaPath,xmlSchema);
42 end;
43 /
PL/SQL procedure successfully completed.
SQL> begin
2    dbms_xmlschema.registerSchema
3    (
4      :schemaURL,
5      xdbURIType(:schemaPath).getClob(),
6      TRUE,TRUE,FALSE,TRUE
7    );
8 end;
9 /
PL/SQL procedure successfully completed.
SQL> --
SQL> desc ROOT_TABLE
Name                                                                                Null?    Type
TABLE of SYS.XMLTYPE(XMLSchema "testcase.xsd" Element "root") STORAGE Object-relational TYPE "ROOT_T"
SQL> --
SQL> desc ROOT_T
ROOT_T is NOT FINAL
Name                                                                                Null?    Type
SYS_XDBPD$                                                                                   XDB.XDB$RAW_LIST_T
head                                                                                         HEAD_T
SQL> --
SQL> desc HEAD_T
HEAD_T is NOT FINAL
HEAD_T is NOT INSTANTIABLE
Name                                                                                Null?    Type
SYS_XDBPD$                                                                                   XDB.XDB$RAW_LIST_T
SQL> --
SQL> desc GLOBAL_HEAD_TABLE
Name                                                                                Null?    Type
TABLE of SYS.XMLTYPE(XMLSchema "testcase.xsd" Element "head") STORAGE Object-relational TYPE "HEAD_T"
SQL> --
SQL> desc GLOBAL_MEMBER1_TABLE
Name                                                                                Null?    Type
TABLE of SYS.XMLTYPE(XMLSchema "testcase.xsd" Element "member1") STORAGE Object-relational TYPE "MEMBER1_T"
SQL> --
SQL> desc MEMBER1_T
MEMBER1_T extends SCOTT.HEAD_T
MEMBER1_T is NOT FINAL
Name                                                                                Null?    Type
SYS_XDBPD$                                                                                   XDB.XDB$RAW_LIST_T
Member1.Child1                                                                               VARCHAR2(4000 CHAR)
Member1.Child2                                                                               VARCHAR2(4000 CHAR)
SQL> --
SQL> desc GLOBAL_MEMBER2_TABLE
Name                                                                                Null?    Type
TABLE of SYS.XMLTYPE(XMLSchema "testcase.xsd" Element "member2") STORAGE Object-relational TYPE "MEMBER2_T"
SQL> --
SQL> desc MEMBER2_T
MEMBER2_T extends SCOTT.HEAD_T
MEMBER2_T is NOT FINAL
Name                                                                                Null?    Type
SYS_XDBPD$                                                                                   XDB.XDB$RAW_LIST_T
Member2.Child1                                                                               VARCHAR2(4000 CHAR)
Member2.Child2                                                                               VARCHAR2(4000 CHAR)
SQL> --
SQL> select qualified_col_name, data_type from user_tab_cols where table_name = 'ROOT_TABLE'
2 /
QUALIFIED_COL_NAME                                               DATA_TYPE
SYS_NC_OID$                                                      RAW
SYS_NC_ROWINFO$                                                  XMLTYPE
XMLEXTRA                                                         XMLTYPEEXTRA
"XMLEXTRA"."NAMESPACES"                                          XMLTYPEPI
"XMLEXTRA"."EXTRADATA"                                           XMLTYPEPI
XMLDATA                                                          ROOT_T
SYS_TYPEID("XMLDATA")                                            RAW
"XMLDATA"."SYS_XDBPD$"                                           XDB$RAW_LIST_T
"XMLDATA"."head"                                                 HEAD_T
SYS_TYPEID("XMLDATA"."head")                                     RAW
"XMLDATA"."head"."SYS_XDBPD$"                                    XDB$RAW_LIST_T
TREAT("XMLDATA"."head" AS "MEMBER2_T")."Member2.Child1"          VARCHAR2
TREAT("XMLDATA"."head" AS "MEMBER2_T")."Member2.Child2"          VARCHAR2
TREAT("XMLDATA"."head" AS "MEMBER1_T")."Member1.Child1"          VARCHAR2
TREAT("XMLDATA"."head" AS "MEMBER1_T")."Member1.Child2"          VARCHAR2
ACLOID                                                           RAW
OWNERID                                                          RAW
17 rows selected.
SQL> select qualified_col_name, data_type from user_tab_cols where table_name = 'GLOBAL_MEMBER1_TABLE'
2 /
QUALIFIED_COL_NAME                                               DATA_TYPE
SYS_NC_OID$                                                      RAW
SYS_NC_ROWINFO$                                                  XMLTYPE
XMLEXTRA                                                         XMLTYPEEXTRA
"XMLEXTRA"."NAMESPACES"                                          XMLTYPEPI
"XMLEXTRA"."EXTRADATA"                                           XMLTYPEPI
XMLDATA                                                          MEMBER1_T
SYS_TYPEID("XMLDATA")                                            RAW
"XMLDATA"."SYS_XDBPD$"                                           XDB$RAW_LIST_T
"XMLDATA"."Member1.Child1"                                       VARCHAR2
"XMLDATA"."Member1.Child2"                                       VARCHAR2
ACLOID                                                           RAW
OWNERID                                                          RAW
12 rows selected.
SQL> select qualified_col_name, data_type from user_tab_cols where table_name = 'GLOBAL_MEMBER2_TABLE'
2 /
QUALIFIED_COL_NAME                                               DATA_TYPE
SYS_NC_OID$                                                      RAW
SYS_NC_ROWINFO$                                                  XMLTYPE
XMLEXTRA                                                         XMLTYPEEXTRA
"XMLEXTRA"."NAMESPACES"                                          XMLTYPEPI
"XMLEXTRA"."EXTRADATA"                                           XMLTYPEPI
XMLDATA                                                          MEMBER2_T
SYS_TYPEID("XMLDATA")                                            RAW
"XMLDATA"."SYS_XDBPD$"                                           XDB$RAW_LIST_T
"XMLDATA"."Member2.Child1"                                       VARCHAR2
"XMLDATA"."Member2.Child2"                                       VARCHAR2
ACLOID                                                           RAW
OWNERID                                                          RAW
12 rows selected.
SQL> insert into ROOT_TABLE values( XMLType (
2 '<root>
3    <member1>
4      <Member1.Child1>AAA</Member1.Child1>
5      <Member1.Child2>BBB</Member1.Child2>
6    </member1>
7 </root>'))
8 /
1 row created.
SQL> insert into ROOT_TABLE values( XMLType (
2 '<root>
3    <member2>
4      <Member2.Child1>CCC</Member2.Child1>
5      <Member2.Child2>DDD</Member2.Child2>
6    </member2>
7 </root>'))
8 /
1 row created.
SQL> set long 1000 pages 20
SQL> --
SQL> select * from ROOT_TABLE
2 /
SYS_NC_ROWINFO$
<root>
<member1>
    <Member1.Child1>AAA</Member1.Child1>
    <Member1.Child2>BBB</Member1.Child2>
</member1>
</root>
<root>
<member2>
    <Member2.Child1>CCC</Member2.Child1>
    <Member2.Child2>DDD</Member2.Child2>
</member2>
</root>
SQL> var schemaURL varchar2(256)
SQL> var schemaPath varchar2(256)
SQL> --
SQL> begin
2    :schemaURL := 'testcase.xsd';
3    :schemaPath := '/public/testcase.xsd';
4 end;
5 /
PL/SQL procedure successfully completed.
SQL> call dbms_xmlSchema.deleteSchema(:schemaURL,4)
2 /
Call completed.
SQL> declare
2    res boolean;
3    xmlSchema xmlType := xmlType(
4 '<?xml version="1.0" encoding="UTF-8"?>
5 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" elementFormDefault="qualified" attribute
FormDefault="unqualified" xdb:storeVarrayAsTable="true">
6     <xs:element name="root" type="rootType" xdb:defaultTable="ROOT_TABLE"/>
7     <xs:complexType name="rootType" xdb:SQLType="ROOT_T">
8             <xs:choice>
9                     <xs:element ref="member1" xdb:SQLInline="false" xdb:defaultTable="MEMBER1_TABLE"/>
10                     <xs:element ref="member2" xdb:SQLInline="false" xdb:defaultTable="MEMBER2_TABLE"/>
11             </xs:choice>
12     </xs:complexType>
13     <xs:complexType name="member1Type" xdb:SQLType="MEMBER1_T">
14                             <xs:sequence>
15                                     <xs:element name="Member1.Child1" type="xs:string"/>
16                                     <xs:element name="Member1.Child2" type="xs:string"/>
17                             </xs:sequence>
18     </xs:complexType>
19     <xs:complexType name="member2Type" xdb:SQLType="MEMBER2_T">
20                             <xs:sequence>
21                                     <xs:element name="Member2.Child1" type="xs:string"/>
22                                     <xs:element name="Member2.Child2" type="xs:string"/>
23                             </xs:sequence>
24     </xs:complexType>
25     <xs:element name="member1" type="member1Type" xdb:defaultTable="GLOBAL_MEMBER1_TABLE"/>
26     <xs:element name="member2" type="member2Type" xdb:defaultTable="GLOBAL_MEMBER2_TABLE"/>
27 </xs:schema>');
28 begin
29    if (dbms_xdb.existsResource(:schemaPath)) then
30      dbms_xdb.deleteResource(:schemaPath);
31    end if;
32    res := dbms_xdb.createResource(:schemaPath,xmlSchema);
33 end;
34 /
PL/SQL procedure successfully completed.
SQL> begin
2    dbms_xmlschema.registerSchema
3    (
4      :schemaURL,
5      xdbURIType(:schemaPath).getClob(),
6      TRUE,TRUE,FALSE,TRUE
7    );
8 end;
9 /
PL/SQL procedure successfully completed.
SQL> --
SQL> desc ROOT_TABLE
Name                                                                                Null?    Type
TABLE of SYS.XMLTYPE(XMLSchema "testcase.xsd" Element "root") STORAGE Object-relational TYPE "ROOT_T"
SQL> --
SQL> desc ROOT_T
ROOT_T is NOT FINAL
Name                                                                                Null?    Type
SYS_XDBPD$                                                                                   XDB.XDB$RAW_LIST_T
member1                                                                                      REF OF XMLTYPE
member2                                                                                      REF OF XMLTYPE
SQL> --
SQL> desc GLOBAL_MEMBER1_TABLE
Name                                                                                Null?    Type
TABLE of SYS.XMLTYPE(XMLSchema "testcase.xsd" Element "member1") STORAGE Object-relational TYPE "MEMBER1_T"
SQL> --
SQL> desc MEMBER1_T
MEMBER1_T is NOT FINAL
Name                                                                                Null?    Type
SYS_XDBPD$                                                                                   XDB.XDB$RAW_LIST_T
Member1.Child1                                                                               VARCHAR2(4000 CHAR)
Member1.Child2                                                                               VARCHAR2(4000 CHAR)
SQL> --
SQL> desc GLOBAL_MEMBER2_TABLE
Name                                                                                Null?    Type
TABLE of SYS.XMLTYPE(XMLSchema "testcase.xsd" Element "member2") STORAGE Object-relational TYPE "MEMBER2_T"
SQL> --
SQL> desc MEMBER2_T
MEMBER2_T is NOT FINAL
Name                                                                                Null?    Type
SYS_XDBPD$                                                                                   XDB.XDB$RAW_LIST_T
Member2.Child1                                                                               VARCHAR2(4000 CHAR)
Member2.Child2                                                                               VARCHAR2(4000 CHAR)
SQL> --
SQL> select qualified_col_name, data_type from user_tab_cols where table_name = 'ROOT_TABLE'
2 /
QUALIFIED_COL_NAME                                               DATA_TYPE
SYS_NC_OID$                                                      RAW
SYS_NC_ROWINFO$                                                  XMLTYPE
XMLEXTRA                                                         XMLTYPEEXTRA
"XMLEXTRA"."NAMESPACES"                                          XMLTYPEPI
"XMLEXTRA"."EXTRADATA"                                           XMLTYPEPI
XMLDATA                                                          ROOT_T
SYS_TYPEID("XMLDATA")                                            RAW
"XMLDATA"."SYS_XDBPD$"                                           XDB$RAW_LIST_T
"XMLDATA"."member1"                                              XMLTYPE
"XMLDATA"."member2"                                              XMLTYPE
ACLOID                                                           RAW
OWNERID                                                          RAW
12 rows selected.
SQL> select qualified_col_name, data_type from user_tab_cols where table_name = 'GLOBAL_MEMBER1_TABLE'
2 /
QUALIFIED_COL_NAME                                               DATA_TYPE
SYS_NC_OID$                                                      RAW
SYS_NC_ROWINFO$                                                  XMLTYPE
XMLEXTRA                                                         XMLTYPEEXTRA
"XMLEXTRA"."NAMESPACES"                                          XMLTYPEPI
"XMLEXTRA"."EXTRADATA"                                           XMLTYPEPI
XMLDATA                                                          MEMBER1_T
SYS_TYPEID("XMLDATA")                                            RAW
"XMLDATA"."SYS_XDBPD$"                                           XDB$RAW_LIST_T
"XMLDATA"."Member1.Child1"                                       VARCHAR2
"XMLDATA"."Member1.Child2"                                       VARCHAR2
ACLOID                                                           RAW
OWNERID                                                          RAW
12 rows selected.
SQL> select qualified_col_name, data_type from user_tab_cols where table_name = 'GLOBAL_MEMBER2_TABLE'
2 /
QUALIFIED_COL_NAME                                               DATA_TYPE
SYS_NC_OID$                                                      RAW
SYS_NC_ROWINFO$                                                  XMLTYPE
XMLEXTRA                                                         XMLTYPEEXTRA
"XMLEXTRA"."NAMESPACES"                                          XMLTYPEPI
"XMLEXTRA"."EXTRADATA"                                           XMLTYPEPI
XMLDATA                                                          MEMBER2_T
SYS_TYPEID("XMLDATA")                                            RAW
"XMLDATA"."SYS_XDBPD$"                                           XDB$RAW_LIST_T
"XMLDATA"."Member2.Child1"                                       VARCHAR2
"XMLDATA"."Member2.Child2"                                       VARCHAR2
ACLOID                                                           RAW
OWNERID                                                          RAW
12 rows selected.
SQL> insert into ROOT_TABLE values( XMLType (
2 '<root>
3    <member1>
4      <Member1.Child1>AAA</Member1.Child1>
5      <Member1.Child2>BBB</Member1.Child2>
6    </member1>
7 </root>'))
8 /
1 row created.
SQL> insert into ROOT_TABLE values( XMLType (
2 '<root>
3    <member2>
4      <Member2.Child1>CCC</Member2.Child1>
5      <Member2.Child2>DDD</Member2.Child2>
6    </member2>
7 </root>'))
8 /
1 row created.
SQL> set long 1000 pages 20
SQL> --
SQL> select * from ROOT_TABLE
2 /
SYS_NC_ROWINFO$
<root>
<member1>
    <Member1.Child1>AAA</Member1.Child1>
    <Member1.Child2>BBB</Member1.Child2>
</member1>
</root>
<root>
<member2>
    <Member2.Child1>CCC</Member2.Child1>
    <Member2.Child2>DDD</Member2.Child2>
</member2>
</root>
SQL>
SQL>
SQL>

Tried installing itunes 10.5 and recieved this error An error occured during the installation of assembly 'Micrsoft .VC80.CRT .type="win32" ,version="8.0.50727.6195".publicKeyToken="1fc8b3b9a1e18e3b".processorArchitectu re="x86"'. Please refer to Help and

Tried to install itunes 10/5 and got this error:
An error occured during the installation of assembly 'Micrsoft .VC80.CRT .type="win32" ,version="8.0.50727.6195".publicKeyToken="1fc8b3b9a1e18e3b".processorArchitectu re="x86"'. Please refer to Help and Support for more information. HRESULT: 0x80073712
Can anyone help solve this problem

Exactly the same problems as many others with iTunes 10.5 and my Windows 7 32 bit laptop: An error occurred during the installation of assembly 'Microsoft.VC80.CRT .type="win32", … HRESULT:0x800736FD. I followed the Apple instructions to completely uninstall earlier iTunes and all Apple applications and then tried to re-install iTunes 10.5. Numerous attempts. Still no success. Constantly goes through the install and then rolls back after failure.
By unzipping using WinRAR and installing each module separately it seems that the module that fails is the AppleApplicationSupport.msi
Finally I uninstalled everything again and reinstalled iTunes 10.4.1. This installed perfectly. So at least I still have iTunes.
I was able to install iTunes 10.5 on myWindows XP SP3 desktop.
I noticed with WinRAR that the AppleApplicationSupport.msi file with 10.5 is a completely different size to that with 10.4.1. This suggests to me a conflict between the latest AppleApplicationSupport.msi and Windows 7.

Order type and Item category group

Can anyone tell me which is the relation between order type and Item category group from material master ??
In fact the problem is that I have created a material and when I want to create new sales order it gives me this errror:
"No item category available (Table T184 ZORDER ZITGR)"
Is there a tranzaction where I can assign Item category group ZITGR to sale order type ZORDER or something like that??
What should i do?

Hi Dan,
Goto T-Code VOV4 and maintain the table
Sales Doc type + Item Category Group + Usage + Higher level Item Category = Item Category
TA + NORM + Nil + Nil = TAN
If you have Customized your own Document Type and Item Category Group and Item Category then give your
Sales Doc type (ZORDER)+ Item Category Group (ZITGR)+ Usage + Higher level Item Category = Item Category (ZTAN)
Reward if helpful
Regards PAVAN

Has anyone found a solution to sending mail to groups in Mavericks? I've been given 2 approaches - 1 to type user name group into address and the other to go to address book and right click on group. Neither are satisfactory. Does anyone have a solution?

Has anyone found a solution to sending mail to Groups in Mavericks? I've been given two solutions - neither are satisfactory. One is to type name of group into address line, the other is to go to address book and right click on group.

thanks a lot for your kind help... saved me a lot of time and effort, could not believe it at first that the process is so simple but once i followed the steps it worked fine. appreciate your help.

Link between code and code groups and inspection type

Hi All,
I want to know the link between code and Code Group for UD and inspection type?
There is an option of choosing Usage selected set in SPRO "Seeting for inspection type".If i dont enter anything there,will it show all the code groups in the system while taking UD?
Pls guide

Hi Shreya,
Yes, the link between code and Code Group for UD and inspection type is specific selection of UD related to specific inspection type. Ex. there are separate UD codes individually for Goods receipt against PO, Gr against Production or for In-process inspection ets. so If you assign the selected sets at SPRO Inspection type, then while doing UD system will show UD codes related to only that inspection type.
If you don't enter anything there at SPRO, you will see all the code groups in the system while taking UD and one can get confused in selecting the relevant code.
so assigning of UD selected sets, plant wise (tick) at " Inspection types" is best practice.
Best Regards,
Shekhar

Wage type and group

hi all,
i have created a labour activities. after production order conf or delivery i want cost of labour to flow to HR.
i know in work center we can create wage type and pls let me know what are the steps in achieving this
thank you
sanjeev

Dear llija,
These were the most predominant factor for Payroll. Though there are lots to explain on these factors, I had just highlighted on important aspect, by which you can have an idea on what is it all about in creating a wage type.
Wage Type Group(T-code:PU96) : Combination of all the Wage types which are to be populated in the particular infotype. Say for instance: 0008 Basic Pay Infotype has a group of Wage types clubbed together which helps to get populated during the creation of Basic Pay 0008 infotype. Which means, only these particular wage types will appear in 0008.
Wage Type Catalog(OH11) : Here, we copy the Primary Wage type and name it according to the customer specific requirements. All the custom wage type should be copied from the standard model wage type.
Wage Type Model (Table : V_T539A): This Wage type model is created in order to make the wage types get defaulted in 0008 Basic Pay infotype using the LGMST Feature. Where, LGMST feature ends with the return value as No:of Enterable Wage types / Wage Type Model.
Hope this brief information gives you a clear understanding on Wage Type concept.
Regards
Veena

Type and Group color doesn't change.

I'm having a problem with Adobe Illustrator CC 17.1.0 with colors, types and groups.
If I select a text or a group and try to change its color, the Fill color stays correct a the panel, but the text or the group maintains the old color, like the screenshot below.
The only way to change color its is selecting all text characters or all group's elements.

Here they are.
Thanks for trying to help!

JAXB: Abstract Types and Substitution Group Errors

Similar Messages

Maybe you are looking for