Assign ora:getCompositeInstanceId() in the xsd element

I need to assign BPEL process id, ora:getCompositeInstanceId(), to one of element in the xsd. Is this function available in the Transformation mapping so that I can assign to the element? I found the function in the mediator functions but I didn't work in the BPEL. Any of your idea will be appreciated.
SOA: 11.1.1.6

It works in BPEL, it is available as part of Advanced Functions in Expression Builder. However, it does not in Transformations(XSLT). So to work around two alternatives can be used
Alternate 1:
- Create a temp variable like "varCompositeInstanceId".
- Create a assign activity, before the transformation, set the value of the variable to "ora:getCompositeInstanceId()" inside this Assign activity.
- Send the variable as a parameter to the transformation.
- Use the parameter to map to the target inside the transformation(XSLT).
Alternate 2:
- Set the target in the XSLT to some random text.
- After the transformation, add an assign activity and inside it, set the value of the taget to "ora:getCompositeInstanceId()".
Mark the posting appropriately as "helpful" or "correct answer", if your issue is resolved.

Similar Messages

Creating XML from XSD, Only create The First Element

Hi,
I create a XML File from a xsd schema by this way:
            DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
          factory.setNamespaceAware(true);
          factory.setValidating(true);
               factory.setAttribute(JAXP_SCHEMA_LANGUAGE,W3C_XML_SCHEMA);
               factory.setAttribute(JAXP_SCHEMA_SOURCE, new File(MY_SCHEMA));
                DocumentBuilder documentBuilder =factory.newDocumentBuilder();
          documentBuilder.setErrorHandler(new SimpleDOMHandler());
          Document parse = documentBuilder.parse(new File(MY_XML));The first lines of the schema:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
     targetNamespace="http://gencat.net/scsp/esquemes/peticion"
     elementFormDefault="qualified" attributeFormDefault="unqualified"
     id="Peticio" xmlns:p="http://gencat.net/scsp/esquemes/peticion">
     <xs:element name="Apellido1">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:maxLength value="40" />
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="Apellido2">
        .............................The problem is that the created document only have the first element "Apellido1". I dont know if it is a wrong xsd, or i'm using a bad way to do it.
Thanks a lot, and apologize for my english

Hi,
Is it possible to create and populate XML from an XSD
without knowing what the XSD elements are beforehand
(all the examples appear to know what the input XSD
will be, and therefore know what the set and get
methods should be called)? I think it is possible--you would have to recompile each time (unless you can dynamically recompile, which would be neat), but using the classes getMethod() function, you can list all the methods. You would then have to do some tricky logic to determine which of the getMethods you want (for example NOT getClass()), and you can basically call them in sequence. You also need to worry about handling lists & recursively call xxxType classes.
I'm experimenting with this, and it can get a little frustrating because there are a lot of odd cases to handle (for example, while setting the elements of a list, you need to actually get the list & add elements to it), but I think it's possible.
>
Can a user browse for an xsd to input, and the java
will dynamically create the get methods, and be able
to create instances and populate variables before
converting to XML?
What I'm puzzled about is where you'd get the data to populate the variables? Perhaps a database, or a bean? If you just want to make a test xml file, then it doesn't matter, but with real data, I think you'd still have to change how you actually get the variables you want to populate the xml file with, right? In other words, if your schema changed, the parameters you're passing to the set methods would change as well.
Maybe we'll see some more packages in the future to make this task easier.

Xsd:element ref not working with jaxb

