Extenal Refence in External Definition

Hi,
I need to use an external WSDL as a External Definition. The WSDL contains this line:
<b><xsd:include schemaLocation="../service/FordringModtagSAP38Interface.xsd" /></b>
How do i import the includet schema? It´s not allowed to call it <b>../service</b>
How do i do it??
/Jakob

Let me try to explain it better.
Assume the XSD A refers to XSD B.
1. Import XSD A.
2. In XSD A ( the main XSD ), you will find a tab EXTERNAL REFERENCES . In this you should find an entry for Source. Copy this.
3. Import XSD B.
4. When you import, you will find a field called Source after you import it. Paste the Copied Text of step 2 here.
5. Save and activate.
6. Now, XSD A, in External References should contain both Name and Source filled.
Regards
Bhavesh

Similar Messages

  • When to User Extenal Refence in External Defination

    HI Guys.
         Can you please  help me How to import the XSD file and WSDL files..into XI..if they are extenal.. after createing External Defination  how should i need to imported them.. in xi.
    Regd's
    Raj

    Hi,
    Save the schema as .xsd into system. And then import the same .xsd file from local machine into External Definition by choosing type option is xsd.
    Similarly .wsdl file will be imported , by choosing the type option as wsdl.
    You can import any external xsds, or wsdl into xi.
    For more-
    http://help.sap.com/saphelp_nw2004s/helpdata/en/26/9e97b0f525d743882936c2d6f375c7/content.htm
    For answering your subject , External refrence is mainly used in the Webservice structure. ie in WSDL. When you have many funtionality in the Webservice application, then there will be a an external reference for the main wsdl structure.
    Regards,
    moorthy

  • 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

  • How to remove namespaces in mapping when using External Definition

    Hi,
    I read in the blog (/people/sameer.shadab/blog/2005/12/05/how-to-remove-namespaces-in-mapping--xi) that you are able to remove namespaces in mapping by deleting the value from XML Namespace under the Message Type. However, is it possible to do this when you are using External Definition (xsd) ? The blog only describe how to do this if you define a Data Type.

    Hi ,
    No ..it is not possible to remove the namespace once you imported into IR of external defintion.You can remove your namesapce from external definition before importing into IR.
    Sekhar

  • Multi-Mapping Error in PI 7.1 - External Definitions

    Hi all,
    We have just upgraded to PI 7.1 from 7.0 and run into an issue with message multi-mappings, just wondered if anyone else had met the same issue and worked it out...
    When creating a message mapping, we are using as the target an external definition which is defined by an XSD generated by a third party tool (Seeburger).
    When I map 1:1 (1 source message to one target message) in the message mapper, all is fine but if I try to create a multi mapping, I get an error. The process is:
    a) I have a message mapping with one target message, defined as an External Definition.
    b) I then go to Signature tab and add a second target message as an External Definition
    c) Click back to Definition tab
    d) Get the error "Object XXXXX | YYYYY not found" - where XXXXX is the external def name and YYYYY is the namespace (the SWCV namespace that is, not the XML namespace)
    This only seems to happen with External Definitions which are autogenerated and I strongly suspect that is has to do with the fact that the tool that generates them always  does so without an XML namespace. I have not proved this though (other Ext Defs with namespaces work for multi-mappings but that is not the only difference so I can't be sure that is the issue but have a strong hunch. This problem did not occur in 7.0.
    Anyone got any ideas?
    Thanks,
    Chris

    Hi,
    This would not be of much help but, I was able to encounter this issue in XI 3.0.
    What we did was to manually edit the XSD and add a namespace to it. I'm not sure if PI 7.1 is able to handle mutiple namespaces, so we limited it to this value <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"> and made sure that this value is used for all the External Definitions used in the multi-mapping.
    Regards,

  • File to multiple Idocs using external definitions.

    Hi all,
    I have to create multiple idocs based on one field from source side.
    Inorder to do this..I have decided to change the occurance of Idoc from 1 to 1..unbounded , in the xsd i have downloaded from standard Idoc.
    which i have a plan to map to the filed , based on that i need to create new Idoc.
    I have tried importing the modified xsd into external definition. but how i should relate it to standard idoc which I have mapped earlier?.
    Thanks,
    venu.

    HI Venu,
    <i>
    I have tried importing the modified xsd into external definition. but how i should relate it to standard idoc which I have mapped earlier?.</i>
    After changing the Idoc occurence , you have imported the xsd into external definition. So this will act as as new message type for you in the mapping.
    You can not use old mapping here.
    Regards,
    Moorthy

  • 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

  • Not able to see "External Definitions" in Integration Repository

    Hi Experts,
    I am working on PI 7.1.
    In the Integration Repository Menu :
    SAP Basis --->SAP Basis 7.10 ->http://sap.com/xi/XI/System ->
    "Service Interfaces",
    "Message Types"
    "Fault Message Types",
    "Data Types",
    "Adapter Metadata"
                                      only are visible.
    We need the "External Definitions". Is it  not available in the standard SAP PI 7.1 ?
    Do we have to import it explicitly?
    Kindly advice.
    Thanks in advance
    ~ Suraj

    Hey NM,
        Thanks a lot for your suggestion. problem got resolved when i did what you said (checking the attributes with developers user id's)
    Thanks
      Sourav

  • 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.

  • 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

  • Scenario proxy to soap synchronous with external definitions

    Hi all,
    I have a problem with my scenario.
    In development environment all is working fine, but when I have transported to preproduction environment and we have executed my scenario I have the following error:
    <SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: http://geisiedes.endesa.es/WSRespuesta/WsRespuestaSIE.asmx/EnviarRespuestaNocturnaWF.</SAP:AdditionalText>
    <SAP:Stack />
    I attach the receiver communication channel configuration.(cc_config.jpg)
    I changed the target URL in the receiver channel, with the preproduction machine, but I didn't change the sopa action because is define in the wsdl ( soap_action.jpg).
    I have othe external definitions for preproduction environmet but its contect is different to external definitions in development change the reference to machine where geisiepre instead geiseides.
    Whe I import this external definitions I lose the configuration in messages mappings.
    How can I solve this problem? Is mandatory to have the same external definitions in the three environments??
    Thanks and best regards
    Mónica

    Hi Monica,
    I normally use the all the tag content in the SOAPAction tag, but you can try with EnviarRespuestaNocturnaPC in the SOAP receiver communication channel.
    Have you tried to test your wsdl endpoint with SOAPui?, you can get sometimes valuable information about how design/configure in PI and if the request is identical in PI and in SOAPui.
    Regards.

  • 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.

  • "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

  • 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.

  • Can External Definition be used or Receiver File content conversion (CSV)?

    Hi Experts,
    I'm a newbie to SAP PI and I started working on file to File(FCC) scenario in which I am provided with the receiver structure as an External definition. The structure is like
    Name
    Place
    Designation
    Salary
    hike
    Can I use the same structure (External Definition) for the receiver file content conversion or do I need to create another specific structure?
    Can I convert the target CSV file to UTF-8 encoding?
    Please help.
    Regards,
    Taro

    Hi,
    Can the above specified structure be used for receiver FCC? Does this work? Can this be converted to UTF-8?
    If it can be used, how do we specify the parameters for FCC then as there's no root element?
    Regards,
    Taro

Maybe you are looking for

  • When I click on signin In Eprint

    When I click on signin In Eprint I get a java void message bottom left screen and nothing else happens. Imam a novice where techno is involved any help appreciated. This question was solved. View Solution.

  • Can't load swf into editable region

    Am using DW CS4 in W7 64. Have designed an html site with one page that has a swf to control dynamic content with php. All the pages are created based on one template and al is fine until I try to place the flash file in the editable area of the html

  • SDO_RELATE rectanlge works but circle doesn't?

    Hello I have two queries. the first uses a rectangle to find a polygon ID. SELECT A.fid FROM f10 A WHERE sdo_relate(A.points, mdsys.sdo_geometry(2003,NULL,NULL, mdsys.sdo_elem_info_array(1,1003,3), mdsys.sdo_ordinate_array(592368.93,46518840.02,59661

  • Sales Order Date and Despatch Advice Date

    Hi all, I need to create a view that contains Sales Order #, Despatch Advice # , Sales Order Date, Despatch Advice Date and Sales Organization. Please tell me that using which tables, required view can be created? Regards, AI.

  • Is it possible to play BF3 in macbook MC700LL/A (13 inch i5 intel 3000)

    is it possible to play BF3 in macbook MC700LL/A (13 inch i5 intel 3000)