Numbers modifies while importing long numbers

I do have a CSV file with EAN and UPC Codes.
when i do open the CSV file with Numbers, it automaticly formats the sell to "automatic" and downsizes my digit.
Exp.
Code in Overview is still ok:
8024221492019
as soon its open in numbers code changes to
8.02422E+12
Is it possible that Number does not change my files?
thx

It is best to open the csv file in a text editor and replace the commas with tabs, then select ALL, copy, then paste into a Numbers table ALREADY FORMATTED AS TEXT.  To format as text select the table, then use the formatter in the toolbar:

Similar Messages

  • Itunes no longer plays the first CD track etc. while importing?

    Now when I start importing from a CD Itunes no longer starts playing the first track after it has downloaded and the second track begins downloading. I can't see a switch or button that has shut that feature off but Itunes used to play it without being prompted but no longer does. What am I missing?

    hs,
    Just in case you haven't found the answer to your question in other postings, what works is to open the Terminal (found in Apps>Utilities) and type in : -
    defaults write com.apple.iTunes play-songs-while-importing -bool TRUE
    Hit return and then close the Terminal. The next time you open iTunes it should play again as you import cds.
    I guess it's all part of the "Macs are easier to use" policy of Apple :o)

  • TS3899 Battery powered off while composing long important email how to not loose it when battery is charged.

    My iPhone battery accidentally powered off while composing long important email. I've had this happen before and the emAil is gone disappeared, not in drafts etc..is there a way to make sure this doesn't happen when I unplug from charger and try to finish it or will I have to start over?

    You can turn it on while connected to the power source. It may have saved your draft; but if not it is gone. Normally most apps will save work in progress. Were you using the mail app, the gmail app, or the Safari browser? If it was gmail and you were using Safari the gmail.com site will save drafts periodically.

  • Error while importing swf file in to Crystal Xcelsius Designer 4.5

    help me...., Error while importing swf file in to Crystal Xcelsius Designer 4.5

    I read in the book called "CRYSTAL XCELSIUS for DUMMIES" on page 243 under topic called Nesting a Dashboard within another Dashboard.
    sorry i used the wrong word embed, here i am importing the swf using image component.
    My requirement is somethis like this parent child dependency menu.
    eg: i have to two tabs 1)alphabets 2) Numerics  First levet menu
    if you click alphabets tab then the following menu A/B/C/D/..... Z i have diff charts.. under each alphabet.
    If you click numberic tab then the follwing menu should one/two/three/.......ten  here also i have diff charts under number
    in over to avoid complexity in dynamic visibility i divided the into 3 dashboards.  1- alphabets 2- number and 3 -importing both swfs.. everything works fine except first tab and last tab under alphabets and numerics.
    If some one help me with some alernative ... would be great.
    Thanks

  • Lost photos from SD cards in Mac while importing new pictures from iPhone 5

    I imported photos to my MBP iPhoto from my camera, I subsequently selected those photos from my SD cards. After that I tried to import photos from my iPhone 5S to the same MBP. At the end there was an error message saying importing could not be done. Then I found out that the imported photos from my SD cards were gone. Is it because I used both my camera and iPhone the same day? How can I solve this problem?

    Hi Elements User
    The issue is not with how I view them in Elements but how Elements decides to re-name the pictures while importing them from my SD card to my hard drive.  I would expect that it'll re-name the photos while uploading by using the custom name I gave it(ex Europe Vacation) and start the numbers (ex Europe Vacation 0001.jpg) with the oldest picture and work its way up.  However is doing it folder by folder (folders in SD card) and using the chronological order inside each folder. This means that the photos in the most recent folder created by the camera will be re-named 0001-000x and the second most recent folder will be renamed 000x-000y and so on until the last folder.  When I import photos using the Windows Importer it'll custom name each photo using the date/time taken in ascending order regardless of what folder they are in.
    Any additional help will be appreciated as I'd like to use Elements to do the import, if not I'll have to go back and use the Windows Importer.

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

  • Trigger while importing from .csv file

    hey
    i am importing data from .csv file into a table called temp.
    .csv file is having column sales. the data in that also contains some empty filed or N/A or -
    sales coulmn in my table is NUMBER.
    so while importing some column are not able to import.
    how to write a trigger to eliminate '-' or 'N/A' or ' ' values from the sales column before inserting into the table

    It might be easier if the field on temp was a varchar2 field instead?
    The values entered should be loaded into this field and you can then use the trigger to test the values and convert these into numbers or nulls before inserting onto the proper data table.
    Check out the TO_NUMBER() function in SQL for info on how to convert strings to numbers.
    Regards
    Andy

  • Error,while importing METADATA  from production to development

    Folks,
    I am getting the following error while importing the metadata. I have exported from production server and want to do some modification to the existing mappings. Can some body help me to resolve this?
    Here is the error.
    Import started at 10/07/2004 11:12:19 AM
    * Import for OWB Release: 9.0.2.56.0 Version: 9.0.2.0.0
    * User: owb_rep Connect String: (DESCRIPTION=(ADDRESS=(HOST=vectrenabp)(PROTOCOL=tcp)(PORT=1521))(CONNECT_DATA=(SID=SDWSTEST)))
    * Data File: C:\oracle\OWBHome\owb\bin\win32\SDWSDEV-MAPPINGS-20041007_0916.mdl
    * Log File: c:\oracle\OWBHome\owb\bin\win32\Log.log Log Message Level: ALL
    * Physical Names: Y Mode: CREATE Character Set: WE8MSWIN1252
    * Ignore Universal Identifier: N Commit At End: Y
    Informational at line 15: MDL1205: PROJECT with Unique Object ID (UOID) <85247BBFEA1B44C6B10CDB3B70155A63> already exists, so PROJECT with physical name <SDWSDEV> and logical name <SDWSDEV> not imported.
    Informational at line 24: MDL1205: DATAWAREHOUSE with Unique Object ID (UOID) <268F5A9F43364309A8C0D01374C4A867> already exists, so DATAWAREHOUSE with physical name <DWH_TARGET> and logical name <DWH_TARGET> not imported.
    Error at line 141: MDL1247: Error occurred importing mapping <DWH_ZIP_CODE_DMGRPHCS_DIM_MAP/DWH_ZIP_CODE_DMGRPHCS_DIM_MAP> (at line 141).
    Detailed Error Message:
    API2014: Internal Error: Error in createStage:

    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?

  • XPRA_EXECUTION error while importing Support stack 8 in Solution manager 4

    We have installed Solution managr 4.0 on Windows 2003 OS. We are trying to inport support stack 8, but we are getting the XPRA_EXECUTION error while importing SAPKW70009. Following is the error log
    Short text
    Syntax error in program "CL_RSOBJS_TYPE_MANAGER========CP ".
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLRSVERS" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program
    "CL_RSOBJS_TYPE_MANAGER========CP " in include
    "CL_RSOBJS_TYPE_MANAGER========CM00G " in
    line 1:
    "Method "GET_TEXT_OF_SEARCH_ATTRIBUTE" does not exist. There is, howeve"
    "r a method with the similar name "GET_SEARCH_ATTRIBUTES"."
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "SAP "
    What can you do?
    Please eliminate the error by performing a syntax check
    (or an extended program check) on the program "CL_RSOBJS_TYPE_MANAGER========CP
    You can also perform the syntax check from the ABAP Editor.
    If the problem persists, proceed as follows:
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    The following syntax error was found in the program
    CL_RSOBJS_TYPE_MANAGER========CP :
    "Method "GET_TEXT_OF_SEARCH_ATTRIBUTE" does not exist. There is, howeve"
    "r a method with the similar name "GET_SEARCH_ATTRIBUTES"."
    We have tried clearing the queue and restarting the import but it does not work.
    Can anyone please help us with the same.

    Please, i need help. I have a problem when importing SAPKB62030 on phase XPRA_EXECUTION. This is the error:
      The import was stopped, since an error occurred during the phase          
      XPRA_EXECUTION, which the Support Package Manager is unable to resolve    
      without your input.                                                                               
    After you have corrected the cause of the error, continue with the        
      import by choosing Support Package -> Import queue from the initial       
      screen of the Support Package Manager.                                                                               
    The following details help you to analyze the problem:                                                                               
    -   Error in phase: XPRA_EXECUTION                                                                               
    -   Reason for error: TP_STEP_FAILURE                                                                               
    -   Return code: 0008                                                                               
    -   Error message: OCS Package SAPKB62030, tp step R, return code     
              0008                                                                               
    What can i doing?

  • Urgent:Error while importing project in ODI..plz help

    Hi All,
    We are getting below errors after importing the project folder.
    In interfaces having file as source datastores, we are getting below errors
    1) On source datastore,its giving error that "could not build the property panel for an object".
    2) On requesting for data of source datastore it is showing:cannot display data: datastores are not on the same data server
    3) On executing the interface its giving below error:
    --the object no longer exists
    Also, we are not able to see any field of source datastore(technology-File) in Source panel in the interaface after we imported project.
    Message was edited by:
    user625028

    Make sure that, you might have selected Duplicate mode while importing
    and data stores id may be different .

  • Selecting a layer while importing an InDesign Document

    Hello All,
    Does any one know how to select a layer while importing an InDesign document into another document. I have been trying to achieve this since a long time but not able to find the correct API.
    If any one has tried please do let me know.
    Thanks all in advance
    Regards
    Farzana.

    Hello all,
    Some how from previous post I found I would be able to manage layers of the imported document using IGrpahicLayerInfo. With this I am able to get the Layer name and its information. But not able to set the Layers visibility through command. The command is executed successfully but does not reflect in the document.
    Please let me know if anyone has achieved this succesfully.
    Thanks all.
    Regards
    Farzana.

  • Transports while importing  DS error "Source system QAS does not exit "

    Hi Experts,
          For a specific reason we are importing a DS from quality to development.While importing DS in Development side we are getting an error " Source system QAS does not exist".Error message as  below:
       Start of the after-import method RS_ISMP_AFTER_IMPORT for object type(s) ISMP (Activation Mode)
       Source system QAS does not exist
       Start of the after-import method RS_ISTS_AFTER_IMPORT for object type(s) ISTS (Activation Mode)
       There is no DataSource with these attributes
       Start of the after-import method RS_ISTS_AFTER_IMPORT for object type(s) ISTS (Delete Mode)
       Start of the after-import method RS_ISMP_AFTER_IMPORT for object type(s) ISMP (Delete Mode)
       Start of the after-import method RS_ISCS_AFTER_IMPORT for object type(s) ISCS (Delete Mode)
       Start of the after-import method RS_ISTD_AFTER_IMPORT for object type(s) ISTD (Delete Mode)
       Start of the after-import method RS_ROUT_AFTER_IMPORT for object type(s) ROUT (Delete Mode)
       Errors occurred during post-handling RS_AFTER_IMPORT for ISCS L
       The errors affect the following components:
          BW-WHM (Warehouse Management)
       Post-import methods of change/transport request CXCK900023 completed
            Start of subsequent processing ... 20090306024549
            End of subsequent processing... 20090306024550
       Execute reports for change/transport request: CXCK900023
       Reports for change/transport request CXCK900023 have been executed
            Start of................ 20090306024550
            End of.................. 20090306024550
       Execution of programs after import (XPRA)
       End date and time : 20090306024550
       Ended with return code:  ===> 8 <===
    Our system sap bi is not new system, we are using from long time.Transports are working while moving dev to quality and quality to prod.
    Can any body suggest on this.
    Regards
    Vinod

    Hi vinod kumar,
    i hope you need to map source system From QAS to DEV system,
    genereally from DEV to QAS configuration will be there, but here request is moving from QAS to DEV so i think this should be configured.
    RSA1-> Tools -> conversion of logical system names -> maintain original system and target system name for both BI and ECC systems.
    Regards
    Daya Sagar

  • While importing from my digital camera (Olympus XZ-2), iMovies quits, WHile importgin from my digital camera (Olympus XZ-2), iMovies quits

    While importing from my digital camera (Olympus XZ-2), it "unexpectedly quits" - seems to happen on slightly larger clips (over 90 seconds) - not sure if it is related to the model camera or iMovie 11'. Any advice?

    Lion is 10.7, Snow Lepoard is 10.6, Leopard is 10.5.
    I woul strongly recomend you update to 10.6.8 (the last snow lepoard update) for a number of reasons. First 10.6.8. is a solid OS at this point you won't have to many (or any) gotcha's. Second Leopard (10.5.x) is going away. Pretty sure there will be no more updates for it at this point. If not it won't be long before that happens. Also you will need to have 10.6.8 installed in the event you want to at some point upgrade to Lion.
    But finally perhaps the most important point if you don't have 10.6.8 you can't acess the App Store and if you can;t acess the App Store you will need to get the boxed version of Aperture 3. The differerence in price between the boxed version and the App Store version will more then pay for the upgrade to Snow Leopard. In fact you should have  a fair bit of change left over.
    good luck

  • Line truncation error while importing ECC 6.0 transports in R/3 4.6C

    Hi,
    We are trying to import few objects which have been created in ECC6.0 into SAP 4.6C system.
    While importing the transport we are getting errors for all lined of code which exceed 72 characters. The transport log shows the following error:
    *line XYZ is too long, truncated from 255 to 72 bytes. *
    Any suggestions to remove this error ?
    Thanks.
    Harmeet.

    Frnds ,
    I think I got the solution !
    Thx anyways....

  • Problem while importing NWDI components in CRM5.0.

    Hi All,
        I'm facing problem while importing NWDI components in CRM5.0. Imports are running for long time and failing.
    Could anyone please help me out.
    Thanks in advance.
    Regards,
    Deepthi.

    Thanks for your replies.
    Can any one guide me Is there any need to deploy once again into production  after or before importing into production through NWDI?
    From development i released activities and able to see them in NWDI(CMS). I was able to successfully import in consolidation and even approved it without any errors. But when I tried to import in production tab , I am facing above problem.
    Can any one explain me do I need to deploy directly into production (through NWDS) in WebDynpro perspective before importing into production from NWDI?
    As far as my understanding if I import successfully into production I may need not to deploy it again.

Maybe you are looking for