Hi,
I'm trying to implement a simple web service based on jax-ws.
My probem is that binding does not working when I use the <xsd:element ref="..."/> attribute in the schema description.
Here is the web service implementation :
@Stateless()
@WebService(
serviceName="AlarmBeanService",
targetNamespace="http://two.one.net/jws/alarm/",
endpointInterface="net.one.two.jws.alarm.AlarmBeanPortType")
public class AlarmBean implements AlarmBeanPortType {
public AlarmCreateOut persist(AlarmCreateIn in) {
return new AlarmCreateOut();
My AlarmCreateIn message is defined in AlarmCreateIn.xsd :
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:c="http://two.one.net/jws/alarm/schema/common/"
targetNamespace="http://two.one.net/jws/alarm/schema/create/in/"
elementFormDefault="unqualified"
attributeFormDefault="unqualified">
<xsd:import namespace="http://two.one.net/jws/alarm/schema/common/" schemaLocation="../common/AlarmDataTypes.xsd"/>
<xsd:element name="AlarmCreateIn">
<xsd:annotation>
<xsd:documentation>
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="c:alarm" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
This way it's not working, my "alarm" object in AlarmCreateIn is always null.
But it works if referencing my alarm object like in the following xsd :
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
     xmlns:alarm="http://two.one.net/jws/ctypes/alarm/"
     targetNamespace="http://two.one.net/jws/alarm/schema/create/in/"
     elementFormDefault="unqualified"
     attributeFormDefault="unqualified">
     <xsd:import namespace="http://two.one.net/jws/ctypes/alarm/" schemaLocation="../../ctypes/alarm/Alarm.xsd" />
     <xsd:element name="AlarmCreateIn">
          <xsd:annotation>
               <xsd:documentation>
               </xsd:documentation>
          </xsd:annotation>
          <xsd:complexType>
               <xsd:sequence>
                    <xsd:element name="alarm"      type="alarm:AlarmXsd"          minOccurs="0" />
               </xsd:sequence>
          </xsd:complexType>
     </xsd:element>
</xsd:schema>
Any ideas on what happen?
Thanks.
Edited by will_mad at 07/24/2007 10:15 AM

Most likely you chose the logical file instead of the correct file for the PSE editor. The one you can see, at the top level of the PSE 10 folder in Applications, is the welcome screen. The actual editor is hidden in the Support Files folder. You want this one:

Is an assigned value to an variable in the domain of the data element

Hi
how can I check if the value, which I want to assign to an variable is in the domain of the data element of that variable.
Example:
I defined a data element myDataElement. The Elementary Type of myDataElement is the Domain myDomain.
myDomain has the Format: Char with Length 1 and the fixed values 'A' and 'B'.
The following code works, but IMHO should not:
DATA testVar TYPE myDomain.
testVar = 'Foo'.
The value of testVar is now: 'F' .
As 'F' is not in the fixed values, this is a behaviour which I don't want. How can I prevent this from not happening (without using a bunch of IFs)?
In such a case, it were nice if an exception were raised.
Regards
Gilles

Thanks Gungor.
I tried it with DDUT_DOMVALUES_GET. Works so far. I think I will write some FMs on my own, like this one:
FUNCTION z_valueisindomain.
*"*"Local Interface:
*" IMPORTING
*"     REFERENCE(IV_DOMAINNAME) TYPE DDOBJNAME
*"     REFERENCE(IV_EVALUATING_VALUE) TYPE ANY
*" EXPORTING
*"     REFERENCE(EV_DESTINATION) TYPE ANY
*" EXCEPTIONS
*"      ILLEGAL_INPUT
*"      NOT_IN_DOMAIN
DATA domainvalues TYPE TABLE OF dd07v.
CALL FUNCTION 'DDUT_DOMVALUES_GET'
    EXPORTING
      name          = iv_domainname
    TABLES
      dd07v_tab     = domainvalues
    EXCEPTIONS
      illegal_input = 1
      OTHERS        = 2.
IF sy-subrc <> 0.
    RAISE illegal_input.
ENDIF.
DATA oneline TYPE dd07v.
LOOP AT domainvalues INTO oneline.
    IF oneline-domvalue_l EQ iv_evaluating_value.
      ev_destination = iv_evaluating_value.
      EXIT.
    ENDIF.
ENDLOOP.
IF ev_destination IS INITIAL.
    RAISE not_in_domain.
ENDIF.
ENDFUNCTION.
I'm pretty new to ABAP, so this FM might not be very elegant.
Regards
Gilles

Uniqueness for xml element is not validated with the xsd:unique

Hi
I am using <xsd:unique> to specify uniqueness for certain elements in the schema. But when i create the xml for the schema,it allows me to create elements with duplicate values for which the uniqueness is defined and also it is allowed to parse the xml correctly.I am using jaxb2.0 and jaxp2.0 to bind the xml and parse it. The schema is described below :
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
     <xsd:include schemaLocation="ArtifactDetails.xsd" />
     <xsd:element name="EKMArtifacts">
          <xsd:complexType>
               <xsd:sequence>
                    <xsd:element name="Artifact" minOccurs="0" maxOccurs="unbounded">
                         <xsd:complexType>
                              <xsd:sequence>
                                   <xsd:element name="ArtifactType" type="xsd:string" nillable="false" minOccurs="1" maxOccurs="1" />
                                   <xsd:element name="ArtifactName" type="xsd:string" nillable="false" minOccurs="1" maxOccurs="1" />
                                   <xsd:element name="Status" type="xsd:string" nillable="false" minOccurs="1" maxOccurs="1" />
                                   <xsd:element name="VersionString" type="xsd:string" nillable="false" minOccurs="1" maxOccurs="1" />
                                   <xsd:element name="Artifactdesc" type="xsd:string" nillable="false" minOccurs="1" maxOccurs="1" />
                                   <xsd:element name="Functionaldesc" type="xsd:string" nillable="false" minOccurs="1" maxOccurs="1" />
                                   <xsd:element name="Department" type="xsd:string" nillable="false" minOccurs="1" maxOccurs="1" />
                                   <xsd:element name="Location" type="xsd:string" nillable="false" minOccurs="1" maxOccurs="1" />
                                   <xsd:element name="Rated" type="xsd:string" nillable="false" minOccurs="1" maxOccurs="1" />
                                   <xsd:element name="Category" type="xsd:string" nillable="false" minOccurs="1" maxOccurs="1" />
                                   <xsd:element name="Createdby" type="xsd:string" nillable="false" minOccurs="1" maxOccurs="1" />
                                   <xsd:element name="OSPlatform" type="xsd:string" nillable="false" minOccurs="1" maxOccurs="1" />
                                   <xsd:element name="APPPlatform" type="xsd:string" nillable="false" minOccurs="1" maxOccurs="1" />
                                   <xsd:element name="Country" type="xsd:string" nillable="false" minOccurs="1" maxOccurs="1" />
                                   <xsd:element name="State" type="xsd:string" nillable="false" minOccurs="1" maxOccurs="1" />
                                   <xsd:element name="Vendor" type="xsd:string" nillable="false" minOccurs="1" maxOccurs="1" />
                                   <xsd:element ref="ArtifactDetails" minOccurs="0" maxOccurs="1" />
                              </xsd:sequence>
                         </xsd:complexType>
                    </xsd:element>
               </xsd:sequence>
          </xsd:complexType>
          <xsd:unique name="ArtifactNameUnique">
               <xsd:selector xpath="Artifact" />
               <xsd:field xpath="ArtifactName" />
          </xsd:unique>
     </xsd:element>
</xsd:schema>
Can anyone help me out
Thanks in advance

Well there's nothing wrong with your schema (I copyied it into XMLSpy and wasn't able to create two artifacts with the same name). My guess is that JAXB still does not support xsd:unqiue
http://www.onjava.com/pub/a/onjava/2004/12/15/jaxb.html

WSDL incorrect - in XSD elements always must be the root element?

Hi!
First of all, sorry about my english, but I'm not accustomed to write in this language ;-)
We're trying to publish a Webservice with JAXWS and with a classes generated via JAXB parsing a group of XSD files, always in a maven project with java 5.
More explained the steps we are trying to follow:
1) parse the XSD files with JAXB and generate a JAR file to be included like a dependency in the webapp
2) use the classes packaged in the JAR in other maven project and define and deploy a webapp with the webservice using JAXWS defining a SEI that uses and returns a Type included in the JAR generated in the previous step. Here it is the interface that implements the SEI:
@WebMethod
     public TESTELEMENT test(
               @WebParam(name = "test")
               TESTELEMENT element);The problem seems to be that if the elements in the original XSD files aren't root elements the WSDL generated is incorrect.
Here there are the XSD files we are using and the WSDL error result (XMLSpy dixit, "ns1:Example" must refer to an existing element).
Anyone knows what happens?
Thank you in advance and sorry about this large message!
+--- start of TEST.XSD --+
<?xml version="1.0" encoding="utf-8"?>
<xs:schema xmlns="http://example.work/test" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://example.work/test" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:include schemaLocation="TEST_TYPE.xsd"/>

<xs:element name="TEST_ELEMENT">
<xs:annotation>
<xs:documentation>Blablabla</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence minOccurs="0" maxOccurs="unbounded">
<xs:element name="Example" type="TestType"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>+-- end --+
+--- start of TEST_TYPE.xsd --+
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns="http://example.work/test" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://example.work/test" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:complexType name="TestType">
<xs:annotation>
<xs:documentation>Example type</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="Element_A" type="xs:string"/>
<xs:element name="Elment_B" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:schema>+-- end --+
+-- start WSDL error --+
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions name="TestBO" targetNamespace="http://our.package.test/" xmlns:ns1="http://our.package.test/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://example.work/test" xmlns:tns="http://example.work/test" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="TEST_ELEMENT">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" name="Example" type="tns:TestType"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="TestType">
<xs:sequence>
<xs:element name="Element_A" type="xs:string"/>
<xs:element name="Elment_B" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="unqualified" targetNamespace="http://our.package.test" xmlns:ns1="http://example.work/test" xmlns:tns="http://our.package.test" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import namespace="http://example.work/test"/>
<xs:element name="test" type="tns:test"/>
<xs:element name="testResponse" type="tns:testResponse"/>
<xs:complexType name="test">
<xs:sequence>
<xs:element minOccurs="0" name="test">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" ref="ns1:Example"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexType name="testResponse">
<xs:sequence>
<xs:element minOccurs="0" name="return">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" ref="ns1:Example"/> **
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:schema>
</wsdl:types>
<wsdl:message name="test">
<wsdl:part element="ns1:test" name="parameters">
</wsdl:part>
</wsdl:message>
<wsdl:message name="testResponse">
<wsdl:part element="ns1:testResponse" name="parameters">
</wsdl:part>
</wsdl:message>
<wsdl:portType name="TestBO">
<wsdl:operation name="test">
<wsdl:input message="ns1:test" name="test">
</wsdl:input>
<wsdl:output message="ns1:testResponse" name="testResponse">
</wsdl:output>
</wsdl:operation>
</wsdl:portType>
</wsdl:definitions>+-- end --+

Hi again.
About my last post, say that the WSDL generated, in fact, was generated with CXF, sorry.
Using JAXWS (wsgen to be more explicit) the WSDL results still are not ok, as you can see, the error is in the last ns1:Example reference in ServeiTestBO_schema1.xsd, that XMLSpy says that doesn't exists :-( :
+--- ServeiTestBOImplService.wsdl [ServeiTestBOImpl - SEI] ---+
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<definitions targetNamespace="http://impl.our.package.test/" name="ServeiTestBOImplService" xmlns:tns="http://impl.our.package.test/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl/">
<import namespace="http://our.package.test/" location="ServeiTestBO.wsdl"/>
<binding name="ServeiTestBOImplPortBinding" type="ns1:ServeiTestBO" xmlns:ns1="http://our.package.test/">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
    <operation name="test">
      <soap:operation soapAction=""/>
      <input>
        <soap:body use="literal"/>
      </input>
      <output>
        <soap:body use="literal"/>
      </output>
    </operation>
