Import external definition to message type

Hello
I have scenario file to IDOC.
I don’t know way in this time I not successful to import my external definition to message type.
Any idea?
Elad

Hello again,
I try to solve mapping problem
Hello again,
I have scenario from file(xml) to IDOC.
In outbound side I have XSD file and I imported this file and I use with him in outbound interface.
In inbound side I have IDOC.
I have mapping problem issue.
When I test this mapping I have this error message:
Cannot produce target element /ZORD_CREATE. Check xml instance is valid for source XSD and target-field mapping fulfills requirements of target XSD
Any idea?
Elad

Similar Messages

  • Possible? Using External Definitions for data type/message type definitions

    Hi all,
    i want to use external definitons in my own data type definitions. Is that possible? And if yes, how?
    I imported many definitions via a mass import. Now I also want to use these definitions for further interfaces (than the imported ones). The most convenient would be of course to just use them as a custom created type. Can I somehow "convert" an external definition to a data type/message type?
    KR
    Felix

    Hello Felix,
          The External defination which you has been imported that cant use in DT and MT but yeah you can use this in Service interface.
    you cant modify that External defination if you want to do that then 1st of all modify it and then reimport it as an another external defination.
    and creating service interface with this ED you can use it in your message mapping .
    i hope this will help to you to clear your doubt.
    Monica

  • Definition of Message Type and Transaction Type from the Implementation per

    My assumption is that both, Notification Type and Message Types are same.
    <b>Is the above assumption right?</b>
    In Sol Man 4.0, the notification types required are
    1)     ABSC  2) SLF1 3) TASK
    <b>Are there any other notification types required for Sol Man 4.0?</b>
    The main transaction types required in Sol Man 4.0 are
    SLFI, SLFT and SLFN
    <b>What is the significance of External Number range and Internal Number range used in the transaction type?</b>

    Hi
    1 > A data type</i> in a programming language is a set of data with values having predefined characteristics. Examples of data types are: integer, floating point unit number, character, string, and pointer.
    The characteristic of columns and variables that defines what types of data values they can store. Examples include character, floating point and integer
    Check out the details:
    http://en.wikipedia.org/wiki/Data_type
    A message type comprises a data type that describes the structure of a message. At the following points in SAP Exchange Infrastructure you can refer to the message to be exchanged at runtime by using the message type:
    details:
    http://help.sap.com/saphelp_nw04/helpdata/en/2d/c0633c3a892251e10000000a114084/content.htm
    2) Regarding the difference between XI 3.0 and PI 7.0, this threads will clear your doubts:
    difference between XI 3.0 and P.I 7.0
    Difference/ changes from XI 3.0 to PI 7.0
    Regard's
    Chetan Ahuja

  • Messages not adviced in extern definition after import wsdl-file from WAS

    Hi friends,
    after importing the three wsld-files in repository (extern definitions) the messages are not adviced. The referendes to the files are fine, because the name is shown at the tab externe...
    But i´m not shure wheather i tool the right link ant Web Service Navigator. It is right to download the default SAP WSDL Files or the default one? Because in the SAP WSDL-files there will be an exception during import in XI repository (tag sap:useFeatur). What is the problem that the messages are not shown on the tab messages in externe definitions?
    Thanks in advance,
    Frank

    I've the same problem. Here is my WSDL:
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions targetNamespace="http://blablabla.de:8080/jboss-net/services/MyServices" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://blablabla.de:8080/jboss-net/services/MyServices" xmlns:intf="http://blablabla.de:8080/jboss-net/services/MyServices" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns1="blablabla.de" xmlns:tns2="http://net.jboss.org/jmx" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
         <wsdl:types>
              <schema targetNamespace="blablabla.de" xmlns="http://www.w3.org/2001/XMLSchema">
                   <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
                   <complexType name="MSOBean">
                        <sequence>
                             <element name="installationName" nillable="true" type="xsd:string"/>
                             <element name="requestId" nillable="true" type="xsd:string"/>
                             <element name="returnCode" type="xsd:int"/>
                             <element name="returnMessage" nillable="true" type="xsd:string"/>
                        </sequence>
                   </complexType>
                   <complexType name="MSIBean">
                        <sequence>
                             <element name="password" nillable="true" type="xsd:string"/>
                             <element name="project" nillable="true" type="xsd:string"/>
                             <element name="requestId" nillable="true" type="xsd:string"/>
                             <element name="userId" nillable="true" type="xsd:string"/>
                        </sequence>
                   </complexType>
              </schema>
         </wsdl:types>
         <wsdl:message name="actualizeRequest">
              <wsdl:part name="inData" type="tns1:MSIBean"/>
         </wsdl:message>
         <wsdl:message name="actualizeResponse">
              <wsdl:part name="actualizeReturn" type="tns1:MSOBean"/>
         </wsdl:message>
         <wsdl:portType name="MSService">
              <wsdl:operation name="actualize" parameterOrder="inData">
                   <wsdl:input message="impl:actualizeRequest" name="actualizeRequest"/>
                   <wsdl:output message="impl:actualizeResponse" name="actualizeResponse"/>
              </wsdl:operation>
         </wsdl:portType>
         <wsdl:binding name="MyServicesSoapBinding" type="impl:MSService">
              <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
              <wsdl:operation name="actualize">
                   <wsdlsoap:operation soapAction=""/>
                   <wsdl:input name="actualizeRequest">
                        <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://blablabla.de" use="encoded"/>
                   </wsdl:input>
                   <wsdl:output name="actualizeResponse">
                        <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://blablabla.de:8080/jboss-net/services/MyServices" use="encoded"/>
                   </wsdl:output>
              </wsdl:operation>
         </wsdl:binding>
         <wsdl:service name="MSServiceService">
              <wsdl:port binding="impl:MyServicesSoapBinding" name="MyServices">
                   <wsdlsoap:address location="http://blablabla.de:8080/jboss-net/services/MyServices"/>
              </wsdl:port>
         </wsdl:service>
    </wsdl:definitions>
    No Idea.

  • PI does not keep sequence of XSD for external definition

    Hi,
    currently I face following problem. I have an XSD which decribes a MSCONS market message that contains following sequence:
         <xs:complexType name="MSCONS">
              <xs:sequence>
                   <xs:element name="UNH" type="UNH"/>
                   <xs:element name="BGM" type="BGM"/>
                   <xs:element name="DTM" type="DTM"/>
                   <xs:element name="NAD" type="NAD" minOccurs="2" maxOccurs="2"/>
                   <xs:element name="UNS" type="UNS"/>
                   <xs:element name="NAD" type="NAD" maxOccurs="unbounded"/>
                   <xs:element name="CNT" type="CNT" minOccurs="0" maxOccurs="99"/>
                   <xs:element name="UNT" type="UNT"/>
              </xs:sequence>
         </xs:complexType>
    There are 2 NAD elements, followed by an UNS element, followed by an NAD element again. When I upload that XSD to PI as an external definition, the message is described as:
    MSCONS     Message                         
    -> MSCONS     Element     MSCONS     1               Metered services consumption report message
    -> -> UNH     Element     UNH     1               
    -> -> BGM     Element     BGM     1               
    -> -> DTM     Element     DTM     1               
    -> -> NAD     Element     NAD     1..unbounded               
    -> -> UNS     Element     UNS     1               
    -> -> CNT     Element     CNT     0..99               
    -> -> UNT     Element     UNT     1     
    All the NAD elements are summarized before UNS element. After mapping I will get an message which is not valid to XSD, because sequence is not correct.
    Does anyone knows a solution/workaround for that issue. Would appreciate you help.
    Thank you and Best Regards,
    Nico

    > All the NAD elements are summarized before UNS element. After mapping I will get an message which is not valid to XSD, because sequence is not correct.
    >
    > Does anyone knows a solution/workaround for that issue. Would appreciate you help.
    No. There is no way. The way how graphical mapping works internally makes it impossible to achieve your requirement.
    As work around use two different nodes NDA and NAD1 and rename it with a simple Java mapping as second mapping step.

  • Problem Loading WSDL in External Definition

    Hello people,
    i'm having some problems When i'm Importing the WSDL in external definitions, the Messages are not being Recognized, it doesnt load the message structures, if i try in any other program that uses the WSDL like SoapUI, the wsdl works fine.
    Here is the WSDL links
    http://siatepqa.suseso.cl:8888/Siatep/WSToken?wsdl
    http://siatepqa.suseso.cl:8888/Siatep/WSIngreso?wsdl
    http://siatep.suseso.cl:8888/SusesoSiatep/WSToken?wsdl
    http://siatep.suseso.cl:8888/SusesoSiatep/WSIngreso?wsdl
    anyone can help?

    Hi,
    http://siatepqa.suseso.cl:8888/Siatep/WSToken?wsdl
    I checked the WSDL from the above link. The issue that I noticed is that you are importing the schema structure in your above WSDL. PI is unable to recognize the external reference. SOAPUI (or similar tool) will recognize the external reference.
    Best option is that you should re-modify your above WSDL and provide the schema in this WSDL itself. It should then work just fine.
    Hope this helps.
    Regards,
    Neetesh

  • External Definitions under SAP Basis 7.10

    Hi All,
    We are trying with Directory API Developement using the following blog,
             https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/11655. [original link is broken] [original link is broken] [original link is broken]
    As per the blog we need to import External definition from SAP Basis software component(under the namespace http://sap.com/xi/XI/System).But we are not able to see any external definitions.
    Could you please guide us what are the extra setting needed to be done to get those external definitions.
    Thanks and Regards
    Senthil.

    Hi Senthil,
    from that blog:
    Java proxies can be generated in NetWeaver Developer Studio (NWDS) from:
    1. Web service URL from the web service runtime of the JEE server, by using the "Web Services Navigator"
    2. External definitions in the "SAP Basis 7.00" SWCV
    You will find the external definitions in Basis Component 7.00, but not in 7.10. Just load the 7.00 into your ESR.
    Regards,
    Udo

  • External definition import WSDL complex type problem

    Hi,
    i have created a webservice using apache axis and created an external definition for the service. You can see the respective WSDL recognized by XI below. The service takes an array of adresses. Unfortunately, when I want to define the message mapping, theres only the array but not the address attributes. What would be a proper definition of the service?
    Cheers,
    Heiko
    ===================================================
    1. WSDL from external defintion:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://localhost:8080/axis/services/AdressService">
         <wsdl:types>
              <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://localhost:8080/axis/services/AdressService" targetNamespace="http://localhost:8080/axis/services/AdressService">
                   <xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
                   <xsd:complexType xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" name="AddressDto">
                        <xsd:sequence>
                             <xsd:element name="ID" type="xsd:string" nillable="true" />
                             <xsd:element name="name" type="xsd:string" nillable="true" />
                             <xsd:element name="strasse" type="xsd:string" nillable="true" />
                             <xsd:element name="ort" type="xsd:string" nillable="true" />
                        </xsd:sequence>
                   </xsd:complexType>
                   <xsd:complexType xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" name="ArrayOfAddressDto">
                        <xsd:complexContent>
                             <xsd:restriction base="soapenc:Array">
                                  <xsd:attribute ref="soapenc:arrayType" wsdl:arrayType="impl:AddressDto[]" />
                             </xsd:restriction>
                        </xsd:complexContent>
                   </xsd:complexType>
              </xsd:schema>
         </wsdl:types>
         <wsdl:message name="writeAddressDataResponse" />
         <wsdl:message name="writeAddressDataRequest">
              <wsdl:part xmlns:generateduniqueprefix3="http://localhost:8080/axis/services/AdressService" name="addresses" type="generateduniqueprefix3:ArrayOfAddressDto" />
         </wsdl:message>
    </wsdl:definitions>
    2. XSD extracted from WSDL:
    <?xml version="1.0" encoding="UTF-8"?>
    <xsd:schema targetNamespace="http://localhost:8080/axis/services/AdressService" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://localhost:8080/axis/services/AdressService">
      <xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
      <xsd:element name="addresses" type="ArrayOfAddressDto" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" />
      <xsd:complexType name="ArrayOfAddressDto" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
        <xsd:complexContent>
          <xsd:restriction base="soapenc:Array">
            <xsd:attribute ref="soapenc:arrayType" wsdl:arrayType="impl:AddressDto[]" xmlns:xsd="http://www.w3.org/2001/XMLSchema" />
          </xsd:restriction>
        </xsd:complexContent>
      </xsd:complexType>
    </xsd:schema>
    ??? Where are the atributes of the address here ???

    Hi Heiko,
    XI does not support the use of soapenc:array. Please refer to http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement16556272 regarding the use of this construct.
    Greetings Stephan

  • "Messages" problem after importing .xsd file as external definition

    Hello,
    I received an .xsd file from a customer and need to import it as an "External Definition" in order to create the "Message Interface". The structure of the xsd looks like this:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:px="http://www.opentrans.org/XMLSchema/1.0" targetNamespace="http://www.opentrans.org/XMLSchema/1.0" elementFormDefault="qualified">
    <xsd:element name="ORDER">
    </xsd:element>
    <xsd:element name="ADDRESS">
    </xsd:element>
    <xsd:element name="ARTICLE_ID">
    </xsd:element>
    </xsd:schema>
    After importing and looking at the tab "Messages" I get numerous entries, for each <xsd:element> I get one message! But I basically only need one "Message" that holds my complete xsd-file.
    I tried inserting <xsd:element name="COMPLETEORDER"> right after the <xsd:schema>-Tag but that didn't work either. Somehow I need to sum up all the <xsd:elements>.
    Does anyone have an idea? Thank you very much!
    Peter

    Hello Prateek, Hello everyone,
    I now know what the problem is. I downloaded XMLspy and checked on the structure:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:px="http://www.opentrans.org/XMLSchema/1.0" targetNamespace="http://www.opentrans.org/XMLSchema/1.0" elementFormDefault="qualified">
    <xsd:element name="ORDER">
    </xsd:element>
    <xsd:element name="ADDRESS">
    </xsd:element>
    <xsd:element name="ARTICLE_ID">
    </xsd:element>
    <xsd:simpleType name="dtBOOLEAN">
    </xsd:simpleType>
    <xsd:simpleType name="dtCOUNTRIES">
    </xsd:simpleType>
    <xsd:element name="SUPPLIER_AID">
    </xsd:element>
    <xsd:simpleType name="typeSUPPLIER_AID">
    </xsd:simpleType>
    </xsd:schema>
    Between the long list of <xsd:element> tags there are some simpleTypes on the same
    level. Now if I insert
    <xsd:element name="COMPLETEORDER">
    <xsd:complexType>
    <xsd:sequence>
    on top, the <xsd:sequence> would be on the same level as the simpleTypes - which is not valid!
    But can I just move all the simpleTypes, e.g. into an <xsd:element>??
    That would be changing the customer's structure which I think is not a good thing!?
    Thank you again for your help! I really appreciate it!
    Best regards,
    Peter

  • External definitions import into Message mapping

    Hi,
    I have a DTD message in external definitions to be imported into the message mapping. But I am not able to choose the object in the mapping editor. It does not allow even if the message is a valid WSDL. The only time it allows to import into the message editor is when its an XSD.I am not sure why the external definitions in DTD or WSDL formats are not able to be imported or am I missing something??
    -Ken

    Hi,
      A conversion of the downloaded cXML DTD into XSD by using XMLSPY yields 3 XSD files. Using the initial XSD(which has the major fields) yields the same error(i.e cannot create messages or valid WSDL) in external definitions.
    I also tried using one of the standard xml's from the cXML site and the funny part was XMLSPY validated them without errors and while importing them directly into the mapping editor, XI throws an error "XML NOT WELL FORMED". Its so weird.
      Also is there a possibility to write a script to manipulate the payload message after passing through the adapters? For eg : Creating a script which will delete a valid tag in payload before it reaches the 3rd party. ...By adding the DOCTYPE in the prolog, the message would look like this :
    "<?xml...utf-8>
    <!DOCTYPE......'Cxml.org'>
    <?xml.....utf-8>
    <start tag></start tag>”
    Therefore some kind of a script that would remove the second <?xml tag on line 3>..
    This is just a round about thinking…
    Any ideas..

  • No messages under the 'Messages' tab for imported WSDL in External Definitions

    Dear All,
    I import this WSDL to the External Definitions but it is not showing any messages in the 'Messages' tab while WSDL clearly has message interfaces in it. Attached is the WSDL. You help is very much appreciated.
    Regards,
    Adil Khalil

    Hi, imported wsdl shouldn't have any import instruction.
    All import instruction should be changed to content of importing file.
    I see the code <xsd:import namespace="http://ouaf.oracle.com/"/> in your file.
    Hmm. but I imported you file and everything is fine
    Message was edited by: Mikhail Koshkin

  • Unable to see Messages in External Definitions

    I imported the WSDL below and created a Message Interface based on JobSubmitRequest but, when I come to map to it, all I see in the tree structure is node 'JobSubmitRequest' with elements 'parameter' and 'request_header'.
    I also cannot see any messages in External Definitions.
    Can anyone help with a solution?
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xoa="http://xoa.xpedite.com/2004/11/xoa" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://xoa.xpedite.com/2004/11/xoa">
         <types>
              <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://xoa.xpedite.com/2004/11/xoa" xmlns="http://xoa.xpedite.com/2004/11/xoa">
                   <!-- address type enum -->
                   <xs:simpleType name="AddressType">
                        <xs:restriction base="xs:string">
                             <xs:enumeration value="fax"/>
                             <xs:enumeration value="internet"/>
                             <xs:enumeration value="mbox"/>
                             <xs:enumeration value="x400"/>
                             <xs:enumeration value="telex"/>
                             <xs:enumeration value="cablegram"/>
                             <xs:enumeration value="mailgram"/>
                             <xs:enumeration value="ddd"/>
                             <xs:enumeration value="dedLine"/>
                             <xs:enumeration value="softswitch"/>
                             <xs:enumeration value="voice"/>
                             <xs:enumeration value="sms"/>
                             <xs:enumeration value="fod"/>
                             <xs:enumeration value="list"/>
                             <xs:enumeration value="smQuery"/>
                        </xs:restriction>
                   </xs:simpleType>
                   <!--includes for standalone validation
         <xs:include schemaLocation="StatusType.xsd"/>
         ================ -->
                   <xs:element name="AuthenticateRequest">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element minOccurs="0" name="Domain" type="xs:string"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <!-- The authenticate result (used to send back results for synchronous and asynchronous requests) -->
                   <xs:element name="AuthenticateResult">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element name="Status" type="xoa:StatusType"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <!-- includes for standalone validation
         <xs:include schemaLocation="StatusType.xsd"/>
         ================ -->
                   <xs:element name="CFSCreateDirRequest">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element name="RelativePath" type="xs:string"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <xs:element name="CFSCreateDirResult">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element name="Status" type="xoa:StatusType"/>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <!-- includes for standalone validation
         <xs:include schemaLocation="StatusType.xsd"/>
         ================ -->
                   <xs:element name="CFSDeleteRequest">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element name="RelativePath" type="xs:string"/>
                                  <xs:element minOccurs="0" name="DeleteDir" type="xs:boolean"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <xs:element name="CFSDeleteResult">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element name="Status" type="xoa:StatusType"/>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <!-- includes for standalone validation
         <xs:include schemaLocation="OwnershipLevelType.xsd"/>
         <xs:include schemaLocation="StatusType.xsd"/>
         <xs:include schemaLocation="Document.xsd"/>
         ================ -->
                   <xs:element name="CFSDownloadRequest">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element name="RelativePath" type="xs:string"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <xs:element name="CFSDownloadResult">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element name="Status" type="xoa:StatusType"/>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
                                  <xs:element minOccurs="0" name="FileData" type="xoa:DocDataType"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <!-- includes for standalone validation
         <xs:include schemaLocation="OwnershipLevelType.xsd"/>
         <xs:include schemaLocation="StatusType.xsd"/>
         <xs:include schemaLocation="Document.xsd"/>
         ================ -->
                   <xs:element name="CFSListRequest">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element name="RelativePath" type="xs:string"/>
                                  <xs:element minOccurs="0" name="IncludeSubDir" type="xs:boolean"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <xs:simpleType name="EntryType">
                        <xs:restriction base="xs:string">
                             <xs:enumeration value="file"/>
                             <xs:enumeration value="directory"/>
                        </xs:restriction>
                   </xs:simpleType>
                   <xs:element name="CFSListResult">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element name="Status" type="xoa:StatusType"/>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
                                  <xs:element maxOccurs="unbounded" minOccurs="0" name="DirectoryEntry" type="xoa:DirectoryEntryType">
                                       <xs:annotation>
                                            <xs:documentation>content of
                                        DirectoryEntry is path relative to
                                        the RelativePath</xs:documentation>
                                       </xs:annotation>
                                  </xs:element>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <xs:complexType name="DirectoryEntryType">
                        <xs:simpleContent>
                             <xs:extension base="xs:string">
                                  <xs:attribute name="type" type="xoa:EntryType" use="required"/>
                                  <xs:attribute name="modified" type="xs:dateTime" use="optional"/>
                                  <xs:attribute name="size" type="xs:integer" use="optional"/>
                             </xs:extension>
                        </xs:simpleContent>
                   </xs:complexType>
                   <!-- includes for standalone validation
         <xs:include schemaLocation="StatusType.xsd"/>
         ================ -->
                   <xs:element name="CFSRenameRequest">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element name="OldRelativePath" type="xs:string"/>
                                  <xs:element name="NewRelativePath" type="xs:string"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <xs:element name="CFSRenameResult">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element name="Status" type="xoa:StatusType"/>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element minOccurs="0" name="OldRelativePath" type="xs:string"/>
                                  <xs:element minOccurs="0" name="NewRelativePath" type="xs:string"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <!-- includes for standalone validation
         <xs:include schemaLocation="OwnershipLevelType.xsd"/>
         <xs:include schemaLocation="StatusType.xsd"/>
         <xs:include schemaLocation="Document.xsd"/>
         ================ -->
                   <xs:element name="CFSUploadRequest">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element name="RelativePath" type="xs:string"/>
                                  <xs:element name="FileData" type="xoa:DocDataType"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <xs:element name="CFSUploadResult">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element name="Status" type="xoa:StatusType"/>
                                  <xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
                                  <xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
                   <!-- ===============================
         <xs:include schemaLocation="AddressType.xsd"/>
         <xs:include schemaLocation="Document.xsd"/>
         <xs:include schemaLocation="EncodableStringType.xsd"/>
         <xs:include schemaLocation="OwnershipLevelType.xsd"/>
         <xs:include schemaLocation="StatusType.xsd"/>
         =============================== -->
                   <!-- Type definitions -->
                   <!-- Phone element -->
                   <xs:element name="Phone">
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <!-- <xs:pattern value="[0-9+x\-() ]{5,20}"/> -->
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <!-- Email element -->
                   <xs:element name="Email">
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:minLength value="2"/>
                                  <!-- <xs:pattern value="[@]{1,64}@([@\.]{1,64}\.){1,10}[^@\.]{1,64}"/> -->
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <!-- Eformat type -->
                   <xs:simpleType name="EformatType">
                        <xs:annotation>
                             <xs:documentation>      Only used in messageREACH.
                            Indicates the preferred email      format of the
                            message body the recipient will      receive.
                            Leaving the field empty or setting it to
                            "default" will send a multipart message body
                            rather than      just a single message body if
                            it would do so normally.   </xs:documentation>
                        </xs:annotation>
                        <xs:restriction base="xs:string">
                             <xs:enumeration value="text"/>
                             <xs:enumeration value="html"/>
                             <xs:enumeration value="htmllite"/>
                             <xs:enumeration value="default"/>
                        </xs:restriction>
                   </xs:simpleType>
                   <!-- insert list element -->
                   <xs:element name="InsertList">
                        <xs:complexType>
                             <xs:choice>
                                  <xs:element maxOccurs="unbounded" name="Insert">
                                       <xs:complexType>
                                            <xs:simpleContent>
                                                 <xs:extension base="xs:string">
                                                      <xs:attribute name="number" type="xs:integer"/>
                                                      <xs:attribute name="b64charset" type="xs:string" use="optional"/>
                                                 </xs:extension>
                                            </xs:simpleContent>
                                       </xs:complexType>
                                  </xs:element>
                             </xs:choice>
                        </xs:complexType>
                   </xs:element>
                   <!-- extension element -->
                   <xs:complexType name="SegmentType">
                        <xs:choice>
                             <xs:element maxOccurs="unbounded" name="Property">
                                  <xs:complexType>
                                       <xs:simpleContent>
                                            <xs:extension base="xs:string">
                                                 <xs:attribute name="name" type="xs:string"/>
                                                 <xs:attribute name="b64charset" type="xs:string" use="optional"/>
                                            </xs:extension>
                                       </xs:simpleContent>
                                  </xs:complexType>
                             </xs:element>
                        </xs:choice>
                        <xs:attribute name="name" type="xs:string"/>
                   </xs:complexType>
                   <xs:element name="Extension">
                        <xs:complexType>
                             <xs:choice maxOccurs="unbounded">
                                  <xs:element name="Segment" type="xoa:SegmentType"/>
                             </xs:choice>
                        </xs:complexType>
                   </xs:element>
                   <!-- field mapping type -->
                   <xs:complexType name="FieldMappingType">
                        <xs:annotation>
                             <xs:documentation>      Describes the correspondence
                            between the segment/keyword      pairs in the
                            XDDS header file and columns in a table. Only
                            two table formats currently supported: CSV
                            (comma-separated values) and XSL (Excel
                            spreadsheet).       The mapping may go either
                            from field name to the      segment/keyword pair
                            or vice versa. In both cases, the      same
                            structure may be used.   </xs:documentation>
                        </xs:annotation>
                        <xs:sequence>
                             <xs:element maxOccurs="unbounded" name="Map">
                                  <xs:complexType>
                                       <xs:sequence>
                                            <xs:element name="FieldName" type="xs:string"/>
                                            <xs:element minOccurs="0" name="SegmentName" type="xs:string"/>
                                            <xs:element name="PropertyName" type="xs:string"/>
                                            <xs:element minOccurs="0" name="IsBase64Encoded" type="xs:boolean"/>
                                       </xs:sequence>
                                  </xs:complexType>
                             </xs:element>
                        </xs:sequence>
                   </xs:complexType>
                   <!-- class definitions -->
                   <!-- delivery item base class -->
                   <xs:element abstract="true" name="DeliveryItem" type="xoa:DeliveryItemType"/>
                   <xs:complexType abstract="true" name="DeliveryItemType">
                        <xs:attribute name="ref" type="xs:string" use="optional"/>
                        <xs:attribute name="refb64" type="xs:string" use="optional"/>
                   </xs:complexType>
                   <!-- new branch -->
                   <!-- delivery item container class -->
                   <xs:element abstract="true" name="DeliveryItemContainer" type="xoa:DeliveryItemContainerType"/>
                   <xs:complexType abstract="true" name="DeliveryItemContainerType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemType"/>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- list delivery item class -->
                   <xs:element name="List" type="xoa:ListType"/>
                   <xs:complexType name="ListType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemContainerType">
                                  <xs:sequence>
                                       <xs:element name="Name" type="xs:string"/>
                                  </xs:sequence>
                                  <xs:attribute name="ownershipLevel" type="xoa:OwnershipLevelType"/>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- SmQuery delivery item class -->
                   <xs:element name="SmQuery" type="xoa:SmQueryType"/>
                   <xs:complexType name="SmQueryType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemContainerType">
                                  <xs:sequence>
                                       <xs:element name="Name" type="xs:string"/>
                                  </xs:sequence>
                                  <xs:attribute name="ownershipLevel" type="xoa:OwnershipLevelType"/>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- External table delivery item class -->
                   <!-- This includes CSV and XLS files -->
                   <xs:element name="Table" type="xoa:TableType"/>
                   <xs:complexType name="TableType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemContainerType">
                                  <xs:sequence>
                                       <xs:element minOccurs="0" name="FieldMapping" type="xoa:FieldMappingType"/>
                                       <xs:choice>
                                            <xs:element name="DocRef" type="xs:string"/>
                                            <xs:element name="Document" type="xoa:DocumentType"/>
                                       </xs:choice>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- new branch -->
                   <!-- delivery item simple class -->
                   <xs:element abstract="true" name="DeliveryItemSimple" type="xoa:DeliveryItemSimpleType"/>
                   <xs:complexType abstract="true" name="DeliveryItemSimpleType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemType">
                                  <xs:sequence>
                                       <xs:element minOccurs="0" name="Alternate">
                                            <xs:complexType>
                                                 <xs:choice>
                                                      <xs:element ref="xoa:Fax"/>
                                                      <xs:element ref="xoa:Internet"/>
                                                      <xs:element ref="xoa:Voice"/>
                                                      <xs:element ref="xoa:Fod"/>
                                                      <xs:element ref="xoa:Mbox"/>
                                                      <xs:element ref="xoa:Sms"/>
                                                      <xs:element ref="xoa:Telex"/>
                                                      <xs:element ref="xoa:DeliveryItemGeneric"/>
                                                 </xs:choice>
                                            </xs:complexType>
                                       </xs:element>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- mbox delivery item class -->
                   <xs:element name="Mbox" type="xoa:MboxType"/>
                   <xs:complexType name="MboxType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemSimpleType">
                                  <xs:sequence>
                                       <xs:element name="UserId" type="xs:string"/>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- telex delivery item class -->
                   <xs:element name="Telex" type="xoa:TelexType"/>
                   <xs:complexType name="TelexType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemSimpleType">
                                  <xs:sequence>
                                       <xs:element name="Number" type="xs:string"/>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- FOD delivery item class -->
                   <xs:element name="Fod" type="xoa:FodType"/>
                   <xs:complexType name="FodType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemSimpleType">
                                  <xs:sequence>
                                       <xs:element name="Address" type="xs:string"/>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- SMS delivery item class -->
                   <xs:element name="Sms" type="xoa:SmsType"/>
                   <xs:complexType name="SmsType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemSimpleType">
                                  <xs:sequence>
                                       <xs:element ref="xoa:Phone"/>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- new branch -->
                   <!-- Complex delivery item class -->
                   <xs:element abstract="true" name="DeliveryItemComplex" type="xoa:DeliveryItemComplexType"/>
                   <xs:complexType abstract="true" name="DeliveryItemComplexType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemSimpleType">
                                  <xs:sequence>
                                       <xs:element minOccurs="0" ref="xoa:InsertList"/>
                                       <xs:element minOccurs="0" ref="xoa:Extension"/>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- fax delivery item class -->
                   <xs:element name="Fax" type="xoa:FaxType"/>
                   <xs:complexType name="FaxType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemComplexType">
                                  <xs:sequence>
                                       <xs:element ref="xoa:Phone"/>
                                       <xs:element minOccurs="0" name="Att" type="xoa:EncodableStringType"/>
                                       <xs:element minOccurs="0" name="From" type="xoa:EncodableStringType"/>
                                       <xs:element minOccurs="0" name="To" type="xoa:EncodableStringType"/>
                                       <xs:element minOccurs="0" name="Salutation" type="xs:string"/>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- voice delivery item class -->
                   <xs:element name="Voice" type="xoa:VoiceType"/>
                   <xs:complexType name="VoiceType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemComplexType">
                                  <xs:sequence>
                                       <xs:element ref="xoa:Phone"/>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- internet delivery item class -->
                   <xs:element name="Internet" type="xoa:InternetType"/>
                   <xs:complexType name="InternetType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemComplexType">
                                  <xs:sequence>
                                       <xs:element ref="xoa:Email"/>
                                       <xs:element minOccurs="0" name="Subject" type="xoa:EncodableStringType"/>
                                       <xs:element minOccurs="0" name="From" type="xoa:EncodableStringType"/>
                                       <xs:element minOccurs="0" name="Eformat" type="xoa:EformatType"/>
                                       <xs:element minOccurs="0" name="Password" type="xs:string">
                                            <xs:annotation>
                                                 <xs:documentation>    Only used in
                                        messageREACH. The password used
                                        by this recipient to retrieve
                                        pull    attachments.        </xs:documentation>
                                            </xs:annotation>
                                       </xs:element>
                                  </xs:sequence>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- fax delivery item class -->
                   <xs:element name="DeliveryItemGeneric" type="xoa:DeliveryItemGenericType"/>
                   <xs:complexType name="DeliveryItemGenericType">
                        <xs:complexContent>
                             <xs:extension base="xoa:DeliveryItemComplexType">
                                  <xs:sequence>
                                       <xs:element name="Address" type="xs:string"/>
                                  </xs:sequence>
                                  <xs:attribute name="type" type="xoa:AddressType" use="required"/>
                             </xs:extension>
                        </xs:complexContent>
                   </xs:complexType>
                   <!-- Finally, delivery item list -->
                   <!-- delivery item list type -->
                   <xs:complexType name="DeliveryItemListType">
                        <xs:choice maxOccurs="unbounded">
                             <xs:element ref="xoa:List"/>
                             <xs:element ref="xoa:SmQuery"/>
                             <xs:element ref="xoa:Table"/>
                             <xs:element ref="xoa:DeliveryItemGeneric"/>
                             <xs:element ref="xoa:Fax"/>
                             <xs:element ref="xoa:Internet"/>
                             <xs:element ref="xoa:Voice"/>
                             <xs:element ref="xoa:Fod"/>
                             <xs:element ref="xoa:Mbox"/>
                             <xs:element ref="xoa:Sms"/>
                             <xs:element ref="xoa:Telex"/>
                        </xs:choice>
                   </xs:complexType>
                   <!--remove includes later
         <xs:include schemaLocation="AddressType.xsd"/>
         ================ -->
                   <xs:complexType name="DestinationType">
                        <xs:simpleContent>
                             <xs:extension base="xs:string">
                                  <xs:attribute name="type" type="xoa:AddressType"/>
                             </xs:extension>
                        </xs:simpleContent>
                   </xs:complexType>
                   <!-- ===============================
         <xs:include schemaLocation="OwnershipLevelType.xsd"/>
         =============================== -->
                   <!-- Elementary definitions go first -->
                   <xs:element name="CharacterSet" type="xs:string">
                        <xs:annotation>
                             <xs:documentation>use ISO names</xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <!-- Document type -->
                   <xs:simpleType name="DocFormatType">
                        <xs:restriction base="xs:string">
                             <xs:enumeration value="text"/>
                             <xs:enumeration value="XMF"/>
                             <xs:enumeration value="TIFF"/>
                             <xs:enumeration value="XAR"/>
                             <xs:enumeration value="PS"/>
                             <xs:enumeration value="PCL"/>
                             <xs:enumeration value="PDF"/>
                             <xs:enumeration value="MSW"/>
                             <xs:enumeration value="WAV"/>
                             <xs:enumeration value="RTF"/>
                             <xs:enumeration value="XLS"/>
                             <xs:enumeration value="HTML"/>
                             <xs:enumeration value="HTMLLITE"/>
                             <xs:enumeration value="unspec"/>
                             <xs:enumeration value="GIF"/>
                             <xs:enumeration value="JPEG"/>
                             <xs:enumeration value="PPT"/>
                             <xs:enumeration value="BMP"/>
                             <xs:enumeration value="VSD"/>
                             <xs:enumeration value="PUB"/>
                             <xs:enumeration value="MPP"/>
                             <xs:enumeration value="empty"/>
                             <!-- We do not need to know the document type for the -->
                             <!-- email attachments. -->
                        </xs:restriction>
                   </xs:simpleType>
                   <!-- Document Encoding format -->
                   <xs:simpleType name="DocEncodingFormat">
                        <xs:restriction base="xs:string">
                             <xs:enumeration value="text"/>
                             <xs:enumeration value="base64"/>
                        </xs:restriction>
                   </xs:simpleType>
                   <!-- Document embedded into the request -->
                   <xs:complexType name="DocDataType">
                        <xs:simpleContent>
                             <xs:extension base="xs:string">
                                  <xs:attribute name="format" type="xoa:DocEncodingFormat" use="required"/>
                             </xs:extension>
                        </xs:simpleContent>
                   </xs:complexType>
                   <!-- All supported stored object types -->
                   <xs:simpleType name="SosObjectType">
                        <xs:restriction base="xs:string">
                             <xs:enumeration value="tts"/>
                             <xs:enumeration value="vcs"/>
                        </xs:restriction>
                   </xs:simpleType>
                   <!-- The types of the sos stored objects -->
                   <xs:complexType name="SosObjectIdType">
                        <xs:simpleContent>
                             <xs:extension base="xs:string">
                                  <xs:attribute name="sosType" type="xoa:SosObjectType" use="required"/>
                                  <xs:attribute name="ownershipLevel" type="xoa:OwnershipLevelType"/>
                             </xs:extension>
                        </xs:simpleContent>
                   </xs:complexType>
                   <!-- Another Document type -->
                   <xs:complexType name="DocumentType">
                        <xs:sequence>
                             <xs:element name="DocType" type="xoa:DocFormatType"/>
                             <xs:element minOccurs="0" name="Filename" type="xs:string"/>
                             <xs:choice>
                                  <xs:element name="DocData" type="xoa:DocDataType"/>
                                  <xs:element name="DocCfs" type="xs:string"/>
                                  <xs:element name="DocUrl" type="xs:anyURI"/>
                                  <xs:element name="SosObject" type="xoa:SosObjectIdType"/>
                             </xs:choice>
                             <xs:element minOccurs="0" ref="xoa:CharacterSet"/>
                        </xs:sequence>
                        <xs:attribute name="ref" type="xs:string" use="optional"/>
                   </xs:complexType>
                   <!-- The document set type -->
                   <xs:complexType name="DocumentSetType">
                        <xs:sequence>
                             <xs:element maxOccurs="unbounded" minOccurs="0" name="Document" type="xoa:DocumentType"/>
                        </xs:sequence>
                   </xs:complexType>
                   <!-- The document by value or by reference -->
                   <xs:complexType name="DocumentOrRefType">
                        <xs:choice>
                             <xs:element name="DocRef" type="xs:string">
                                  <xs:annotation>
                                       <xs:documentation>must refer to a document
                                    in document_set</xs:documentation>
                                  </xs:annotation>
                             </xs:element>
                             <xs:element name="Document" type="xoa:DocumentType"/>
                        </xs:choice>
                   </xs:complexType>
                   <xs:complexType name="EncodableStringType">
                        <xs:simpleContent>
                             <xs:extension base="xs:string">
                                  <xs:attribute name="b64charset" type="xs:string" use="optional"/>
                             </xs:extension>
                        </xs:simpleContent>
                   </xs:complexType>
                   <!--includes for standalone validation
         ================ -->
                   <xs:simpleType name="HistoryActionType">
                        <xs:restriction base="xs:string">
                             <xs:enumeration value="inserted"/>
                             <xs:enumeration value="updated"/>
                             <xs:enumeration value="deleted"/>
                        </xs:restriction>
                   </xs:simpleType>
                   <xs:complexType name="ItemCountType">
                        <xs:simpleContent>
                             <xs:extension base="xs:integer">
                                  <xs:attribute name="type" type="xoa:HistoryActionType"/>
                             </xs:extension>
                        </xs:simpleContent>
                   </xs:complexType>
                   <xs:complexType name="HistoryType">
                        <xs:sequence>
                             <xs:element name="Action" type="xs:string"/>
                             <xs:element name="Operator" type="xs:string"/>
                             <xs:element name="Agent" type="xs:string"/>
                             <xs:element name="Time" type="xs:dateTime"/>
                             <xs:element name="ItemCount" type="xoa:ItemCountType"/>
                        </xs:sequence>
                   </xs:complexType>
                   <!-- ================
         <xs:include schemaLocation="AddressType.xsd"/>
         <xs:include schemaLocation="DestinationType.xsd"/>
         <xs:include schemaLocation="Document.xsd"/>
         <xs:include schemaLocation="JobIdType.xsd"/>
         <xs:include schemaLocation="OwnershipLevelType.xsd"/>
         <xs:include schemaLocation="StatusType.xsd"/>
         <xs:include schemaLocation="RecStatusType.xsd"/>
         ================ -->
                   <xs:simpleType name="JobCancelType">
                        <xs:annotation>
                             <xs:documentation>The set of cancellation types/options</xs:documentation>
                        </xs:annotation>
                        <xs:restriction base="xs:string">
                             <xs:enumeration value="All"/>
                             <xs:enumeration value="Deliveries"/>
                             <xs:enumeration value="Reports"/>
                             <xs:enumeration value="AcceptanceReport"/>
                             <xs:enumeration value="CancellationNotice"/>
                             <xs:enumeration value="Pulls"/>
                             <xs:enumeration value="FriendDeliveries"/>
                        </xs:restriction>
                   </xs:simpleType>
                   <xs:complexType name="JobCancelItemType">
                        <xs:sequence>
                             <xs:element name="JobId" type="xoa:JobIdType">
                                  <xs:annotation>
                                       <xs:documentation>requested JobId</xs:documentation>
                                  </xs:annotation>
                             </xs:element>
                             <xs:element minOccurs="0" name="CancelType" type="xoa:JobCancelType"/>
                             <xs:element minOccurs="0" name="NotificationAddress" type="xoa:DestinationType"/>
                             <xs:choice minOccurs="0">
                                  <xs:element name="NotificationType" type="xs:string"/>
                                  <xs:element name="NotificationText" type="xoa:DocDataType"/>
                             </xs:choice>
                        </xs:sequence>
                   </xs:complexType>
                   &

    Hi,
    Not all data types from WSDL are supported during import. There is SAP Note about it.
    please read it:
    /people/kevin.liu/blog/2005/10/07/a-note-on-wsdl-and-xsd-imports--part-ii
    regards,
    wojtek
    Message was edited by: Wojciech Gasiorowski

  • Can't use Data type created with External Definition

    Hi,
    In the repository, I would like to transport a very complexe DataType from one XI system to an other one. As I don't want to spend a week to create data types, I created a new External Definitions and loaded my XSD schema (that I exported as XSD from Source system) with Messages parameter set to "From All Available Global Elements". I don't set the "Source". I can see the "Imported Document" and "WSDL", but the Messages and External References tabs are empty. Furthermore, I can't use my new message type in a Outbound Asyncrhronous Message Interface.
    Here is a very small XSD file that I use to test my scenario.
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://veilleux.1" targetNamespace="http://veilleux.1">
         <xsd:complexType name="SimpleType1">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   bdfdbef1df9711daa2c9001125f86068
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="Name" type="SimpleType2">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             bdfdbef0df9711daa821001125f86068
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
              </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="SimpleType2">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   0fecc852df9811da899a000f206d294f
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="Name" type="xsd:string">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             ac58afc0df9711da86af001125f86068
                             </xsd:appinfo>
                        </xsd:annotation>
                   </xsd:element>
              </xsd:sequence>
         </xsd:complexType>
    </xsd:schema>
    Any one can help me please.
    Thanks, Davy

    Hello Moorthy,
    My XSD is correct since it's XI itself that generated it from real Data Type on my source System (but I tested it in Internet Explorer and it looks fine).
    I tried to select my ExternalDefinition as source in MessageMapping, but XI doesn't let me specify it (Apply button is disabled when I select my ExternalDefinition).
    I'm pretty sure that it is related to the fact that I should have a Data Type in "Messages" and "External References" tabs and I have nothing. My XSD is legal, but it seems that XI can't automatically create the data type from it.
    Do you have any other idea?
    Thanks, Davy

  • Message Mapping - External Definitions

    My Scenario
    1) File1(Request with Employee Number) - Sent to XI (Async)
    2) XI will send the Request over HTTP and will Receive the Response(Employee Details) (Synchronous)
    3) The HTTP Response will be sent to File2(Employee Details) (Async)
    The Request and Responses are XSD Messages. I have Imported them into External Definition in my Repository.
    Created a File Request - Abstract - Asynchronous - Message interface
    Created a HTTP Request-Response - Abstract - Synch - Message interface
    Created a File Response - Abstract - Asynchronous - Message interface
    Message Mapping: (I am stuck here)
    I need to Map the File Request to HTTP Request
    I need to Map the HTTP Response to File2Response
    How can I creat the Message Mapping for the above situation?
    Thanks.

    Hi,
    You will need to create the following message mapping:
    1. File Request - HTTP Request
    2. HTTP Response - File Response
    you can map Message Types to External Definitions and vice versa.
    They should appear in the list for the relevant software component.
    Or am I missimng something here ?
    Cheers
    colin.

  • Creating message type in XI with imported objects

    Hi,
    I have imported an Idoc Structure into XI.
    Now I need to create a message type with structure from imported Idoc + some additional fields.
    Can some one tell me how to go about this. Because once I drag and drop the imported Idoc structure, I doesn't allow me to add any more fields during message type creation.
    Is there a different to way to achieve this.
    Best Regards,
    Kiran

    Hi Kiran,
    the Integration Builder supports two ways of modelling an interface. The first way is to build the required datatypes from scratch (with the datatype editor) then define (fault) message types using these datatypes and finally define the message interface.
    The second way is to use an externally defined structure by importing an IDoc or RFC from an R/3 or an external DTD/XSD/WSDL from filesystem. Then define your Message Interface using the messages from the imported objects.
    Currently there is nearly no support for mixing these two approaches as you have in mind (taking an externally defined structure as starting point, then enhance this structure within the Integration Builder).
    The best workaround I can suggest to you, is import the IDoc, take the XSD which is displayed for it, download it to your local file system, edit it there (with notepad when you are an XSD expert, with some other tool like XML Spy otherwise) and upload the modified file as External Definition.
    BTW: For this procedure you do not necessarily need to upload the IDoc to the Repository. As far as I know the R/3 also offers the possibility to generate an XSD representation for an IDoc (do not remember the exact way to go there).
    Greetings Stephan

