Error while settling Commodity futures 70D while TBB1

Hi
We are getting both profit as well as loss when we run TBB1 for settlement of Commodity futures
for Product type 70D.
We have added brokerage, service tax in other flows both in purchase and sale transaction.
The other flows of purchases are coming as loss and other flows from sales transaciton are
getting reduced from the profits. We understand some issue with DBT_B020 (Derived flow for
Variation margin Loss).
We are expecting the other flows of purchase transaciton to be deducted from profits as it is
doing for other flows of sale transaciton.
Wanted to check here whether any config needs to be done to arrive at this.
Example
Purchase transaction
Purchase value Rs 1,00,000-
Other flows      Rs    2,000-
Total cost     Rs 1,02,000-
Sale transaciton
Sale value     Rs 1,20,000+
Other flows    Rs    2,000-
Total cost     Rs 1,18,000+
But we are getting two entries
1. Profit on sale  Dr.       Rs 18,000
      To. Margin Variantion  Rs 18,000
And
2. Margin Variantion  Rs 2,000
       T0. Loss on sale   Rs  2,000
When we run TBB1 we expect only one entry for profit of Rs. 16,000
Regards
Venkat

Similar Messages

  • Error while running Internal Order Settlement (KO88)

    Hi,
    We are in ECC 6.  We are facing an error while settling one internal order using T.Code KO88.
    The error message says :
    Execute amount settlement up to and including settlement period 001 2009 first
    Message KD262
    We have already settled the internal order upto previous month. But, we are unable to settle the order for the current month.
    Any suggestion please.
    Regards,
    Ganesan

    In production Order maintain Settlement type as Full Settlement.
    In CO01 Create production Order or CO02 Change production order go to
    Header -
    > Settlement Rule
    Maintain Category, Receiver, Percentage, FUL (as settlement type)
    Change settlement type to FUL if it is PER.
    PER Settlement Type - Only settles the cost incurred on the posting period
    FUL Settlment Type - Settles all the cost incurred after the previous costing run

  • Error while doing AIAB Settlement

    Hi I am facing the below error while doing AIAB during AUC settlement. Please do the needful.
    Data for determination of capitalization not managed in area 01
    Message no. AW507
    Diagnosis
    You have chosen a depreciation area, which does not carry the depreciation data from table COEPBR.
    Procedure
    Choose a different depreciation area.
    Thanks
    KC

    Hi,
    This message could be helpful:
    Error AW507
    Please check the field T082AVIEWB-AUTHORITY. If it is not on 2 this is the reason.
    In this case, you can change the value in T093-VIEW1 using the coding as per SAP note 29706 which you have already discovered. There will be no risk involved in changing this value.
    regards Bernhard

  • Error while settlement of Internal order

    Dear All
    I am getting the following error while executing KO88 "Choose transaction type and base value appropriate for asset values".
    The settlement and posting period are 12 and the processing type is "Partial Capitalization".
    Pls advice
    Rgds
    Nitika

    hi.....
    check you settlemnt rule for internal order. forsure you will find mismatch between settlemnt rule and actual settlemnt. check in settlement rule the % to be settled.
    Regards
    Manish Jain
    Pls assign points if your problem get solved.

  • Error while doing AUC Settlement in KO88

    Hi
    I am getting the below error while doing KO88. I have maintained the Allocation structure for FXA and given the cost element group in the Source field & Given FXA in Receiver category and selected By cost element option aginast Receiver category FXA in Settlement Cost Element field. I am getting the below error while settling in KO88.
    Define a settlement cost element for receiver type FXA
    Message no. KD506
    Diagnosis
    In allocation structure A1 (controlling area BP01), you did not define which cost element should be used when settling costs/revenues of the sender. Nor did you define receiver type FXA.
    Procedure
    Assign a different allocation structure to the settlement sender (-> Master data -> Settlement rule -> Goto -> Settlement parameters), or maintain allocation structure A1.
    Please help me
    Thanks
    Kishore

    Please check your allocation structure , it looks that settlement cost element that you have assigned in the allocation strcuture is not having correct cost element category.
    regards
    Ranjan

  • Error while doing settlement from WBS to P&L Account

    Hello
    I am trying to do a settlement from WBS to P&L Account(Expense account). In this case, "Dummy" Prof Ctr is getting derived from 0KE5 (we have maintained a dummy prof ctr). We have set the validations to disallow any postings/settlements to dummy prof ctr. Hence I am getting an error while doing settlement.
    Now I am maintaning a Prof ctr in my WBS master data. I am unable to understand why system is deriving dummy prof ctr and not the one maintained on WBS master data. The settlements are working fine when I do them against Balance sheet accounts and proper prof ctr is getting derived, which is being maintained on WBS master data. I am getting trouble only while doing settlement to my P&lL i.e. expense accounts.
    can anyone throw some light on this?
    Thks
    Sarang

    Dear Sarang,
    You have maintained profit center in WBS master which is not updated at the time settlement to FI that what makes you worried. If you are making FI posting and give WBS as an additional account assignment then Profit center in WBS master will be updated. Here in settlement WBS is sender not the receiver so that profit center will not be updated. In settlement receiver (any) is debited and sender (WBS) is credited so this credit entry will be updated in profit center.
    To your second query that when you carry out settlement to balance sheet account right profit center is updated then please make sure, that balance sheet account is maintained in 3KEH with profit center or OKB9.
    Your P&L account (expense) receives dummy profit center because it is not able to find cost center which can fetch profit center from the master. So, if you can afford, maintain that cost elements (expense account) with profit center in OKB9.
    might help you..........................................................

  • Error while doing settlement

    Hi,
    I am getting the below error while doing the settelment
    Program Errors: no COBRB found 001
    Kindly advice me
    Thanks
    Supriya

    Hi Supriya,
    COBRB is table for Settlement Rules for Order Settlement. Debug if the Table itself is missing or table contains no entries to be picked up for settlement...
    Pls revert back with update...
    Srikanth Munnaluri

  • Error while transferring Forwarding settlement document to ERP Billing

    Hi Experts,
    My forwarding settlement document is consistent.
    All the basic customizing in SAP ERP, TM has been completed as follows, but getting error while transferring forwarding settlement document to ERP billing (Ref. 1st screenshot).
    I am using SAVE AND TRANSFER button to send the document to ERP, also same error is displaying while using PREVIEW INVOICE button (Ref.2nd screenshot)
    Please suggest if I missed anything to send forwarding settlement document to ERP.
    Customizing settings for transferring Forwarding settlement document to SAP ERP.
    1. In SD Billing all condition types has been maintained, pricing procedure determination configured.
    2. In SAP ERP SD condition types mapped to TM charge types using following path.
    Integration with other sap components - Transportation management - Invoice integration - Billing - Definition for transportation charge elements - Define charge types.
    3. Assignment of charge types in ERPSD
    4. Define charge category, subcategory codes
    5. Mapped ERP SD, TM sales organization with logical TM system, sales area, Order type, Billing type, Pricing procedure
    6. Output types determination configured for ERP Billing in SD

    Dear Serhat,
    I don't think this is an RFC problem or an error. But you wrote:
    When I checked why its value is 'X', I saw that if the RFC destination and the current system are the same, then lv_no_commit = 'X', (means if the R3 and the GTS are in the same server, same client.)
    It is impossible to have GTS and R/3 on the same system and same client. At least the client should be different. So try to check why the call is performed like that.
    Balazs

  • Getting 'Maintain Settlement Rule' Error while GI

    Hello Friends,
    While posting GI through MB31, I am getting an error of settlement rule, I was wondering what the error of kind and how to resolve it.... what are the entries need to make ?
    Regards,
    Rahul

    Hi,
    Actually you are doing GR through MB31, go to order change CO02 and in the menu to to Header tab and click Settlement rule from the menu. In that screen whether settlement rule is assigned or not, if it not assigned assign a receiver (category) and percentage and save.
    (In this situation, you can choose catrgory CTR and give any cost center number in the order.)
    (For information, this settlement is defaulted from OKO7 transaction code, check with your CO consultant about the entries
    then try to do the MB31.
    Thanks,
    JK

  • Error while activating DSO

    Hi,
            I am getting an error while activating the DSO. I am able to load the data but this occurs when I try to activate the data. I get the follwing error message
    "Value "09020751987.44 " from characteristic 0REF_DOC_NO contains an error at position 15
    Message no. BRAIN290
    Diagnosis
    Characters that have a hexadecimal display between HEX00 and HEX1F are not permitted in characteristic values. The character at position 15 is one of these characters. The value is therefore not permitted.
    Note that these characters cannot be displayed and are therefore displayed as '#'. The actual character '#' has the hexadecimal display HEX23.
    Procedure
    Check the origin of the characteristic value. If possible, change the characteristic value in the source.
    Incorrect source text in update routines and transfer routines can also cause this problem."
    Any thoughts how I should correct/

    Hi Tanu,
    this is an error in the data loaded. If you have used PSA, then try searching for the packet containing this record using the change log table, by request id. (This step is to precisely find the position of the record in PSA).
    Now delete the request from the DSO and correct the data in PSA. The issue could be a tab or a space in the reference document feild and then save the data. Reconstruct this packet from PSA and then try activating.
    Subsequently let the data team/ user know about the correction in the source system as well, in order to avoid any future failures.
    This should correct the issue.
    regards,
    Naveen.A

  • Error while running OBIA configuration configApps.bat

    I am receiving error while running configapps.bat.
    I have the following wnvironment installed:
    64 Bit windows
    Java 6 (JDK1.6.x)
    Weblogic server 10.3.6 in software only mode
    Ran OBIEE 11.1.1.7.0 RCU utility to create BIPLATFORM and MDS schemas.
    configured OBIEE 11.1.1.7
    Installed ODI 11.1.1.7 with All components and “Skip Repository Configuration”
    Ran OBI Apps RCU to create schemas for:
    ODI Master and Work Repositories (DEV_BIA_ODIREPO)
    Oracle Business Applications Components (DEV_BIACOMP)
    Oracle Business Analytics Datwarehouse (DEV_DW)
    Update to MDS schema.
    Installed BI Apps 11.1.1.7.1
    Applied FMW Platform Patches
    Updated BIACOMP Schema with ATGLite patch scripts
    Everything was up and running until now, when i try to configure OBIA via running configApps.bat, it is getting stuck at ODI configuration.
    Also the server seems to be going to idle/suspended state every now and after 5-6 mins of startup and i see this message repeated again and again in server log :
    <Warning> <oracle.mds> <BEA-000000> < The MDS session was created by the ADF framework with a transaction key for its "single flush" feature, and the call to flushchanges is restricted to that framework. This call does not use that transaction key and although working now, will fail with an exception in future. To find the originator of the call, set the log level for logger "oracle.mds.transkey" to FINEST. Note that the ADF framework manages the MDS session created for the request so an explicit call to flushchanges should be removed>
    Has anyone encountered this issue and any idea how to resolve this.
    Appreciate any help in advance ...

    The re-install has been successful. Didnt encounter any issues in any configuration.
    However the waring still appears
    <Warning> <oracle.mds> <BEA-000000> < The MDS session was created by the ADF framework with a transaction key for its "single flush" feature, and the call to flushchanges is restricted to that framework. This call does not use that transaction key and although working now, will fail with an exception in future. To find the originator of the call, set the log level for logger "oracle.mds.transkey" to FINEST. Note that the ADF framework manages the MDS session created for the request so an explicit call to flushchanges should be removed>
    Also in the log i am getting the following errors as well in the Weblogic server log
    BEA -101020  Servelet failed with exception Java.lang.illegalstateexception: Cannot forward a response that is already committed
    Oracle.as.management.mbeans.opmn  OPMN.queryProcessStatus failed with the following exception  oracle.as.management.opmn.optic.OpticBadConnectionException: Failed to create secure socket for OPMN
    All patches were applied successfully, including weblogic one's.
    Has anyone got any idea how to resolve these issues.
    Thanks in advance.

  • Error while creating partition table

    Hi frnds i am getting error while i am trying to create a partition table using range
    getting error ORA-00906: missing left parenthesis.I used the following statement to create partition table
    CREATE TABLE SAMPLE_ORDERS
    (ORDER_NUMBER NUMBER,
    ORDER_DATE DATE,
    CUST_NUM NUMBER,
    TOTAL_PRICE NUMBER,
    TOTAL_TAX NUMBER,
    TOTAL_SHIPPING NUMBER)
    PARTITION BY RANGE(ORDER_DATE)
    PARTITION SO99Q1 VALUES LESS THAN TO_DATE(‘01-APR-1999’, ‘DD-MON-YYYY’),
    PARTITION SO99Q2 VALUES LESS THAN TO_DATE(‘01-JUL-1999’, ‘DD-MON-YYYY’),
    PARTITION SO99Q3 VALUES LESS THAN TO_DATE(‘01-OCT-1999’, ‘DD-MON-YYYY’),
    PARTITION SO99Q4 VALUES LESS THAN TO_DATE(‘01-JAN-2000’, ‘DD-MON-YYYY’),
    PARTITION SO00Q1 VALUES LESS THAN TO_DATE(‘01-APR-2000’, ‘DD-MON-YYYY’),
    PARTITION SO00Q2 VALUES LESS THAN TO_DATE(‘01-JUL-2000’, ‘DD-MON-YYYY’),
    PARTITION SO00Q3 VALUES LESS THAN TO_DATE(‘01-OCT-2000’, ‘DD-MON-YYYY’),
    PARTITION SO00Q4 VALUES LESS THAN TO_DATE(‘01-JAN-2001’, ‘DD-MON-YYYY’)
    ;

    More than one of them. Try this instead:
    CREATE TABLE SAMPLE_ORDERS
    (ORDER_NUMBER NUMBER,
    ORDER_DATE DATE,
    CUST_NUM NUMBER,
    TOTAL_PRICE NUMBER,
    TOTAL_TAX NUMBER,
    TOTAL_SHIPPING NUMBER)
    PARTITION BY RANGE(ORDER_DATE) (
    PARTITION SO99Q1 VALUES LESS THAN (TO_DATE('01-APR-1999', 'DD-MON-YYYY')),
    PARTITION SO99Q2 VALUES LESS THAN (TO_DATE('01-JUL-1999', 'DD-MON-YYYY')),
    PARTITION SO99Q3 VALUES LESS THAN (TO_DATE('01-OCT-1999', 'DD-MON-YYYY')),
    PARTITION SO99Q4 VALUES LESS THAN (TO_DATE('01-JAN-2000', 'DD-MON-YYYY')),
    PARTITION SO00Q1 VALUES LESS THAN (TO_DATE('01-APR-2000', 'DD-MON-YYYY')),
    PARTITION SO00Q2 VALUES LESS THAN (TO_DATE('01-JUL-2000', 'DD-MON-YYYY')),
    PARTITION SO00Q3 VALUES LESS THAN (TO_DATE('01-OCT-2000', 'DD-MON-YYYY')),
    PARTITION SO00Q4 VALUES LESS THAN (TO_DATE('01-JAN-2001', 'DD-MON-YYYY')))In the future, if you are having problems, go to Morgan's Library at www.psoug.org.
    Find a working demo, copy it, then modify it for your purposes.

  • Error while registering a schema

    Hi :
    I get this error while I am registering my XML schema.
    ERROR at line 1:
    ORA-31154: invalid XML document
    ORA-19202: Error occurred in XML processing
    LPX-00217: invalid character 0 (\u0000)
    ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 0
    ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 26
    ORA-06512: at line 2
    I have marked in bold the part of the schema which bombs while registering. (When I validate this scehms in XML Spy it says it is a valid schems)
    The Schema definition is as follows :
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema targetNamespace="urn:uk:ac:ebi:spml" xmlns="urn:uk:ac:ebi:spml" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
    <xs:include schemaLocation="feature.xsd"/>
    <!-- Evidence definition begins -->
    <xs:complexType name="evidenceListType">
    <xs:annotation>
    <xs:documentation>The list of all evidences stored in one entry.</xs:documentation>
    </xs:annotation>
    <xs:sequence>
    <xs:element name="evidence" type="evidenceType" maxOccurs="unbounded"/>
    </xs:sequence>
    </xs:complexType>
    <xs:complexType name="evidenceType">
    <xs:annotation>
    <xs:documentation>The evidence element is equivalent to the actual evidence (**EV line).</xs:documentation>
    </xs:annotation>
    <xs:attribute name="category" use="required">
    <xs:simpleType>
    <xs:restriction base="xs:string">
    <xs:enumeration value="curator"/>
    <xs:enumeration value="import"/>
    <xs:enumeration value="program"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="type" use="required">
    <xs:simpleType>
    <xs:restriction base="xs:string">
    <xs:enumeration value="ANU-2DPAGE_ADD"/>
    <xs:enumeration value="COMPLUYEAST-2DPAGE_ADD"/>
    <xs:enumeration value="Curator"/>
    <xs:enumeration value="EMBL"/>
    <xs:enumeration value="Experimental"/>
    <xs:enumeration value="FLYBASE_ADD"/>
    <xs:enumeration value="GENEW_ADD"/>
    <xs:enumeration value="GOA_ADD"/>
    <xs:enumeration value="GRAMENE_ADD"/>
    <xs:enumeration value="HSSP_ADD"/>
    <xs:enumeration value="Import"/>
    <xs:enumeration value="MEROPS_ADD"/>
    <xs:enumeration value="MGD_ADD"/>
    <xs:enumeration value="Opinion"/>
    <xs:enumeration value="PHCI-2DPAGE_ADD"/>
    <xs:enumeration value="PMMA-2DPAGE_ADD"/>
    <xs:enumeration value="ProtImp"/>
    <xs:enumeration value="REBASE_ADD"/>
    <xs:enumeration value="Rulebase"/>
    <xs:enumeration value="SGD_ADD"/>
    <xs:enumeration value="SIENA-2DPAGE_ADD"/>
    <xs:enumeration value="SignalP"/>
    <xs:enumeration value="Similarity"/>
    <xs:enumeration value="TRANSFAC_ADD"/>
    <xs:enumeration value="TrEMBL"/>
    <xs:enumeration value="ZFIN_ADD"/>
    <xs:enumeration value="internal"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="attribute" type="xs:string" use="optional"/>
    <xs:attribute name="date" type="xs:date" use="required"/>
    <xs:attribute name="evID" type="xs:string" use="required"/>
    </xs:complexType>
    <!-- Evidence definition ends -->
    <!-- Definition of the protein begins -->
    <xs:complexType name="proteinType">
    <xs:sequence>
    <xs:element name="name" type="nameType" maxOccurs="unbounded"/>
    <xs:element name="iRefList" type="iRefListType" minOccurs="0">
    <xs:annotation>
    <xs:documentation>This is referring to a possible EC number (ENZYME database cross reference).</xs:documentation>
    </xs:annotation>
    </xs:element>
    <xs:choice minOccurs="0">
    <xs:element name="componentList">
    <xs:annotation>
    <xs:documentation>The component list is equivalent to the CONTAINS section of the DE line.</xs:documentation>
    </xs:annotation>
    <xs:complexType>
    <xs:sequence>
    <xs:element name="component" maxOccurs="unbounded">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="name" type="nameType" maxOccurs="unbounded"/>
    <xs:element name="iRefList" type="iRefListType" minOccurs="0">
    <xs:annotation>
    <xs:documentation>This is referring to a possible EC number (ENZYME database cross reference).</xs:documentation>
    </xs:annotation>
    </xs:element>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="domainList">
    <xs:annotation>
    <xs:documentation>The domain list is equivalent to the INCLUDES section of the DE line.</xs:documentation>
    </xs:annotation>
    <xs:complexType>
    <xs:sequence>
    <xs:element name="domain" maxOccurs="unbounded">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="name" type="nameType" maxOccurs="unbounded"/>
    <xs:element name="iRefList" type="iRefListType" minOccurs="0">
    <xs:annotation>
    <xs:documentation>This is referring to a possible EC number (ENZYME database cross reference).</xs:documentation>
    </xs:annotation>
    </xs:element>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    </xs:choice>
    <xs:element name="evList" type="evListType" minOccurs="0">
    <xs:annotation>
    <xs:documentation>This contains all evidence that are connected to the complete DE line (For the time being also the ones that couldn't be resolved to a single name).</xs:documentation>
    </xs:annotation>
    </xs:element>
    </xs:sequence>
    <xs:attribute name="evidenceStatus">
    <xs:simpleType>
    <xs:restriction base="xs:NMTOKEN">
    <xs:enumeration value="hypothetical"/>
    <xs:enumeration value="putative"/>
    <xs:enumeration value="possible"/>
    <xs:enumeration value="probable"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="type">
    <xs:simpleType>
    <xs:restriction base="xs:NMTOKEN">
    <xs:enumeration value="fragment"/>
    <xs:enumeration value="fragments"/>
    <xs:enumeration value="version1"/>
    <xs:enumeration value="version2"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:attribute>
    </xs:complexType>
    <!-- Definition of the protein ends -->
    <!-- DB reference definition begins -->
    <xs:complexType name="sptrProperties">
    <xs:complexContent>
    <xs:restriction base="propertyBaseType">
    <xs:attribute name="name" use="required">
    <xs:simpleType>
    <xs:restriction base="xs:string">
    <xs:enumeration value="edition"/>
    <xs:enumeration value="entry name"/>
    <xs:enumeration value="evidence"/>
    <xs:enumeration value="gene designation"/>
    <xs:enumeration value="last revision date"/>
    <xs:enumeration value="match status"/>
    <xs:enumeration value="match status hits"/>
    <xs:enumeration value="method"/>
    <xs:enumeration value="organism name"/>
    <xs:enumeration value="pdb accession"/>
    <xs:enumeration value="protein sequence ID"/>
    <xs:enumeration value="status"/>
    <xs:enumeration value="term"/>
    <xs:enumeration value="type"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="value" type="xs:string" use="required"/>
    </xs:restriction>
    </xs:complexContent>
    </xs:complexType>
    <xs:simpleType name="allSPTrDbsType">
    <xs:restriction base="xs:string">
    <xs:enumeration value="ANU-2DPAGE"/>
    <xs:enumeration value="Aarhus/Ghent-2DPAGE"/>
    <xs:enumeration value="COMPLUYEAST-2DPAGE"/>
    <xs:enumeration value="DictyDb"/>
    <xs:enumeration value="EC"/>
    <xs:enumeration value="ECO2DBASE"/>
    <xs:enumeration value="EMBL"/>
    <xs:enumeration value="EcoGene"/>
    <xs:enumeration value="FlyBase"/>
    <xs:enumeration value="GO"/>
    <xs:enumeration value="Genew"/>
    <xs:enumeration value="GlycoSuiteDB"/>
    <xs:enumeration value="Gramene"/>
    <xs:enumeration value="HIV"/>
    <xs:enumeration value="HSC-2DPAGE"/>
    <xs:enumeration value="HSSP"/>
    <xs:enumeration value="InterPro"/>
    <xs:enumeration value="Leproma"/>
    <xs:enumeration value="ListiList"/>
    <xs:enumeration value="MAIZE-2DPAGE"/>
    <xs:enumeration value="MEROPS"/>
    <xs:enumeration value="MGD"/>
    <xs:enumeration value="MIM"/>
    <xs:enumeration value="MaizeDB"/>
    <xs:enumeration value="MypuList"/>
    <xs:enumeration value="PDB"/>
    <xs:enumeration value="PHCI-2DPAGE"/>
    <xs:enumeration value="PhosSite"/>
    <xs:enumeration value="PIR"/>
    <xs:enumeration value="PMMA-2DPAGE"/>
    <xs:enumeration value="PRINTS"/>
    <xs:enumeration value="PROSITE"/>
    <xs:enumeration value="Pfam"/>
    <xs:enumeration value="ProDom"/>
    <xs:enumeration value="REBASE"/>
    <xs:enumeration value="SGD"/>
    <xs:enumeration value="SMART"/>
    <xs:enumeration value="SWISS-2DPAGE"/>
    <xs:enumeration value="Siena-2DPAGE"/>
    <xs:enumeration value="StyGene"/>
    <xs:enumeration value="SubtiList"/>
    <xs:enumeration value="TIGR"/>
    <xs:enumeration value="TIGRFAMs"/>
    <xs:enumeration value="TRANSFAC"/>
    <xs:enumeration value="TubercuList"/>
    <xs:enumeration value="WormPep"/>
    <xs:enumeration value="ZFIN"/>
    </xs:restriction>
    </xs:simpleType>
    <!-- <xs:complexType name="sptrDbReferenceType" abstract="true">-->
    <xs:complexType name="sptrDbReferenceType">
    <xs:complexContent>
    <xs:restriction base="dbReferenceBaseType">
    <xs:sequence>
    <xs:element name="property" type="propertyBaseType" minOccurs="0" maxOccurs="unbounded"/>
    <xs:element name="evList" type="evListType" minOccurs="0"/>
    </xs:sequence>
    <xs:attribute name="db" type="allSPTrDbsType" use="required"/>
    <xs:attribute name="id" type="xs:string" use="required"/>
    <xs:attribute name="iRefID" type="xs:string" use="required"/>
    </xs:restriction>
    </xs:complexContent>
    </xs:complexType>
    <!-- EMBL -->
    <!--
    <xs:complexType name="emblDbProperties">
    <xs:complexContent>
    <xs:restriction base="propertyBaseType">
    <xs:attribute name="name" use="required">
    <xs:simpleType>
    <xs:restriction base="xs:string">
    <xs:enumeration value="protein sequence ID"/>
    <xs:enumeration value="status"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="value" type="xs:string" use="required"/>
    </xs:restriction>
    </xs:complexContent>
    </xs:complexType>
    <xs:complexType name="emblDbReferenceType">
    <xs:complexContent>
    <xs:restriction base="sptrDbReferenceType">
    <xs:sequence>
    <xs:element name="property" type="emblDbProperties" minOccurs="0" maxOccurs="unbounded"/>
    <xs:element name="evList" type="evListType" minOccurs="0"/>
    </xs:sequence>
    <xs:attribute name="db" use="required">
    <xs:simpleType>
    <xs:restriction base="allSPTrDbsType">
    <xs:enumeration value="EMBL"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="id" type="xs:string" use="required"/>
    <xs:attribute name="iRefID" type="xs:string" use="required"/>
    </xs:restriction>
    </xs:complexContent>
    </xs:complexType>
    -->
    <!-- EMBL -->
    <!-- NCBI Taxonomy -->
    <xs:complexType name="taxonomyDBType">
    <xs:annotation>
    <xs:documentation>This dbRef type is meant for taxonomy database such as the NCBI taxonomy database.</xs:documentation>
    </xs:annotation>
    <xs:complexContent>
    <xs:restriction base="dbReferenceBaseType">
    <xs:sequence>
    <xs:element name="evList" type="evListType" minOccurs="0"/>
    </xs:sequence>
    <xs:attribute name="db" use="required">
    <xs:simpleType>
    <xs:restriction base="xs:string">
    <xs:enumeration value="NCBI Taxonomy"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="id" type="xs:string" use="required"/>
    <xs:attribute name="iRefID" type="xs:string" use="required"/>
    </xs:restriction>
    </xs:complexContent>
    </xs:complexType>
    <!-- NCBI Taxonomy -->
    <!-- DB reference definition ends -->
    <!-- Name definition begins -->
    <xs:complexType name="nameType" mixed="true">
    <xs:annotation>
    <xs:documentation>The name type is used for all names occuring in an entry.</xs:documentation>
    </xs:annotation>
    <xs:sequence minOccurs="0" maxOccurs="unbounded">
    <xs:element name="evList" type="evListType" minOccurs="0"/>
    </xs:sequence>
    </xs:complexType>
    <xs:complexType name="organismNameType">
    <xs:annotation>
    <xs:documentation>The name type is used for source organism names.</xs:documentation>
    </xs:annotation>
    <xs:simpleContent>
    <xs:extension base="xs:string">
    <xs:attribute name="type" use="required">
    <xs:simpleType>
    <xs:restriction base="xs:string">
    <xs:enumeration value="common name"/>
    <xs:enumeration value="full name"/>
    <xs:enumeration value="scientific name"/>
    <xs:enumeration value="synonym"/>
    <xs:enumeration value="abbreviation"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:attribute>
    </xs:extension>
    </xs:simpleContent>
    </xs:complexType>
    <!-- Name definition ends -->
    <!-- Definition of the geneLocation begins -->
    <xs:complexType name="geneLocationListType">
    <xs:annotation>
    <xs:documentation>Defines the locations/origins of the shown sequence (OG line).</xs:documentation>
    </xs:annotation>
    <xs:sequence>
    <xs:element name="geneLocation" type="geneLocationBaseType" maxOccurs="unbounded"/>
    </xs:sequence>
    </xs:complexType>
    <xs:complexType name="geneLocationBaseType" abstract="true">
    <xs:annotation>
    <xs:documentation>The location's supertype.</xs:documentation>
    </xs:annotation>
    </xs:complexType>
    <xs:complexType name="organelleLocationType">
    <xs:annotation>
    <xs:documentation>This type stores the location if it's a chloroplast, cyanelle or mitochondrium.</xs:documentation>
    </xs:annotation>
    <xs:complexContent>
    <xs:extension base="geneLocationBaseType">
    <xs:sequence>
    <xs:element name="evList" type="evListType" minOccurs="0"/>
    </xs:sequence>
    <xs:attribute name="type" use="required">
    <xs:simpleType>
    <xs:restriction base="xs:NMTOKEN">
    <xs:enumeration value="chloroplast"/>
    <xs:enumeration value="cyanelle"/>
    <xs:enumeration value="mitochondrion"/>
    <xs:enumeration value="nucleomorph"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:attribute>
    </xs:extension>
    </xs:complexContent>
    </xs:complexType>
    <xs:complexType name="plasmidLocationType">
    <xs:annotation>
    <xs:documentation>This type stores the location if it's a plasmid including all plasmid names.</xs:documentation>
    </xs:annotation>
    <xs:complexContent>
    <xs:extension base="geneLocationBaseType">
    <xs:sequence>
    <xs:element name="name" type="nameType"/>
    <xs:element name="evList" type="evListType" minOccurs="0"/>
    </xs:sequence>
    <xs:attribute name="type" use="required">
    <xs:simpleType>
    <xs:restriction base="xs:NMTOKEN">
    <xs:enumeration value="plasmid"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:attribute>
    </xs:extension>
    </xs:complexContent>
    </xs:complexType>
    <!-- Definition of the geneLocation ends -->
    <!-- Feature definition begins -->
    <xs:complexType name="baseFeatureType" mixed="true">
    <xs:annotation>
    <xs:documentation>The feature's supertype from which all other feature element types are derived.</xs:documentation>
    </xs:annotation>
    <xs:sequence>
    <xs:group ref="locationGroup" minOccurs="0"/>
    <xs:element name="evList" type="evListType" minOccurs="0"/>
    </xs:sequence>
    <xs:attribute name="description" type="xs:string" use="optional"/>
    </xs:complexType>
    <xs:complexType name="featureType" mixed="true">
    <xs:annotation>
    <xs:documentation>Currently there is only one basic feature type, but this will change in future with enhancement of the FT line parsers.</xs:documentation>
    </xs:annotation>
    <xs:complexContent mixed="true">
    <xs:extension base="baseFeatureType">
    <xs:attribute name="type" use="required">
    <xs:simpleType>
    <xs:restriction base="xs:string">
    <xs:enumeration value="active site"/>
    <xs:enumeration value="binding site"/>
    <xs:enumeration value="calcium-binding region"/>
    <xs:enumeration value="glycosylation site"/>
    <xs:enumeration value="chain"/>
    <xs:enumeration value="sequence conflict"/>
    <xs:enumeration value="disulfide bond"/>
    <xs:enumeration value="DNA-binding region"/>
    <xs:enumeration value="domain"/>
    <xs:enumeration value="helix"/>
    <xs:enumeration value="initiator methionine"/>
    <xs:enumeration value="lipid moiety-binding region"/>
    <xs:enumeration value="metal ion-binding site"/>
    <xs:enumeration value="modified residue"/>
    <xs:enumeration value="mutagenesis site"/>
    <xs:enumeration value="non-consecutive residues"/>
    <xs:enumeration value="non-terminal residue"/>
    <xs:enumeration value="nucleotide phosphate-binding region"/>
    <xs:enumeration value="peptide"/>
    <xs:enumeration value="propeptide"/>
    <xs:enumeration value="repeat"/>
    <xs:enumeration value="selenocysteine"/>
    <xs:enumeration value="signal peptide"/>
    <xs:enumeration value="site"/>
    <xs:enumeration value="strand"/>
    <xs:enumeration value="thioether bond"/>
    <xs:enumeration value="thiolester bond"/>
    <xs:enumeration value="transit peptide"/>
    <xs:enumeration value="transmembrane region"/>
    <xs:enumeration value="turn"/>
    <xs:enumeration value="unsure residue"/>
    <xs:enumeration value="sequence variant"/>
    <xs:enumeration value="splice variant"/>
    <xs:enumeration value="zinc finger region"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:attribute>
    </xs:extension>
    </xs:complexContent>
    </xs:complexType>
    <!-- Feature definition ends -->
    <!-- Comment definition begins -->
    <xs:complexType name="baseCommentType" abstract="true" mixed="true">
    <xs:annotation>
    <xs:documentation>The comment's supertype from which all other comment element types are derived</xs:documentation>
    </xs:annotation>
    <xs:sequence>
    <xs:element name="evList" type="evListType" minOccurs="0"/>
    </xs:sequence>
    </xs:complexType>
    <xs:complexType name="commentType" mixed="true">
    <xs:annotation>
    <xs:documentation>Basic comment type which contains only text and evidence tags, no extra structure/attributes.</xs:documentation>
    </xs:annotation>
    <xs:complexContent mixed="true">
    <xs:extension base="baseCommentType">
    <xs:attribute name="topic" use="required">
    <xs:simpleType>
    <xs:restriction base="xs:string">
    <xs:enumeration value="alternative products"/>
    <xs:enumeration value="biotechnology"/>
    <xs:enumeration value="catalytic activity"/>
    <xs:enumeration value="caution"/>
    <xs:enumeration value="cofactor"/>
    <xs:enumeration value="database"/>
    <xs:enumeration value="developmental stage"/>
    <xs:enumeration value="disease"/>
    <xs:enumeration value="domain"/>
    <xs:enumeration value="enzyme regulation"/>
    <xs:enumeration value="function"/>
    <xs:enumeration value="induction"/>
    <xs:enumeration value="miscellaneous"/>
    <xs:enumeration value="pathway"/>
    <xs:enumeration value="pharmaceutical"/>
    <xs:enumeration value="polymorphism"/>
    <xs:enumeration value="ptm"/>
    <xs:enumeration value="similarity"/>
    <xs:enumeration value="subcellular location"/>
    <xs:enumeration value="subunit"/>
    <xs:enumeration value="tissue specificity"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:attribute>
    </xs:extension>
    </xs:complexContent>
    </xs:complexType>
    <!--
    <xs:complexType name="commentDatabaseType" mixed="true">
    <xs:complexContent mixed="true">
    <xs:extension base="baseCommentType">
    <xs:attribute name="topic" use="required">
    <xs:simpleType>
    <xs:restriction base="xs:string">
    <xs:enumeration value="database"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="name" type="xs:string" use="required"/>
    <xs:attribute name="note" type="xs:string" use="optional"/>
    <xs:attribute name="www" type="xs:anyURI" use="optional"/>
    <xs:attribute name="ftp" type="xs:anyURI" use="optional"/>
    </xs:extension>
    </xs:complexContent>
    </xs:complexType>
    -->
    <xs:complexType name="massSpecType" mixed="true">
    <xs:annotation>
    <xs:documentation>The information of the mass spectrometry comment is stored in the attributes:
    -molWeight (molecular weight)
    -mwError (error of the molecular weight)
    -msMethod (the method used for the mass spectrometry)
    -range (which amino acids were messured. It's not mentioned if the complete sequence as shown in the entry was messured)</xs:documentation>
    </xs:annotation>
    <xs:complexContent mixed="true">
    <xs:extension base="baseCommentType">
    <xs:sequence minOccurs="0">
    <xs:element name="range" minOccurs="0" maxOccurs="unbounded">
    <xs:complexType>
    <xs:attribute name="begin" type="xs:int" use="required"/>
    <xs:attribute name="end" type="xs:int" use="required"/>
    </xs:complexType>
    </xs:element>
    </xs:sequence>
    <xs:attribute name="topic" use="required">
    <xs:simpleType>
    <xs:restriction base="xs:string">
    <xs:enumeration value="mass spectrometry"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="molWeight" type="xs:float" use="required"/>
    <xs:attribute name="mwError" type="xs:string" use="optional"/>
    <xs:attribute name="msMethod" type="xs:string" use="optional"/>
    </xs:extension>
    </xs:complexContent>
    </xs:complexType>
    <!-- Comment definition ends -->
    <!-- Citation type section begins -->
    <!-- Definitions for SPTr's additional citation information begins -->
    <xs:complexType name="scopeListType">
    <xs:annotation>
    <xs:documentation>Contains a list of scopes regarding a citation. There is no classification currently, but will be introduced in future. (RP lines).</xs:documentation>
    </xs:annotation>
    <xs:sequence>
    <xs:element name="scope" type="xs:string" maxOccurs="unbounded"/>
    </xs:sequence>
    </xs:complexType>
    <xs:complexType name="sourceDataType">
    <xs:annotation>
    <xs:documentation>Contains specific information about the sequence source that was used in the ciation (RC lines).</xs:documentation>
    </xs:annotation>
    <xs:choice maxOccurs="unbounded">
    <xs:element name="species">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="iRefList" type="iRefListType"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="strain">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="name" type="xs:string" maxOccurs="unbounded"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="plasmid" type="xs:string"/>
    <xs:element name="transposon" type="xs:string"/>
    <xs:element name="tissue" type="xs:string"/>
    </xs:choice>
    </xs:complexType>
    <xs:group name="sptrCitationGroup">
    <xs:annotation>
    <xs:documentation>Groups the scope and source data lists.</xs:documentation>
    </xs:annotation>
    <xs:sequence>
    <xs:element name="scopeList" type="scopeListType"/>
    <xs:element name="source" type="sourceDataType" minOccurs="0"/>
    <xs:element name="evList" type="evListType" minOccurs="0"/>
    </xs:sequence>
    </xs:group>
    <!-- Definitions for SPTr's additional citation information ends -->
    <xs:complexType name="referenceType">
    <xs:annotation>
    <xs:documentation>Stores all information of the reference block in SPTr (RN, RP, RC, RX, RA, RT and RL line).</xs:documentation>
    </xs:annotation>
    <xs:sequence>
    <xs:element name="citation" type="citationType"/>
    <xs:group ref="sptrCitationGroup"/>
    </xs:sequence>
    <xs:attribute name="iRefID" type="xs:string" use="required"/>
    </xs:complexType>
    <!-- Citation type section ends -->
    <!-- Entry type definition begins -->
    <xs:complexType name="entryType">
    <xs:annotation>
    <xs:documentation>A (public) SPTr entry</xs:documentation>
    </xs:annotation>
    <xs:sequence>
    <xs:element name="secondaryAccessionList" minOccurs="0">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="accession" type="xs:string" maxOccurs="unbounded"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="secondaryNameList" minOccurs="0">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="name" type="xs:string" maxOccurs="unbounded"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="protein" type="proteinType"/>
    <xs:element name="geneList" minOccurs="0">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="gene" maxOccurs="unbounded">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="name" type="nameType" maxOccurs="unbounded"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="organismList">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="organism" maxOccurs="unbounded">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="name" type="organismNameType" maxOccurs="unbounded"/>
    <xs:element name="dbReferenceList">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="dbReference" type="taxonomyDBType" maxOccurs="unbounded"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="lineage" minOccurs="0">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="taxon" type="xs:string" maxOccurs="unbounded"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    </xs:sequence>
    <xs:attribute name="iRefID" type="xs:string" use="optional"/>
    </xs:complexType>
    </xs:element>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="geneLocationList" type="geneLocationListType" minOccurs="0"/>
    <xs:element name="referenceList">
    <xs:complexType>
    <xs:choice maxOccurs="unbounded">
    <xs:element name="reference" type="referenceType"/>
    </xs:choice>
    </xs:complexType>
    </xs:element>
    <xs:element name="commentList" minOccurs="0">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="comment" type="baseCommentType" nillable="true" maxOccurs="unbounded"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="dbReferenceList" minOccurs="0">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="dbReference" type="sptrDbReferenceType" maxOccurs="unbounded"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="keywordList" minOccurs="0">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="keyword" maxOccurs="unbounded">
    <xs:complexType mixed="true">
    <xs:choice minOccurs="0" maxOccurs="unbounded">
    <xs:element name="evList" type="evListType"/>
    </xs:choice>
    </xs:complexType>
    </xs:element>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="featureList" minOccurs="0">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="feature" type="featureType" maxOccurs="unbounded"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="evidenceList" type="evidenceListType" minOccurs="0"/>
    <xs:element name="sequence">
    <xs:complexType>
    <xs:simpleContent>
    <xs:extension base="xs:string">
    <xs:attribute name="length" type="xs:integer" use="required"/>
    <xs:attribute name="weight" type="xs:integer" use="required"/>
    <xs:attribute name="crc64" type="xs:string" use="required"/>
    <xs:attribute name="lastUpdate" type="xs:date" use="required"/>
    </xs:extension>
    </xs:simpleContent>
    </xs:complexType>
    </xs:element>
    </xs:sequence>
    <xs:attribute name="accession" type="xs:string" use="required"/>
    <xs:attribute name="database" type="xs:string" use="required"/>
    <xs:attribute name="name" type="xs:string" use="required"/>
    <xs:attribute name="firstPublic" type="xs:date" use="required"/>
    <xs:attribute name="lastAnnotationUpdate" type="xs:date" use="required"/>
    </xs:complexType>
    <!-- Entry type definition ends -->
    <!-- Definition of the content of the root element "swissprot" -->
    <xs:element name="sptr">
    <xs:annotation>
    <xs:documentation>Contains a collection of Swiss-Prot entries.</xs:documentation>
    </xs:annotation>
    <xs:complexType>
    <xs:sequence>
    <xs:element name="entry" type="entryType" maxOccurs="unbounded">
    <xs:key name="referenceKey">
    <xs:annotation>
    <xs:documentation>Defines the key constraint for iRefID attribute where possible in the entry (citations are missing still).</xs:documentation>
    </xs:annotation>
    <xs:selector xpath="organismList/organism|dbReferenceList/dbReference"/>
    <xs:field xpath="iRefID"/>
    </xs:key>
    <xs:key name="evidenceReferenceKey">
    <xs:annotation>
    <xs:documentation>Defines the key constraint for evID attribute in evidence elements.</xs:documentation>
    </xs:annotation>
    <xs:selector xpath="evidenceList/evidence"/>
    <xs:field xpath="evID"/>
    </xs:key>
    <!--
    <xs:keyref name="internalReference" refer="referenceKey">
    <xs:selector xpath=".//iRef"/>
    <xs:field xpath="ref"/>
    </xs:keyref>
    -->
    <xs:keyref name="evidenceReference" refer="evidenceReferenceKey">
    <xs:selector xpath=".//ev"/>
    <xs:field xpath="ref"/>
    </xs:keyref> <!--
    -->
    </xs:element>
    <xs:element name="copyright">
    <xs:complexType>
    <xs:simpleContent>
    <xs:extension base="xs:string">
    <xs:attribute name="iRefID" type="xs:string" use="required"/>
    </xs:extension>
    </xs:simpleContent>
    </xs:complexType>
    </xs:element>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    </xs:schema>
    feature.xsd is below :
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema targetNamespace="urn:uk:ac:ebi:spml" xmlns="urn:uk:ac:ebi:spml" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
    <!-- Feature location definition begins -->
    <xs:complexType name="positionType">
    <xs:attribute name="position" type="xs:unsignedLong" use="required"/>
    </xs:complexType>
    <xs:complexType name="gapType">
    <xs:complexContent>
    <xs:extension base="positionType">
    <xs:attribute name="length" type="xs:unsignedLong" use="optional"/>
    </xs:extension>
    </xs:complexContent>
    </xs:complexType>
    <xs:complexType name="intervalType">
    <xs:attribute name="begin" type="xs:unsignedLong" use="required"/>
    <xs:attribute name="end" type="xs:unsignedLong" use="required"/>
    </xs:complexType>
    <xs:complexType name="baseLocationType">
    <xs:annotation>
    <xs:documentation>A location can be either a position, site or have a start and end, only start, only end or is an empty element if the position is unknown.
    The iRef attribute points to an external database reference (equivalent to J00194:100..202 in EMBL).</xs:documentation>
    </xs:annotation>
    <xs:choice>
    <xs:sequence>
    <xs:choice minOccurs="0">
    <xs:element name="begin" type="positionType"/>
    <xs:element name="beginInterval" type="intervalType"/>
    </xs:choice>
    <xs:choice minOccurs="0">
    <xs:element name="end" type="positionType"/>
    <xs:element name="endInterval" type="intervalType"/>
    </xs:choice>
    </xs:sequence>
    <xs:element name="position" type="positionType"/>
    <xs:element name="positionInterval" type="intervalType"/>
    <xs:element name="site" type="positionType"/>
    </xs:choice>
    <xs:attribute name="iRef" type="xs:string" use="optional"/>
    <xs:attribute name="complement" type="xs:boolean" use="optional" default="false"/>
    </xs:complexType>
    <xs:complexType name="fuzzyLocationType">
    <xs:annotation>
    <xs:documentation>A location can be either a position, site or have a start and end, only start, only end or is an empty element if the position is unknown.
    The iRef attribute points to an external database reference (equivalent to J00194:100..202 in EMBL).</xs:documentation>
    </xs:annotation>
    <xs:complexContent>
    <xs:extension base="baseLocationType">
    <xs:attribute name="fuzzy" use="optional" default="none">
    <xs:simpleType>
    <xs:restriction base="xs:NMTOKEN">
    <xs:enumeration value="left"/>
    <xs:enumeration value="right"/>
    <xs:enumeration value="both"/>
    <xs:enumeration value="none"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:attribute>
    </xs:extension>
    </xs:complexContent>
    </xs:complexType>
    <xs:complexType name="joinType">
    <xs:sequence>
    <xs:choice maxOccurs="unbounded">
    <xs:element name="location" type="baseLocationType"/>
    <xs:element name="gap" type="gapType"/>
    </xs:choice>
    </xs:sequence>
    <xs:attribute name="fuzzy" use="optional" default="none">
    <xs:simpleType>
    <xs:restriction base="xs:NMTOKEN">
    <xs:enumeration value="left"/>
    <xs:enumeration value="right"/>
    <xs:enumeration value="both"/>
    <xs:enumeration value="none"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="complement" type="xs:boolean" use="optional" default="false"/>
    </xs:complexType>
    <xs:group name="locationGroup">
    <xs:choice>
    <xs:element name="location" type="fuzzyLocationType"/>
    <xs:element name="join" type="joinType"/>
    </xs:choice>
    </xs:group>
    <!-- Feature location definition ends -->
    <!-- Evidence definition begins -->
    <xs:complexType name="evListType">
    <xs:annotation>
    <xs:documentation>Contains a list of evidence tags.</xs:documentation>
    </xs:annotation>
    <xs:sequence>
    <xs:element name="ev" maxOccurs="unbounded">
    <xs:annotation>
    <xs:documentation>The ev element is equivalent to an evidence tags.</xs:documentation>
    </xs:annotation>
    <xs:complexType>
    <xs:attribute name="ref" type="xs:string" use="required"/>
    </xs:complexType>
    </xs:element>
    </xs:sequence>
    </xs:complexType>
    <!-- Evidence definition ends -->
    <!-- DB reference definition begins -->
    <xs:complexType name="propertyBaseType">
    <xs:attribute name="name" type="xs:string" use="required"/>
    <xs:attribute name="value" type="xs:string" use="required"/>
    </xs:complexType>
    <xs:complexType name="dbReferenceBaseType" abstract="true">
    <xs:annotation>
    <xs:documentation>DR line</xs:documentation>
    </xs:annotation>
    <xs:sequence>
    <xs:element name="property" type="propertyBaseType" minOccurs="0" maxOccurs="unbounded"/>
    <xs:element name="evList" type="evListType" minOccurs="0"/>
    </xs:sequence>
    <xs:attribute name="db" type="xs:string" use="required"/>
    <xs:attribute name="id" type="xs:string" use="required"/>
    <xs:attribute name="iRefID" type="xs:string" use="required"/>
    </xs:complexType>
    <xs:complexType name="citationDBType">
    <xs:annotation>
    <xs:documentation>This dbRef type is meant for citation database such as PubMed and MEDLINE.</xs:documentation>
    <xs:documentation>This dbRef type is meant for citation database such as PubMed and MEDLINE.</xs:documentation>
    </xs:annotation>
    <xs:complexContent>
    <xs:restriction base="dbReferenceBaseType">
    <xs:sequence>
    <xs:element name="evList" type="evListType" minOccurs="0"/>
    </xs:sequence>
    <xs:attribute name="db" use="required">
    <xs:simpleType>
    <xs:restriction base="xs:string">
    <xs:enumeration value="PubMed"/>
    <xs:enumeration value="MEDLINE"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="id" type="xs:string" use="required"/>
    <xs:attribute name="iRefID" type="xs:string" use="required"/>
    </xs:restriction>
    </xs:complexContent>
    </xs:complexType>
    <!-- DB reference definition ends -->
    <!-- Citation type section begins -->
    <xs:group name="citationContentGroup">
    <xs:sequence>
    <xs:element name="authorList" type="nameListType"/>
    <xs:element name="dbReferenceList" minOccurs="0">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="dbReference" type="citationDBType" maxOccurs="unbounded"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="iRefList" type="iRefListType" minOccurs="0"/>
    </xs:sequence>
    </xs:group>
    <xs:complexType name="citationType" abstract="true">
    <xs:annotation>
    <xs:documentation>The citation super type</xs:documentation>
    </xs:annotation>
    <xs:attribute name="iRefID" type="xs:string" use="optional"/>
    </xs:complexType>
    <xs:complexType name="bookType">
    <xs:annotation>
    <xs:documentation>Stores all information about a book.</xs:documentation>
    </xs:annotation>
    <xs:complexContent>
    <xs:extension base="citationType">
    <xs:sequence>
    <xs:element name="title" type="freeTextType" minOccurs="0"/>
    <xs:element name="bookTitle" type="xs:string"/>
    <xs:element name="editorList" type="nameListType" minOccurs="0"/>
    <xs:group ref="citationContentGroup"/>
    </xs:sequence>
    <xs:attribute name="type" use="required">
    <xs:simpleType>
    <xs:restriction base="xs:string">
    <xs:enumeration value="book"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="volume" type="xs:string" use="optional"/>
    <xs:attribute name="year" type="xs:int" use="required"/>
    <xs:attribute name="first" type="xs:unsignedInt" use="required"/>
    <xs:attribute name="last" type="xs:unsignedInt" use="required"/>
    <xs:attribute name="ISDN" type="xs:string" use="optional"/>
    <xs:attribute name="publisher" type="xs:string" use="required"/>
    <xs:attribute name="city" type="xs:string" use="required"/>
    <xs:attribute name="country" type="xs:string" use="optional"/>
    </xs:extension>
    </xs:complexContent>
    </xs:complexType>
    <xs:complexType name="electronicType">
    <xs:annotation>
    <xs:documentation>Stores all information about a so-called online citation.</xs:documentation>
    </xs:annotation>
    <xs:complexContent>
    <xs:extension base="citationType">
    <xs:sequence>
    <xs:element name="title" type="freeTextType" minOccurs="0"/>
    <xs:group ref="citationContentGroup"/>
    </xs:sequence>
    <xs:attribute name="type" use="required">
    <xs:simpleType>
    <xs:restriction base="xs:string">
    <xs:enumeration value="online journal article"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="volume" type="xs:string" use="optional"/>
    <xs:attribute name="year" type="xs:int" use="required"/>
    <xs:attribute name="issue" type="xs:unsignedInt" use="optional">
    <xs:annotation>
    <xs:documentation>Currently used only in the "Worm Breeder's Gazette".</xs:documentation>
    </xs:annotation>
    </xs:attribute>
    <xs:attribute name="articleNo" type="xs:unsignedInt" use="required">
    <xs:annotation>
    <xs:documentation>Currently used only in the "Worm Breeder's Gazette".</xs:documentation>
    </xs:annotation>
    </xs:attribute>
    <xs:attribute name="name" type="xs:string" use="optional">
    <xs:annotation>
    <xs:documentation>Can be used for stating the name of the electronic journal.</xs:documentation>
    </xs:annotation>
    </xs:attribute>
    </xs:extension>
    </xs:complexContent>
    </xs:complexType>
    <xs:complexType name="incompleteJournalType">
    <xs:annotation>
    <xs:documentation>Stores all information about an incomplete journal article.</xs:documentation>
    </xs:annotation>
    <xs:complexContent>
    <xs:extension base="citationType">
    <xs:sequence>
    <xs:element name="title" type="freeTextType" minOccurs="0"/>
    <xs:group ref="citationContentGroup"/>
    </xs:sequence>
    <xs:attribute name="type" use="required">
    <xs:simpleType>
    <xs:restriction base="xs:string">
    <xs:enumeration value="incomplete journal article"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="first" type="xs:string" use="optional"/>
    <xs:attribute name="last" type="xs:string" use="optional"/>
    <xs:attribute name="volume" type="xs:string" use="optional"/>
    <xs:attribute name="year" type="xs:int" use="optional"/>
    <xs:attribute name="name" type="xs:string" use="optional"/>
    <xs:attribute name="ISSN" type="xs:string" use="optional"/>
    </xs:extension>
    </xs:complexContent>
    </xs:complexType>
    <xs:complexType name="journalType">
    <xs:annotation>
    <xs:documentation>Stores all information about a journal article.</xs:documentation>
    </xs:annotation>
    <xs:complexContent>
    <xs:extension base="citationType">
    <xs:sequence>
    <xs:element name="title" type="freeTextType"/>
    <xs:group ref="citationContentGroup"/>
    </xs:sequence>
    <xs:attribute name="type" use="required">
    <xs:simpleType>
    <xs:restriction base="xs:string">
    <xs:enumeration value="journal article"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="first" type="xs:string" use="required"/>
    <xs:attribute name="last" type="xs:string" use="required"/>
    <xs:attribute name="volume" type="xs:string" use="required"/>
    <xs:attribute name="year" type="xs:int" use="required"/>
    <xs:attribute name="name" type="xs:string" use="required"/>
    <xs:attribute name="ISSN" type="xs:string" use="optional"/>
    </xs:extension>
    </xs:complexContent>
    </xs:complexType>
    <xs:complexType name="observationType">
    <xs:annotation>
    <xs:documentation>Stores all information about a citation of the type "Unpublished Observations".</xs:documentation>
    </xs:annotation>
    <xs:complexContent>
    <xs:extension base="citationType">
    <xs:sequence>
    <xs:group ref="citationContentGroup"/>
    </xs:sequence>
    <xs:attribute name="type" use="required">
    <xs:simpleType>
    <xs:restriction base="xs:string">
    <xs:enumeration value="unpublished observations"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="date" type="xs:gYearMonth" use="required"/>
    </xs:extension>
    </xs:complexContent>
    </xs:complexType>
    <xs:complexType name="patentType">
    <xs:annotation>
    <xs:documentation>Stores all information about a patent.</xs:documentation>
    </xs:annotation>
    <xs:complexContent>
    <xs:extension base="citationType">
    <xs:sequence>
    <xs:element name="title" type="freeTextType" minOccurs="0"/>
    <xs:group ref="citationContentGroup" minOccurs="0"/>
    </xs:sequence>
    <xs:attribute name="type" use="required">
    <xs:simpleType>
    <xs:restriction base="xs:string">
    <xs:enumeration value="patent"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="number" type="xs:string" use="required"/>
    <xs:attribute name="date" type="xs:date" use="required"/>
    </xs:extension>
    </xs:complexContent>
    </xs:complexType>
    <xs:complexType name="resultType">
    <xs:annotation>
    <xs:documentation>Stores all information about a citation of the type "Unpublished Results". For the unpublished results type it is necessary that the title element is optional, since one won't find this data in flat files (and might not be added in future, either).</xs:documentation>
    </xs:annotation>
    <xs:complexContent>
    <xs:extension base="citationType">
    <xs:sequence>
    <xs:element name="title" type="freeTextType" minOccurs="0"/>
    <xs:group ref="citationContentGroup"/>
    <xs:choice>
    <xs:element name="citedInBook" type="bookType"/>
    <xs:element name="citedInArticle" type="incompleteJournalType">
    <xs:annotation>
    <xs:documentation>The type of this element needs to be the incompleteJournalType as the SP-ML converter cannot create the title yet (it doesn't evaluate the PubMed database).</xs:documentation>
    </xs:annotation>
    </xs:element>
    <xs:element name="citedInElectronic" type="electronicType"/>
    <xs:element name="citedInThesis" type="thesisType"/>
    </xs:choice>
    </xs:sequence>
    <xs:attribute name="type" use="required">
    <xs:simpleType>
    <xs:restriction base="xs:string">
    <xs:enumeration value="unpublished results"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:attribute>
    </xs:extension>
    </xs:complexContent>
    </xs:complexType>
    <xs:complexType name="submissionType">
    <xs:annotation>
    <xs:documentation>Stores all information about a submission to one of the following databases:
    -EMBL/GenBank/DDBJ databases
    -SWISS-PROT data bank
    -HIV data bank
    -PDB data bank
    -PIR data bank</xs:documentation>
    </xs:annotation>
    <xs:complexContent>
    <xs:extension base="citationType">
    <xs:sequence>
    <xs:element name="title" type="freeTextType" minOccurs="0"/>
    <xs:group ref="citationContentGroup"/>
    </xs:sequence>
    <xs:attribute name="type" use="required">
    <xs:simpleType>
    <xs:restriction base="xs:string">
    <xs:enumeration value="submission"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="date" type="xs:gYearMonth" use="required"/>
    <xs:attribute name="db" type="xs:string" use="required"/>
    </xs:extension>
    </xs:complexContent>
    </xs:complexType>
    <xs:complexType name="thesisType">
    <xs:annotation>
    <xs:documentation>Stores all information about a thesis.</xs:documentation>
    </xs:annotation>
    <xs:complexContent>
    <xs:extension base="citationType">
    <xs:sequence>
    <xs:element name="title" type="freeTextType" minOccurs="0"/>
    <xs:group ref="citationContentGroup"/>
    </xs:sequence>
    <xs:attribute name="type" use="required">
    <xs:simpleType>
    <xs:restriction base="xs:string">
    <xs:enumeration value="thesis"/>
    </xs:restriction>
    </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="institute" type="xs:string" use="required"/>
    <xs:attribute name="city" type="xs:string" use="optional"/>
    <xs:attribute name="country" type="xs:string" use="required"/>
    <xs:attribute name="year" type="xs:int" use="required"/>
    </xs:extension>
    </xs:complexContent>
    </xs:complexType>
    <xs:complexType name="groupType">
    <xs:attribute name="name" type="xs:string" use="required"/>
    </xs:complexType>
    <xs:complexType name="personType">
    <xs:attribute name="name" type="xs:string" use="required"/>
    <xs:attribute name="forename" type="xs:string" use="optional"/>
    <xs:attribute name="surname" type="xs:string" use="optional"/>
    </xs:complexType>
    <xs:complexType name="nameListType">
    <xs:choice maxOccurs="unbounded">
    <xs:element name="person" type="personType"/>
    <xs:element name="group" type="groupType"/>
    </xs:choice>
    </xs:complexType>
    <!-- Citation type section ends -->
    <xs:complexType name="freeTextType" mixed="true">
    <xs:sequence minOccurs="0">
    <xs:element name="iRefList" type="iRefListType"/>
    </xs:sequence>
    </xs:complexType>
    <xs:complexType name="iRefType">
    <xs:attribute name="type" type="xs:string" use="optional"/>
    <xs:attribute name="ref" type="xs:string" use="required"/>
    </xs:complexType>
    <xs:complexType name="iRefListType">
    <xs:sequence>
    <xs:element name="iRef" type="iRefType" maxOccurs="unbounded"/>
    </xs:sequence>
    </xs:complexType>
    </xs:schema>

    We've found two errors, both which can be worked around.
    Currently there is a bug in XMLDB which fails to create a unique name for the case where the subtype and supertype both define an element or attribute with the same name. In your schema both baseCommentType defines an element called evList. massSpecType extends baseCommentType and adds an element with the same name.
    This causes an error creating the massSpecType SQLType. The workaround for this is to declare the XMLDB namespace in the schema and use the xdb:SQLName annotation to define a unique name for the second element.
    Eg
         <xs:complexType name="massSpecType" mixed="true">
              <xs:complexContent mixed="true">
                   <xs:extension base="baseCommentType">
                        <xs:sequence minOccurs="0">
                             <xs:element name="range" minOccurs="0" maxOccurs="unbounded">
                                  <xs:complexType>
                                       <xs:attribute name="begin" type="xs:int" use="required"/>
                                       <xs:attribute name="end" type="xs:int" use="required"/>
                                  </xs:complexType>
                             </xs:element>
                             <xs:element name="evList" type="evListType" minOccurs="0" xdb:SQLName="EVLIST1"/>
                        </xs:sequence>
                        <xs:attribute name="topic" use="required">
                             <xs:simpleType>
                                  <xs:restriction base="xs:string">
                                       <xs:enumeration value="mass spectrometry"/>
                                  </xs:restriction>
                             </xs:simpleType>
                        </xs:attribute>
                        <xs:attribute name="molWeight" type="xs:float" use="required"/>
                        <xs:attribute name="mwError" type="xs:string" use="optional"/>
                        <xs:attribute name="msMethod" type="xs:string" use="optional"/>
                   </xs:extension>
              </xs:complexContent>
         </xs:complexType>
    Eg...
    The second issue with the /u0000 is caused by the key/key reference definitions in the schema.
    If you comment them out the schema will register
                             <!--
                             <xs:key name="referenceKey">
                                  <xs:selector xpath="organismList/organism|dbReferenceList/dbReference"/>
                                  <xs:field xpath="@iRefID"/>
                             </xs:key>
                             <xs:key name="evidenceReferenceKey">
                                  <xs:selector xpath="evidenceList/evidence"/>
                                  <xs:field xpath="@evID"/>
                             </xs:key>
                             <xs:keyref name="evidenceReference" refer="evidenceReferenceKey">
                                  <xs:selector xpath=".//ev"/>
                                  <xs:field xpath="@ref"/>
                             </xs:keyref>
    -->

  • Background job finishes but error Error While Updating Material into Standard SAP5678

    Dear
    we run background job which finishes successfully but when we sqw logs it shows
    Error While Updating Material into Standard SAP5678
    Kindly share the reasons
    Regards

    This is an ERP Upgrade space and you should consider raising threads in the right space for prompt replies. Next time consider using SAP NetWeaver Administrator space for issues like these. Also you should consider closing your previous thread with the correct answer for future reference.
    What I see is a custom job. You should check what the job does and also the trace file of the work process and the consult with the application team or the developer for more information. Unfortunately with that screenshot there is nothing much we can advice you.
    Regards
    RB

  • Please help me. I am getting an error while launching an web start applic

    I am getting the following error while launching an java web start apllication.
    Exception in thread"javaWSApplicationMains"java.lan.NoClassDefFound:SimpleSerial.
    The jnlp file i have used is as follows:
    <?xml version="1.0" encoding="utf-8"?>
    <!-- JNLP File for Aeon HHBM Manager Application -->
    <jnlp spec="1.0+" codebase="http://zycomm:8080" href="Aeon.jnlp">
    <information>
    <title>Aeon HHBM Manager</title>
    <vendor>ME</vendor>     
    <description>Aeon HHBM Manager</description>
    </information>
    <offline_allowed/>
    <resources>
    <j2se version="1.4+"/>
    <jar href="aeon.jar"/>
    </resources>
    <application-desc main-class="Aeon_PManager" />
    <component-desc/>
    </jnlp>
    The java code is as follows:
    SimpleSerial.java
    import java.io.*;
    //import java.lang.*;
    //import java.lang.ClassNotFoundException;
    Interface class for SimpleSerial.
    If you don't know what an interface is, don't worry. An interface defines the functions
    that can be called by implementors of this class. Currently there are two implementors,
    SimpleSerialNative, and SimpleSerialJava. There might be more in the future.
    SimpleSerialNative requires the file "SimpleSerialNative.dll" to be in the same folder as your Java
    project file. It's that simple.
    SimpleSerialJava requires the correct installation of Sun's Javacomm communication package. It's much
    more powerful, but it can be tricky for the newcomer to configure, and use.
    If you have problems with one, why don't you try the other.
    A VERY SIMPLE IMPLEMENTATION:
    public static void main(String args[]) {
    SimpleSerial ss; // delcare the SimpleSerial object
    ss = new SimpleSerialNative(2); // The argument is the commport number. There is no Comm0.
    ss.writeByte((byte)'a'); // write a byte to the serial port
    // Give the PIC chip time to digest the byte to make sure it's ready for the next byte.
    try { Thread.sleep(1); } catch (InterruptedException e) {}
    ss.writeByte((byte)'!'); // write another byte to the serial port
    String inputString = ss.readString(); // read any string from the serial port
    System.out.println("I read the string: " + inputString);
    A few important things to note:
    1. When you write data to the serial port, it just writes the data, whether or not the PIC chip is
    ready to receive data. There's no handshaking or signaling. If you send data and the PIC chip
    isn't ready for it, it will be ignored. Some PIC chips have a hardware UART which will buffer a
    few bytes of data for later retrieval. But this isn't a cure-all. If the buffer fills up, it
    creates an error condition which prevents further data from being read. You need to include
    custom PIC code to reset the error flag.
    2 In contrast to the PIC chip, the computer has a rather large hardware buffer. If the PIC chip
    sends serial data to your computer when you're not around to read it, it gets stored.
    3. If you make a call to readByte(), and there's no data to be read, readByte() waits until there
    is data. If you want to know how much data (if any) is available, make a call to available().
    4. Conversely, if you make a call to readBytes() or readString() and there's no data to be read,
    readBytes() returns a byte array of zero length, and readString() returns and empty string.
    5. If you want to use Sun's JavaComm package instead of this code, subsitute your calls to
    new SimpleSerialNative(2);
    with
    new SImpleSerialJava(2);
    public interface SimpleSerial {
    // These are copied right out of WINBASE.H
    // Most applications should be fine with the defaults.
    public static final int NOPARITY = 0;
    public static final int ODDPARITY = 1;
    public static final int EVENPARITY = 2;
    public static final int MARKPARITY = 3;
    public static final int SPACEPARITY = 4;
    public static final int ONESTOPBIT = 0;
    public static final int ONE5STOPBITS = 1;
    public static final int TWOSTOPBITS = 2;
    Returns the number of bytes available at the time of this call.
    It's possible there are more bytes by the time readByte() or
    readBytes() is executed. But there will never be fewer.
    public int available();
    public void waitForData(int n);
    public boolean writeString(String string);
    returns TRUE if port is fully operationsal
    returns FALSE if there is a problem with the port
    public boolean isValid();
    Be sure to close your serial port when done. Note that port is
    automatically closed on exit if you don't close it yourself
    public void close();
    Reads a single byte from the input stream.
    Return value will be from -128 to 127 (inclusive)
    If no data at serial port, waits in routine for data to arrive.
    Use available() to check how much data is available.
    If error, returns 256.
    public int readByte();
    Reads all the bytes in the serial port.
    If no bytes availble, returns array with zero elements.
    Never waits for data to arrive
    public byte[] readBytes();
    Reads bytes from serial port and converts to a text string.
    DO NOT use this routine to read data. Char->Byte converstion
    does strange things when the values are negative. For non-
    text values, use readBytes() above
    public String readString();
    Writes a single byte to the serial port.
    This writes the data, whether the PIC is ready to receive or not.
    Be careful not to overwhelm the PIC chip with data.
    On pics without a hardware UART, the data will be ignored.
    On pics with a hardware UART, overflowing will loose data AND require
    the UART on the PIC to be reset. You can reset the UART in PIC code,
    or manually turn the PIC off and then on.
    NOTE: A byte has a value in the range of -128 to 127
    NOTE: If you want to write a character, you need to cast it to a byte,
    for example: simpleSerial.writeByte((char)'b');
    public boolean writeByte(byte val);
    For more advanced use. Gets the input stream associated with serial port
    public InputStream getInputStream();
    For more advanced use. Gets the output stream associated with serial port
    public OutputStream getOutputStream();
    Please help I am the beginner in web start.Please

    Notes:
    1) Please use the code tags when posting code or JNLP/HTML. It helps to retain indentation and avoids asterisks and plus sings being interpreted as formatting marks. To do that, select the code/JNLP etc. and click the CODE button seen on the Plain Text tab of the message posting form.
    2) That launch file is invalid. You might check it (and the project in general) using JaNeLA.
    3) The only place that SimpleSerial class could be, that the JRE would find, is in the root of aeon.jar. Is it actually there?

Maybe you are looking for

  • I need help urgently!!!  How do you get a button to open up a menu or something that has more buttons on it.

    I need to find out how to create a button that when pressed will bring up a menu with other buttons on it. I am doing this for a school assignment. Basicly, i select "Shoes" and that brings up a menu where i can chose from a bunch of different shoes.

  • Cursors in XY Graph are blinking

    Hello, The graph at XY graph component should be repainted too often (2 - 3 times in second). The graph doesn't blink, because "Update smoothing" option is on. But cursors at this graph are repainted every time so they are blinking very strong and cu

  • Oracle MS SQL Migration

    Hi I am following the steps listed here: http://www.oracle.com/technology/obe/hol08/sqldev_migration/mssqlserver/migrate_microsoft_sqlserver_otn.htm I get to step 5 of Capturing the Microsoft SQL Server Exported Files it does not pickup any of the us

  • About configuring IM in multipile domains

    Hi all, I can use IM service in single domain, but when I create more domains in DA, users in other domains can't sign on IM service. And I saw the error message from console as the following WARNING: Attention! The organization o=isp is not associat

  • Trying to decide on a T-series - advice appreciated!

    I'm going into my second year of college and would like to buy a laptop that's sleeker and lighter for taking to computer science classes, engineering clubs, and the like. My current Inspiron 9300 semi-gaming machine is 9 pounds - even if it is the o