</binding>
<service name="ServeiTestBOImplService">
    <port name="ServeiTestBOImplPort" binding="tns:ServeiTestBOImplPortBinding">
      <soap:address location="REPLACE_WITH_ACTUAL_URL"/>
    </port>
</service>
</definitions>+--- ServeiTestBO.wsdl [SEI interface] ---+
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<definitions targetNamespace="http://our.package.test/" xmlns:tns="http://our.package.test/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/">
<types>
    <xsd:schema>
      <xsd:import namespace="http://our.package.test/" schemaLocation="ServeiTestBO_schema1.xsd"/>
    </xsd:schema>
    <xsd:schema>
      <xsd:import namespace="http://example.work/test" schemaLocation="ServeiTestBO_schema2.xsd"/>
    </xsd:schema>
</types>
<message name="test">
    <part name="parameters" element="tns:test"/>
</message>
<message name="testResponse">
    <part name="parameters" element="tns:testResponse"/>
</message>
<portType name="ServeiTestBO">
    <operation name="test">
      <input message="tns:test"/>
      <output message="tns:testResponse"/>
    </operation>
</portType>
</definitions>+--- ServeiTestBO_schema1.xsd *[with error in the last "ns1:Example"]* ---+
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<xs:schema version="1.0" targetNamespace="http://our.package.test/" xmlns:tns="http://our.package.test/" xmlns:ns1="http://example.work/test" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import namespace="http://example.work/test" schemaLocation="ServeiTestBO_schema2.xsd"/>
<xs:element name="test" type="tns:test"/>
<xs:element name="testResponse" type="tns:testResponse"/>
<xs:complexType name="test">
    <xs:sequence>
      <xs:element name="test" minOccurs="0">
        <xs:complexType>
          <xs:sequence>
            <xs:element ref="ns1:Example" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
</xs:complexType>
<xs:complexType name="testResponse">
    <xs:sequence>
      <xs:element name="return" minOccurs="0">
        <xs:complexType>
          <xs:sequence>
            <xs:element ref="ns1:Example" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
</xs:complexType>
</xs:schema>
--- ServeiTestBO_schema2.xsd ---
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<xs:schema elementFormDefault="qualified" version="1.0" targetNamespace="http://example.work/test" xmlns:tns="http://example.work/test" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="TEST_ELEMENT">
    <xs:complexType>
      <xs:sequence>
        <xs:element name="Example" type="tns:TestType" minOccurs="0" maxOccurs="unbounded"/>
      </xs:sequence>
    </xs:complexType>
</xs:element>
<xs:complexType name="TestType">
    <xs:sequence>
      <xs:element name="Element_A" type="xs:string"/>
      <xs:element name="Elment_B" type="xs:boolean"/>
      <xs:element name="Sex" type="tns:SexType"/>
    </xs:sequence>
</xs:complexType>
<xs:simpleType name="SexType">
    <xs:restriction base="xs:string">
      <xs:enumeration value="M"/>
      <xs:enumeration value="W"/>
    </xs:restriction>
</xs:simpleType>
</xs:schema>Thanks in advance again.

Multiple Root elements in the XSD Schema

Hi Dear MDM gurus,
I have manually created an XSD Schema and I can import it in the Syndicator without any problem.
I have 3 different Root elements in the schema that I want to use and map to the corresponding table of this type.
In my Syndicator screen in the Rood dropdown box I can see all three of the Root elements that I have in the schema.
If I select the first Root element - everything goes fine and I can do my mapping, save the map, etc.
The problem is that if I select the second or third root element to do the mapping for them, the syndicator does not show the structure in the Item Mapping after that.
I tried moving the Second root element of the schema and make it first and it works with it, but then the other two are not appearing and I have the same issue.
Does MDM support only one Root element in the Schema? If that's the case, why does it show all three of them in the dropdown?
Here is an example:
1. If I have them in this order in my XSD
          <xs:element name="ManufacturerGroupNumber" type="ManufacturerGroupNumbers"/>
          <xs:element name="SupplierGroupNumber" type="SupplierGroupNumbers"/>
          <xs:element name="SupplierLocationNumber" type="Suppliers"/>
I can only see the structure when I select the "ManufacturerGroupNumber".
2. If I have them in the Schema in this order
          <xs:element name="SupplierLocationNumber" type="Suppliers"/>
          <xs:element name="SupplierGroupNumber" type="SupplierGroupNumbers"/>
          <xs:element name="ManufacturerGroupNumber" type="ManufacturerGroupNumbers"/>
I can only see the structure when I select the first one again "SupplierLocationNumber" and I can only do the mapping for it.
Any help would be appreciated.
Thanks in advance,
Boris

Hello Satish,
Thank you for your quick response.
I read some of the architectural approaches and XML specifications and depending on your design, you may have only one Root element or in rare cases Several Root elements. In my case, I was advised by our PI experts to use Multiple Root elements and this gives me the following:
Advantages:
u2022 The reusability of the schema definition is available for all types and all elements defined in the global namespace.
Disadvantages:
u2022 Since there are many global elements, there are many valid XML documents.
I initially had the schema as you suggested, but they didn't like it in PI and advised me to change it with having multiple roots.
What I'm trying to figure out is if there is a bug in MDM that does not allow to use the rest of the root elements, so I can open an OSS message.
Thanks,
Boris

Function module to get the wbs element by entering Assignment No.

Is there any Function module to get the wbs element by entering Assignment No.???????
Thanks and regards
Manish Thakur

hi Manish,
Just look at this function module.
function wbs_assignment_check.
""Lokale Schnittstelle:
*" IMPORTING
*"     REFERENCE(I_COMPONENT) LIKE RESBDGET STRUCTURE RESBDGET
*"     REFERENCE(I_PSPEL) LIKE RESB-PSPEL
*"     REFERENCE(I_RFPNT) LIKE AFVC-RFPNT
*" EXPORTING
*"     REFERENCE(E_PSPEL) LIKE RESB-PSPEL
e_pspel = i_pspel.
endfunction.
hope this helps u
REWARD IF USEFUL
thanks and regards
suma sailaja

Making XSD element name match the column name/header

The XML format of the answer I created looks like the following. How can I change the element name from C0, C1... to real column name? http://host:port/analytics/saw.dll?Go&searchid provided the XML
<?xml version="1.0" encoding="utf-8" ?>
- <RS xmlns="urn:schemas-microsoft-com:xml-analysis:rowset">
- <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:saw-sql="urn:saw-sql" targetNamespace="urn:schemas-microsoft-com:xml-analysis:rowset">
- <xsd:complexType name="R">
- <xsd:sequence>
<xsd:element name="C0" type="xsd:double" minOccurs="0" maxOccurs="1" saw-sql:type="double" saw-sql:displayFormula=""CUSTOMERS"."SALES"" saw-sql:aggregationRule="none" saw-sql:aggregationType="nonAgg" saw-sql:tableHeading="CUSTOMERS" saw-sql:columnHeading="SALES" />
<xsd:element name="C1" type="xsd:string" minOccurs="0" maxOccurs="1" saw-sql:type="varchar" saw-sql:displayFormula=""CUSTOMERS"."CITY"" saw-sql:aggregationRule="none" saw-sql:aggregationType="nonAgg" saw-sql:tableHeading="CUSTOMERS" saw-sql:columnHeading="CITY" />
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
- <R>
*<C0>0.3</C0>*
*<C1>WILLITS</C1>*
</R>
Edited by: user732932 on Jan 7, 2010 11:38 AM

