Error on importing OpenTrans dtd

Hi,
I have some difficulties importing a dtd of the german OpenTrans standard.
The part which seems to be a problem is:
<b>  <!ELEMENT ORDER (ORDER_HEADER , ORDER_ITEM_LIST , ORDER_SUMMARY)>
    <!ATTLIST ORDER
                     version  CDATA  #FIXED "1.0"
                     xmlns    CDATA  #FIXED 'http://www.opentrans.org/opentrans/1.0/opentrans_order'
                     type     (standard | express | release | consignment )  'standard' ></b>
The error is:
<b>The name "xmlns" is not correct!</b>
How can I fix this without removing xmlns from the dtd?

Hi,
I have the same problem with the DTD. Did any one find the solution ?
Myr problem is that our partner demands that the xml file has the <!-- DOCTYPE ORDER SYSTEM "openTRANS_ORDER_1_0.dtd" --> tag .
So I see 2 solution.
1) use the DTD
2) Use XSD an some how insert this tag with xslt. I could not solved this properly !

Similar Messages

  • Error While Importing DTD to XI

    Hi all,
    I have a DTD from cxml.org. While importing that DTD into the XI as external definitions, the message types couldn't be shown.
    Can anybody please suggest the reason?
    Any help will be appriciated.
    Kind regards,
    Kulwant

    Hi,
    Thanks alll for reply. Let me bit explain more. While i import this DTD, i get an error in the WSDL tab in the imported external definitions screen,
    Unable to convert imported document to WSDL
    Reason: Entity "Method.ANY" already declared
    Check the selected category
    Can any body suggest
    I have posted the dtd below:
    <?xml version="1.0" encoding="UTF-8"?>
    <!--
        For cXML license agreement information, please see
        http://www.cxml.org/home/license.asp
        $Id: //ariba/cxml/modules/Common.mod#6 $
    -->
    <!--
        A few character entities the XML recommendation says should be defined
        "for interoperability" with existing SGML parsers.  By default, these
        are not included to avoid warnings (about entity redefinition) from
        many XML parsers.
    -->
    <!ENTITY % SGML-help "IGNORE">
    <![%SGML-help;[
    <!ENTITY lt     "&#38;#60;">
    <!ENTITY gt     "&#62;">
    <!ENTITY amp    "&#38;#38;">
    <!ENTITY apos   "&#39;">
    <!ENTITY quot   "&#34;">
    ]]>
    <!--
        Common types used throughout the cXML definition.
        The types try to follow the XML DATA definition submitted to the W3C. See
        the following for more information,
            http://msdn.microsoft.com/xml/reference/schema/datatypes.asp
            http://www.w3c.org/TR/1998/NOTE-XML-data-0105/
    -->
    <!-- Atomic-level Types -->
    <!ENTITY % bin.base64 "CDATA">
    <!ENTITY % bin.hex "CDATA">
    <!ENTITY % boolean "(0 | 1)">    <!-- 0 is false, 1 is true -->
    <!ENTITY % char "CDATA">
    <!ENTITY % date "CDATA">
    <!ENTITY % datetime.tz "CDATA">  <!-- Time zone is required -->
    <!ENTITY % fixed.14.4 "CDATA">
    <!ENTITY % i8 "CDATA">
    <!ENTITY % int "%i8;">
    <!ENTITY % r8 "CDATA">
    <!ENTITY % number "CDATA">       <!-- No limit on number of digits, unlike
                                          %r8; -->
    <!ENTITY % string "CDATA">
    <!ENTITY % time.tz "CDATA">      <!-- Time zone is required -->
    <!ENTITY % duration "CDATA">      <!--ISO8601 duration http://www.w3.org/TR/xmlschema-2/#duration  -->
    <!ENTITY % ui8 "CDATA">
    <!ENTITY % uint "%ui8;">         <!-- Unique to this specification -->
    <!ENTITY % uri "CDATA">
    <!ENTITY % uuid "CDATA">
    <!-- Higher-level Types -->
    <!--
        NOTE: The following is a temporary hack to allow empty values for
        some attributes with these types.  The nmtoken entity should resolve to
        NMTOKEN.
    -->
    <!ENTITY % nmtoken "CDATA">      <!-- Any combination of XML name chars. -->
    <!ENTITY % isoLangCode "%nmtoken;">         <!-- ISO 639 Language Code -->
    <!ENTITY % isoCountryCode "%nmtoken;">      <!-- ISO 3166 Country Code -->
    <!ENTITY % isoCurrencyCode "%nmtoken;">     <!-- ISO 4217 Currency Code -->
    <!ENTITY % xmlLangCode "%nmtoken;"> <!-- Language code as defined by XML
                                             recommendation: Language and
                              country. -->
    <!ENTITY % URL "%uri;">
    <!--
        For cXML license agreement information, please see
        http://www.cxml.org/home/license.asp
        $Id: //ariba/cxml/schema/Modules/Base.mod#8 $
    -->
    <!--
        This file defines the basic elements used to build higher level
        constructs in cXML.
    -->
    <!-- Basic Name/Data Elements -->
    <!--
        Name is used to provide an identifier for other elements.
        xml:lang
            The language in which the name is written.
    -->
    <!ELEMENT Name (#PCDATA)> <!-- string -->
    <!ATTLIST Name
        xml:lang  %xmlLangCode;  #REQUIRED
    >
    <!--
        An Extrinsic is an element which can be used to extend the data
        associated with known elements.
        Since this Element is of type ANY, it could contain any arbitrary XML
        document within itself, or a binary ![CDATA[]] document.
        name
            Name used to identify this extrinsic.
    -->
    <!ELEMENT Extrinsic ANY>
    <!ATTLIST Extrinsic
        name  %string;  #REQUIRED
    >
    <!--
        Description is a string which describes something.
        Though text may be interspersed with ShortName elements in this content
        model, placing the ShortName at the beginning or end of the element is
        much preferred.  At most one ShortName element is allowed per
        Description.  The intended content model would be more like
        (( ShortName, #PCDATA ) | ( #PCDATA | ShortName? )) if DTD syntax
        supported it.
        xml:lang
            The language in which the description is written.
    -->
    <!ELEMENT Description ( #PCDATA | ShortName )* > <!-- mixed: string and
                                                          ShortName -->
    <!ATTLIST Description
        xml:lang  %xmlLangCode;  #REQUIRED
    >
    <!--
        A short string which describes something in fewer characters than the
        entire Description.  This should be used when limited space is available.
        For example, a table of elements might show the ShortName's of each.  A
        linked "details" view would show the entire Description (including the
        ShortName).  Without a ShortName, the user interface must default to a
        truncation of the Description.
        This element does not require an xml:lang attribute since it appears only
        within a Description element.  The language of the ShortName must match
        that of the surrounding Description.
    -->
    <!ELEMENT ShortName (#PCDATA)> <!-- string -->
    <!-- Telephone Number Elements -->
    <!--
        International ITU dial code for the country code in question.  This
        code would be entered after any escape code necessary to begin
        International dialing.  That is, the escape code does not appear in the
        content of this element.
        isoCountryCode
            The ISO 3166 2-letter country code for the dial code in question.
    -->
    <!ELEMENT CountryCode (#PCDATA)> <!-- uint -->
    <!ATTLIST CountryCode
        isoCountryCode  %isoCountryCode;  #REQUIRED
    >
    <!--
        The areacode or city code within a CountryCode.
    -->
    <!ELEMENT AreaOrCityCode (#PCDATA)> <!-- uint -->
    <!--
        The local number part of a telephone number.
    -->
    <!ELEMENT Number (#PCDATA)> <!-- string -->
    <!--
        An extension within relative to the Number element. This element has no
        meaning without an associated Number element.
    -->
    <!ELEMENT Extension (#PCDATA)> <!-- uint -->
    <!--
        TelephoneNumber represents international telephone numbers.
    -->
    <!ELEMENT TelephoneNumber (CountryCode, AreaOrCityCode, Number, Extension?)>
    <!--
         Phone is a "named" TelephoneNumber.
         name
              specifies an identifier which indicates the type of phone number.
              US examples would include "work","home", etc.
    -->
    <!ELEMENT Phone (TelephoneNumber)>
    <!ATTLIST Phone
        name  %string;  #IMPLIED
    >
    <!--
        Fax number.
    -->
    <!ELEMENT Fax (TelephoneNumber | URL | Email)>
    <!ATTLIST Fax
        name  %string;  #IMPLIED
    >
    <!-- Addressing Elements -->
    <!--
        URL. A string which represents a URL
    -->
    <!ELEMENT URL (#PCDATA)> <!-- URL -->
    <!ATTLIST URL
        name  %string;  #IMPLIED
    >
    <!--
        An email address. Address must conform to RFC 821 (SMTP Standard).
        preferredLang
            optional language that the email owner prefers to receive
            emails in. Refer to the definition of xmlLangCode entity.
    -->
    <!ELEMENT Email (#PCDATA)> <!-- string -->
    <!ATTLIST Email
        name          %string;       #IMPLIED
        preferredLang %xmlLangCode;  #IMPLIED
    >
    <!--
        Contact represents an entity at a location. The nature of this
        element is that it represents a communication "end point" for a
        location.
        role
            Position this person or group plays in the procurement process.
            Likely values include endUser, administrator, purchasingAgent,
            technicalSupport, customerService, sales,
            supplierCorporate, supplierMasterAccount, supplierAccount,
            buyerCorporate, buyerMasterAccount, buyerAccount, buyer,
            subsequentBuyer. Other values may be allowed in some cases.
            from and to roles are reserved for future use.
        addressID
            An id for the address. Needed to support address codes for
            relationships that require id references.
    -->
    <!ELEMENT Contact (Name, PostalAddress*, Email*, Phone*, Fax*, URL*)>
    <!ATTLIST Contact
        role             NMTOKEN           #IMPLIED
        addressID        %string;          #IMPLIED
    >
    <!--
        The DeliverTo part of an Address. This would be internal to the actual
        address know to the outside world. Similar to what an extension is to a
        TelephoneNumber.
    -->
    <!ELEMENT DeliverTo (#PCDATA)> <!-- string -->
    <!--
        Street is a single line of an Address' location.
    -->
    <!ELEMENT Street (#PCDATA)> <!-- string -->
    <!--
        City is the name of the city in an Address' location.
    -->
    <!ELEMENT City (#PCDATA)> <!-- string -->
    <!--
        State is an optional state identifier in an Address' location.
    -->
    <!ELEMENT State (#PCDATA)> <!-- string -->
    <!--
        PostalCode (I have no idea how to describe it)
    -->
    <!ELEMENT PostalCode (#PCDATA)> <!-- string -->
    <!--
        Country is the name of the country in an Address' location.  The
        content of this element is a string which may (for example) be printed
        directly to a shipping label.  The content is the human-readable
        equivalent of the isoCountryCode used by applications.
        isoCountryCode
            The ISO 3166 2-letter country code for this country.
    -->
    <!ELEMENT Country (#PCDATA)> <!-- string -->
    <!ATTLIST Country
        isoCountryCode  %isoCountryCode;  #REQUIRED
    >
    <!--
        PostalAddress is a real-world location for a business or person.
    -->
    <!ELEMENT PostalAddress (DeliverTo*, Street+, City, State?,
                             PostalCode?, Country)>
    <!ATTLIST PostalAddress
        name  %string;  #IMPLIED
    >
    <!--
        Address is the association of a Contact and an Location.
        isoCountryCode
            The ISO 3166 2-letter country code for the country containing this
            location.
        addressID
            An id for the address.  Needed to support address codes for
            relationships that require id references.  An example would be a
            shipping code.
    -->
    <!ELEMENT Address (Name, PostalAddress?, Email?, Phone?, Fax?, URL?)>
    <!ATTLIST Address
        isoCountryCode  %isoCountryCode;  #IMPLIED
        addressID       %string;          #IMPLIED
    >
    <!-- Financial Elements -->
    <!--
        Money is the representation of the object used to pay for items.
        currency
            specifies the currency in which amount is stated, must conform to ISO
            4217 currency codes.
        alternateAmount
            the amount of money in the alternateCurrency. Optional and used to
            support dual-currency requirements such as the Euro.
        alternateCurrency
            specifies the currency in which the alternateAmount is stated, must
            conform to ISO 4217 currency codes.
    -->
    <!ELEMENT Money (#PCDATA)> <!-- number -->
    <!ATTLIST Money
        currency           %isoCurrencyCode;  #REQUIRED
        alternateAmount    %number;           #IMPLIED
        alternateCurrency  %isoCurrencyCode;  #IMPLIED
    >
    <!--
        Optional textual child for communicating arbitrary comments or
        description along with the parent.
        Though text may be interspersed with Attachment elements in this content
        model, grouping the Attachment list at the begging or end of the element
        is much preferred.  The intended content model would be more like
        (( Attachment+, #PCDATA ) | ( #PCDATA | Attachment* )) if the DTD syntax
        supported it.
        xml:lang
            The language in which the Comments are written.  This attribute
        will be required in a future version of cXML.  (Leaving it out is
        deprecated.)
    -->
    <!ELEMENT Comments ( #PCDATA | Attachment )* > <!-- mixed: string and
                                                        opt. Attachment list -->
    <!ATTLIST Comments
        xml:lang  %xmlLangCode;  #IMPLIED
    >
    <!--
        Optional child of Comments element referencing a part in a multipart MIME
        transmission.
        The contained URL must use the scheme "cid:".  This is the identifier for
        the referenced attachment within the larger transmission.  Must match the
        Content-ID header of one (and only one) part of the MIME transmission
        containing this cXML document.  May also be used to retrieve the
        attachment file separately.
    -->
    <!ELEMENT Attachment (URL)>
    <!---
        Reference to a remote attachment.
        AttachmentReference is used inside Extrinsic elements that have a
        predefined name of "Attachments".
        In the context of AttachmentReference, the domain attribute of
        InternalID is currently optional. However, as a way to prevent
        circular request paths, the sending application may use a
        predefined value of "local" to indicate that the attachment
        requested is local to the other application.
        length
            length of the attachment in bytes.
    -->
    <!ELEMENT AttachmentReference (Name, Description, InternalID)>
    <!ATTLIST AttachmentReference
        length  %uint;  #IMPLIED
    >
    <!--
        Price per unit of item.
    -->
    <!ELEMENT UnitPrice (Money)>
    <!--
        Reference to an earlier document (for example, OrderRequest).  In a
        StatusUpdateRequest, this element identifies the purchase order to be
        updated.
        payloadID
            A unique identifier for the document.  Copied directly from the
            cXML element of the original document.
    -->
    <!ELEMENT DocumentReference EMPTY>
    <!ATTLIST DocumentReference
        payloadID       %string;      #REQUIRED
    >
    <!ELEMENT InternalID (#PCDATA)> <!-- string -->
    <!ATTLIST InternalID
        domain   %string;  #IMPLIED
    >
    <!-- ====
        Common to most variants of the PunchOut transaction set.  Defined here
        to be easily shared between multiple DTD files without requiring
        inclusion of Transaction.mod in all of them.
        All of the PunchOut transaction sets include an originating Request
        (ProviderSetupRequest for example), relatively simple Response
        (PunchOutSetupResponse for example) and final Message
        (ProviderDoneMessage or PunchOutOrderMessage).  The Request and
        Response comprise a back-end transaction between two cooperating
        applications that wish to extend an interactive session from one to the
        other.  The Request provides the destination application with
        authentication, identification and other setup information.  The
        Response provides the originating application with a unique starting
        location for the interactive (HTML) session at the destination system.
        After receiving a Response of this type, the originating application
        redirects the user's browser to the provided location.  (For some
        non-HTML applications, opening a new browser window at that location
        may be more appropriate.)  The destination system eventually provides
        an HTML form to the user's browser.  This form submits the final
        Message to close the remote session, return that user to the
        originating application and carry any required information back to the
        originating application.
    ==== -->
    <!--
        OriginatorCookie - Identification of a specific PunchOut session.  Used
        in both originating Request and later Message that returns user to
        originating application.
        Note: The BuyerCookie element used in a 'regular' PunchOut transaction
        (defined in Transaction.mod) is of type ANY.  That does not seem
        useful.  The string required below better matches the needs for this
        element.  Future transactions similar to the PunchOut transaction will
        use this element.
    -->
    <!ELEMENT OriginatorCookie (#PCDATA)>
    <!--
        BrowserFormPost - Location to which the user's browser must submit the
        final Message.  This location (carried in the originating Request) does
        not need to be specific to a PunchOut session since the
        OriginatorCookie is returned in the Message.
    -->
    <!ELEMENT BrowserFormPost (URL)>
    <!--
        SelectedService - Identification of a service offered by this provider
        and requested in this transaction.  Used only in the originating
        Request.
    -->
    <!ELEMENT SelectedService (#PCDATA)>
    <!--
        StartPage - Location to which the user's browser must be redirected to
        begin the interactive portion of the session at the remote site.  The
        destination system returns this information in the Response document.
        This location must be specific to a particular session.  It is
        effectively a one time key, providing authenticated entry into the
        destination system.
    -->
    <!ELEMENT StartPage (URL)>
    <!--
        ReturnData - Any information the originator must know about the
        completed operation at the provider site.  The ReturnValue is for
        applications; the Name is for human consumption (direct presentation in
        the User Interface of the application).  Where appropriate for the
        possible services, this element may appear in the final Message for a
        PunchOut session.
        name
            An identifier for the data returned.  Provides a meaning for the
            contents of a ReturnData element.
    -->
    <!ELEMENT ReturnData (ReturnValue, Name)>
    <!ATTLIST ReturnData
        name  %string;  #IMPLIED
    >
    <!ELEMENT ReturnValue (#PCDATA)>
    <!--
        Defines a time range. The start and end can be unbounded
        startDate
            The starting date of the time range
        endDate
            The ending date of the range
    -->
    <!ELEMENT TimeRange EMPTY>
    <!ATTLIST TimeRange
        startDate      %datetime.tz;         #IMPLIED
        endDate        %datetime.tz;         #IMPLIED
    >
    <!--
        Defines a period in time.
        startDate
            The starting date of the period
        endDate
            The ending date of the period
    -->
    <!ELEMENT Period EMPTY>
    <!ATTLIST Period
        startDate      %datetime.tz;         #REQUIRED
        endDate        %datetime.tz;         #REQUIRED
    >
    <!--
        Must be a UN/CEFACT (Recommendation 20) unit of measure code.
    -->
    <!ELEMENT UnitOfMeasure (#PCDATA)> <!-- nmtoken -->
    <!--
        Defines a reference to a term which is defined
        in another document.
        termName
            The name of the ID attribute containing the term.
        term
            The value of that attribute (i.e., the term itself).
    -->
    <!ELEMENT TermReference EMPTY>
    <!ATTLIST TermReference
         termName %string; #REQUIRED
         term %string; #REQUIRED
    >
    <!--
        Defines an optionally named monetary rate at which goods or services are
        charged or paid.
        Money
            The amount of Money per UnitOfMeasure to be charged or paid.
        UnitOfMeasure
            Unit of measure.
        TermReference
            Identifies the definition of this UnitRate
            (found, for example,  in contracts, master agreements, and other documents
            which may or may not be cXML documents).
    -->
    <!ELEMENT UnitRate (
        Money,
        UnitOfMeasure,
        TermReference?
    )>
    <!--
        The rate information used to define the rate of a purchase.  For
        example, this could be the total room rate for 4 nights of stay
        at a hotel.
        Total
            The total amount for the rate.  The total amount must equal
            to quantity x UnitRate.
        UnitRate
            The single unit rate.
        Description
            Textual description for the rate.  For example, hotel nightly rate.
        Quantity
            The quantity.  For example, a 4 nights stay at a hotel will
            have quantity set to 4 with UnitofMesure in UnitRate set to Day.
    -->
    <!ELEMENT Rate (Total, UnitRate, Description?)>
    <!ATTLIST Rate
        quantity    %r8;    #REQUIRED
    >
    <!--
        The total for something.
    -->
    <!ELEMENT Total (Money)>
    <!--
        For cXML license agreement information, please see
        http://www.cxml.org/home/license.asp
        $Id: //ariba/cxml/modules/Version.mod#4 $
    -->
    <!--
         Another top-level entity used in Transport.mod.  Defined here to allow
         easy updates to the release version of cXML without opening
         Transport.mod.  This should also provide an easy file to search for
         the current release version string.
    -->
    <!-- cxml.version
        Current default string for the cXML@version attribute.  Corresponds to
        the final directory of the SYSTEM identifier used in all up-to-date
        cXML documents.
        For easy parsing of this file, do not remove whitespace surrounding the
        actual version string.
    -->
    <!ENTITY cxml.version "1.2.019" >
    <!--
        For cXML license agreement information, please see
        http://www.cxml.org/home/license.asp
        $Id: //ariba/cxml/schema/Modules/Supplier.mod#1 $
    -->
    <!--
        Supplier of goods and services. Includes a list of SupplierIDs which
        identify the Supplier.
        corporateURL
            URL to web site about the supplier
        storeFrontURL
            URL to web site where a user can shop or browse
    -->
    <!ELEMENT Supplier (Name, Comments?, SupplierID+, SupplierLocation*)>
    <!ATTLIST Supplier
        corporateURL   %URL;  #IMPLIED
        storeFrontURL  %URL;  #IMPLIED
    >
    <!--
        One of the locations for a supplier. Supplier location is
        generally a physical location.
    -->
    <!ELEMENT SupplierLocation (Address, OrderMethods)>
    <!--
        OrderMethods is the list of methods by which one can order
        from a supplier. The contact element is the technical contact
        who should be able to assist with order processing issues.
        The list is to be ordered by supplier preference, the first
        element having the highest degree of preference.
    -->
    <!ELEMENT OrderMethods (OrderMethod+, Contact?)>
    <!--
        OrderMethod is a method for ordering. It is comprised of a
        target address for the order and the protocol expected by
        the address.
    -->
    <!ELEMENT OrderMethod (OrderTarget, OrderProtocol?)>
    <!--
        OrderTarget represents an address to which orders can be
        sent.
    -->
    <!ELEMENT OrderTarget (Phone | Email | Fax | URL | OtherOrderTarget)>
    <!--
        OrderProtocol is the communication method to be used when
        communicating an order to a supplier. An example would be "cXML".
    -->
    <!ELEMENT OrderProtocol (#PCDATA)> <!-- string -->
    <!--
        OtherOrderTarget represents an address which is not enumerated by
        default in the OrderTarget Element. This may contain address targets
        beyond the ability of this document to describe.
        name
            Optional name for target.
    -->
    <!ELEMENT OtherOrderTarget ANY>
    <!ATTLIST OtherOrderTarget
        name  %string;  #IMPLIED
    >
    <!--
        Definition of a supplier id.  A supplier id is a (domain, value)
        pair so that suppliers have the flexibility to define their id's
        according to an arbitrary convention (e.g., (DUNS, 12345),
        (TaxID, 88888888)).
        domain
            the domain of the id
    -->
    <!ELEMENT SupplierID (#PCDATA)> <!-- string -->
    <!ATTLIST SupplierID
        domain  %string;  #REQUIRED
    >
    <!--
       Defines a List of Suppliers that might be associated with a quote Item. Used in
       ItemOut.
    -->
    <!ELEMENT SupplierList (Supplier+)>
    <!--
        For cXML license agreement information, please see
        http://www.cxml.org/home/license.asp
        $Id: //ariba/cxml/modules/Item.mod#6 $
    -->
    <!--
        ID with which the item's manufacturer identifies the item.
    -->
    <!ELEMENT ManufacturerPartID (#PCDATA)> <!-- string -->
    <!--
        Name of the item's manufacturer.
        xml:lang
            The language in which the ManufacturerName is written.  This
        attribute will be required in a future version of cXML.  (Leaving it
        out is deprecated.)
    -->
    <!ELEMENT ManufacturerName (#PCDATA)> <!-- string -->
    <!ATTLIST ManufacturerName
        xml:lang %xmlLangCode; #IMPLIED
    >
    <!--
        Classification is used to group items into similar categories.
        domain
            "name" of classification, ie., SPSC
    -->
    <!ELEMENT Classification (#PCDATA)> <!-- string -->
    <!ATTLIST Classification
        domain  %string;  #REQUIRED
    >
    <!--
         LeadTime specifies, in days, the amount of time required to
         receive the item.
    -->
    <!ELEMENT LeadTime (#PCDATA)>   <!-- uint -->
    <!--
        How the supplier identifies an item they sell.
        If SupplierPartID does not provide a unique key to identify the item,
        then the supplier should generate a key which identifies the part
        uniquely when combined with the SupplierID and SupplierPartID. The
        key is called SupplierPartAuxiliaryID.
        An example is where a Supplier would use the same PartID for an
        item but have a different price for units of "EA" versus "BOX".
        In this case, the ItemIDs should be:
        <ItemID>
            <SupplierPartID>pn12345</SupplierPartID>
            <SupplierPartAuxiliaryID>EA</SupplierPartAuxiliaryID>
        </ItemID>
        <ItemID>
            <SupplierPartID>pn12345</SupplierPartID>
            <SupplierPartAuxiliaryID>
               <foo>well formed XML here</foo>
            </SupplierPartAuxiliaryID>
        </ItemID>
        In this case, the "foo" element must be defined in an internal subset
        sent with the cXML document.  Otherwise, parsers will not be able to
        validate that document.
        In a preferred approach, the sending application may escape the contained
        XML using CDATA sections.  This would appear as:
           <SupplierPartAuxiliaryID>
               <![CDATA[<foo>well formed XML here</foo>]]>
           </SupplierPartAuxiliaryID>
        Finally, the angle brackets could be escaped using XML character
        entities.  This might be a bit harder for humans to read.  For example:
           <SupplierPartAuxiliaryID>
               &lt;foo&gt;well formed XML here&lt;/foo&gt;
           </SupplierPartAuxiliaryID>
    -->
    <!ELEMENT SupplierPartID (#PCDATA)> <!-- string -->
    <!ELEMENT SupplierPartAuxiliaryID ANY>
    <!--
        A unique identification of an item. SupplierID is not required since
        ItemIDs never travel alone.
        ItemIDs used to define a Supplier/Commodity level Blanket Order Item should
        use Empty SupplierPartID tag. These type of items do not have specific part numbers
        at the time of placing the Blanket Order. There will be subsequent release orders
        or invoices that will define the SupplierID.
    -->
    <!ELEMENT ItemID (SupplierPartID, SupplierPartAuxiliaryID?)>
    <!--
        ItemDetail contains detailed information about an item. All the data that
        a user would want to see about an item instead of the bare essentials
        that are represented in the ItemID.
        LeadTime
            time in days to receive the item
    -->
    <!ELEMENT ItemDetail (UnitPrice, Description+, UnitOfMeasure,
                          Classification+, ManufacturerPartID?,
                          ManufacturerName?, URL?, LeadTime?, Extrinsic*)>
    <!--
         Item details specific for items that describe blanket purchase order items.
         This element should only be used for items in a purchase order of
         type "blanket"     
    -->
    <!ELEMENT BlanketItemDetail (Description+, MaxAmount?, MinAmount?,
                                 MaxQuantity?, MinQuantity?,
                        UnitPrice?, UnitOfMeasure?,
                        Classification*, Extrinsic*)>
    <!--
        For cXML license agreement information, please see
        http://www.cxml.org/home/license.asp
        $Id$
    -->
    <!--
        This element captures travel information.  It could be one of four
        types: air, car rental, hotel or rail.
        AirDetail
            Air travel detail.
        CarRentalDetail
            Car rental detail.
        HotelDetail
            Hotel detail.
        RailDetail
            Rail detail.
        PolicyViolation
            List of policy violations (if any) associated with this
            travel line item.
        Comments
            Top level comments for this travel line item (if any).  This
            is not the policy violation comment but a top level comment
            given by the user for this travel line item while in Travel
            Booking Provider's web site.
        TermsAndConditions
            List of Terms and conditions (if any) associated with this
            travel line item.
        confirmationNumber
            A unique confirmation number that is useful to both the
            traveler and the vendor who is providing the service for this
            travel line item.  For example, hotel reservation number or
            e-ticket number from the airline.
        pnrLocator
            Passenger Name Record (PNR) Locator that is useful to the
            Travel Booking Provider.
        quoteExpirationTime
            Date and time that this quote will expire.  This value is
            normally supplied in the PunchoutOrderMessage.  If no value is
            supplied, it is assumed that there is no expiration time or
            date for this quote.
    -->
    <!ELEMENT  TravelDetail ((AirDetail | CarRentalDetail | HotelDetail | RailDetail),
                              PolicyViolation*,
                              Comments?,
                              TermsAndConditions?)>
    <!ATTLIST TravelDetail
        confirmationNumber  %string;        #REQUIRED
        pnrLocator          %string;        #IMPLIED
        quoteExpirationTime %datetime.tz;   #IMPLIED
    >
    <!-- Air -->
    <!--
        Air detail information for the air trip.
        TripType
            Round Trip, One Way, or Multi Leg
        AirLeg
            Different air leg that makes up this air detail.
            For example a round trip from SFO -> TPE with no stops
            will have two air legs.  One air leg from SFO -> TPE
            and another from TPE -> SFO.
        AvailablePrice
            Other available airfare prices that the user did not pick.
        Penalty
            Penalty amount (if any).  This is normally due to changes or
            cancelation of the ticket.
    -->
    <!ELEMENT AirDetail (TripType,
                         AirLeg+,
                         AvailablePrice*,
                         Penalty?)>
    <!--
        Define a single leg in the air travel.
        Vendor
            Airline vendor name and information.
        AirLegOrigin
            Originating airport for this air leg.
        AirLegDestination
            Destination airport for this air leg.
        BookingClassCode
            Airline booking class code.  This is the de-facto
            airline standard.  For example,
            F, FN, P, R, A      - first class
            C, CN, D, J, I, Z   - business class.
            Y, YN, B, BN, M, H, V, VN, O, Q, QN, S,
                K, KN, L, U, T, W - coach class.
        Rate
            Rate for this particular air leg.  If specify, the total
            of all the rate for the different air legs must add up
            to the total the line item level.
        Meal
            Meal information for this air leg (if any)
        travelSegment
            Textual information to identify this travel segment.
            This information is specific to the Travel Booking Provider.
        departureTime
            Departure date and time for this air leg
        arrivalTime
            Arrival date and time for this air leg
        flightNumber
            Flight number for this air leg
        seatNumber
            Seat number for this air leg
        seatType
             Seat type
                 aisle       - Aisle
                 window      - Window
                 middle      - Middle
        upgrade
            Is this ticket an upgrade?
        stops
            The number of stop for this air leg.
            0 if it is a direct flight.  If no information is supplied
            it is defaulted to 0.
        equipment
            The plane equipment information for this air leg
    -->
    <!ELEMENT AirLeg (Vendor,
                      AirLegOrigin,
                      AirLegDestination,
                      BookingClassCode?,
                      Rate?,
                      Meal*)>
    <!ATTLIST AirLeg
        travelSegment   %string;        #REQUIRED
        departureTime   %datetime.tz;   #REQUIRED
        arrivalTime     %datetime.tz;   #REQUIRED
        flightNumber    %string;        #REQUIRED
        seatNumber      %string;        #IMPLIED
        seatType        (window | aisle | middle) #IMPLIED
        upgrade         (yes)           #IMPLIED
        stops           %r8;            #IMPLIED
        equipment       %string;        #IMPLIED
    >
    <!--
        Originating airport for this Air Leg.
        Airport
            Originating airport
    -->
    <!ELEMENT AirLegOrigin (Airport)>
    <!--
        Destination airport for this Air Leg.
        Airport
            Destination airport
    -->
    <!ELEMENT AirLegDestination (Airport)>
    <!--
        Airport information that includes the iso airport code
        Address
            Physical adress of the airport.
        airportCode
            The 3 letter IATA airport code.
    -->
    <!ELEMENT Airport (Address?)>
    <!ATTLIST Airport airportCode %string; #REQUIRED>
    <!---
        Meal information used by air, hotel and rail.
        BookingClassCode
            Code for the meal.  For example, airlines use
              B     - Breakfast
                C     - Complimentary liquor
                D     - Dinner
                F     - Food for purchase
                G     - Food and beverage for purchase
                H     - Hot meal
                K     - Continental breakfast
                L     - Lunch
                M     - Meal
                N     - No meal service
                O     - Cold meal
                P     - Liquor for purchase
                R     - Refreshments
                S     - Snack or brunch
                V     - Refreshments for purchase
        Description
            Textual description of the meal, including any special needs
            such as vegetarian or dairy-free.
    -->
    <!ELEMENT Meal (BookingClassCode?, Description?)>
    <!-- Car Rental -->
    <!--
        Car rental information.
        Vendor
            Car rental vendor information.
        CarRentalPickup
            Pickup location for the rental car.
        CarRentalDropoff
            Drop off location for the rental car.
        BookingClassCode
            4 letter code for car.
            1st Letter - M (Mini), E (Economy), C (Compact), S (Standard),
                         I (Intermediate), F (Full size), P (Premium), L (Luxury)
                         V (MiniVan), X (Special)
            2nd Letter - B (2 door), C (2/4 door), D (4 door), T (Convertible),
                         F (Four wheel drive), V (Van), W (Wagon), S (Sport)
                         X (Special)
            3rd Letter - A (Automatic), M (Manual)
            4th Letter - R (A/c), N (No A/C)
        CarRentalFee
            Mutliple car rental fee can be specified to capture the
            break down of different fees.  The total of these fees must
            add up to the total at the line item level.
        LimitedMileage
            Mileage limit information
        AvailablePrice
            Other available prices for car rental that the user did not pick.
        travelSegment
            Textual information to identify this travel segment.
            This information is specific to the Travel Booking Provider.
        pickupTime
            The intended pickup date and time
        dropoffTime
            The intended dropoff date and time
    -->
    <!ELEMENT CarRentalDetail (Vendor,
                               CarRentalPickup,
                               CarRentalDropoff,
                               BookingClassCode?,
                               CarRentalFee+,
                               LimitedMileage?,
                               AvailablePrice*)>
    <!ATTLIST CarRentalDetail
        travelSegment %string;          #REQUIRED
        pickupTime    %datetime.tz;      #REQUIRED
        dropoffTime   %datetime.tz;      #REQUIRED
    >
    <!--
        Physical location where the rental car should be picked up.  This
        is either an Airport or off airport car rental location.
        Airport
            An airport location.
        Address
            Physical address of the car rental location
    -->
    <!ELEMENT CarRentalPickup (Airport | Address)>
    <!--
        Physical location where the rental car should be dropped off.
        This is either an Airport or off-airport car rental location.
        Airport
            An airport location.
        Address
            Physical address of the car rental location
    -->
    <!ELEMENT CarRentalDropoff (Airport | Address)>
    <!--
        This specifies the quantity and the unit of measure of the mileage
        limit.
        UnitOfMeasure
            Unit of measure either miles or kilometers.
        quantity
            The mileage limit amount.
    -->
    <!ELEMENT LimitedMileage (UnitOfMeasure)>
    <!ATTLIST LimitedMileage
        quantity   %r8;      #REQUIRED
    >
    <!--
        Car rental fee information.  CarRentalFee captures the actual
        charges and fee that applies to this rental.  Conditional charges
        such as extra mileages that are over the mileage limit should not
        be specified here but rather in the TermsAndConditions text.
        Total
            Total amount for this car rental fee.  All the total for the rates
            must add up to this amount.
        Rate
            The individual broken-down fee information.
        type
            Type of rate
                baseRate            - Base rental rate
                additionalDriver    - Additional driver fee
                airportAccessFee    - Airport Access fee
                dropOffCharge       - Drop off charge
                vehicleLicensingFee - Vehicle lincensing fee
                touristTax          - Tourist tax
                prepaidGasoline     - Prepaid gasoline charge
                navigationSystem    - Navigation system
                childSeat           - Child seat charge
                luggageRack         - Luggage rack charge
                collisionDamageInsurance    - Collision damage insurance
                liabilityInsurance          - Liability insurance
                mobilePhone         - Mobile phone base charge
                other               - Other charges.
    -->
    <!ELEMENT CarRentalFee (Total, Rate*)>
    <!ATTLIST CarRentalFee
        type (baseRate | additionalDriver | airportAccessFee | dropOffCharge |
              vehicleLicensingFee | touristTax | prepaidGasoline |
              navigationSystem | childSeat | luggageRack | collisionDamageInsurance |
              liabilityInsurance | mobilePhone | other) "baseRate"
    >
    <!-- Hotel -->
    <!--
        Hotel detail information.
        Vendor
            Hotel vendor information.
        Address
            Physical address of the hotel.  This is might be different
            from the address specified in the Vendor field as the vendor
            address might be the head quarter address.
        RoomType
            The type of room reserved.
        BookingClassCode
            Hotel booking class code.
        Meal
            Any complementary meals that are included with the room.  For
            example, complementary continental breakfast.
        Rate
            Hotel rate information.  Multiple rates can be specified.  For
            example, the night rate, valet parking rate, and other rates.
        AvailablePrice
            Other available prices that user did not pick.  Available
            prices can be from the same vendor or different vendor.
        travelSegment
            Textual information to identify this travel segment.  This
            information is specific to the Travel Booking Provider.

  • Data Integrator import XSD / DTD error

    Hi experts,
    Really need your help here!  I am trying to import an XSD or DTD schema into BODI.  I have both the XSD and DTD which I generated from the XML source file, using Altova XMLSpy.  BODI is allowing me to select the root element, but when I run the import, the memory usage on my PC against the BODI service goes to 1.5Gb, after which the following error is returned:
    Unknown error when importing metadata. (BODI-1112416)
    When I clear this error and try any other operations in the DI Designer I get out of memory errors and I have to close down the application and restart.  I am running a 4Gb RAM, Intel Core Duo, Windows 7 laptop.  I suspect the XSD / DTD structure is simply to large for BODI to parse.  The XSD and DTD is about 500Kb in size and contain over 16000 rows when viewed in a text editor!
    Any suggestions on how to process this XML in BODI will be greatly appreciated.
    Regards,
    Johann

    Hi,
    replace choice with sequence
    <b><xsd:complexType>
         <xsd:choice>
              <xsd:element name = “A” type=”xsd:string” />
              <xsd:element name= B” type=”xsd:string” maxOccurs=”unbounded” />
         </xsd:choice>
    </xsd:complexType></b>
    is handled identical to
    <b><xsd:complexType>
         <xsd:sequence>
              <xsd:element name = “A” type=”xsd:string” minOccurs=”0” />
              <xsd:element name= B” type=”xsd:string”
    minOccurs=”0” maxOccurs=”unbounded” />
         </xsd:sequence>
    </xsd:complexType></b>
    Regards
    Tarun Telang

  • Exception while importing waveset.dtd file in IDM

    Hi .
    I am trying to import waveset.dtd file in IDM am i got exception
    " An error occurred importing the file, although some of the file data may have been processed. ==> com.waveset.exception.XmlParseException: XML Error: 11:3: The markup in the document preceding the root element must be well-formed."
    actually i am trying to add Cc field for email template.

    I have never come across the scenario to import the DTD file?
    For email , you have to modify the template to incorporate the cc field

  • Import cXml dtd

    We downloaded cxml 1.2 dtd from cxml.org and tried to import into XI external def.  We imported cxml.dtd and received no errors.  When accessing from message mapping and Message Type we are unable to import/select cXml dtd structures/messages.
    How do we import cXml dtd message into XI?
    We have tried to convert to a .xsd file using Xml Spy and are experience namespace errors.

    Hi Frank,
    concerning namespaces the philosophies of DTD and XSD are not compatible (indeed the philosophy of DTD is not compatible with that of XML namespaces itself). As XI is completely XSD-based it is not able to deal with DTDs containing namespace information, although they are well-formed.
    Other tools (like XMLSpy) may try to make a conversion anyway (on a somehow heuristic basis). The result of that maybe imported as External Definition, but sometimes it is necessary to make some adjustments to the XSD.
    According other DTDs coming from cxml I cannot tell you, because I do not know. Anyway, the namespace information is an important information which cannot be left out. If the XML structure defined by cxml really uses xml namespaces, then DTDs are not a suitable way to describe this structure (as explained above). XML structures with namespaces should always be described using XSD.
    Greetings Stephan

  • Error while importing music in iMovie 11 From itunes 10

    Error while importing music in iMovie 11
    I have the same error explained in a other post which was still left unanswered
    I have this sound problem after reorganising folders by itunes, i tried to delete al files in itunes and also
    deleted the xml file in the itunes dir, created new playlists, but still i have no music sound in imovie timeline
    after dragging a mp3 into it. When i preview the file in imovie it souds ok.
    Also i see the red dot with the number 1 in the itunes logo while dragging the mp3.
    Is there a solution for this problem?
    Former post;
    Re: Error while importing music in iMovie 09 from iTunes 09
    Posted: Jul 24, 2010 8:08 AM   in response to: vincentplaces  
    I'm having the exact same issue, but still haven't figured out what it is. I note that at the top of this thread it indicates that there are two "helpful" entries and one "solved" entry, but I can't find the solved one, so maybe someone will repost it here or kindly link to it.
    There is one icon missing though.
    As I read through the excellent tutorial at http://www.kenstone.net/fcphomepage/imovie_09stone.html I scroll down to the point where he talks about dragging music in from iTunes, which is what I'm trying to do. I can see, in his screen shot, the extra little icon that is a red oval and a white "1" in it. I don't get that icon when I am trying to drag my music into the video. I do get the green and white plus icon when I try to drag my music in. Also I DO get BOTH the red 1 and the green plus when I try dragging in a sound effect, which I can do with no problem. But why not the music?
    I've been able to drag in music with no problem in other productions, so I can't figure out what is going on with this one. I'm sure there is a setting somewhere that got flipped, but I can't figure out where.
    In desperation I also tried adding an extra title slide at the end of my video just to make sure there is more video time than music time in the production, but that didn't help at all.
    Any help guys?
    iMac 27"   Mac OS X (10.6.4)    

    Hi
    Due to some kind of copy protection in iTunes - I don't copy directly from this in iMovie
    to my projects. (Most often the result of doing it in iMovie is a DVD without any sound)
    I do
    • In iTunes - collect needed audio into a new Playlist
    • then burn this out as an Audio-CD .aiff (NOT .mp3)
    • This CD I copy into a folder on my Mac (often containing other material that's connected to the project)
    • And then I drag and drop these .aiff files into my movie project in iMovie.
    This works Greatly and even more so when I do my DVD.
    Yours Bengt W

  • Error while importing a new CERT in oracle 10G B2B

    Hi All,
    I am trying to upload a new certificate in 10 G B2B server, its not updating a certificate, I am facing the below error while importing
    Error
    An error occurred when updating the certificate.
    Error -: AIP-16001: The model validation engine failed due to an internal system error.
    Error -: AIP-11052: Writing following objects: Certificate failed due to following constraint violation: CERTIFICATE. CAN NOT UPDATE UNVERSIONABLE OBJECT IN A VALIDATED CONFIGURATION.
    Note: Please help me in resolving this ASAP.
    Regards
    Sai

    Hi Sai,
    It seems you are updating certificate in a delivery channel which is being used in a validated (or may be deployed) agreement. Please retire/purge any deployed configuration which is using that delivery channel and also make sure no such agreement is in valid state(which is using this delivery channel).
    Regards,
    Anuj

  • Error while importing a table index.

    Hi,
    We are facing a problem while importing an index to the production region. Below are the details.
    1. A secondary index was created on standard SAP table ILOA in DEV region.
    2. The Index was successfully moved to the Quality system, without any glitches.
    3. Due to some issue (releated to testing, for which we had to revert back the changes), we had to delete the index on ILOA in the DEV region. The transports were moved to the PPD region and hence, the index on ILOA was deleted in PPD also.
    4. Once the issue related to testing was resolved, we again created an index on the table ILOA and moved it to PPD.
    All these 4 mentioned steps happened successfully and in PPD there was no error while importing the transports.
    But, while moving the above transports to the Production region, there was an error :
    "Index ILOA~Y could not be activated
    (E - No index ILOA~Y found with status M)"
    Please note that Y is the name of the index that was created on the table ILOA.
    The error code that we have got is "8".
    Can anyone please shed any light on what the issue is?? WE cannot re-import the transports in to Production without analysing this issue,because our client doesnt permit that.
    Thanks and eagerly awaiting a kind reply.
    Regards,
    Raghavendra.

    You've three transports - one to create the index, one to delete, and one to recreate.  It could be that the the third one tried to run before the database had finished with the second?
    Have you looked on SE14 for the actual status on production of the index?
    matt

  • Error while importing N Accounts to 1 Address with UCM Batch Manager

    Hi,
    I got a problem with importing Accounts using the UCM Batch Manager. Previous steps were loading the EIM Tables EIM_UCM_ORG and EIM_UCM_ADRPER. To associate addresses I used the column EIM_UCM_ADRPER.PAR_UCM_ACCNT_UID. No errors occured during an Enterprise Integration Mgr jobs to load the data into SDH tables.
    The error described below occurs if I have N Accounts using one Address. Example:
    h5. Account Name --> City --> Postal Code --> State --> Street
    Account #1 --- Munich --- 80331 --- N/A --- Some Street 1
    Account #2 --- Munich --- 80331 --- N/A --- Some Street 1
    h5. If I try to get the Accounts into the Base tables using the UCM Batch Manager I get the following message from the log file:
    ObjMgrBusCompLog     Error     1     000003084c571160:0     2010-08-03 19:11:14     (odbccon.cpp (2097)) SBL-DBC-00111: An error has occurred writing to a record.
    Please continue or ask your systems administrator to check your application configuration if the problem persists.
    DBCLog     DBCLogError     1     000003084c571160:0     2010-08-03 19:11:14     SQLError: [23000],[Microsoft][SQL Native Client][SQL Server]Cannot insert duplicate key row in object 'dbo.S_ADDR_PER'-Objekt with unique index 'S_ADDR_PER_U1'.
    DBCLog     DBCLogError     1     000003084c571160:0     2010-08-03 19:11:14     SQLError: [01000],[Microsoft][SQL Native Client][SQL Server]The statement has been terminated.
    ObjMgrBusCompLog     Error     1     000003084c571160:0     2010-08-03 19:11:14     (sqlobj.cpp (43735)) SBL-DAT-00381: A record that contains identical values to the record you have created already exists.
    If you would like to enter a new record, please ensure that the field values are unique.
    ObjMgrLog     Error     1     000003084c571160:0     2010-08-03 19:11:14     (adptutils.cpp (5715)) SBL-EAI-04381: For instance of Integration Component 'Account_Business Address', using user key '[City] = "Munich" AND [Postal Code] = "80331" AND [State] = "N/A" AND [Street Address] = "Some Street 1"', a record with identical values already exists in the Siebel database.
    Please ensure that the field values in the input message are unique.
    EAISiebAdpt     EAISiebAdptErr     1     000003084c571160:0     2010-08-03 19:11:15     [0] For instance of Integration Component 'Account_Business Address', using user key '[City] = "Munich" AND [Postal Code] = "80331" AND [State] = "N/A" AND [Street Address] = "Some Street 1"', a record with identical values already exists in the Siebel database.
    Please ensure that the field values in the input message are unique.(SBL-EAI-04381) (0x75017d)
    h5. Result:
    Account #1 gets inserted with Record Type: "Source-Insert"
    Account #2 will not be imported and gets Record Type: "Incomplete"
    Does anyone know how to handle this problem?
    Many Thanks
    Sebastian
    Edited by: user13098670 on 04.08.2010 06:34

    I have selected the option
    Add new metadata and replace existing objetcs. But it is not importing. Also I tried other options like
    1. deleting the existing mapping and tried.
    2. Putting the mapping in recycle bin and try.
    3. Take it from recycle bin.Even during taking it from recycle it is giving me the following error .
    Error occurred importing mapping
    <DWH_CMMDTY_INVC_FACT_MAP/DWH_CMMDTY_INVC_FACT_MAP>
    (at line 141).
    Detailed Error Message:
    API2014: Internal Error: Error in createStage:
    In above all cases it is giving me the error.
    Could you please help?

  • Javac(1.4.2) gives error in import statement

    Hi All,
    I am facing a surprising problem. I have 2 java class files. I write the import statement for second one in the first one. There is no package & these are in the same directory. I have compiled the second one. But when I try to compile the First one. Javac throws error at import statement like below :
    D:\Clubs\oct\6>javac -d . ManojTest.java
    ManojTest.java:1: '.' expected
    import SessionBean;
    ^
    1 error
    My Java Files are as below :
    import SessionBean;
    public class ManojTest
         public static void main(String args[])
    //ManojTest.java
    public class SessionBean
         public static void main(String args[])
    //SessionBean.java
    I have compiled SessionBean.java successfully but when I try to compile ManojTest.java I get error mentioned above.
    However this probelm comes when I use j2se 1.4.2.. but works in j2se 1.3.1..
    Another way could be I use package structure.
    But I can't do any of these, as I have to port my big project to j2se1.4.2.. from j2se1.3.1.. (Live project is running on Tomcat).
    Problems is similar in Unix & Windows both.
    Is this javac compiler issue or there is some setting which I can make.
    I have already included . (dot) in PATH & CLASSPATH environment varibales.
    Please help me out if there is any way around this, as i am stuck up in between
    thank you
    Manoj :confused:

    Use a package and then add that package in your classpathOr don't use a package, leave the file in the default (noname) package, and don't use the import statement. Java will find it in the default package without the import.
    Explicit import statements from the default package are no longer allowed

  • Order Import Erroring while importing closed Order

    Hello,
    I am working on importing closed order for historical purpose and order import is erroring without giving much details. I set the debug level to 5 and log file contains only one error' ORDER IMPORT FAIL DUE TO UNEXPECTED ERROR.
    I am attaching the insert statements for headers and lines. Please review and hope to get a solution from one of the OM gurus here.
    Thanks a bunch in advance.
    Anant
    INSERT INTO OE_HEADERS_IFACE_ALL
    (ORIG_SYS_DOCUMENT_REF
    ,ORDER_SOURCE_ID
    ,ORG_ID
    ,ORDER_NUMBER
    ,ORDERED_DATE
    ,ORDER_TYPE_ID
    ,PRICE_LIST_ID
    ,SOLD_FROM_ORG_ID
    ,SOLD_TO_ORG_ID
    ,CUSTOMER_NUMBER
    ,TAX_EXEMPT_FLAG
    ,TRANSACTIONAL_CURR_CODE
    ,INVOICING_RULE_ID
    ,ACCOUNTING_RULE_ID
    ,PAYMENT_TERM_ID
    ,CREATION_DATE
    ,CREATED_BY
    ,LAST_UPDATED_BY
    ,LAST_UPDATE_DATE
    ,SALESREP_ID
    ,OPERATION_CODE
    ,CLOSED_FLAG --BOOKED_FLAG
    ,DROP_SHIP_FLAG
    ,SHIP_TO_ORG_ID
    ,INVOICE_TO_ORG_ID
    ,SHIP_FROM_ORG_ID
    ,ORIG_SYS_CUSTOMER_REF
    ,ORIG_SHIP_ADDRESS_REF
    ,ORDER_CATEGORY
    ,BOOKED_FLAG)
    VALUES
    ('514'     -- ORIG_SYS_DOCUMENT_REF
    ,1001                    -- ORDER SOURCE ID
    ,'102'                    -- ORG ID          
    ,10001006               -- ORDER NUMBER
    ,SYSDATE               -- ORDERED_DATE               
    ,1021                    -- ORDER TYPE ID
    ,6024                    -- PRICE LIST ID
    ,102                    -- SOLD FROM ORG ID
    ,2632                    -- SOLD TO ORG ID      
    ,'UN1666'               -- CUSTOMER NUMBER
    ,'S'                    -- TAX_EXEMPT_FLAG
    ,'USD'                    -- TRANS CURRENCY_CODE
    ,-2                         -- INVOICING_RULE_ID
    ,1                         -- ACCOUNTING_RULE_ID
    ,5                         -- TERMS_ID
    ,SYSDATE               -- CREATION_DATE
    ,1150                    -- CREATED_BY
    ,1150                    -- LAST_UPDATED_BY
    ,SYSDATE               -- LAST_UPDATE_DATE
    ,-3                         -- SALESREP_ID
    ,'INSERT'               -- OPERATION CODE
    ,'Y'                    -- CLOSED FLAG
    ,'N'                    -- DROP SHIP FLAG
    ,NULL                     -- SHIP_TO_ORG_ID (SITE USE ID FROM RA_SITE_USES_ALL, SITE_USE_CODE = SHIP_TO)
    ,1712                     -- INVOICE_TO_ORG_ID (SITE USE ID FROM RA_SITE_USES_ALL, SITE_USE_CODE = BILL_TO)
    ,103                    -- SHIP FROM ORG ID
    ,NULL                    -- ORIG_SYS_CUSTOMER_REF
    ,NULL                    -- ORIG_SHIP_ADDRESS_REF
    ,'Order'               -- ORDER CATEGORY
    ,'N')                    -- BOOKED_FLAG
    COMMIT
    INSERT INTO OE_LINES_IFACE_ALL
    (ORDER_SOURCE_ID
    ,ORIG_SYS_DOCUMENT_REF
    ,ORIG_SYS_LINE_REF
    ,ORIG_SYS_SHIPMENT_REF
    ,INVENTORY_ITEM
    ,REQUEST_DATE
    ,ORDERED_QUANTITY
    ,ORDER_QUANTITY_UOM
    ,PRICE_LIST_ID
    ,UNIT_SELLING_PRICE --UNIT_LIST_PRICE
    ,ACCOUNTING_RULE_ID
    ,PAYMENT_TERM_ID
    ,SALESREP_ID
    ,CREATION_DATE
    ,CREATED_BY
    ,LAST_UPDATE_DATE
    ,LAST_UPDATED_BY
    ,OPERATION_CODE
    ,DROP_SHIP_FLAG
    ,SHIP_TO_ADDRESS1
    ,SHIP_TO_ADDRESS2
    ,SHIP_TO_CITY
    ,SHIP_TO_POSTAL_CODE
    ,SHIP_TO_sTATE
    ,SHIP_TO_COUNTRY
    ,CLOSED_FLAG
    ,ITEM_TYPE_CODE
    ,INVENTORY_ITEM_ID
    ,DELIVERY_LEAD_TIME
    ,DELIVERY_ID
    ,TAX_EXEMPT_FLAG)
    VALUES
    (1001                    -- ORDER SOURCE ID
    ,'514'          -- ORIG SYS DOC REF
    ,'L4'               -- ORIG SYS LINE REF
    ,NULL               -- ORIG SYS SHIP REF
    ,'KR4R362478-07'     -- ITEM NUMBER
    ,SYSDATE               -- REQUEST DATE
    ,40                    -- ORDER QTY
    ,'EA'                    -- ORDER QTY UOM
    ,6024                    -- PRICE LIST ID
    ,95                -- UNIT LIST PRICE
    ,1                    -- ACCOUNTING RULE ID
    ,5                    -- PAY TERM ID
    ,-3                    -- SALESREP ID
    ,SYSDATE               -- CREATION DATE
    ,1150                    -- CREATED BY
    ,SYSDATE               -- LAST UPDATE DATE
    ,1150                    -- LAST UPDATED BY
    ,'INSERT'               -- OPERATION_CODE
    ,'N'                    -- DROP SHIP FLAG
    ,NULL --'1003 WASHINGTON AVE'     -- SHIP ADD1
    ,NULL --'SUITE 340'          -- SHIP ADD2
    ,NULL -- 'CHICAGO'          -- CITY
    ,NULL -- 60610               -- POSTAL
    ,NULL -- 'IL'               -- STATE
    ,NULL -- 'US')               -- COUNTRY
    ,'Y'
    ,'FG'
    ,7488
    ,1
    ,1
    ,'Y')
    commit
    ---------------------------------------

    Ganapati,
    Did you try passing the customer_number like -1 or some random high number that does not exist in hz_cust_accounts table in the account_number for party_type='PERSON' in the table oe_customer_info_iface_all?
    As I see this check for the first_name||last_name is done only of the customer number is not passed and customer_number is not used any where in the customer creation (if you are using automatic numbering for the customer accounts then you will obviously not passing any value to new_account_number which is used to created).
    Give it a try while I keep myself busy with my airport woes here.
    Thanks
    Nagamohan

  • MII 14.0 SP4 :Migration error while importing SAP BM Templates

    Hi Experts,
    I am facing some migration errors while importing SAP Batch Manufacturing Templates into MII 14.0 SP4.
    There are almost 23 transactions which are not getting imported and the error message for all of them is-
    "Unable to migrate transaction Unable to import file
    <Name of the Transaction>"
    Any first hand experiences will be really helpful for me to proceed further.
    Regards,
    Muddassar Khan

    Hi All,
    Got the solution. The STARTUP.BAT file is been placed in the installation directory(usr/sap) and then it works fine. Also I have installed the patches and all working fine.
    Any way thanks for the answer christian libich.
    Regards
    G.Partheeban

  • Error while import PAR with schedule task

    Hi everybody
    I've the following error while import a new PAR with schedule task in Portal NW04s
    Inner Stack is:
    Unable to lock the local configuration to run import "import_it.tsf.pld.cercapersone.updateadgruppofs.st.prjconfig_config_fwk_service_4692550,4692550_(ready)".
    System error is "LockConfigException: Configuration framework system error: "configuration-lock-service overloaded: cannot acquire central-lock file for config://local"".
    Inner Stack is:
    LockConfigException: Configuration framework system error: "configuration-lock-service overloaded: cannot acquire central-lock file for config://local"
    at com.sapportals.config.fwk.data.ConfigLockManager.lockWithDependent(ConfigLockManager.java:507)
    thanks in advance

    Hi Ram,
    I've encountered the problem only on productive instance with offline deployment (Scheduler Tasks reinitialize CRT). Before a restart I have to make sure it works.
    thanks for your help!
    Gennaro

  • Error: An error occurred importing the file. Detail: File does not exist or

    Hi,
    I am getting the error the below error while importing the file in FDM. I have read and write access to the folder. I tried loading text and excel files, I am getting the same error.
    An error occurred importing the file.
    Detail: File does not exist or access denied.
    Thanks.

    Hi Tony,
    Thanks for the reply.
    I have Oracle Database and the version is 11.1.0.7; So even for this version do I need to have SQLLDR.exe on the server where FDM is installed.
    Thanks,
    Edited by: user10720012 on May 16, 2011 11:42 AM

  • Error While Importing a MDL file

    Hi Guys,
    Here I have a requirement of cloning one module of UAT system as like Prod. I exported the MDL file of that module and trying to import into UAT. The UAT system already has that module, but I want to override the existing mappings.
    When I try to import, OWB is throwing an error.
    To give brief about the actual items, I have a Project (FFH1) in Prod and one of the modules (STG1) need to be copied.
    Here below the error Message:
    MDL1261: Error importing PROJECT FFH1.
    Detailed Error Message:
    MDL1406: Cannot import PROJECT with physical name <FFH1> matching by object identifier because a PROJECT <FFH> with the same business name <FFH_1_3> but different object identifier already exists.
    Import ended at Oct 12, 2009 12:58:20 PM
    Can any one suggest me How to overcome this error Or How to achieve my requirement of copying a single module to another repository.
    Edited by: [email protected] on Oct 12, 2009 2:36 AM

    Hi
    i have got a similar error - the difference is that I have one repository and one of the mappings was deleted. When I tried to import it from an export which was taken earlier in the day and no change was made to any of the mappings in the project except the action of the offending mapping been deleted I got the following error:
    Import started at Jan 6, 2010 3:28:07 PM
    Informational at line 10: MDL1205: PROJECT with Unique Object ID (UOID) <63B9EC83C5BA270CE04400306EF32B09> already exists, so PROJECT with name <COSMOS_MIGRATION> not imported.
    Informational at line 11: MDL1205: ORACLE_MODULE with Unique Object ID (UOID) <6561D379074111DFE04400306EF32B09> already exists, so ORACLE_MODULE with name <COSMOS_MIGRATION.STG_OWB> not imported.
    Error at line 2,107: MDL1261: Error importing ATTRIBUTE COSMOS_MIGRATION.STG_OWB.WIP_LOADED_SPREADSHEETS_DATA.XXCONV_OP_SEQ_NUMBER.INOUTGRP1.TARGET_QTY.
    Detailed Error Message:
    MDL1406: Cannot import ATTRIBUTE with physical name <TARGET_QTY> matching by object identifier because a ATTRIBUTE <COSMOS_MIGRATION.STG_OWB.WIP_LOADED_SPREADSHEETS_DATA.BASIS> with the same business name <INOUT1_5> but different object identifier already exists.
    Import ended at Jan 6, 2010 3:28:11 PM
    I then tried to do the import matching on name but got the following error.
    Import started at Jan 6, 2010 3:38:57 PM
    Informational at line 10: MDL1207: PROJECT with name <COSMOS_MIGRATION> not imported because it already exists.
    Informational at line 11: MDL1207: ORACLE_MODULE with name <COSMOS_MIGRATION.STG_OWB> not imported because it already exists.
    Informational at line 37: MDL1292: Skipping MAPPING <COSMOS_MIGRATION.STG_OWB.WIP_INSTANCES> because it was not requested for import.
    Informational at line 450: MDL1292: Skipping MAPPING <COSMOS_MIGRATION.STG_OWB.WIP_JOBS_WORK_ORDERS> because it was not requested for import.
    Error at line 2,107: MDL1261: Error importing ATTRIBUTE COSMOS_MIGRATION.STG_OWB.WIP_LOADED_SPREADSHEETS_DATA.XXCONV_OP_SEQ_NUMBER.INOUTGRP1.TARGET_QTY.
    Detailed Error Message:
    MDL1408: Cannot import ATTRIBUTE with physical name <TARGET_QTY> matching by physical name because a ATTRIBUTE <COSMOS_MIGRATION.STG_OWB.WIP_LOADED_SPREADSHEETS_DATA.BASIS> with the same business name <INOUT1_5> but different physical name already exists.
    This attributes that the messages are referring to are columns in a table and I can't see where I can change a business name and physical name of a column in a table. What I don't understand is that this mapping created ok, deployed, ran and was included in an export and at no time did an error appear. It first appeared when trying to import it back into the project.
    Has anyone got any ideas how I could get this mapping imported?
    Thanks
    Edwin

Maybe you are looking for