Maybe you are looking for

  • Can I use the backup of one iPod Touch on another?

             Hello, The other day, I accidentally dropped my 4th generation 32GB iPod Touch on concrete from a couple of feet.  The screen has many cracks and the top-right corner is missing a few chunks of screen. The corner is completely shattered and

  • How do I install LR on second computer without disk or serial number

    I need to install LR onto a new computer.  I cannot find the LR 3 dish but I do have the Adobe order number for my purchase of LR3,  but I do not have a serial no. or codes for installing LR 3.  I do have the LR 5 upgrade disk.  I have tried to chat

  • That USB/Firewire question again

    OK, I've done my research, no converter exists. Just bought my fiance a 60gb iPod to replace his old white one which had died. But he has been keeping his music on our old blue G3, and both its USB ports are occupied - keyboard and external hard driv

  • The role of multicasting in clustering

    I'm looking to clarify the role of multicasting in WLS clusters. As I understand it, multicasting is used exclusively to exchange heartbeats - and in-memory replication of sessions and EJBs is a point-to-point exchange. Is this correct?Thanks.-C     

  • Most satisfying indestructible shock-absorbing tank armor for iphone 3G

    I need the best (best=highly satisfying) case in terms of protection for the iphone 3G I ordered. I know there are a lot of posts on this subject but I have very specific preferences and don't want to spend hours reading tons of posts on every channe