OR is there a way to pass the column headers from OBIEE to a URL? For example, session parameters can be passed using @{parmName}

Assign personal resource to the internal activity element with diff. UOM.

Hi All,
Is it possible to assign personal resource to the internal processing activity ELEMENT if the unit of measure for the work assigned is different than the unit of measure of the internal processing ACTIVITY.....
Regards,
Arunchalam.An

My activity type UOM and the work UOM are the same.
I would explain again the scenario, I have created a internal processing activity and the work UOM is HR as well as the activity type UOM is HR and to that i have assigned an internally processing activity element with work UOM as M3 and the activity type UOM also as M3.
Now, while i am in CMP2, I am not able to assign the work force to both activity and activity element. The conflict is the UOM. Hope now I am clear.
Regards,
Arunachalam.An

How can I set the caption text of picture controls inside an array or how can I choose which array element is assigned using the array elements caption text property.

I have 8 picture controls inside an array and I would like to set the caption text of these controls.
I have used the property node of the array and used the array elements property caption text to set the text.
The problem is however that I set the same text to all the picture controls inside the array.
My question is how to set caption text of specific elements (Picture control) that I have so far only been able to access using the array elements caption text property.

Some more help
1 You could use the caption of the array and place it in front of the selected picture and update that using property nodes.
2 Like Norbett said if you use a cluster of pictures then their caption can be updated individually.
Here is a an example that demonstrates the above
David
Attachments:
Modify the Captions Of Pictures.vi ‏83 KB

ORA-07445 in the alert log when inserting into table with XMLType column

I'm trying to insert an xml-document into a table with a schema-based XMLType column. When I try to insert a row (using plsql-developer) - oracle is busy for a few seconds and then the connection to oracle is lost.
Below you''ll find the following to recreate the problem:
a) contents from the alert log
b) create script for the table
c) the before-insert trigger
d) the xml-schema
e) code for registering the schema
f) the test program
g) platform information
Alert Log:
Fri Aug 17 00:44:11 2007
Errors in file /oracle/app/oracle/product/10.2.0/db_1/admin/dntspilot2/udump/dntspilot2_ora_13807.trc:
ORA-07445: exception encountered: core dump [SIGSEGV] [Address not mapped to object] [475177] [] [] []
Create script for the table:
CREATE TABLE "DNTSB"."SIGNATURETABLE"
(     "XML_DOCUMENT" "SYS"."XMLTYPE" ,
"TS" TIMESTAMP (6) WITH TIME ZONE NOT NULL ENABLE
) XMLTYPE COLUMN "XML_DOCUMENT" XMLSCHEMA "http://www.sporfori.fo/schemas/www.w3.org/TR/xmldsig-core/xmldsig-core-schema.xsd" ELEMENT "Object"
ROWDEPENDENCIES ;
Before-insert trigger:
create or replace trigger BIS_SIGNATURETABLE
before insert on signaturetable
for each row
declare
-- local variables here
l_sigtab_rec signaturetable%rowtype;
begin
if (:new.xml_document is not null) then
:new.xml_document.schemavalidate();
end if;
l_sigtab_rec.xml_document := :new.xml_document;
end BIS_SIGNATURETABLE2;
XML-Schema (xmldsig-core-schema.xsd):
=====================================================================================
<?xml version="1.0" encoding="utf-8"?>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:xdb="http://xmlns.oracle.com/xdb"
targetNamespace="http://www.w3.org/2000/09/xmldsig#" version="0.1" elementFormDefault="qualified">

<xs:simpleType name="CryptoBinary">
<xs:restriction base="xs:base64Binary">
</xs:restriction>
</xs:simpleType>

<xs:element name="Signature" type="ds:SignatureType"/>
<xs:complexType name="SignatureType">
<xs:sequence>
<xs:element ref="ds:SignedInfo"/>
<xs:element ref="ds:SignatureValue"/>
<xs:element ref="ds:KeyInfo" minOccurs="0"/>
<xs:element ref="ds:Object" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="Id" type="xs:ID" use="optional"/>
</xs:complexType>
<xs:element name="SignatureValue" type="ds:SignatureValueType"/>
<xs:complexType name="SignatureValueType">
<xs:simpleContent>
<xs:extension base="xs:base64Binary">
<xs:attribute name="Id" type="xs:ID" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>

<xs:element name="SignedInfo" type="ds:SignedInfoType"/>
<xs:complexType name="SignedInfoType">
<xs:sequence>
<xs:element ref="ds:CanonicalizationMethod"/>
<xs:element ref="ds:SignatureMethod"/>
<xs:element ref="ds:Reference" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="Id" type="xs:ID" use="optional"/>
</xs:complexType>
<xs:element name="CanonicalizationMethod" type="ds:CanonicalizationMethodType"/>
<xs:complexType name="CanonicalizationMethodType" mixed="true">
<xs:sequence>
<xs:any namespace="##any" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>
<xs:attribute name="Algorithm" type="xs:anyURI" use="required"/>
</xs:complexType>
<xs:element name="SignatureMethod" type="ds:SignatureMethodType"/>
<xs:complexType name="SignatureMethodType" mixed="true">
<xs:sequence>
<xs:element name="HMACOutputLength" minOccurs="0" type="ds:HMACOutputLengthType"/>
<xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>
<xs:attribute name="Algorithm" type="xs:anyURI" use="required"/>
</xs:complexType>

<xs:element name="Reference" type="ds:ReferenceType"/>
<xs:complexType name="ReferenceType">
<xs:sequence>
<xs:element ref="ds:Transforms" minOccurs="0"/>
<xs:element ref="ds:DigestMethod"/>
<xs:element ref="ds:DigestValue"/>
</xs:sequence>
<xs:attribute name="Id" type="xs:ID" use="optional"/>
<xs:attribute name="URI" type="xs:anyURI" use="optional"/>
<xs:attribute name="Type" type="xs:anyURI" use="optional"/>
</xs:complexType>
<xs:element name="Transforms" type="ds:TransformsType"/>
<xs:complexType name="TransformsType">
<xs:sequence>
<xs:element ref="ds:Transform" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:element name="Transform" type="ds:TransformType"/>
<xs:complexType name="TransformType" mixed="true">
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:any namespace="##other" processContents="lax"/>

<xs:element name="XPath" type="xs:string"/>
</xs:choice>
<xs:attribute name="Algorithm" type="xs:anyURI" use="required"/>
</xs:complexType>

<xs:element name="DigestMethod" type="ds:DigestMethodType"/>
<xs:complexType name="DigestMethodType" mixed="true">
<xs:sequence>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="Algorithm" type="xs:anyURI" use="required"/>
</xs:complexType>
<xs:element name="DigestValue" type="ds:DigestValueType"/>
<xs:simpleType name="DigestValueType">
<xs:restriction base="xs:base64Binary"/>
</xs:simpleType>


<xs:element name="KeyInfo" type="ds:KeyInfoType"/>
<xs:complexType name="KeyInfoType" mixed="true">
<xs:choice maxOccurs="unbounded">
<xs:element ref="ds:KeyName"/>
<xs:element ref="ds:KeyValue"/>
<xs:element ref="ds:RetrievalMethod"/>
<xs:element ref="ds:X509Data"/>
<xs:element ref="ds:PGPData"/>
<xs:element ref="ds:SPKIData"/>
<xs:element ref="ds:MgmtData"/>
<xs:any processContents="lax" namespace="##other"/>

