Cost of Elements 12

Why to update Elements 11 @ 12  I must pay mor than to buy Elements 12?
Maybe something is wrong in the offer!
To buy the new version the discount is 40%, to update: no discount!
Creazy!
Max

I'm talking about the offer I saw in Adobe.
Good idea Amazon!
Max
Il giorno 27/nov/2013, alle ore 00:43, Moon52 <[email protected]> ha scritto:
Re: Cost of Elements 12
created by Moon52 in Photoshop Elements - View the full discussion
Don't know the costs you are working with but I just purchased Elements 12 through Amazon.com, with 30 day trial of Amazon Prime for $49 ish then without installing it I used the product key to convert my 30 day Adobe trial to full version.
Seemed like a pretty good deal considering I was in Walmart today and they are selling it for $99.
Sent from my iPhone
Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/5877805#5877805
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/5877805#5877805
To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/5877805#5877805. In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Photoshop Elements at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/thread/416458?tstart=0.

Similar Messages

  • Cost center / Element report downloadable to excel

    Hi
    does anybody know of a cost center/elements total report by period?
    s_alr_87013613 has the information but can not get both values (cost center and elements) in columns that it is usable for excel.
    I looked deeply and could not find anything.
    I searched also the forums and could not find a valid awnser.
    My only workaround is run KSB1 and create a PIVOT which does not really make sense
    also there might be many line items.
    Anybody else has an idea?
    I can not believe it is not available. It seems like such a basic report.
    Thanks so much for your support
    Cheers
    Tim

    Nikolas,
    thanks for the help.
    I decided to make a query on COSP (not COEP due to runtime).
    Cost object i splitt with local fields and field[[first digit:last digit]] function if there is another person looking for the same.
    Cheers
    Tim
    Edited by: Tim Schmid on Jul 4, 2011 5:26 PM

  • Upload cost center/element groups

    Hi everybody,
    Is there any possibility for excel upload of cost center/element GROUPS?
    Thank you for your feedback in advance!
    Greetings,
    Pam

    Hi everybody,
    I meant not to import/export cost center/element groups in/from one system to another but to create them totally new automatically (like it is possible for cost centers via LSMW and excel file).
    The question is if there is one possibility not to create all the cost center/element groups manually (for the first time - if they are existing in one system, I know that it is possible to transfer it to other systems).
    Thanks for your answers!
    Greetings
    Pam

  • Project Cost - WBS Element

    Experts,
    If we collect costs at the Project level (i.e by entering Project Number and not by the WBS Element) on the PO, is there anyway we can kind of split that costs to the WBS Elements - Please note that we are doing a settlement on the costs collected by the project to an AuC during period end.
    All answers/inputs/thoughts would be duly appreciated and rewarded with points.
    Thanks,
    Nandita

    as Venkat said, you CANNOT post cost directly to project definition..
    as per my understanding you have a PO and you want to allocate it to different WBS elements?
    example PO XXXXXX with amount 500; you want say 350 to go to WBSX and 150 to go to WBSY? is that your requirement?
    if yes, you could do manual reposting (500 will go to WBSX then you repost 150 to WBSY)
    or perhaps in your settlement you define more than 1 settlemtn rule and you can allocate it by percentage, amount or equivalence number to several WBS.
    best regards.

  • Costing of elements and employees

    i have the following fields in my COA.
    Company               
    Branch               
    Region               
    Cost Center          
    Account               
    Activity               
    Cost Allocation Flexfield
    The same fields are in the costing KFF.
    Now if the costing is done at Cost Center level then what all i am suppose to enable in Cost Allocation KFF Qualifier?
    please note Cost Center = Department Name
    how will the element links be treated.
    please assist/help me !

    KK
    could you please explain me based on your experience as to what impact it will have on the setup. I am a bit new with this just want to know how the info shall be costed for an employee and the element. Appreciate all ur responses
    Please help/Assist me.
    Thanx
    Account Debit Amount Credit Amount Accrual Type
    TT.DAP.0000.0000.231003.0000 30.00 188.00 (Element Link) This is Basic salary CR and total Deductions DR
    TT.DAP.2001.4001.231027.0000 .00 14.00 (EMP Costing) This is emp ded 1
    TT.DAP.2001.4001.232002.0000 .00 16.00 (EMP Costing) This is emp ded 2
    TT.DAP.2001.4001.530001.0000 188.00 .00 (EMP Costing) This is emp add 1
    Total 218.00 218.00
    Company =TT
    Branch =DAP
    Region =2001
    Cost Center=4001
    Account =231027
    Activity = 0000
    KK Please let me know if i have done correctly...?

  • Best practice for reclassifying Cost Center/Element

    Dear experts,
    Currently the company I'm working for are using SA document (FB50) if there are mistakes when posting cost to Cost Center, they will DR New Cost Center and CR Old Cost Center.
    However, it is seem a bit difficult to trace the changes later on. Hence, I would like to ask for opinions on what is the best practice for reclassifying cost center or cost element.
    Right now, I'm planning to propose of using KB11N to reclassify cost center. Is this a good practice and easy to trace the cost movement? Is there any different with normal journal adjustment via FB50 and KB11N?
    Need some advices from experts.

    Hi:
            Both options are viable. If you reverse posting in FB50 then FI GL account postings will also be reversed and along with cost center postings. Hence here advantage is that cost center reversal will be with referenced to the original document with which wrong posting were made. Disadvantage here is that you will to post the entry again in FB50 . In KB11N you will simply transfer cost center amount from wrong to new one that should be in place of it but here you will have no reference . I personally think reversing posting through FB50 is viable options , reverse postings can be seen in KSB1 as well against that cost center.
    Regards

  • Planned Cost WBS Element = which extractor

    Der all,
    i try to extract the planned cost for an WBS element.
    The extractor 0CO_OM_WBS_2 delivers no data and 0CO_OM_WBS_3 only a few.
    Am I using the correct extractors.
    I want to extract the same figures you can see in R/3 with transaction CJ41.
    Thanks for help !
    Marc

    Hi,
    Please try the 0CO_OM_WBS_1 extractor for WBS Element Costs (Plan). Data can be extracted using Currency Type = 00 (transaction Currency), 10 (CC Currency) and 20 (Controlling area currency).
    Refer to the below link for fields of origin in the extract Structure.
    http://help.sap.com/saphelp_nw04/helpdata/EN/dc/f8ab39bae14c67e10000000a114084/frameset.htm
    Thanks.

  • Cost center & cost element

    Hi Experts,
    Can anybody please tell me,
    What is difference between cost center and cost element.
    what is exact role of both.

    Hi,
    Cost Center
    Definition
    External object (object type K) from Controlling which represents a clear origin of costs.
    If you implement the Controlling component, you can find more information in SAP Library under Cost Center (Financials u2192 Controlling u2192 Cost Center Accounting u2192 Master Data in Cost Center Accounting (CO-OM-CCA) u2192 Cost Center)
    and
    Cost Center Accounting (Financials u2192 Controlling u2192 Cost Element Accounting).
    Use
    By assigning cost centers to organizational objects, you determine where costs incurred by the object are to be charged. The inheritance principle applies: If an organizational object is not assigned a cost center, the cost center assigned to the superior object applies.
    An organizational object may also be assigned more than one cost center. For more information, see Cost Distribution (infotype 1018).
    Integration
    A cost center can be related to the following organizational objects:
    ·        an organizational unit via relationship A 011 (Cost center assignment)
    ·        a position via relationship A 011 (Cost center assignment)
    ·        a work center via relationship A 011 (Cost center assignment)
    Cost Elements
    Definition
    Cost elements classify an organizationu2019s valuated consumption of production factors within a controlling area. A cost element corresponds to a cost-relevant item in the chart of accounts.
    Structure
    We distinguish between primary cost and revenue elements and secondary cost elements.
    Primary Cost/Revenue Elements
    A primary cost or revenue element is a cost or revenue-relevant item in the chart of accounts, for which a corresponding general ledger (G/L) account exists in Financial Accounting (FI). You can only create the cost or revenue element if you have first defined it as a G/L account in the chart of accounts and created it as an account in Financial Accounting. The SAP System checks whether a corresponding account exists in Financial Accounting.
    Examples of primary cost elements include:
    · Material costs
    · Personnel costs
    · Energy costs
    Secondary Cost Elements
    Secondary cost elements can only be created and administrated in cost accounting (CO). They portray internal value flows, such as those found in internal activity allocation, overhead calculations and settlement transactions.
    When you create a secondary cost element, the SAP System checks whether a corresponding account already exists in Financial Accounting. If one exists, you can not create the secondary cost element in cost accounting.
    Examples of secondary cost elements include:
    · Assessment cost elements
    · Cost elements for Internal Activity Allocation
    · Cost elements for Order Settlement
    Integration
    Cost elements in Controlling (CO) are closely related to the general ledger accounts used in Financial Accounting (FI). This is because the SAP System is structured as an Integrated Accounting System:
    Cost elements document which costs (differentiated by category) are incurred within a settlement period, and in which amount. They provide information concerning the value flow and the value consumption within the organization. Cost Element Accounting and Cost Center Accounting/Internal Orders are closely linked in the SAP System. Each posting to an account that is also a cost element, is assigned either to a cost center or order. This ensures that at period-end the data is subdivided by cost elements and cost centers/internal orders for analysis purposes. The following section describes how you can subdivide and characterize cost elements in the SAP System.
    Cost element characteristics depend on the controlling area and the allocation methods used in your organization.
    Hope this helps clarifying your doubt about cost center & cost element.
    Regards,
    Tejas

  • Maintaining sub element Costs for the Service Activity

    Dear Experts & MM Gurus,
    Requirement is to maintain the Sub Cost Elements for the activity and to maintain different unit & Rate for the sub cost elements .
    Scenario is explained below.
    1. while making Purchase Requisition for Services
          in Services Tab at item level i maintained Service Activity and for that activity i had maintained sub cost elements (Such as cost estimate for the activity) like labour cost,material & consumables cost,Transportation cost with the help of Pricing MS0000.
    2. My Concern is i need to maintain different unit and rate for the sub cost elements ,but system is not allowing to maintain different unit from unit available with activity unit.How can i maintain different unit for the Sub cost (pricing elements like PRSO,PRS1,PRS2) .
    EXAMPLE :1. Activity is Laying of Road where unit is AU  and price will be combination of all Sub cost elements .
                      2. Sub Cost Elements like labour cost where unit is man days,system doesnt allow to maintain this unit.
    pl comment /suggest on the above scenario.
    Thanks in Advance ,
    Regds,
    Injeti

    Hi
    For services, U create activity group in AC03.
    U can have upto four levels.
    And Model service specifications u maintain in ML10.
    Then mainatin service conditions in ML33 / ML 39 based on with or with out plant.
    Then create the document, the price will pick it from the conditios u maintained.
    Please check and revert back
    Regards,
    Raman

  • Depreciation as Cost Element (OKTZ)

    Hi,
    I need to see the Depreciation posting as a cost element (OKTZ).
    I´ve already created a cost element called Depreciation, and asigned the depreciation cost elements to it. But even after I´ve executed the transaction KSS4 (Plan Cost Splitting) the Depreciation cost element lines cames zero after the execution of the Material Cost Estimate with Quantity Structure (CK11N).
    I expected to see the cost component elements as the example below:
    Material 6001
    Cost Component | Name of Cost Component | Value
    1        |                 Raw Material            |           1,36
    2         |                M/H                          |          3,02
    3          |               Depreciation               |         0,68
    Raw Material = Primary Cost Element (OBYC)
    M/H = Secondary Cost Element ctg. 43 (Activity Type)
    Depreciation: Primary Cost Element
    Thanks a lot,
    Bruno

    Hi Sridhar,
    I tried to follow this document, but without success.
    I' ve created 2 Costs Component Structures (ME and M2).
    ME:
    - 10 Raw Material
    - 20 Indirect Costs
    - 30 Machine Hour
    M2 (Primary Cost Component Structure):
    - 40 Raw Material
    - 50 Indirect Costs
    - 60 Depreciation
    - 70 Machine Hour
    TransferStructure:
    - 10 Raw Material_________ 10 Raw Material
    - 20 Indirect Costs________ 20 Indirect Costs
    - 30 Machine Hour________30 Machine Hour
    - 30 Machine Hour________40 Depreciation
    But, it´s not working...
    Can you help me?
    regards,
    Bruno

  • XML file too large or XML element too large

    I am attempting to import an xml file into the repository and have it shred into the object-relational tables. I registered a schema and it created object-relational xml_tables, triggers, and types. The full xml file is > 80MB. XDB created all the fields as VARCHAR2(4000).
    error code when importing the full XML file. This is what I need to ultimately fix.
    DECLARE
      res BOOLEAN;
    BEGIN
      res := DBMS_XDB.createResource('/home/pharma/drugbank.xml',
                    bfilename('XMLPHARMA', 'drugbank.xml'),
                    nls_charset_id('AL32UTF8'));
    END;
    COMMIT;
    XML file encounters errors on the import.
    An error was encountered performing the requested operation
    ORA-30951: Element or attribute at Xpath references exceeds maximum length
    ORA-06512 at "XDB.DBMS_XDB", line 315
    ORA-06512 at line 4
    30951.00000 - "Element or attribute at Xpath %x exceeds maximum length"
    *Cause: An attempt was made to insert a node of length exceeding the maximum length (specified by the maxLength facet) into an XML document.
    *Action: Do not attempt to add a node exceeding the maximum length to XML documents.
    Vendor code 30951Error at Line:18I would guess that some of the fields have max lengths > 4000. I plan to annotate the schema with SQLType="CLOB", but need to know which fields to change. I was able to copy the xml file and reduce that xml file to one record, which imported into the tables. My plan was to write a view over the bfile to get the lengths of certain fields, annotate the .xsd with CLOBS where needed, and then import again. In order to do that, I have a 1 record file imported into a table and as a bfile.
    Here is my code selecting length from a generated object-relational table of only one record.
    CREATE OR REPLACE VIEW pharma.drugs_vw AS
    SELECT d.*
    FROM drugs, XMLTABLE
      ('/drugs' PASSING OBJECT_VALUE COLUMNS
        drugbank_id        VARCHAR2(20)   PATH 'drug/drugbank-id',
        name               VARCHAR2(50)   PATH 'drug/name',
        description        VARCHAR2(4000) PATH 'drug/description'   
      ) d
    select max(length(drugbank_id)) as dbidlen,
          max(length(name)) as nmlen,
          max(length(description)) as desclen
    from drugs_vw;
            DBIDLEN           NMLEN         DESCLEN
                  7               9             229
    1 row selected.Here is the code for the bfile. Same results, but using deprecated functions. I read the whitepaper, Oracle XML DB: Best practices to get optimal performance out of XML Queries. It says that extract(), extractvalue(), Table(XMLSequence()), and XMLType() are deprecated in 11gr2.
    -- Note extractvalue is deprecated in 11gr2 replaced by W3C standard
    --                                          XMLCast(XMLQuery())
    -- TABLE(XMLSequence) is replaced by XMLTable
    -- XMLType() is replaced by XMLParse()
    SELECT max(length(extractvalue(column_value, '/drug/drugbank-id'))) dbidlen,
           max(length(extractvalue(column_value, '/drug/name'))) nmlen,
           max(length(extractvalue(column_value, '/drug/description'))) desclen
    FROM TABLE(XMLSequence(XMLTYPE(bfilename('XMLPHARMA',
    'db00001.xml'),nls_charset_id('AL32UTF8')).extract('/drugs/drug'))) d
    WHERE ROWNUM <= 5;
            DBIDLEN           NMLEN         DESCLEN
                  7               9             229Is this better code for getting the maximum length of xml fields from a bfile? Here is what I have so far. This works on a single drugbank-id.
    SELECT max(length(drugbank_id)) AS dbidlen,
           max(length(name)) AS nmlen,
           max(length(description)) AS desclen
    FROM (XMLTABLE('*'
                    PASSING (XMLType(bfilename('XMLPHARMA', 'db00001.xml'),nls_charset_id('AL32UTF8')))
                    COLUMNS
        drugbank_id        VARCHAR2(20)   PATH 'drug/drugbank-id',
        name               VARCHAR2(50)   PATH 'drug/name',
        description        VARCHAR2(4000) PATH 'drug/description'
    );I try to run it on the full file and get this error
    Error report:
    SQL Error: ORA-31011: XML parsing failed
    ORA-19202: Error occurred in XML processing
    LPX-00007: unexpected end-of-file encountered
    31011. 00000 -  "XML parsing failed"
    *Cause:    XML parser returned an error while trying to parse the document.
    *Action:   Check if the document to be parsed is valid.The code to create schema and object-relational tables. This worked fine.
    set serveroutput on
    -- Create resource file for schema
    DECLARE
      res BOOLEAN;
    BEGIN
      res := DBMS_XDB.createResource('/home/pharma/drugbank.xsd',
                    bfilename('XMLPHARMA', 'drugbank.xsd'),
                    nls_charset_id('AL32UTF8'));
      COMMIT;
    END;
    -- optional debugging of create types and tables if you want a trace
    ALTER SESSION SET EVENTS = '31098 TRACE NAME CONTEXT FOREVER';
    BEGIN
      DBMS_XMLSCHEMA.registerSchema(
          SCHEMAURL => 'http://localhost:8080/home/pharma/drugbank.xsd',
          SCHEMADOC => bfilename('XMLPHARMA', 'drugbank.xsd'),
          CSID      => nls_charset_id('AL32UTF8'),
          LOCAL     => TRUE,
          GENTYPES  => TRUE,
          GENTABLES => TRUE,
          OWNER     => 'PHARMA');
      COMMIT;
    END;
    SQL> select * from v$version;
    BANNER
    Oracle Database 11g Release 11.2.0.2.0 - Production
    PL/SQL Release 11.2.0.2.0 - Production
    CORE    11.2.0.2.0      Production
    TNS for 32-bit Windows: Version 11.2.0.2.0 - Production
    NLSRTL Version 11.2.0.2.0 - ProductionThe xml schema follows. Sorry about the length, but I think I might break something if I snipped it.
    <?xml version="1.0" encoding="UTF-8"?>
         <xs:schema 
         xmlns:xs="http://www.w3.org/2001/XMLSchema" 
         xmlns:xdb="http://xmlns.oracle.com/xdb"
         >
         <!-- General type definitions -->
         <xs:simpleType name="DecimalOrEmptyType">
              <xs:union memberTypes="xs:decimal EmptyStringType"/>
         </xs:simpleType>
         <xs:simpleType name="EmptyStringType">
              <xs:restriction base="xs:string">
                   <xs:enumeration value=""/>
              </xs:restriction>
         </xs:simpleType>
         <!-- Element Definitions -->
         <!-- Drug secondary accession number definition begins -->
         <xs:element name="secondary-accession-numbers" xdb:defaultTable="SECONDARY_ACCESSION_NUMBERS">
              <xs:complexType>
                   <xs:sequence maxOccurs="unbounded" minOccurs="0">
                        <xs:element name="secondary-accession-number" type="xs:string"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <!-- Drug secondary accession number definition ends -->
         <!-- Drug groups definition begins -->
         <xs:element name="groups" xdb:defaultTable="GROUPS">
              <xs:complexType>
                   <xs:sequence maxOccurs="unbounded" minOccurs="0">
                        <xs:element name="group">
                             <xs:simpleType>
                                  <xs:restriction base="xs:string">
                                       <xs:enumeration value="approved"/>
                                       <xs:enumeration value="illicit"/>
                                       <xs:enumeration value="experimental"/>
                                       <xs:enumeration value="withdrawn"/>
                                       <xs:enumeration value="nutraceutical"/>
                                  </xs:restriction>
                             </xs:simpleType>
                        </xs:element>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <!-- Drug groups definition ends -->
         <!-- Drug taxonomy definition begins -->
         <xs:element name="substructure">
              <xs:complexType>
                   <xs:simpleContent>
                        <xs:extension base="xs:string">
                             <xs:attribute name="class" type="xs:string" use="required"/>
                        </xs:extension>
                   </xs:simpleContent>
              </xs:complexType>
         </xs:element>
         <xs:element name="substructures" xdb:defaultTable="SUBSTRUCTURES">
              <xs:complexType>
                   <xs:sequence maxOccurs="unbounded" minOccurs="0">
                        <xs:element ref="substructure"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="taxonomy" xdb:defaultTable="TAXONOMY">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="kingdom" type="xs:string"/>
                        <xs:element ref="substructures"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <!-- Drug taxonomy definition ends -->
         <!-- Drug brands definition begins -->
         <xs:element name="brands" xdb:defaultTable="BRANDS">
              <xs:complexType>
                   <xs:sequence maxOccurs="unbounded" minOccurs="0">
                        <xs:element name="brand" type="xs:string"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <!-- Drug brands definition ends -->
         <!-- Drug mixtures definition begins -->
         <xs:element name="mixture">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="name" type="xs:string"/>
                        <xs:element name="ingredients" type="xs:string"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="mixtures" xdb:defaultTable="MIXTURES">
              <xs:complexType>
                   <xs:sequence maxOccurs="unbounded" minOccurs="0">
                        <xs:element ref="mixture"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <!-- Drug mixtures definition ends -->
         <!-- Drug packagers definition begins -->
         <xs:element name="packager">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="name" type="xs:string"/>
                        <xs:element name="url" type="xs:string"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="packagers" xdb:defaultTable="PACKAGERS">
              <xs:complexType>
                   <xs:sequence maxOccurs="unbounded" minOccurs="0">
                        <xs:element ref="packager"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <!-- Drug packagers definition ends -->
         <!-- Drug manufacturers definition begins -->
         <xs:element name="manufacturer">
              <xs:complexType>
                   <xs:simpleContent>
                        <xs:extension base="xs:string">
                             <xs:attribute name="generic" type="xs:string" use="required"/>
                        </xs:extension>
                   </xs:simpleContent>
              </xs:complexType>
         </xs:element>
         <xs:element name="manufacturers" xdb:defaultTable="MANUFACTURERS">
              <xs:complexType>
                   <xs:sequence maxOccurs="unbounded" minOccurs="0">
                        <xs:element ref="manufacturer"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <!-- Drug manufactures definition ends -->
         <!-- Drug pricing definition begins -->
         <xs:element name="cost">
              <xs:complexType>
                   <xs:simpleContent>
                        <xs:extension base="xs:string">
                             <xs:attribute name="currency" type="xs:string" use="required"/>
                        </xs:extension>
                   </xs:simpleContent>
              </xs:complexType>
         </xs:element>
         <xs:element name="price">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="description" type="xs:string"/>
                        <xs:element ref="cost"/>
                        <xs:element name="unit" type="xs:string"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="prices" xdb:defaultTable="PRICES">
              <xs:complexType>
                   <xs:sequence maxOccurs="unbounded" minOccurs="0">
                        <xs:element ref="price"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <!-- Drug pricing definition ends -->
         <!-- Drug categories definition begins -->
         <xs:element name="categories" xdb:defaultTable="CATEGORIES">
              <xs:complexType>
                   <xs:sequence maxOccurs="unbounded" minOccurs="0">
                        <xs:element name="category" type="xs:string"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <!-- Drug categories definition ends -->
         <!-- Drug affected orgainsms definition begins -->
         <xs:element name="affected-organisms" xdb:defaultTable="AFFECTED_ORGANISMS">
              <xs:complexType>
                   <xs:sequence maxOccurs="unbounded" minOccurs="0">
                        <xs:element name="affected-organism" type="xs:string"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <!-- Drug affected organisms definition ends -->
         <!-- Drug dosage definition begins -->
         <xs:element name="dosage">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="form" type="xs:string"/>
                        <xs:element name="route" type="xs:string"/>
                        <xs:element name="strength" type="xs:string"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="dosages" xdb:defaultTable="DOSAGES">
              <xs:complexType>
                   <xs:sequence maxOccurs="unbounded" minOccurs="0">
                        <xs:element ref="dosage"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <!-- Drug dosages definition ends -->
         <!-- Drug ATC codes definition begins -->
         <xs:element name="atc-codes" xdb:defaultTable="ATC_CODES">
              <xs:complexType>
                   <xs:sequence maxOccurs="unbounded" minOccurs="0">
                        <xs:element name="atc-code" type="xs:string"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <!-- Drug ATC codes definition ends -->
         <!-- Drug AHFS codes definition begins -->
         <xs:element name="ahfs-codes" xdb:defaultTable="AHFS_CODES">
              <xs:complexType>
                   <xs:sequence maxOccurs="unbounded" minOccurs="0">
                        <xs:element name="ahfs-code" type="xs:string"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <!-- Drug AHFS codes definition ends -->
         <!-- Drug Patent definition begins -->
         <xs:element name="patent">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="number" type="xs:string"/>
                        <xs:element name="country" type="xs:string"/>
                        <xs:element name="approved" type="xs:string"/>
                        <xs:element name="expires" type="xs:string"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="patents" xdb:defaultTable="PATENTS">
              <xs:complexType>
                   <xs:sequence maxOccurs="unbounded" minOccurs="0">
                        <xs:element ref="patent"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <!-- Drug patent definition ends -->
         <!-- Drug food interactions definition begins -->
         <xs:element name="food-interactions" xdb:defaultTable="FOOD_INTERACTIONS">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="food-interaction" type="xs:string" maxOccurs="unbounded" minOccurs="0"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <!-- Drug food interactions definition ends -->
         <!-- Drug drug interactions definition begins -->
         <xs:element name="drug-interaction">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="drug" type="xs:integer"/>
                        <xs:element name="description" type="xs:string"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="drug-interactions" xdb:defaultTable="DRUG_INTERACTIONS">
              <xs:complexType>
                   <xs:sequence maxOccurs="unbounded" minOccurs="0">
                        <xs:element ref="drug-interaction"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <!-- Drug drug interactions definition ends -->
         <!-- Drug protein sequences (biotech) definition begins -->
         <xs:element name="protein-sequences" xdb:defaultTable="PROTEIN_SEQUENCES">
              <xs:complexType>
                   <xs:sequence maxOccurs="unbounded" minOccurs="0">
                        <xs:element name="protein-sequence" type="SequenceType"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <!-- Drug protein sequences (biotech) definition ends-->
         <!-- Drug external links definition begins -->
         <xs:element name="external-link">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="resource" type="xs:string"/>
                        <xs:element name="url" type="xs:string"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="external-links" xdb:defaultTable="EXTERNAL_LINKS">
              <xs:complexType>
                   <xs:sequence maxOccurs="unbounded" minOccurs="0">
                        <xs:element ref="external-link"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <!-- Drug external links definition ends -->
         <!-- Drug targets definition begins -->
         <xs:element name="targets" xdb:defaultTable="TARGETS">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="target" type="TargetBondType" minOccurs="0" maxOccurs="unbounded"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <!-- Drug targets definition ends -->
         <!-- Drug enzymes definition begins -->
         <xs:element name="enzymes" xdb:defaultTable="ENZYMES">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="enzyme" type="BondType" minOccurs="0" maxOccurs="unbounded"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <!-- Drug enzmes definition ends -->
         <!-- Drug transporters definition begins -->
         <xs:element name="transporters" xdb:defaultTable="TRANSPORTERS">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="transporter" type="BondType" minOccurs="0" maxOccurs="unbounded"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <!-- Drug transporters definition ends -->
         <!-- Drug carriers definition begins -->
         <xs:element name="carriers" xdb:defaultTable="CARRIERS">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="carrier" type="BondType" minOccurs="0" maxOccurs="unbounded"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <!-- Drug carriers definition ends -->
         <!-- Partner  Pfams definition begins -->
         <xs:element name="pfam">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="identifier" type="xs:string"/>
                        <xs:element name="name" type="xs:string"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="pfams" xdb:defaultTable="PFAMS">
              <xs:complexType>
                   <xs:sequence minOccurs="0" maxOccurs="unbounded">
                        <xs:element ref="pfam"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <!-- Partner  Pfams definition end -->
         <!-- Partner  GO Classification definition begins -->
         <xs:element name="go-classifier">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="category" type="xs:string"/>
                        <xs:element name="description" type="xs:string"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="go-classifiers" xdb:defaultTable="GO_CLASSIFIERS">
              <xs:complexType>
                   <xs:sequence minOccurs="0" maxOccurs="unbounded">
                        <xs:element ref="go-classifier"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <!-- Partner  GO Classification definition ends -->
         <!-- Partner Essentiality definition begins -->
         <xs:element name="essentiality">
              <xs:simpleType>
                   <xs:restriction base="xs:string">
                        <xs:enumeration value="Essential"/>
                        <xs:enumeration value="Non-Essential"/>
                   </xs:restriction>
              </xs:simpleType>
         </xs:element>
         <!-- Partner Essentiality definition ends -->
         <!-- Complex Type Definitions -->
         <xs:complexType name="SequenceType">
              <xs:sequence>
                   <xs:element name="header" type="xs:string"/>
                   <xs:element name="chain" type="xs:string"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="PropertyType">
              <xs:sequence>
                   <xs:element name="kind">
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:enumeration value="logP"/>
                                  <xs:enumeration value="logS"/>
                                  <xs:enumeration value="logP/hydrophobicity"/>
                                  <xs:enumeration value="Water Solubility"/>
                                  <xs:enumeration value="caco2 Permeability"/>
                                  <xs:enumeration value="pKa"/>
                                  <xs:enumeration value="IUPAC Name"/>
                                  <xs:enumeration value="Molecular Weight"/>
                                  <xs:enumeration value="Monoisotopic Weight"/>
                                  <xs:enumeration value="SMILES"/>
                                  <xs:enumeration value="Molecular Formula"/>
                                  <xs:enumeration value="InChI"/>
                                  <xs:enumeration value="InChIKey"/>
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
                   <xs:element name="value" type="xs:string"/>
                   <xs:element name="source">
                        <xs:simpleType>
                             <xs:restriction base="xs:string">
                                  <xs:enumeration value="JChem"/>
                                  <xs:enumeration value="ALOGPS"/>
                                  <xs:enumeration value=""/>
                             </xs:restriction>
                        </xs:simpleType>
                   </xs:element>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="PropertiesType">
              <xs:sequence>
                   <xs:element name="property" type="PropertyType" minOccurs="0" maxOccurs="unbounded"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="SynonymsType">
              <xs:sequence maxOccurs="unbounded" minOccurs="0">
                   <xs:element name="synonym" type="xs:string"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="IdentifiersType">
              <xs:sequence maxOccurs="unbounded" minOccurs="0">
                   <xs:element name="external-identifier">
                        <xs:complexType>
                             <xs:sequence>
                                  <xs:element name="resource" type="xs:string"/>
                                  <xs:element name="identifier" type="xs:string"/>
                             </xs:sequence>
                        </xs:complexType>
                   </xs:element>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="BondActionsType">
              <xs:sequence maxOccurs="unbounded" minOccurs="0">
                   <xs:element name="action" type="xs:string"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="BondType">
              <xs:sequence>
                   <xs:element name="actions" type="BondActionsType"/>
                   <xs:element name="references" type="xs:string"/>
              </xs:sequence>
              <xs:attribute name="position" type="xs:integer" use="optional"/>
              <xs:attribute name="partner" type="xs:integer"/>
         </xs:complexType>
         <xs:complexType name="TargetBondType">
              <xs:complexContent>
                   <xs:extension base="BondType">
                        <xs:sequence>
                             <xs:element name="known-action">
                                  <xs:simpleType>
                                       <xs:restriction base="xs:string">
                                            <xs:enumeration value="yes"/>
                                            <xs:enumeration value="no"/>
                                            <xs:enumeration value="unknown"/>
                                       </xs:restriction>
                                  </xs:simpleType>
                             </xs:element>
                        </xs:sequence>
                   </xs:extension>
              </xs:complexContent>
         </xs:complexType>
         <xs:complexType name="PartnerType">
              <xs:sequence>
                   <xs:element name="name" type="xs:string"/>
                   <xs:element name="general-function" type="xs:string"/>
                   <xs:element name="specific-function" type="xs:string"/>
                   <xs:element name="gene-name" type="xs:string"/>
                   <xs:element name="locus" type="xs:string"/>
                   <xs:element name="reaction" type="xs:string"/>
                   <xs:element name="signals" type="xs:string"/>
                   <xs:element name="cellular-location" type="xs:string"/>
                   <xs:element name="transmembrane-regions" type="xs:string"/>
                   <xs:element name="theoretical-pi" type="DecimalOrEmptyType"/>
                   <xs:element name="molecular-weight" type="DecimalOrEmptyType"/>
                   <xs:element name="chromosome" type="xs:string"/>
                   <xs:element ref="essentiality"/>
                   <xs:element name="references" type="xs:string"/>
                   <xs:element name="external-identifiers" type="IdentifiersType"/>
                   <xs:element name="synonyms" type="SynonymsType"/>
                   <xs:element name="protein-sequence" type="SequenceType" minOccurs="0"/>
                   <xs:element name="gene-sequence" type="SequenceType" minOccurs="0"/>
                   <xs:element ref="pfams"/>
                   <xs:element ref="go-classifiers"/>
              </xs:sequence>
              <xs:attribute name="id" type="xs:integer" use="required"/>
         </xs:complexType>
         <xs:complexType name="DrugType">
              <xs:sequence>
                   <xs:element name="drugbank-id" type="xs:string"/>
                   <xs:element name="name" type="xs:string"/>
                   <xs:element name="description" type="xs:string"/>
                   <xs:element name="cas-number" type="xs:string"/>
                   <xs:element name="general-references" type="xs:string"/>
                   <xs:element name="synthesis-reference" type="xs:string"/>
                   <xs:element name="indication" type="xs:string"/>
                   <xs:element name="pharmacology" type="xs:string"/>
                   <xs:element name="mechanism-of-action" type="xs:string"/>
                   <xs:element name="toxicity" type="xs:string"/>
                   <xs:element name="biotransformation" type="xs:string"/>
                   <xs:element name="absorption" type="xs:string"/>
                   <xs:element name="half-life" type="xs:string"/>
                   <xs:element name="protein-binding" type="xs:string"/>
                   <xs:element name="route-of-elimination" type="xs:string"/>
                   <xs:element name="volume-of-distribution" type="xs:string"/>
                   <xs:element name="clearance" type="xs:string"/>
                   <xs:element ref="secondary-accession-numbers"/>
                   <xs:element ref="groups"/>
                   <xs:element ref="taxonomy"/>
                   <xs:element name="synonyms" type="SynonymsType"/>
                   <xs:element ref="brands"/>
                   <xs:element ref="mixtures"/>
                   <xs:element ref="packagers"/>
                   <xs:element ref="manufacturers"/>
                   <xs:element ref="prices"/>
                   <xs:element ref="categories"/>
                   <xs:element ref="affected-organisms"/>
                   <xs:element ref="dosages"/>
                   <xs:element ref="atc-codes"/>
                   <xs:element ref="ahfs-codes"/>
                   <xs:element ref="patents"/>
                   <xs:element ref="food-interactions"/>
                   <xs:element ref="drug-interactions"/>
                   <xs:element ref="protein-sequences" minOccurs="0"/><!-- Only present for biotech drugs -->
                   <xs:element name="calculated-properties" type="PropertiesType" minOccurs="0"/><!-- Only present for small molecule drugs -->
                   <xs:element name="experimental-properties" type="PropertiesType"/>
                   <xs:element name="external-identifiers" type="IdentifiersType"/>
                   <xs:element ref="external-links"/>
                   <xs:element ref="targets"/>
                   <xs:element ref="enzymes"/>
                   <xs:element ref="transporters"/>
                   <xs:element ref="carriers"/>
              </xs:sequence>
              <xs:attribute name="type" use="required">
                   <xs:simpleType>
                        <xs:restriction base="xs:string">
                             <xs:enumeration value="small molecule"/>
                             <xs:enumeration value="biotech"/>
                        </xs:restriction>
                   </xs:simpleType>
              </xs:attribute>
              <xs:attribute name="updated" type="xs:string" use="required"/>
              <xs:attribute name="created" type="xs:string" use="required"/>
              <xs:attribute name="version" type="xs:decimal" use="required"/>
         </xs:complexType>
         <xs:element name="drugs"  xdb:defaultTable="DRUGS">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="drug" type="DrugType" minOccurs="0" maxOccurs="unbounded" />
                        <xs:element name="partners">
                             <xs:complexType>
                                  <xs:sequence>
                                       <xs:element name="partner" type="PartnerType" minOccurs="0" maxOccurs="unbounded" />
                                  </xs:sequence>
                             </xs:complexType>
                        </xs:element>
                   </xs:sequence>
              </xs:complexType>
              <xs:keyref name="targetPartnerIdKeyRef" refer="partnerIdKey">
                   <xs:selector xpath="drug/targets/*"/>
                   <xs:field xpath="@partner"/>
              </xs:keyref>
              <xs:keyref name="enzymePartnerIdKeyRef" refer="partnerIdKey">
                   <xs:selector xpath="drug/enzymes/*"/>
                   <xs:field xpath="@partner"/>
              </xs:keyref>
              <xs:keyref name="transporterPartnerIdKeyRef" refer="partnerIdKey">
                   <xs:selector xpath="drug/transporters/*"/>
                   <xs:field xpath="@partner"/>
              </xs:keyref>
              <xs:keyref name="carrierPartnerIdKeyRef" refer="partnerIdKey">
                   <xs:selector xpath="drug/carriers/*"/>
                   <xs:field xpath="@partner"/>
              </xs:keyref>
              <xs:key name="partnerIdKey">
                   <xs:selector xpath=".//partner"/>
                   <xs:field xpath="@id"/>
              </xs:key>
         </xs:element>     
    </xs:schema>Query optimizing whitepaper
    http://www.oracle.com/technetwork/database/features/xmldb/xmlqueryoptimize11gr2-168036.pdf

    I attempted to insert the xml file into an xml table and into a relational table with an xml column both based on the schema. I get the same errors.
    -This creates an XML table based on the schema successfully
    CREATE TABLE pharma.drugs_xmltype OF XMLTYPE
    XMLSCHEMA "http://localhost:8080/home/pharma/drugbank.xsd"
    ELEMENT "drugs";
    Table created.
    Elapsed: 00:00:02.67
    SQL>desc pharma.drugs_xmltype
    Name                                                                          Null?    Type
    TABLE of SYS.XMLTYPE(XMLSchema "http://localhost:8080/home/pharma/drugbank.xsd" Element "drugs") STORAGE Object-relational TYPE "drugs1200_T"-- it refers to these types
    create or replace TYPE          "drugs1200_T" AS OBJECT ("SYS_XDBPD$" "XDB"."XDB$RAW_LIST_T","drug" "drug1201_COLL","partners" "partners1202_T")FINAL INSTANTIABLE
    create or replace TYPE          "drug1201_COLL" AS VARRAY(2147483647) OF "DrugType1121_T"
    create or replace TYPE          "partners1202_T" AS OBJECT ("SYS_XDBPD$" "XDB"."XDB$RAW_LIST_T","partner" "partner1203_COLL")FINAL INSTANTIABLE
    create or replace TYPE          "partner1203_COLL" AS VARRAY(2147483647) OF "PartnerType1190_T"
    create or replace TYPE          "DrugType1121_T" AS OBJECT ("SYS_XDBPD$" "XDB"."XDB$RAW_LIST_T","type" "XDB"."XDB$ENUM_T","updated" VARCHAR2(4000 CHAR),"created" VARCHAR2(4000 CHAR),"version" NUMBER,"drugbank-id" VARCHAR2(4000 CHAR),"name" VARCHAR2(4000 CHAR),"description" VARCHAR2(4000 CHAR),"cas-number" VARCHAR2(4000 CHAR),"general-references" VARCHAR2(4000 CHAR),"synthesis-reference" VARCHAR2(4000 CHAR),"indication" VARCHAR2(4000 CHAR),"pharmacology" VARCHAR2(4000 CHAR),"mechanism-of-action" VARCHAR2(4000 CHAR),"toxicity" VARCHAR2(4000 CHAR),"biotransformation" VARCHAR2(4000 CHAR),"absorption" VARCHAR2(4000 CHAR),"half-life" VARCHAR2(4000 CHAR),"protein-binding" VARCHAR2(4000 CHAR),"route-of-elimination" VARCHAR2(4000 CHAR),"volume-of-distribution" VARCHAR2(4000 CHAR),"clearance" VARCHAR2(4000 CHAR),"secondary-accession-numbers" "secondary-accession1122_T","groups" "groups1124_T","taxonomy" "taxonomy1126_T","synonyms" "SynonymsType1131_T","brands" "brands1132_T","mixtures" "mixtures1133_T","packagers" "packagers1137_T","manufacturers" "manufacturers1141_T","prices" "prices1145_T","categories" "categories1151_T","affected-organisms" "affected-organisms1152_T","dosages" "dosages1153_T","atc-codes" "atc-codes1157_T","ahfs-codes" "ahfs-codes1158_T","patents" "patents1159_T","food-interactions" "food-interactions1163_T","drug-interactions" "drug-interactions1164_T","protein-sequences" "protein-sequences1168_T","calculated-properties" "PropertiesType1171_T","experimental-properties" "PropertiesType1171_T","external-identifiers" "IdentifiersType1174_T","external-links" "external-links1177_T","targets" "targets1181_T","enzymes" "enzymes1186_T","transporters" "transporters1188_T","carriers" "carriers1189_T")NOT FINAL INSTANTIABLE -- drugs type
    PHARMA@scidev> desc "drugs1200_T"
    Name          Null?    Type
    SYS_XDBPD$             XDB.XDB$RAW_LIST_T
    drug                   drug1201_COLL
    partners               partners1202_T-- I planned to insert using a subselect and got the same error on the select.
    Error starting at line 1 in command:
    SELECT max(length(drugbank_id)) AS dbidlen
    FROM (XMLTABLE('*'
                    PASSING (XMLType(bfilename('XMLPHARMA', 'drugbank.xml'),nls_charset_id('AL32UTF8')))
                    COLUMNS
        drugbank_id        VARCHAR2(20)   PATH 'drug/drugbank-id'
    Error report:
    SQL Error: ORA-31011: XML parsing failed
    ORA-19202: Error occurred in XML processing
    LPX-00007: unexpected end-of-file encountered
    31011. 00000 -  "XML parsing failed"
    *Cause:    XML parser returned an error while trying to parse the document.
    *Action:   Check if the document to be parsed is valid.--This creates a row in the xmltype table from a single drug file.
    INSERT INTO drugs_xmltype
    VALUES(XMLType(bfilename('XMLPHARMA', 'db00001.xml'),nls_charset_id('AL32UTF8')).CreateSchemaBasedXML(
        'http://localhost:8080/home/pharma/drugbank.xsd'))
    ;-- The create using the full xml file fails.
    INSERT INTO drugs_xmltype
    VALUES(XMLType(bfilename('XMLPHARMA', 'drugbank.xml'),nls_charset_id('AL32UTF8')).CreateSchemaBasedXML(
    'http://localhost:8080/home/pharma/drugbank.xsd'))
    VALUES(XMLType(bfilename('XMLPHARMA', 'drugbank.xml'),nls_charset_id('AL32UTF8')).CreateSchemaBasedXML(
    ERROR at line 2:
    ORA-30951: Element or attribute at Xpath references exceeds maximum length
    Elapsed: 00:01:17.90-- Then I tried the same using a relational table with an xml column
    -- Then I created a relational table with an xml column
    CREATE TABLE pharma.drugs_xmlcolumn_type (drug_xml XMLTYPE)
    XMLTYPE COLUMN drug_xml STORE AS OBJECT RELATIONAL
    XMLSCHEMA "http://localhost:8080/home/pharma/drugbank.xsd"
    ELEMENT "drugs";
    CREATE TABLE succeeded.--This command refers to the following types
    SYS.XMLTYPE(XMLSchema "http://localhost:8080/home/pharma/drugbank.xsd" Element "drugs" ) STORAGE Object-relational TYPE "drugs1200_T"-- This creates a row in the xmlcolumn table from a single drug file.
    INSERT INTO drugs_xmlcolumn_type
    VALUES(XMLType(bfilename('XMLPHARMA', 'db00001.xml'),nls_charset_id('AL32UTF8')).CreateSchemaBasedXML(
        'http://localhost:8080/home/pharma/drugbank.xsd'))
    ;--The create using the full xml file into a relational table with an xml column fails
    INSERT INTO drugs_xmlcolumn_type
    VALUES(XMLType(bfilename('XMLPHARMA', 'drugbank.xml'),nls_charset_id('AL32UTF8')).CreateSchemaBasedXML(
    'http://localhost:8080/home/pharma/drugbank.xsd'))
    VALUES(XMLType(bfilename('XMLPHARMA', 'drugbank.xml'),nls_charset_id('AL32UTF8')).CreateSchemaBasedXML(
    ERROR at line 2:
    ORA-30951: Element or attribute at Xpath references exceeds maximum length
    Elapsed: 00:01:06.74

  • How to Update material cost of user defined org specific cost type

    Hi,
    We need to update material cost sub elements of an item for an org specific and user defined cost type.
    I have inserted a sample row in the CST_ITEM_CST_DTLS_INTERFACE, and running open interface 'Mass Update Material Costs', but the program is not at all processing the rows, the Process_flag remains 1.
    insert into cst_item_cst_dtls_interface
    (inventory_item_id,
    organization_id,
    resource_id,
    usage_rate_or_amount,
    cost_element_ID,
    Process_Flag ,
    last_update_date,
    last_updated_by,
    creation_date,
    created_by
    values
    (96023,
    343,
    52538,
    0.00208012,
    1,
    1,
    sysdate,
    fnd_global.user_id,
    sysdate,
    fnd_global.user_id
    Can someone help me out with this, thanks.
    Regards
    Dasu

    I think there is some confusion.
    "Mass Edit Material Costs" program is used to apply new activity rates to item costs. For this, you don't have to insert records in the interface. You have to define/update the new activity rates using screen.
    To process records in the cost interface tables, you have to run the "Cost Import Process" program.
    For more details, refer to http://download.oracle.com/docs/cd/A60725_05/html/comnls/us/cst/settas06.htm
    Hope this answers your question
    Sandeep Gandhi
    Omkar Technologies Inc.
    Independent Techno-functional Consultant

  • Essence of product cost collectors

    In REM
    what is essence of product cost collector (KKF6n), {As I understand production cost collectors
    are cost carrying elements}, but needs to have more insights like how it captures
    production costs ( i.e through activities, price maintained in accounting view....)
    Does it make any difference if product cost collector is executed before MRP run, or it has
    to be executed only after MRP run

    Dear Eshwer,
    1.Product Cost collector is one of the master data in REM scenario.
    2.This product cost collector is no where related to MRP.
    3.Product Cost collector is used as a cost object in REM scenario,which means all the cost will be
    booked under this product cost collector for that material.
    4.Whatever the confirmations that are done in MFBF or MF41 or MF42N,the cost will get debited or
    credited accordingly for that material and the impact will be seen in the product cost collector.
    5.This product cost collector will be having an order number which will be used for order settlement and
    variance calculation.
    6.For creating a product cost collector you will require a production version.
    7.so whenever you do an assembly or activity or component backflush,the cost will be booked under
    this product cost collector.
    8.So as such there's no relation between MRP and a product cost collector.
    I hope this pints will help you to some extent.
    Revert back with your further queries.
    Regards
    Mangalraj.S

  • How to create File description in cost center planning (T Code -KE13)

    Hi,
    Experts,
    I am creating Cost center planning in KP06 and would like to create my own layout(File Description) using excel. e.g. 01_1P1_IDES1572_001IDES-1572 as this is the standard SAP file description. How to create my own this way as per my excel layout.
    Regards,
    Jagruti Collaco

    <b>Three steps:
    Identify or Create planning layout.
    Identify or Create planning profile.
    Create file description.</b>
    Next upload the data.
    Detailed Steps
    Identify or Create planning layout.
    Identify an existing standard layout or else
    Create planning layout through KP65 (you can also copy a standard and modify it)
    Identify or Create planning profile.
    Go to SPRO>Controlling>Cost Center Accounting >Planning>Manual Planning>Define user defined Planning Profiles.
    Create a new Profile. You will see nodes or folders on the left indicating General Controlling>Layouts for controlling> and Default parameters.
    <b>Choose the layout for controlling and enter the layout you chose in earlier step.
    Enable Integrated excel checkbox and overview (everything you can)
    Next, select the layout and double click on default parameters.</b>
    Enter a test data with cost center, elements, period, version, year. and save all. You may want to save the file as a model in your desktop with a different name say CCAPlan.csv. (You will notice, as you come out a new file description field that was blank earlier is now populated with a name like 01_1P1_(layout name)XXXXXX_Profile Name (XXXXX)
    Come out of the screens.
    Go to KP06, extras. excel upload via extras. or KE13

  • Cost Center on HRMS

    Hi All ....
    I need to know what is the diffrence between three types of cost center on HRMS element link screen:
    1. Fixed Cost
    2. Distributed cost.
    3. Normal Cost.
    How I can determine a flexfied qualifier when i define the cost center FF.
    Regards;

    I need to know what is the diffrence between three types of cost center on HRMS element link screen:
    1. Fixed CostWhen you want to cost the element only to one account, the account you specify in element link then you use Fixed Cost. Mostly this is used for deductions.
    2. Distributed cost.When you want the Cost of some elements to be distributed over your earnings like say you want to cost medicare or social security paid by employer back to the cost center to which earnings are costed.
    3. Normal Cost.This is used when each element entered for employee has different costing. this is generally used for regular hours worked by an employee.
    >
    How I can determine a flexfied qualifier when i define the cost center FF.Qualifiers tells u that which segments you want to define for Costing level. As you can define costing a five levels, payroll, organization, link, assignment and entries, you define at the KFF which segments you want to see at each level

Maybe you are looking for

  • Too much errors/messages in Web Analysis reports stops workspace

    Too often workspace stops to work for the client with the following (example) messages. It seems that too much informational and error messages from reports (like a non working report link or missing member) gives the workspace client so much trouble

  • IWork '09 without paper manual and serial

    I just bought a copy of iWork '09 in a retail store, and noticed two thing: - it has no paper manual (version '08 had the manual, instead) - it has no serial coded (infact I installed if and was not prompted about the serial code; version '08 needed

  • How to process a task asynchronously

    Hi all, I have written a FlexUI command that takes a very long time to finish. How can I do the processing asynchronously? I found that the task queue service could do the trick, but I did not find an example. Can anyone help? Many thanks for your at

  • Patch number for upgrading opatch from 10.2.0.1.0 to 10.2.0.1.1

    Please can someone tell me what is the Patch number for upgrading opatch utility from 10.2.0.1.0 to 10.2.0.1.1? Thanks in advance.

  • Calendar server periodically stops responding

    So periodicaly my calendar sever stops responding. It shows on the server as still running which is confusing to me. I found this entry in the error logs. Another twistd server is running, PID 332 2013-09-26 11:35:07-0700 [-] [caldav-0] 2013-09-26 11