.tld not generated for declarative component

i have a declarative component. for quite some time i was racking my brain trying to figure out why my tag alternated between working fine and giving me the error: "Error: Encountered deferred syntax #{ ... ". i finally found out that when i generate my ADF lib JAR from the IDE (project > deploy), there is a .tld file generated and inserted into the resulting JAR, and all works fine.
however, when the ADF library is built indirectly as a dependency of a WAR (profile depdency), there is no .tld generated, it is not present in the ADF lib JAR and i get the error "Error: Encountered deferred syntax #{ ..." when i run my app.
what would cause the .tld NOT to be generated as i described above? any help is appreciated.

Hi,
the recommendation for declarative components is to build them in a separate project and deploy them to consuming apps using the Resource catalog. A WAR deployment does built on dependent librares, but I don't thin k it knows hoa to build the librarries properly. So you create the ADF library and reference it in the WAR file, this then is supposed to work
Frank

Similar Messages

  • Lines are not generated for holidays and sundays

    Hi
    creating a sale order shcedule lines are not generated for sunday for a particular plant .
    Schedule lines are generated for subsequent monday only.
    the plant calander  is also  correct
    with regards
    partha

    Hi
    I would really double check the factory calendar ans the  of the plant and sales organisation
    regards,
    Sidi

  • Excise Accounting document not generated for Imported Asset GR

    Dear all,
    Excise accounting document is not generated for imported asset goods receipt(MIGO)
    but "C" Register part 2 no. is generated,usual accounting document is generated for GR,
    Asset is Dr to GR/IR
    Process is
    1. Create asset purchase order with acct. assignment "A",
    2. Customs miro based on p.o.
    3. Do GR with excise
    4. Post invoice for orginal vendor.
    What will be cause of this problem ?
    How to solve this issue ?

    The above issue may be due to Accout assignmnet -A . Check your accout assignment  in spro -mm-purchasing -accout assignment - Asset A - GR Non valuated has Ticked on . If it is ticked on - No Fi entry will happen at the Time of GR .
    The reason being , if an FI entry happen for the first time , asset is capitalised . To avoid this GR is made in ur config as this .
    rewdzzzz is full if correct
    Edited by: manu m on Apr 24, 2010 11:11 AM

  • Accounting document not generating for excise invoice.

    Dear all ,
    my issue is
    accounting document not generating for excise invoice
    we are creating accounting document in J1iin
    with refferance to billing document but the accounting docuemnt is not generating
    the accounting document for billing document is generated
    so why the accounting document for excise invoice is not genrating its showing the correct amount in BED ,cee and HE Secc.
    please help
    regards
    Subrat

    IMG -> In Logistics u2013 General -> Tax on Goods Movement -> India ->  Account Determination -> Specify Excise Accounts per Excise Transaction
    Check if the following is maintained or not
    DLFC       CR Credit      PLAAED PLA AED account
    DLFC       CR Credit      PLAAT1 PLA AT1 Account
    DLFC       CR Credit      PLABED PLA BED account
    DLFC       CR Credit      PLACESS PLA cess account
    DLFC       CR Credit      PLAECS PLA ECS Account
    DLFC       CR Credit      PLASED PLA SED account
    DLFC       CR Credit      RG23AED RG 23 AED account
    DLFC       CR Credit      RG23AT1 RG 23 AT1 Account
    DLFC       CR Credit      RG23BED RG 23 BED account
    DLFC       CR Credit      RG23ECS RG 23 ECS Account
    DLFC       CR Credit      RG23SED RG 23 SED account
    DLFC       DR Debit       MSUSP CENVAT suspense account
    Also IMG -> In Logistics u2013 General -> Tax on Goods Movement -> India ->  Account Determination -> Specify G/L Accounts per Excise Transaction
    Check if for all Excise group u2013 DLFC u2013 Company Code combination GLs are maintained or not (especially in production client)

  • Accounting document not generating for excise invoice-please help

    Dear all ,
    my issue is
    accounting document not generating for excise invoice
    we are creating accounting document in J1iin
    with refferance to billing document but the accounting docuemnt is not generating
    the accounting document for billing document is generated
    so why the accounting document for excise invoice is not genrating its showing the correct amount in BED ,cee and HE Secc.
    please help

    Dear G. Lakshmipathi,
    As uknow i am getting problem when i am creating the debit memo
    so is there any specific ETT for debit memo is there .because we are not maintaining delivery type to billing type here in CIN setting
    so its not goods removal through sales . so what will be transaction type for this.
    how to check the error that why the accounting document is not generated as no error log is also comming.
    so please help me in this regards.
    Thanks with Regards
    Subrat

  • INTRASTAT / EXTRA - Credit memo not relevant for declaration

    Hi all,
    I have this problem with INTRASTAT declaration:
    Transaction VE08 mark credit memo as not relevant for declaration with this description "No association to a goods movement was found".
    Do you have any solutions?

    Hello,
    check VE80, if you have an exclusion indicator on the item category.
    If not try to run VE01 for your country and mark only credit memos. Use log type B. Check the message in the incompletion log. If your credit memos are not in the incompletion log, than run the transaction transaction VE08 you run before again. The credit memos should show up, otheriwse let me know what is the message in the incompletion log.
    Check also if you need to show credit memo from legal point. From my point of view it should show only data related to deliveries.
    Try and reply.
    Edited by: SAPSD1000 on May 25, 2009 6:03 PM

  • TimeStream  Error (not generated for year 1970)

    Dear Experts ,
    I am facing a problem with Time Stream .... When i try to open a Planning Book i am receiving the following message:
    Timestream (TS ZBRSNP_ZF ) not generated for year 1970
    Message no. T9507
    Diagnosis
    The date is outside the periods maintained in the factory or planning calendar (timestreams).
    System Response
    The error causes a system crash.
    Procedure
    a) Regenerate the timestream as far in the future (or possibly the past) as possible
    or
    b) Use the report ZZTSTRDELE to delete the runtime objects of the timestreams, if changes have been made to Customizing settings. For more information, see SAP Note 169885.
    It starts happen after i included Initial Column at Planning Book .... The Factory Calendar that i am using starts on 2006 and ends on 2020 .... The timestream i am using is looking for 2 years in the past and 9 years in the future.
    *The message above says that it is necessary to execute report ZZTSTRDELE but i am having some problems while donwloading SAP note. It is possible do delete it manually?  exist another way to fix this issue?
    Please i hope someone can help me as soon as possible ....
    My Best Regards
    Mauricio Filho

    Hi Sunitha,
    We have same type of problem now, could you plz adivise me how to fix this error and where we need to configure to overcome this error.
    Thanks in advance
    Sreeenivasu

  • J1INQEFILE is not generating for the month of March 2011

    Hi,
    J1INQEFILE is not generating for the month of March 2011, we have executed Qefile from 01/01/2011 to 31/03/2011 then file is generating but March 2011 data is not available.
    Problem is challans were updated in the month of April 2011 for March 2011 documents, When we executed J1INMIS report with Bank Challan status, documents are coming in the report.
    As per our understanding Challan numbers and Bank Challan update should be done in the month of March 2011 but challans and Bank challans were updated in the April 2011.
    Please suggest.
    Thanks,
    Ratnam

    Hi Vara,
    Please check following thing in the system.
    1) When the Challan is created ( March month or April 2011)
    2) When the Bank challn updated for the challans
    3) If the Challan created in the April and generating returns for the month of March 2011.
    4) Check in J1INMIS report for the month posting date 01.03.2011 to 31.03.2011, if the external Challan number is appearing or not for the documents.
    5) If the Challan created in the April ask user to revere through J1INREV, and make Challan in the month of march 2011.
    Problem will solve.
    Thanks,
    Ratnam.

  • Build Plugin IS NOT DEFINED for this component or the defined Build Plugin

    Hello,
    we have upgraded our NWDI (nw04s) to SP13 and to DB2 V.9. We don't know if this has something to do with our problem. The NWDS developers called us. They can't activate the changes anymore. When I check the CBS I can see, that all components are broken. Any idea?
    REgards,
    Alexander
    Build number assigned: 487
    Change request state from QUEUED to PROCESSING
    REQUEST PROCESSING started at 2007-10-10 10:46:13.526 GMT
        BUILD request in Build Space "NW1_GPMS_D" at Node ID: 27,972,750
         [id: 473; parentID: 0; type: 2]
        Waiting for access: 33 ms
        ===== Pre-Processing =====  started at 2007-10-10 10:46:13.559 GMT
            Calculate all combinations of components and variants to be built...
            Analyze request DC BV... started at 2007-10-10 10:46:13.702 GMT
                    'zurich.com/gpms/jco_pool' variant 'default'
                    'zurich.com/gpms/jco_pool' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/yea' variant 'default'
                    'zurich.com/gpms/yea' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/chgpwd' variant 'default'
                    'zurich.com/gpms/chgpwd' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/rep' variant 'default'
                    'zurich.com/gpms/rep' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/model' variant 'default'
                    'zurich.com/gpms/model' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/idp' variant 'default'
                    'zurich.com/gpms/idp' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/ovt' variant 'default'
                    'zurich.com/gpms/ovt' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/arch' variant 'default'
                    'zurich.com/gpms/arch' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/myr' variant 'default'
                    'zurich.com/gpms/myr' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/div' variant 'default'
                    'zurich.com/gpms/div' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/ume' variant 'default'
                    'zurich.com/gpms/ume' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/com' variant 'default'
                    'zurich.com/gpms/com' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/ovw' variant 'default'
                    'zurich.com/gpms/ovw' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/obj' variant 'default'
                    'zurich.com/gpms/obj' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/chgpwdb' variant 'default'
                    'zurich.com/gpms/chgpwdb' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/pdata' variant 'default'
                    'zurich.com/gpms/pdata' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
            Analyze request DC BV... finished at 2007-10-10 10:46:14.049 GMT and took 347 ms
            Prepare build environment in the file system... started at 2007-10-10 10:46:14.049 GMT
                Synchronize development configuration... started at 2007-10-10 10:46:14.049 GMT
                Synchronize development configuration... finished at 2007-10-10 10:46:14.068 GMT and took 19 ms
                Synchronize used libraries... started at 2007-10-10 10:46:14.068 GMT
                Synchronize used libraries... finished at 2007-10-10 10:46:14.068 GMT and took 0 ms
            Prepare build environment in the file system... finished at 2007-10-10 10:46:14.068 GMT and took 19 ms
        ===== Pre-Processing =====  finished at 2007-10-10 10:46:14.069 GMT and took 510 ms
        Waiting for access: 3 ms
        ===== Processing =====  started at 2007-10-10 10:46:14.072 GMT
            No Components to be built.
            BUILD DCs
        ===== Processing =====  finished at 2007-10-10 10:46:17.407 GMT and took 3 s 335 ms
        ===== Post-Processing =====
        Waiting for access: 5 ms
        ===== Post-Processing =====  started at 2007-10-10 10:46:17.412 GMT
            STORE build results... started at 2007-10-10 10:46:17.413 GMT
                "zurich.com/gpms/jco_pool" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/jco_pool": store meta-data
                "zurich.com/gpms/jco_pool" in "default" variant  is PROCESSED
                "zurich.com/gpms/yea" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/yea": store meta-data
                "zurich.com/gpms/yea" in "default" variant  is PROCESSED
                "zurich.com/gpms/chgpwd" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/chgpwd": store meta-data
                "zurich.com/gpms/chgpwd" in "default" variant  is PROCESSED
                "zurich.com/gpms/rep" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/rep": store meta-data
                "zurich.com/gpms/rep" in "default" variant  is PROCESSED
                "zurich.com/gpms/model" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/model": store meta-data
                "zurich.com/gpms/model" in "default" variant  is PROCESSED
                "zurich.com/gpms/idp" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/idp": store meta-data
                "zurich.com/gpms/idp" in "default" variant  is PROCESSED
                "zurich.com/gpms/ovt" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/ovt": store meta-data
                "zurich.com/gpms/ovt" in "default" variant  is PROCESSED
                "zurich.com/gpms/arch" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/arch": store meta-data
                "zurich.com/gpms/arch" in "default" variant  is PROCESSED
                "zurich.com/gpms/myr" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/myr": store meta-data
                "zurich.com/gpms/myr" in "default" variant  is PROCESSED
                "zurich.com/gpms/div" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/div": store meta-data
                "zurich.com/gpms/div" in "default" variant  is PROCESSED
                "zurich.com/gpms/ume" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/ume": store meta-data
                "zurich.com/gpms/ume" in "default" variant  is PROCESSED
                "zurich.com/gpms/com" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/com": store meta-data
                "zurich.com/gpms/com" in "default" variant  is PROCESSED
                "zurich.com/gpms/ovw" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/ovw": store meta-data
                "zurich.com/gpms/ovw" in "default" variant  is PROCESSED
                "zurich.com/gpms/obj" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/obj": store meta-data
                "zurich.com/gpms/obj" in "default" variant  is PROCESSED
                "zurich.com/gpms/chgpwdb" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/chgpwdb": store meta-data
                "zurich.com/gpms/chgpwdb" in "default" variant  is PROCESSED
                "zurich.com/gpms/pdata" in "default" variant  is BROKEN. No build results to store.
                "zurich.com/gpms/pdata": store meta-data
                "zurich.com/gpms/pdata" in "default" variant  is PROCESSED
            STORE build results... finished at 2007-10-10 10:46:17.440 GMT and took 27 ms
            Change request state from PROCESSING to SUCCEEDED
            Analyze effect of applied changes to buildspace state... started at 2007-10-10 10:46:17.440 GMT
                Skip check for build time dependency cycles. DC metadata is not changed.
                Determine components that have become DIRTY due to the results of this request started at 2007-10-10 10:46:18.601 GMT
                    No such components have been found.
                Determine components that have become DIRTY due to the results of this request finished at 2007-10-10 10:46:18.602 GMT and took 1 ms
                No Internal Build Requests are canceled by this request
            Analyze effect of applied changes to buildspace state... finished at 2007-10-10 10:46:18.642 GMT and took 1 s 202 ms
            Request SUCCEEDED
        ===== Post-Processing =====  finished at 2007-10-10 10:46:18.646 GMT and took 1 s 234 ms
    REQUEST PROCESSING finished at 2007-10-10 10:46:18.646 GMT and took 5 s 120 ms
        ===== Pre-Processing =====  started at 2007-10-10 07:16:55.069 GMT
            Calculate all combinations of components and variants to be built...
            Analyze request DC BV... started at 2007-10-10 07:16:55.104 GMT
                    'zurich.com/gpms/jco_pool' variant 'default'
                    'zurich.com/gpms/jco_pool' variant 'default' cannot be built and will be marked as BROKEN.
                    Build Plugin IS NOT DEFINED for this component or the defined Build Plugin is INVALID.
                    'zurich.com/gpms/yea' variant 'default'

    Here are some things to have a look at:
    - Check your SC definitions and their Usage Dependencies in the SLD
    - Check that the basis SCA's have been imported into the track. You can quickly see this by having a look at the total nr of DCs for these SCs in CBS.

  • Connection has no password, -jdbc.xml file not generated for connection

    Hi,
    I'm migrating a jdev 10g web application (with EJB) to 11g, i did the automatic migration tool offred by 11g, i'm using the integrated weblogic server but it seems there is a *-jdbc.xml file missed, and it must be generated, this is the log file of the start of server :
    IntegratedWebLogicServer started.
    [Running application SAB_ADMIN on Server Instance IntegratedWebLogicServer...]
    [09:14:15 AM] ---- Deployment started. ----
    [09:14:15 AM] Target platform is (Weblogic 10.3).
    [09:14:18 AM] Retrieving existing application information
    [09:14:19 AM] Running dependency analysis...
    [09:14:19 AM] Deploying 4 profiles...
    [09:14:21 AM] Wrote Web Application Module to C:\Users\Moshe\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\o.j2ee\drs\SAB_ADMIN\ViewControllerWebApp.war
    [09:14:21 AM] Wrote Web Application Module to C:\Users\Moshe\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\o.j2ee\drs\SAB_ADMIN\ModelWebApp.war
    [09:14:25 AM] Wrote EJB Module to C:\Users\Moshe\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\o.j2ee\drs\SAB_ADMIN\ModelEJB.jar
    [09:14:25 AM] WARNING: Connection DBConnectionSAB has no password. DBConnectionSAB-jdbc.xml file not generated for connection DBConnectionSAB.
    [09:14:26 AM] Wrote Enterprise Application Module to C:\Users\Moshe\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\o.j2ee\drs\SAB_ADMIN
    [09:14:26 AM] Deploying Application...
    <14 oct. 2010 09 h 14 GMT+01:00> <Notice> <EclipseLink> <BEA-2005000> <2010-10-14 09:14:28.065--ServerSession(40464643)--property eclipselink.jdbc.user is deprecated, property javax.persistence.jdbc.user should be used instead.>
    <14 oct. 2010 09 h 14 GMT+01:00> <Notice> <EclipseLink> <BEA-2005000> <2010-10-14 09:14:28.299--ServerSession(40464643)--property eclipselink.jdbc.driver is deprecated, property javax.persistence.jdbc.driver should be used instead.>
    <14 oct. 2010 09 h 14 GMT+01:00> <Notice> <EclipseLink> <BEA-2005000> <2010-10-14 09:14:28.299--ServerSession(40464643)--property eclipselink.jdbc.url is deprecated, property javax.persistence.jdbc.url should be used instead.>
    <14 oct. 2010 09 h 14 GMT+01:00> <Notice> <EclipseLink> <BEA-2005000> <2010-10-14 09:14:28.299--ServerSession(40464643)--property eclipselink.jdbc.password is deprecated, property javax.persistence.jdbc.password should be used instead.>
    <14 oct. 2010 09 h 14 GMT+01:00> <Warning> <EJB> <BEA-012035> <The Remote interface method: 'public abstract java.lang.Object oracle.user.Session_user.mergeEntity(java.lang.Object)' in EJB 'SessionEJB' contains a parameter of type: 'java.lang.Object' which is not Serializable. Though the EJB 'SessionEJB' has call-by-reference set to false, this parameter is not Serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is Serializable.>
    <14 oct. 2010 09 h 14 GMT+01:00> <Warning> <EJB> <BEA-012035> <The Remote interface method: 'public abstract java.lang.Object oracle.user.Session_user.persistEntity(java.lang.Object)' in EJB 'SessionEJB' contains a parameter of type: 'java.lang.Object' which is not Serializable. Though the EJB 'SessionEJB' has call-by-reference set to false, this parameter is not Serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is Serializable.>
    <14 oct. 2010 09 h 14 GMT+01:00> <Warning> <EJB> <BEA-012035> <The Remote interface method: 'public abstract java.lang.Object oracle.bouton.Session_bouton.mergeEntity(java.lang.Object)' in EJB 'Session_bouton' contains a parameter of type: 'java.lang.Object' which is not Serializable. Though the EJB 'Session_bouton' has call-by-reference set to false, this parameter is not Serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is Serializable.>
    <14 oct. 2010 09 h 14 GMT+01:00> <Warning> <EJB> <BEA-012035> <The Remote interface method: 'public abstract java.lang.Object oracle.bouton.Session_bouton.persistEntity(java.lang.Object)' in EJB 'Session_bouton' contains a parameter of type: 'java.lang.Object' which is not Serializable. Though the EJB 'Session_bouton' has call-by-reference set to false, this parameter is not Serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is Serializable.>
    <14 oct. 2010 09 h 14 GMT+01:00> <Warning> <EJB> <BEA-012035> <The Remote interface method: 'public abstract java.lang.Object oracle.operation.Session_operation.mergeEntity(java.lang.Object)' in EJB 'Session_operation' contains a parameter of type: 'java.lang.Object' which is not Serializable. Though the EJB 'Session_operation' has call-by-reference set to false, this parameter is not Serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is Serializable.>
    <14 oct. 2010 09 h 14 GMT+01:00> <Warning> <EJB> <BEA-012035> <The Remote interface method: 'public abstract java.lang.Object oracle.operation.Session_operation.persistEntity(java.lang.Object)' in EJB 'Session_operation' contains a parameter of type: 'java.lang.Object' which is not Serializable. Though the EJB 'Session_operation' has call-by-reference set to false, this parameter is not Serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is Serializable.>
    <14 oct. 2010 09 h 14 GMT+01:00> <Notice> <EclipseLink> <BEA-2005000> <2010-10-14 09:14:29.656--ServerSession(42285779)--property eclipselink.jdbc.user is deprecated, property javax.persistence.jdbc.user should be used instead.>
    <14 oct. 2010 09 h 14 GMT+01:00> <Notice> <EclipseLink> <BEA-2005000> <2010-10-14 09:14:29.656--ServerSession(42285779)--property eclipselink.jdbc.driver is deprecated, property javax.persistence.jdbc.driver should be used instead.>
    <14 oct. 2010 09 h 14 GMT+01:00> <Notice> <EclipseLink> <BEA-2005000> <2010-10-14 09:14:29.656--ServerSession(42285779)--property eclipselink.jdbc.url is deprecated, property javax.persistence.jdbc.url should be used instead.>
    <14 oct. 2010 09 h 14 GMT+01:00> <Notice> <EclipseLink> <BEA-2005000> <2010-10-14 09:14:29.656--ServerSession(42285779)--property eclipselink.jdbc.password is deprecated, property javax.persistence.jdbc.password should be used instead.>
    <14 oct. 2010 09 h 14 GMT+01:00> <Error> <HTTP> <BEA-101371> <There was a failure when processing annotations for application C:\Users\Moshe\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\o.j2ee\drs\SAB_ADMIN\ModelWebApp.war. Please make sure that the annotations are valid. The error is oracle.adf.view.faces.webapp.ResourceServlet>
    <14 oct. 2010 09 h 14 GMT+01:00> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1287044066833' for task '0'. Error is: 'weblogic.application.ModuleException: Failed to load webapp: 'SAB_CRUD-Model-context-root''
    weblogic.application.ModuleException: Failed to load webapp: 'SAB_CRUD-Model-context-root'
         at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:404)
         at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:508)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         Truncated. see log file for complete stacktrace
    Caused By: java.lang.ClassNotFoundException: oracle.adf.view.faces.webapp.ResourceServlet
         at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:280)
         at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:253)
         at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:56)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
         Truncated. see log file for complete stacktrace

    This is the content of my web.xml file where i found the markup <servlet> and i tried to run without the first one but the error still like it was :
    <servlet>
    <servlet-name>Faces Servlet</servlet-name>
    <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
    <load-on-startup>1</load-on-startup>
    </servlet>
    <servlet>
    <servlet-name>resources</servlet-name>
    <servlet-class>oracle.adf.view.faces.webapp.ResourceServlet</servlet-class>
    </servlet>
    <servlet>
    <servlet-name>resources</servlet-name>
    <servlet-class>org.apache.myfaces.trinidad.webapp.ResourceServlet</servlet-class>
    </servlet>
    <servlet>
    <description>Web Service MyConnexionServiceSoapHttpPort</description>
    <display-name>Web Service MyConnexionServiceSoapHttpPort</display-name>
    <servlet-name>MyConnexionServiceSoapHttpPort</servlet-name>
    <servlet-class>oracle.controll.ConnexionBaseDeDonnees</servlet-class>
    <load-on-startup>1</load-on-startup>
    </servlet>
    <servlet>
    <servlet-name>ResultatRequetePort</servlet-name>
    <servlet-class>oracle.controll.ResultatRequete</servlet-class>
    <load-on-startup>1</load-on-startup>
    </servlet>
    <servlet-mapping>
    <servlet-name>Faces Servlet</servlet-name>
    <url-pattern>/faces/*</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>resources</servlet-name>
    <url-pattern>/adf/*</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>MyConnexionServiceSoapHttpPort</servlet-name>
    <url-pattern>MyConnexionServiceSoapHttpPort</url-pattern>
    </servlet-mapping>
    <servlet-mapping>
    <servlet-name>ResultatRequetePort</servlet-name>
    <url-pattern>/ResultatRequetePort</url-pattern>
    </servlet-mapping>
    Thanks...

  • Credit memo not generated for RMA Receipt

    Hi,
    i created RMA receipt but for this credit memo not generated in AR, Manually i have run the Workflow Background Process  & Receiving transaction processor concurrent also. even though CM not generated(In AR Interface lines table also data is not available)..or else is there any possibility for cancel or return the RMA Receipt quantity?
    regards
    Balaji
    Edited by: user9122706 on May 15, 2012 9:22 PM
    Edited by: user9122706 on May 15, 2012 9:51 PM

    Dear Balaji,
    Credit memo not generated for RMA Receipt,Can u put manual credit in AR
    Regards,
    Shineee..

  • Pur req not generated for MRP element Planned order in stock reqmnts list

    Hi SAP Gurus,
    I have a problem where in MD04, pur req is not generated for the MRP element Planned order for a future date (about two months from now). Is there a specific reason? why is it not being generated? The MRP type is PD. The procurement type is F - external procurement. Can anybody please help me on this?
    Thanks
    Anusha

    Anusha,
    ??  Not sure I understand the question.  Are you saying MRP is creating planned orders instead of  purchase reqs?  Or, are you saying that no proposals at all are being created outside of two months?  Or, are you saying that the system is creating purchase reqs inside of two months, and planned orders outside of two months?
    Regardless, these problems are probably related to your MRP settings.  Try the following settings:
    NEUPL   Regenerative planning             
    1       Purchase requisitions             
    3       Schedule lines                    
    1       MRP list                          
    3       Delete and recreate planning data 
    2       Lead time scheduling and capacity planning
    on your MDBT screen.
    Regards,
    DB49

  • REquirement not generated for component of Phantom Item

    Dear Gurus,
    We have a scenario where A,B,C and D are part of multilevel BOM. A is finshed product. B and C are phantoms. D is RM.
    A is level 1, B level 2and C level 3. D is component of C.
    After MRP run, we found that requirement is generated for Material A. However, corresponsing requirement of material D is not generated. Could you please suggest what can be the problem ?

    Hi
    The parameters maintained by you are more or less OK.
    Your issue is : you are not getting requirements for the part for which you have maintained manual reorder point.
    It seems you have run MD02.
    If you run MD02 requirements for the component with reorder point will not be geneated because it is consumption based planning& it is not requirment based planning.
    For getting rquirement for that either you have to run single item single levelMD03 or total planning for the plant.
    This is std SAP functionality.
    Hope it is clear to you.
    Regards
    YMREDDY

  • Tag Library for Declarative Component

    Hi
    Using JDev 11gR1. I'm new to tag libraries and have the following question...
    How do I deploy a JAR file with a declaritive component as a JSP tag Library? I have created a new project, created a new tag library in the project (.tld file) and created a reusable toolbar in the project. How do I include the tags and attributes of the declarative component in the .tld file? Do I just edit the file or have I missed some steps which would have done this.
    When creating the new declarative component I did us the "Add Tag Library..." button to specify the tag library in the project.
    All declaritive component examples / tutorials / blogs / ADF dev guide, I find just tell you to deploy the jar file as a tag library and include it in the project to use it, but I can't find anything telling you how to deploy it as a tag library. Any help or references to examples will be great.
    Thanks
    Mario

    Shay, thanks for the reply.
    I started off following Grant's article which you referred me to, but ran into the problem I'm having now. Just tried it again and still no luck.
    I created a declarative component in a new project, setup the deployment profile to deploy to an ADF Library JAR and deployed it. Then I add the directory for the JAR to my Resource palette and add the JAR to the project which will be using it.
    But that's as far as I get, still nothing shows in my Component Palette.
    That's when I started on the wild goose chase of the TLD file. I looked at Andrejus' blog posting, [http://andrejusb.blogspot.com/2009/10/custom-declarative-components-in-adf.html| [http://andrejusb.blogspot.com/2009/10/custom-declarative-components-in-adf.html|http://andrejusb.blogspot.com/2009/10/custom-declarative-components-in-adf.html]] and the source and realised he has a tld file inside his generated JAR. Which lead to my question as to when this get's generated / defined?
    Any ideas what I could try to get my Components to display in the Component Palette?
    Thanks,
    Mario
    Edited by: Mario Ribeiro on Oct 28, 2009 10:10 AM

  • Purchase requisition not generate for dependent requirement after MRP run

    Hello PP expert,
      In our MTO scenario after MRP run planned order generate for header material but no PR generate for BOM components, (BOM not explode) when we run MRP component level in MD02 PR generate, system showing message "40- No coverage not provided by master plan" in MD04 order tree. this problem coming after when we DIMP applied. I checked some OSS note also.
    Can any one provide right solution.
    thanks in advance.....its urgent as client requirement.
    regards,
    Amit Awasthi.

    Hi Amit
    You must select the green star for the correct answer, in order to close the thread.
    You may also select the yellow start for the helpful answers, in order to award points for those who helped you. See the blog below for more details:
    How to close a discussion and why
    I can see that most of your old threads are still open, therefore, I'd like to ask you to review and close them, by selecting the correct answer.
    BR
    Caetano

Maybe you are looking for