</xs:choice>
<xs:attribute name="Id" type="xs:ID" use="optional"/>
</xs:complexType>
<xs:element name="KeyName" type="xs:string"/>
<xs:element name="MgmtData" type="xs:string"/>
<xs:element name="KeyValue" type="ds:KeyValueType"/>
<xs:complexType name="KeyValueType" mixed="true">
<xs:choice>
<xs:element ref="ds:DSAKeyValue"/>
<xs:element ref="ds:RSAKeyValue"/>
<xs:any namespace="##other" processContents="lax"/>
</xs:choice>
</xs:complexType>
<xs:element name="RetrievalMethod" type="ds:RetrievalMethodType"/>
<xs:complexType name="RetrievalMethodType">
<xs:sequence>
<xs:element ref="ds:Transforms" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="URI" type="xs:anyURI"/>
<xs:attribute name="Type" type="xs:anyURI" use="optional"/>
</xs:complexType>

<xs:element name="X509Data" type="ds:X509DataType"/>
<xs:complexType name="X509DataType">
<xs:sequence maxOccurs="unbounded">
<xs:choice>
<xs:element name="X509IssuerSerial" type="ds:X509IssuerSerialType"/>
<xs:element name="X509SKI" type="xs:base64Binary"/>
<xs:element name="X509SubjectName" type="xs:string"/>
<xs:element name="X509Certificate" type="xs:base64Binary"/>
<xs:element name="X509CRL" type="xs:base64Binary"/>
<xs:any namespace="##other" processContents="lax"/>
</xs:choice>
</xs:sequence>
</xs:complexType>
<xs:complexType name="X509IssuerSerialType">
<xs:sequence>
<xs:element name="X509IssuerName" type="xs:string"/>
<xs:element name="X509SerialNumber" type="xs:integer"/>
</xs:sequence>
</xs:complexType>


<xs:element name="PGPData" type="ds:PGPDataType"/>
<xs:complexType name="PGPDataType">
<xs:choice>
<xs:sequence>
<xs:element name="PGPKeyID" type="xs:base64Binary"/>
<xs:element name="PGPKeyPacket" type="xs:base64Binary" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:sequence>
<xs:element name="PGPKeyPacket" type="xs:base64Binary"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
</xs:choice>
</xs:complexType>


<xs:element name="SPKIData" type="ds:SPKIDataType"/>
<xs:complexType name="SPKIDataType">
<xs:sequence maxOccurs="unbounded">
<xs:element name="SPKISexp" type="xs:base64Binary"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0"/>
</xs:sequence>
</xs:complexType>



<xs:element name="Object" type="ds:ObjectType"/>
<xs:complexType name="ObjectType" mixed="true">
<xs:sequence minOccurs="0" maxOccurs="unbounded">
<xs:any namespace="##any" processContents="lax"/>
</xs:sequence>
<xs:attribute name="Id" type="xs:ID" use="optional"/>
<xs:attribute name="MimeType" type="xs:string" use="optional"/> 
<xs:attribute name="Encoding" type="xs:anyURI" use="optional"/>
</xs:complexType>
<xs:element name="Manifest" type="ds:ManifestType"/>
<xs:complexType name="ManifestType">
<xs:sequence>
<xs:element ref="ds:Reference" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="Id" type="xs:ID" use="optional"/>
</xs:complexType>
<xs:element name="SignatureProperties" type="ds:SignaturePropertiesType"/>
<xs:complexType name="SignaturePropertiesType">
<xs:sequence>
<xs:element ref="ds:SignatureProperty" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="Id" type="xs:ID" use="optional"/>
</xs:complexType>
<xs:element name="SignatureProperty" type="ds:SignaturePropertyType"/>
<xs:complexType name="SignaturePropertyType" mixed="true">
<xs:choice maxOccurs="unbounded">
<xs:any namespace="##other" processContents="lax"/>

</xs:choice>
<xs:attribute name="Target" type="xs:anyURI" use="required"/>
<xs:attribute name="Id" type="xs:ID" use="optional"/>
</xs:complexType>


<xs:simpleType name="HMACOutputLengthType">
<xs:restriction base="xs:integer"/>
</xs:simpleType>

<xs:element name="DSAKeyValue" type="ds:DSAKeyValueType"/>
<xs:complexType name="DSAKeyValueType">
<xs:sequence>
<xs:sequence minOccurs="0">
<xs:element name="P" type="ds:CryptoBinary"/>
<xs:element name="Q" type="ds:CryptoBinary"/>
</xs:sequence>
<xs:element name="G" type="ds:CryptoBinary" minOccurs="0"/>
<xs:element name="Y" type="ds:CryptoBinary"/>
<xs:element name="J" type="ds:CryptoBinary" minOccurs="0"/>
<xs:sequence minOccurs="0">
<xs:element name="Seed" type="ds:CryptoBinary"/>
<xs:element name="PgenCounter" type="ds:CryptoBinary"/>
</xs:sequence>
</xs:sequence>
</xs:complexType>
<xs:element name="RSAKeyValue" type="ds:RSAKeyValueType"/>
<xs:complexType name="RSAKeyValueType">
<xs:sequence>
<xs:element name="Modulus" type="ds:CryptoBinary"/>
<xs:element name="Exponent" type="ds:CryptoBinary"/>
</xs:sequence>
</xs:complexType>


</xs:schema>
===============================================================================
Code for registering the xml-schema
begin
dbms_xmlschema.deleteSchema('http://xmlns.oracle.com/xdb/schemas/DNTSB/www.sporfori.fo/schemas/www.w3.org/TR/xmldsig-core/xmldsig-core-schema.xsd',
dbms_xmlschema.DELETE_CASCADE_FORCE);
end;
begin
DBMS_XMLSCHEMA.REGISTERURI(
schemaurl => 'http://www.sporfori.fo/schemas/www.w3.org/TR/xmldsig-core/xmldsig-core-schema.xsd',
schemadocuri => 'http://www.sporfori.fo/schemas/www.w3.org/TR/xmldsig-core/xmldsig-core-schema.xsd',
local => TRUE,
gentypes => TRUE,
genbean => FALSE,
gentables => TRUE,
force => FALSE,
owner => 'DNTSB',
options => 0);
end;
Test program
-- Created on 17-07-2006 by EEJ
declare
XML_TEXT3 CLOB := '<Object xmlns="http://www.w3.org/2000/09/xmldsig#">
                              <SignatureProperties>
                                   <SignatureProperty Target="">
                                        <Timestamp xmlns="http://www.sporfori.fo/schemas/dnts/general/2006/11/14">2007-05-10T12:00:00-05:00</Timestamp>
                                   </SignatureProperty>
                              </SignatureProperties>
                         </Object>';
xmldoc xmltype;
begin
xmldoc := xmltype(xml_text3);
insert into signaturetable
(xml_document, ts)
values
(xmldoc, current_timestamp);
end;
Platform information
Operating system:
-bash-3.00$ uname -a
SunOS dntsdb 5.10 Generic_125101-09 i86pc i386 i86pc
SQLPlus:
SQL*Plus: Release 10.2.0.3.0 - Production on Fri Aug 17 00:15:13 2007
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
Enter password:
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning and Data Mining options
Kind Regards,
Eyðun

You should report this in a service request on http://metalink.oracle.com.
It is a shame that you put all the effort here to describe your problem, but on the other hand you can now also copy & paste the question to Oracle Support.
Because you are using 10.2.0.3; I am guessing that you have a valid service contract...

Id and name attributes on xsd elements

id, and name attributes on elements do not have a defined length, correct?
We are shredding an xml document into storage, currently we assign 255 characters for the field that will persist the values, since the id/name fields can be longer than this is there a best practice hat is recommended for xml authors not to create ids, and names with a long string.
I am working in a specialization of xml called XBRL,
Neil

Per the W3C standards, as I read them, you are correct. There is no limit on how long the attribute name (http://www.w3.org/TR/2008/REC-xml-20081126/#attdecls) can be. Follow the Name link on that page and you'll see a Name is defined as NameStartChar (NameChar)*, which is unbounded in length.
What various tools, including Oracle implement, for max name lengths is not known to me but your 255 seems more than reasonable. The best practice in terms of node name length depends upon who created the schema and what pattern they followed.
For example, this ISO standard
ISO/IEC 11179-5:2005, Information technology — Metadata registries (MDR) — Part 5: Naming and identification principles. Available from
http://standards.iso.org/ittf/PubliclyAvailableStandards/c035347_ISO_IEC_11179-5_2005(E).zip.
is used by NIEM but neither it nor additional NIEM restrictions put a max length on node names.
I've played around some with XBRL too and while I've seen a few long ones, I don't think they were over 50 characters so 255 would be more than enough. You could play around with all the .xsd schemas they have and look to see what the longest node name is and then set your length just over that but 255 is more than plenty in my opinion.

Looping Over the Collection elements in the BPEL

Hi Everybody,
Note:It appears this thread long paragraph but those are schems structures only.I am giving them to give full depth of my req.
1) First requirement :I have requirement wherein I have to retrieve the Data from Database adapter and modify it according to my requirements like below.
1) Input data from Database Adapter example: (Initial Schema)
<select_arrid_collection xmlns="http://xmlns.oracle.com/pcbpel/adapter/db/Select_Arrid">
<select_arrid>
<arr_id>arr1</arr_id>
</select_arrid>
<select_arrid>
<arr_id>arr2</arr_id>
</select_arrid>
<select_arrid>
<arr_id>arr1</arr_id>
</select_arrid>
<select_arrid>
<arr_id>arr2</arr_id>
</select_arrid>
</select_arrid_collection>
2) I am modifying to get the collection objects based on element same arr_id(If it is arr1,I have to get the all the elements related arr1 into one of the collection Object that is select_arrid_collection.Likewise for any arr_id ,it has to group them into a select_arrid_collection element) like below:
Modified schema:
<root xmlns="http://xmlns.oracle.com/pcbpel/adapter/db/Select_Arrid">
<select_arrid_collection>
<select_arrid>
<arr_id>arr1</arr_id>
</select_arrid>
<select_arrid>
<arr_id>arr1</arr_id>
</select_arrid>
</select_arrid_collection>
<select_arrid_collection>
<select_arrid>
<arr_id>arr2</arr_id>
</select_arrid>
<select_arrid>
<arr_id>arr2</arr_id>
</select_arrid>
</select_arrid_collection>
</root>
Note: root element is added in the schema that is why this modified xml has different namespace
I am using below xsl file to get the above schema to get the solution for first requirement:
<xsl:stylesheet version="2.0" xmlns:ns1="http://www.example.org" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/">
<ns1:root>
<xsl:for-each-group select="*/ns1:Select_Arrid" group-by="ns1:Arr_id">
<xsl:sort select="current-grouping-key()">
<ns1:select_arrid_collection>
<xsl:copy-of select="current-group()">
<xsl:apply-templates/>
</xsl:copy-of>
</ns1:select_arrid_collection>
</xsl:sort>
</xsl:for-each-group>
</ns1:root>
</xsl:template>
</xsl:stylesheet>
2) Second requirement:
After getting the multiple collection elements(select_arrid_collection),I want to loop through each select_arrid_collection element and map the elements in that to another service schema.
I have created the xsd like above required modified schema and assign it to a variable(element type) which takes same modified schema so that I can have a variable on which I want to apply while activity.
But I want to have the idea how to loop through the multiple collection elements(select_arrid_collection) and map the elements of each select_arrid_collection to a input variable of a service.
My problem is I have to get each select_arrid_collection element in the schema where root element is 'root'.I am not able to trace how to get the no of select_arrid_collection elements so that I can loop through in the transofrm activity.
Can anybody help me put in this?
Edited by: 899283 on Jan 9, 2013 1:48 AM
Edited by: 899283 on Jan 9, 2013 1:52 AM
Edited by: 899283 on Jan 9, 2013 1:53 AM
Edited by: 899283 on Jan 9, 2013 2:02 AM

Can you please let us know if there are some helpful/correct answers in your previous questions and follow the forum etiquette? https://forums.oracle.com/forums/ann.jspa?annID=893
Where Can I create Staging table in SOA server?
regarding sending response at a time to a WSDL in BPEL
Do we need nodemanager for SOA server installation?
I want to set the time for polling of DB Adapter

ORA-19046 with valid xsd-file (on 11.2.0.2)

Hello Experts,
I got an xml-file and had to import it into some relational tables. The xsd-files are given.
I tried: creating ressources for the xsd-files - works; register schema's -> not possible, because of ORA-19046.
In XMLSpy validating all xsd-files (a total of seven files) is possible - not error found.
Are there any ideas, how to import the data to some tables? (I don't really need the xml-file in the database)
Thanky for any help!
Frank

XSD-Upload - Part 1/7
There are seven files - I will post the ORIGINAL Files without oracle annotations:
vda_root_V1.2.xsd
-> vda_header_V1.2.xsd
-> vda_body_V1.2.xsd
-> ehd_root_V1.40.xsd
-> keytabs_V1.40.xsd
-> ehd_header_V1.40.xsd
-> datentypen_V1.40.xsd
My Probelm-baby ist datentypen_V1.40.xsd
<?xml version="1.0" encoding="ISO-8859-1"?>

<xs:schema xmlns="urn:ehd/001" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:ehd/001" elementFormDefault="qualified" attributeFormDefault="unqualified">
     
     <xs:element name="id" type="id_typ">
          <xs:annotation>
               <xs:documentation>enthält eindeutige Instanz-ID</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="id_typ">
          <xs:attribute name="EX" type="xs:string" use="optional"/>
          <xs:attribute name="RT" type="xs:string" use="required"/>
          <xs:attribute name="RTV" type="xs:string" use="optional"/>
     </xs:complexType>
     <xs:complexType name="doc_id_typ">
          <xs:annotation>
               <xs:documentation>ist dem id_typ identisch</xs:documentation>
          </xs:annotation>
          <xs:complexContent>
               <xs:extension base="id_typ"/>
          </xs:complexContent>
     </xs:complexType>
     <xs:element name="set_id" type="id_typ">
          <xs:annotation>
               <xs:documentation>enthält eindeutige Instanz-ID, die über alle Versionen und zusammgengehörende Dokumente konstant bleibt</xs:documentation>
          </xs:annotation>
     </xs:element>
     
     
     <xs:element name="version_nbr" type="version_nbr_typ">
          <xs:annotation>
               <xs:documentation>Versionnummer des XML-Dokuments</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="version_nbr_typ">
          <xs:attribute name="V" type="xs:nonNegativeInteger" use="required"/>
     </xs:complexType>
     
     <xs:element name="document_relationship" type="document_relationship_typ">
          <xs:annotation>
               <xs:documentation>Beziehung zu anderen Dokumenten ("Anhang", "Ersatz")</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="document_relationship_typ">
          <xs:sequence>
               <xs:element name="document_relationship.type_cd" type="document_relationship.type_cd_typ">
                    <xs:annotation>
                         <xs:documentation>Art der Dokumentbeziehung ("Anhang", "Ersatz")</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element ref="related_document"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="document_relationship.type_cd_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ">
                    <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.101"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     
     <xs:element name="related_document" type="related_document_typ">
          <xs:annotation>
               <xs:documentation>Verweis auf das Original/Anhang-Dokument</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="related_document_typ">
          <xs:sequence>
               <xs:element ref="id"/>
               <xs:element ref="set_id" minOccurs="0"/>
               <xs:element ref="version_nbr" minOccurs="0"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     
     <xs:element name="document_type_cd" type="document_type_cd_typ">
          <xs:annotation>
               <xs:documentation>Dokumenttype Code</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="document_type_cd_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ">
                    <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.100"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     
     
     <xs:element name="service_tmr" type="service_tmr_typ">
          <xs:annotation>
               <xs:documentation>Gültigkeitszeitraum (date..date)</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="service_tmr_typ">
          <xs:complexContent>
               <xs:extension base="v_zeitraum_typ"/>
          </xs:complexContent>
     </xs:complexType>
     
     <xs:element name="origination_dttm" type="origination_dttm_typ">
          <xs:annotation>
               <xs:documentation>Erstellungsdatum</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="origination_dttm_typ">
          <xs:complexContent>
               <xs:extension base="v_date_typ"/>
          </xs:complexContent>
     </xs:complexType>
     
     
     <xs:element name="intended_recipient" type="intended_recipient_typ">
          <xs:annotation>
               <xs:documentation>Empfänger / Zielgruppe der Daten</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="intended_recipient_typ">
          <xs:sequence>
               <xs:element name="intended_recipient.type_cd" type="intended_recipient.type_cd_typ" minOccurs="0"/>
               <xs:element ref="function_cd" minOccurs="0"/>
               <xs:element ref="person" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="organization" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="intended_recipient.type_cd_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ">
                    <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.102"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     
     <xs:element name="originator" type="originator_typ">
          <xs:annotation>
               <xs:documentation>Ersteller, Urheber des Dokuments / der Daten</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="originator_typ">
          <xs:sequence>
               <xs:element name="originator.type_cd" type="originator.type_cd_typ" minOccurs="0"/>
               <xs:element ref="function_cd" minOccurs="0"/>
               <xs:element ref="participation_tmr" minOccurs="0"/>
               <xs:element ref="person" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="organization" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="originator.type_cd_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ">
                    <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.103"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     
     <xs:element name="provider" type="provider_typ">
          <xs:annotation>
               <xs:documentation>Sender, Lieferant des Dokuments (kann gleichzeitig der Urheber sein)</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="provider_typ">
          <xs:sequence>
               <xs:element name="provider.type_cd" type="provider.type_cd_typ" minOccurs="0"/>
               <xs:element ref="function_cd" minOccurs="0"/>
               <xs:element ref="participation_tmr" minOccurs="0"/>
               <xs:element ref="person" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="organization" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="provider.type_cd_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ">
                    <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.104"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     <xs:element name="function_cd" type="function_cd_typ">
          <xs:annotation>
               <xs:documentation>Funktion/Rolle der Person/Organisation</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="function_cd_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ">
                    <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.105"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     <xs:element name="participation_tmr" type="v_zeitraum_typ">
          <xs:annotation>
               <xs:documentation>Zeitraum/Zeitpunkt der Teilnahme</xs:documentation>
          </xs:annotation>
     </xs:element>
     
     <xs:element name="person" type="person_typ">
          <xs:annotation>
               <xs:documentation>Person-Daten</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:element name="group" type="group_typ">
          <xs:annotation>
               <xs:documentation>zugehörende Gruppe, Ausprägung (z.B. Augenarzt)</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="group_typ">
          <xs:complexContent>
               <xs:extension base="v_s_string_typ">
                    <xs:sequence>
                         <xs:element ref="group.type_cd"/>
                    </xs:sequence>
               </xs:extension>
          </xs:complexContent>
     </xs:complexType>
     <xs:element name="group.type_cd" type="v_s_string_typ">
          <xs:annotation>
               <xs:documentation>Gruppebezeichnung (z.B. Facharztagruppe)</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="person_typ">
          <xs:sequence>
               <xs:element ref="id" minOccurs="0"/>
               <xs:element ref="person_name" minOccurs="0"/>
               <xs:element name="organization.nm" type="v_string_typ" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="addr" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="telecom" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:element name="telecom" type="v_string_typ">
          <xs:annotation>
               <xs:documentation>Telekomunnikation (tel,mail,fax,...)</xs:documentation>
          </xs:annotation>
     </xs:element>
     
     <xs:element name="person_name" type="person_name_typ">
          <xs:annotation>
               <xs:documentation>Name der Person</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="person_name_typ">
          <xs:sequence>
               <xs:element name="nm" type="person_name_nm_typ"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="person_name_nm_typ">
          <xs:choice minOccurs="0" maxOccurs="unbounded">
               <xs:element name="GIV" type="pnxp_string_typ">
                    <xs:annotation>
                         <xs:documentation>Vorname</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="MID" type="pnxp_string_typ">
                    <xs:annotation>
                         <xs:documentation>Zusatzname</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="FAM" type="pnxp_string_typ">
                    <xs:annotation>
                         <xs:documentation>Nachname</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="PFX" type="pnxp_string_typ">
                    <xs:annotation>
                         <xs:documentation>Titel (Dr.)</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="SFX" type="pnxp_string_typ">
                    <xs:annotation>
                         <xs:documentation>Namenzusatz</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="DEL" type="pnxp_string_typ">
                    <xs:annotation>
                         <xs:documentation>Trennzeichen</xs:documentation>
                    </xs:annotation>
               </xs:element>
          </xs:choice>
     </xs:complexType>
     
     <xs:element name="organization" type="organization_typ">
          <xs:annotation>
               <xs:documentation>Organisations-Daten</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="organization_typ">
          <xs:sequence>
               <xs:element ref="id" minOccurs="0"/>
               <xs:element name="organization.nm" type="v_string_typ" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="addr" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="telecom" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     
     <xs:element name="addr" type="addr_typ">
          <xs:annotation>
               <xs:documentation>Adresse</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="addr_typ">
          <xs:choice minOccurs="0" maxOccurs="unbounded">
               <xs:element name="STR" type="v_string_typ"/>
               <xs:element name="HNR" type="v_string_typ"/>
               <xs:element name="POB" type="v_string_typ"/>
               <xs:element name="ZIP" type="v_string_typ"/>
               <xs:element name="CTY" type="v_string_typ"/>
               <xs:element name="STA" type="v_string_typ"/>
               <xs:element name="CNT" type="v_string_typ"/>
               <xs:element name="ADL" type="v_string_typ"/>
          </xs:choice>
     </xs:complexType>
     
     <xs:element name="patient" type="patient_typ">
          <xs:annotation>
               <xs:appinfo>Patient-Informationen</xs:appinfo>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="patient_typ">
          <xs:sequence>
               <xs:element name="patient.type_cd" type="v_s_string_typ" minOccurs="0"/>
               <xs:element ref="person"/>
               <xs:element name="birth_dttm" type="v_date_typ" minOccurs="0"/>
               <xs:element name="administrative_gender_cd" type="v_s_string_typ" minOccurs="0"/>
               <xs:element ref="local_header" minOccurs="0"/>
          </xs:sequence>
     </xs:complexType>
     
     <xs:element name="local_header" type="local_header-cont.model">
          <xs:annotation>
               <xs:documentation>Element für weitere, datenartspezifische, Metainformationen</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="local_header-cont.model" mixed="true">
          <xs:choice minOccurs="0" maxOccurs="unbounded">
               <xs:any processContents="skip" minOccurs="0" maxOccurs="unbounded"/>
          </xs:choice>
          <xs:attribute name="ignore" type="ignore_typ" default="markup"/>
          <xs:attribute name="descriptor" type="xs:string"/>
          <xs:attribute name="render" type="xs:string"/>
     </xs:complexType>
     
     
     <xs:complexType name="v_string_typ">
          <xs:attribute name="V" type="xs:string" use="required"/>
     </xs:complexType>
     
     <xs:element name="TRANSLTN" type="transltn_typ">
          <xs:annotation>
               <xs:documentation>interne/alternative Kodes und Schlüsseltabellen</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="transltn_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ"/>
          </xs:complexContent>
     </xs:complexType>
     <xs:complexType name="v_s_string_typ">
          <xs:attribute name="V" type="xs:string" use="required"/>
          <xs:attribute name="DN" type="xs:string" use="optional"/>
          <xs:attribute name="S" type="xs:string" use="optional"/>
          <xs:attribute name="SN" type="xs:string" use="optional"/>
          <xs:attribute name="SV" type="xs:string" use="optional"/>
     </xs:complexType>
     
     <xs:complexType name="v_date_typ">
          <xs:attribute name="V" type="xs:date" use="required"/>
     </xs:complexType>
     
     <xs:complexType name="v_zeitraum_typ">
          <xs:annotation>
               <xs:documentation>Zeitraum: datum..datum</xs:documentation>
          </xs:annotation>
          <xs:attribute name="V" type="zeitraum_typ" use="required"/>
     </xs:complexType>
     
     <xs:complexType name="pnxp_string_typ">
          <xs:attribute name="V" type="xs:string" use="required"/>
          <xs:attribute name="QUAL" type="xs:NMTOKENS" use="optional"/>
     </xs:complexType>
     
     
     
     
     
     <xs:element name="interface" type="interface_typ">
          <xs:annotation>
               <xs:documentation>enthält Informationen über die Schnittstelle selbst</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="interface_typ">
          <xs:sequence>
               <xs:element name="id" type="interface_id_typ"/>
               <xs:element name="interface.nm" type="interface_nm_typ"/>
               <xs:element name="version" type="interface_version_typ"/>
               <xs:element ref="originator" minOccurs="0" maxOccurs="unbounded"/>
               <xs:element name="description" type="description_typ" minOccurs="0"/>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="interface_id_typ">
          <xs:complexContent>
               <xs:restriction base="id_typ">
                    <xs:attribute name="RT" type="xs:string" use="required" fixed="1.2.276.0.76.5.109"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     
     <xs:complexType name="interface_nm_typ">
          <xs:annotation>
               <xs:documentation>Bezeichnung der Schnittstelle</xs:documentation>
          </xs:annotation>
          <xs:complexContent>
               <xs:extension base="v_string_typ"/>
          </xs:complexContent>
     </xs:complexType>
     
     <xs:complexType name="interface_version_typ">
          <xs:annotation>
               <xs:documentation>Version der Schnittstellenbeschreibung</xs:documentation>
          </xs:annotation>
          <xs:complexContent>
               <xs:extension base="v_string_typ"/>
          </xs:complexContent>
     </xs:complexType>
     
     <xs:complexType name="description_typ">
          <xs:annotation>
               <xs:documentation>Kurzbeschreibung oder Link auf die WebSite mit der Schnittstellenbeschreibung</xs:documentation>
          </xs:annotation>
          <xs:attribute name="V" type="xs:string" use="required"/>
          <xs:attribute name="URL" type="xs:anyURI" use="optional"/>
     </xs:complexType>
     
     <xs:element name="scope" type="scope_typ">
          <xs:annotation>
               <xs:documentation>Geltungsbereich</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="scope_typ">
          <xs:sequence>
               <xs:element name="id" type="scope_id_typ" maxOccurs="unbounded"/>
               <xs:element name="scope.type_cd" type="scope.type_cd_typ">
                    <xs:annotation>
                         <xs:documentation>z.B. 1=KV-Geltungsbereich</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="scope.nm" type="v_string_typ" minOccurs="0" maxOccurs="unbounded">
                    <xs:annotation>
                         <xs:documentation>Name des Bereichs zu dem id-Element (z.B. KV-Nord)</xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element ref="local_header" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="scope_id_typ">
          <xs:complexContent>
               <xs:restriction base="id_typ">
                    <xs:attribute name="RT" type="xs:string" use="required" fixed="1.2.276.0.76.5.106"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     <xs:complexType name="scope.type_cd_typ">
          <xs:complexContent>
               <xs:restriction base="v_s_string_typ">
                    <xs:attribute name="S" type="xs:string" use="optional" fixed="1.2.276.0.76.5.107"/>
               </xs:restriction>
          </xs:complexContent>
     </xs:complexType>
     
     <xs:element name="state" type="state_typ">
          <xs:annotation>
               <xs:documentation>Bearbeitungszustand</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="state_typ">
          <xs:complexContent>
               <xs:extension base="v_s_string_typ"/>
          </xs:complexContent>
     </xs:complexType>
     
     
     
     <xs:simpleType name="null.code.set">
          <xs:annotation>
               <xs:documentation>Ausprägungen für NULL-Attribut</xs:documentation>
          </xs:annotation>
          <xs:restriction base="xs:string">
               <xs:enumeration value="NI"/>
               <xs:enumeration value="NA"/>
               <xs:enumeration value="UNK"/>
               <xs:enumeration value="NASK"/>
               <xs:enumeration value="ASKU"/>
               <xs:enumeration value="NAV"/>
               <xs:enumeration value="OTH"/>
               <xs:enumeration value="PINF"/>
               <xs:enumeration value="NINF"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="guid_typ">
          <xs:annotation>
               <xs:documentation>Typ für einen Global Unique Identifier</xs:documentation>
          </xs:annotation>
          <xs:restriction base="xs:string">
               <xs:pattern value="[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12}"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="zeitraum_typ">
          <xs:annotation>
               <xs:documentation>Zeitraum datum..datum</xs:documentation>
          </xs:annotation>
          <xs:restriction base="xs:string">
               <xs:pattern value="([1,2][0-9]{3}-[0-1][0-9]-(([0-2][0-9])|([3][0-1]))\.\.[1,2][0-9]{3}-[0-1][0-9]-(([0-2][0-9])|([3][0-1])))|([1,2][0-9]{3}-[0-1][0-9]-(([0-2][0-9])|([3][0-1])))|(\.\.[1,2][0-9]{3}-[0-1][0-9]-(([0-2][0-9])|([3][0-1])))|([1,2][0-9]{3}-[0-1][0-9]-(([0-2][0-9])|([3][0-1]))\.\.)"/>
          </xs:restriction>
     </xs:simpleType>
     <xs:simpleType name="ignore_typ">
          <xs:restriction base="xs:string">
               <xs:enumeration value="all"/>
               <xs:enumeration value="markup"/>
          </xs:restriction>
     </xs:simpleType>
</xs:schema>

Assign ora:getCompositeInstanceId() in the xsd element

Similar Messages

Maybe you are looking for