Handling Transaction in Webdynpro problem?

hi All of you;
I am getting very peculiar problem :The problem is that data that i am inserting into R/3 using BAPI is committing without any call of Commit Bapi.The function Module of that BAPI also donot have commit method.Then also data is inserting into the R/3.I am not able to figure out the solution ;is there any problem by me in handling transaction thru webdynro or some problem in BAPI.
Regards
Nidhideep

Hi,
I guess problem is in BAPI only.
Check from BAPI only, by running that individually.
Coz, from Web Dynpro we wont be having any control on that, unless we call commit statement explicitly.
Regards,
Sridhar

Similar Messages

  • Calling sap transaction in webdynpro

    hi friends,
    can any body provide the solution how to call the standard transaction like va02 or .any . in Web dynpro abap.
    thanks in advance.
    sai.

    Hi,
    It can be posible to display a standard transaction into Webdynpro.for that no coding required.you need to use webgui for that. ( pls refer transaction SICF ). in that case u can specify the Tcode u want use in URL.
    like
    http://<server-name>:8000/sap/bc/gui/sap/its/webgui?~TRANSACTION=va02
    Call this url from linktourl or linktoaction
    Tell me if you find any problem in doing this
    Regards,
    Edited by: Raju.. on Jun 30, 2009 5:51 PM

  • Handle transaction in web dynpro applications

    Hello,
    can you please tell me How to handle transaction in web dynpro applications which is using Adaptive RFC model ?
    Thanks,
    Teja

    Hi,
    please see this [thread|Link to SAP Transaction using WebDynpro for Java;
    regards,

  • Handling transactions from Tuxedo

    Hi!
              I have a problem handling transactions within the WLS 8.1 when they are initiated from a Tuxedo-client.
              I have an EJB handling a tuxedo call. If the caller has not begun a transaction, all works well, but if the caller starts a transaction, the tpcommit() in the client will fail:
              CMDTUX_CAT:1459: ERROR: Can't commit transaction, tpcommit() failed - TPEABORT - transaction cannot commit
              (This error occurs when I run ud32 -t 60, if I skip the '-t 60', it works perfectly well).
              The <transaction-type> for my EJB is 'Container' and the <trans-attribute> is 'Supports'.
              Is there another setting I have to set to have the WTC handle the transaction correctly?
              Regards, Ola
              

              Hi again,
              Ignore this cry for help, I found a solution to my problem.
              I had missed the little checkbox furtherst down in the Advanced Option part of
              the Configuration of Data Sources: "Emulate Two-Phase Commit for non-XA Driver".
              With that one checked (we're using non-XA drivers) everything worked very well.
              So Yes, there was a setting I could use to eliminate my problem ;-)
              /Ola
              Ola Ödling <[email protected]> wrote:
              >Hi!
              >I have a problem handling transactions within the WLS 8.1 when they are
              >initiated from a Tuxedo-client.
              >I have an EJB handling a tuxedo call. If the caller has not begun a transaction,
              >all works well, but if the caller starts a transaction, the tpcommit()
              >in the client will fail:
              >CMDTUX_CAT:1459: ERROR: Can't commit transaction, tpcommit() failed -
              >TPEABORT - transaction cannot commit
              >(This error occurs when I run ud32 -t 60, if I skip the '-t 60', it works
              >perfectly well).
              >The <transaction-type> for my EJB is 'Container' and the <trans-attribute>
              >is 'Supports'.
              >
              >Is there another setting I have to set to have the WTC handle the transaction
              >correctly?
              >
              >Regards, Ola
              

  • Handle transaction in web dynpro

    Hi,
    How to handle transaction in web dynpro applications which is using Adaptive RFC model ?
    Thanks,
    Teja

    Hello Teja,
    Please refer tutorial at https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d352a790-0201-0010-5082-b1a608d22b6c.
    I hope it will help u to understand transaction handling in wd.
    Best Regards,
    Pankaj Sharma

  • How to handle transaction control--- in the dbms query or in JDBC? or BOTH?

    Hi all,
    we have a servlet application which do insert, update to a few sybase tables. so far we don't have any transaction management control in either store procedure or in JDBC call. i like to know where should we enforce this control logic? in both place or either one is enough?
    thanks!!

    according to your answer, is it safe to say that we
    should NOT
    handle transaction control in both query and JDBC
    call? i am on the side of JDBC
    program control. However our manager feels that if we
    handle it in two place, we could be more error-proof.
    i don't know how to convince him that only one place
    could make it work. Double your rollbacks double your fun! Odd that a manager is getting involved at this level...
    Providing transaction control at both places, as a rule makes absolutely no sense at all (to me). I actually believe that this would be far more error-prone (not error-proof). It's really a logistics issue. When you are working on the Java code, you won't have the stored procedure(s) code right there. While you may design it masterfully at first, as maintenance occurs, the mastery can easily be lost as assumptions are made on when and where commit or rollback processing is going to take place. The end result would be a system that could easily corrupt the logical integrity of the database.
    If you have to make a decision up front, and you believe performance will ultimately be a concern, then your decision should be to handle transaction management within the stored procedure(s). However, this decision will make the stored procedures far more complex than what the DBA or application staff is familiar with. You would also have to take some care to release resources as appropriate within the Java code.
    If you decide to manage transactions within JDBC, it is possible that you will have to move a portion of transaction managment to one or two of the stored procedures. This would be a 'fix' for a poorly performing functionality, and you would simply take care to limit this as much as possible.
    I wish I could guide you specifically, but I'm working at 20,000 feet related to your specific application needs.

  • Can we call an SAP transaction in Webdynpro

    Hi,
    I have a requirement to call an SAP transaction in Webdynpro, ie on clicking a button in a view, the particular SAP transaction has to come . Kindly tell me how to do it.
    Regards,
    Lakshmi

    Lakshmi,
    You cannot call a transaction from WDA
    check these threads
    https://forums.sdn.sap.com/click.jspa?searchID=19319106&messageID=6146192
    https://forums.sdn.sap.com/click.jspa?searchID=19319106&messageID=6476084
    Thanks
    Bala Duvvuri

  • How to handle Transactions avoiding EJB

    I am using EJB just to use its transaction feature. I know EJB is heavy and there must be other better ways to handle transactions.Could anybody let me know how to JTA (java transaction APIs) in JBDC or if there is any other recommended way to handle Transactions.
    Many Thanks.

    Google for "JTA tutorials".
    It brought back these:
    http://java.sun.com/products/jta/
    http://java.sun.com/j2ee/tutorial/1_3-fcs/doc/Transaction4.html#63068

  • Drilldown from workbook to R3 Transaction. InfoSource problem

    Hello sapfans,
    Using RSBBS i've made a link between a workbbok and a R3 transaction. The problem is that each time the user choose the path:
    GoTo->MyTransaction the Bex ask him to select an InfoSource.....
    How do i Make this Popup to disapear??? I already chose the infosource and save the workbook but no results... 
    Please Advice,
    Amir

    Amir,
    Have you specified an InfoSource in RSBBS? Specify an InfoSource there and then try. InfoSource popup should not come then.
    Cheers
    Aneesh

  • Can not call RFC contains "call transaction"  in webdynpro

    We use Webdynpro to develope a UI that can create service orders in CRM
    system. We create an RFC funciton "ZKLEE_CRM_ORDER_MODIFY" in CRM,which
    contain a statement of "CALL TRANSACTION 'CRMD_BUS2000120' USING T_BDC
    MODE 'N' MESSAGES INTO MESSTAB.".
    But as we exacute the RFC from WEB,we got 3 error messages in the
    output "MESSTAB":
    1.MESSAGE ID = "DC",MESSAGE NUMBER = "006", MESSAGE = "Control
    Framework: Fatal error - GUI cannot be reached".
    2.MESSAGE ID = "SY",MESSAGE NUMBER = "002", MESSAGE = "Exception
    condition CNTL_ERROR raised."
    3.MESSAGE ID = "00",MESSAGE NUMBER = "359",and it is a terminate
    message.
    The problem is that we can use webdynpro to call RFCs that do not
    contain "call transaction" freely. At first we suspect that it is our
    RFC function's fault, but we tried it in ABAP enviroment,and it works
    OK. We also tried to call this RFC in JSP through JCO,the same error
    occurs.
    Our system enviroment is CRM 4.0, J2EE 640, kernel 640 patch 109.

    HI,
    Thank you for your information.
    Maybe you are right that BAPI/RFC can not contain "call transaction" statement. But two weeks ago, one of my colleagues tried to use "call transaction" in RFC through JCO in our R/3 enviroment(not in CRM),and he successed.
    So I suspect the kernel release. The kernel of R/3 is 640,while CRM is 620(I said our CRM kernel release is 640 before,and it is a mistake.).I will confirm whether what my colleague said is right by myself, and will also told you the result.
    Message was edited by: Vincent zklee

  • Handling Transaction in Stateful Session Bean

    I wrote a public method like public void doTransaction()
    it will call 2 private method, like: methodA and methodB
    Both private methods have db accesss statement and will update the db. They got different db connection and will close the connection when method call finished.
    How to include them to one transaction? I want to be able to rollback the job of the first method when I catch exception thrown by the second method.
    I tried simply define transaction type of the public method to be Container and Required. But it doesn't work, the first method doesn't rollback. Of course I can let the 2 private methods share a same connection and commit after finishing calling them. But how if they are in different DB?

    Ok... Here it goes...
    You can do it in the following manner.
    As you said you have got 2 private methods doing d/b updates and these are called from a public method.
    Stateful session beans since associated with a client across methods, you can take advantage of it. Write your own user defined transaction.
    Begin the transaction scope in your public before calling the 1st private method. Call the 2 methods in a try block. Once you are done with these methods, you can commit and end the transaction. If you get any exception, rollback the transaction in the catch block. Otherwise if u get any exception in the 2nd method, you can rollback the transaction there itself.
    Stateful session beans lets u allow to spawn the bean managed transaction across methods. you can begin your transaction in one method and end it in a differnt method or you can end the transaction after calling the methods.
    The problem you are dealing with can typically very well handled by writing bean managed transaction.
    Hope this helps. If you need anymore clarity on my solution, please let me know.
    -amit

  • Calling a transaction in webdynpro

    Hi,
      As per my requirement when a button click happens I need to call the transaction CAT2 by skipping initial screen. How to achieve this in webdynpro.
    Thanks
    Raghavendra

    Hi Raghavendra,
    If you are using portal as a triggerring point of your web dynpro applications, then the below requirement is achieved by doing the following.
    1. Create a BDC report program to call transaction CAT2 skipping the first screen.
    2. The report has the same input parameters as that of the transaction CAT2.
    3. Associate a transaction to the report program sat 'ZCAT2'.
    In the event handler of the button in your web dynpro do that following
    Data declarations
      Local Internal tables(lt_)
        lt_bus_parameter_list              TYPE wdy_key_value_table,
        lt_launcher_parameter_list         TYPE wdy_key_value_table,
      Local Work area's(ls_)
        ls_keyvalue_pair                   TYPE wdy_key_value,
      Local Variables(l_)
        l_pcdpageurl                       TYPE string,
        l_componentcontroller              TYPE REF TO if_wd_component,
        l_port_manager                     TYPE REF TO if_wd_portal_integration.
    Constants(c_)
      CONSTANTS:
       c_transaction_code            TYPE string VALUE 'ZCAT2',
       c_okcode                            TYPE string VALUE 'F8',
       c_param1                            TYPE string VALUE 'P_Data_Entry_Profile',
       c_param2                            TYPE string VALUE 'P_person_number'.
      l_componentcontroller = wd_this->wd_get_api( ).
      l_port_manager        = l_componentcontroller->get_portal_manager( ).
    Fill all the business parameters
      CLEAR ls_keyvalue_pair.
      ls_keyvalue_pair-key    =  c_param1.
      ls_keyvalue_pair-value  =  'Data Entry Profile'.
      APPEND ls_keyvalue_pair TO lt_bus_parameter_list .
      CLEAR ls_keyvalue_pair.
      ls_keyvalue_pair-key    =  c_param2.
      ls_keyvalue_pair-value  =  'Person Number'.
      APPEND ls_keyvalue_pair TO lt_bus_parameter_list .
    Fill the launcher parameters for the transaction
      CLEAR ls_keyvalue_pair.
      ls_keyvalue_pair-key    =  'AutoStart'.
      ls_keyvalue_pair-value  =  'Yes'.
      APPEND ls_keyvalue_pair TO lt_launcher_parameter_list.
      CLEAR ls_keyvalue_pair.
      ls_keyvalue_pair-key    =  'GuiType'.
      ls_keyvalue_pair-value  =  'WinGui'.
      APPEND ls_keyvalue_pair TO lt_launcher_parameter_list.
      CLEAR ls_keyvalue_pair.
      ls_keyvalue_pair-key    =  'OkCode'.
      ls_keyvalue_pair-value  =  c_okcode.
      APPEND ls_keyvalue_pair TO lt_launcher_parameter_list.
      CLEAR ls_keyvalue_pair.
      ls_keyvalue_pair-key    =  'System'.
      ls_keyvalue_pair-value  =  'SAP_R3_HumanResources'.
      APPEND ls_keyvalue_pair TO lt_launcher_parameter_list.
      CLEAR ls_keyvalue_pair.
      ls_keyvalue_pair-key    =  'TCode'.
      ls_keyvalue_pair-value  =  c_transaction_code.
      APPEND ls_keyvalue_pair TO lt_launcher_parameter_list.
      CLEAR ls_keyvalue_pair.
      ls_keyvalue_pair-key    =  'Technique'.
      ls_keyvalue_pair-value  =  'SSF'.
      APPEND ls_keyvalue_pair TO lt_launcher_parameter_list.
      CLEAR ls_keyvalue_pair.
      ls_keyvalue_pair-key    =  'WinGui_Type'.
      ls_keyvalue_pair-value  =  'Shortcut'.
      APPEND ls_keyvalue_pair TO lt_launcher_parameter_list.
    SAP has provided us with customizing table to maintain the path for the iView.Here Resource_key is the key field to get the path.
    We create a new entry in this table using which we uniquely identify the path of the iVew that needs to be launched.
    get the url of the pcd page for the common transaction iView
      SELECT SINGLE b~text
             INTO  l_pcdpageurl
             FROM  t7xssserstring AS b
             INNER JOIN t7xssserres AS a
             ON    arespcdpage  = bguid
             WHERE a~ressource = /rio/zcl_hse_constants=>c_common_resource.
    Navigate to the Injury Illness details
      CALL METHOD l_port_manager->navigate_absolute
        EXPORTING
          navigation_target   = l_pcdpageurl
          navigation_mode     = l_port_manager->co_show_external
          use_sap_launcher    = abap_true
          business_parameters = lt_bus_parameter_list
          launcher_parameters = lt_launcher_parameter_list.
    The folowing is the flow of the program:
    When user clicks a button to launch transaction CAT2, the event handler associated to it called.
    Here we populate an internal table with the parameters to call transaction ZCAT2 and the iView is launched by calling navigate_absolute method with the right path.
    I am not very much sure as to how the iViews are set up but there is a provision to read the key valure pair there. The values are read and the tranzation ZCAT2 is called which will inturn launch CAT2 transaction.
    By adding Skip First screen statement we can get in the details directly.
    Hope this helps.
    Regards,
    Sravan Varagani

  • Calling transaction through webdynpro abap applicatoin

    hi,
    Is it possible to call an EWT transaction or an transaction from a webdynpro abap application.
    Regards,
    Divya

    The example demo listed works under special circumstance ONLY.
    Logon to SAP.
    At main menu add a favourite of type WDA.
    Choose application wdr_sapgui_demo1  .
    Now run demo.
    The WDA app appears inside an SAP GUI screen.
    Now the when the runtime API call the sapgui manager, a handle to the GUI is available.
    The new transaction can now be fired. EG navigate away to new transation.
    If the GUI is not already active you have another issue.
    I suggest you search the forum for the use of SAPGUI shortcuts and other
    such tricks . There has been a few topics and solutions discussed.
    Cheers
    Phil.

  • Webdynpro problem

    Hello,
    EP 6.0 SP10
    sometimes when we run a create order transaction in the portal we get an error. (see below)
    I would also like to add that sometimes the "continue" button is disabled. So it seems like the connection to R/3 is failing or that de Portal did not receive feedback from R/3.
    Hopefully someone can help me.
    Thank you
    An error has occurred:
    "Failed to process the request."
    Please contact your system administrator.
    Hide details
    Web Dynpro client:
    HTML Client
    Web Dynpro client capabilities:
    User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322), version: null, DOM version: null, client type: msie6, client type profile: ie6, ActiveX: enabled, Cookies: enabled, Frames: enabled, Java applets: enabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
    Web Dynpro runtime:
    Vendor: SAP, Build ID: 6.4010.00.0000.20041209081817.0000 (release=630_VAL_REL, buildtime=2004-12-22:22:25:53[UTC], changelist=311488, host=PWDFM026)
    Web Dynpro code generators of DC local/DMSOrderCreation:
    SapDictionaryGenerationCore: 6.4009.00.0000.20041026131628.0000 (release=630_REL, buildtime=2004-11-02:22:13:11[UTC], changelist=295793, host=PWDFM027.wdf.sap.corp)
    SapMetamodelWebDynpro: 6.4009.00.0000.20041026132448.0000 (release=630_REL, buildtime=2004-11-02:22:17:25[UTC], changelist=295810, host=PWDFM027.wdf.sap.corp)
    SapMetamodelCore: 6.4009.00.0000.20040909194107.0000 (release=630_REL, buildtime=2004-11-02:22:06:29[UTC], changelist=280398, host=PWDFM027.wdf.sap.corp)
    SapWebDynproGenerationTemplates: 6.4009.00.0000.20041102105304.0000 (release=630_REL, buildtime=2004-11-02:22:38:28[UTC], changelist=297524, host=PWDFM027)
    SapWebDynproGenerationCTemplates: 6.4009.00.0000.20041102105304.0000 (release=630_REL, buildtime=2004-11-02:22:38:28[UTC], changelist=297524, host=PWDFM027)
    SapGenerationFrameworkCore: 6.4009.00.0000.20041026132141.0000 (release=630_REL, buildtime=2004-11-02:22:05:28[UTC], changelist=295805, host=PWDFM027.wdf.sap.corp)
    SapIdeWebDynproCheckLayer: 6.4009.00.0000.20041026133106.0000 (release=630_REL, buildtime=2004-11-02:22:21:59[UTC], changelist=295820, host=PWDFM027.wdf.sap.corp)
    SapMetamodelDictionary: 6.4009.00.0000.20040805191532.0000 (release=630_REL, buildtime=2004-11-02:22:10:20[UTC], changelist=270520, host=PWDFM027.wdf.sap.corp)
    SapMetamodelCommon: 6.4009.00.0000.20040909194107.0000 (release=630_REL, buildtime=2004-11-02:22:06:42[UTC], changelist=280398, host=PWDFM027.wdf.sap.corp)
    SapWebDynproGenerationCore: 6.4009.00.0000.20041026133106.0000 (release=630_REL, buildtime=2004-11-02:22:22:31[UTC], changelist=295820, host=PWDFM027.wdf.sap.corp)
    SapDictionaryGenerationTemplates: (unknown)
    Web Dynpro code generators of DC sap.com/tcwddispwda:
    No information available
    Web Dynpro code generators of DC sap.com/tcwdcorecomp:
    No information available
    J2EE Engine:
    No information available
    Java VM:
    Java HotSpot(TM) Server VM, version: 1.4.2_09-b05, vendor: Sun Microsystems Inc.
    Operating system:
    Windows 2003, version: 5.2, architecture: x86
    Error stacktrace:
    com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type com.dms.kubota.orders.models.types.Kunnr could not be loaded: com.sap.dictionary.runtime.DdException:
    at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
    at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:205)
    at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.init(AttributeInfo.java:485)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:771)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:756)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
    at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:346)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:349)
    at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:599)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
    at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:824)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
    at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Caused by: com.sap.dictionary.runtime.DdException:
    at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
    at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:587)
    at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:286)
    at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:81)
    at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
    at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
    at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:234)
    ... 31 more

    Please find the corresponding stacktrace in the logfile and post it here.
    Armin

  • EP Webdynpro problem

    Hello,
    EP 6.0 SP10
    sometimes when we run a create order transaction in the portal we get an error.  (see below)
    I would also like to add that sometimes the "continue" button is disabled. So it seems like the connection to R/3 is failing or that de Portal did not receive feedback from R/3.
    Hopefully someone can help me.
    Thank you
    An error has occurred:
    "Failed to process the request."
    Please contact your system administrator.
    Hide details
    Web Dynpro client:
    HTML Client
    Web Dynpro client capabilities:
    User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322), version: null, DOM version: null, client type: msie6, client type profile: ie6, ActiveX: enabled, Cookies: enabled, Frames: enabled, Java applets: enabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
    Web Dynpro runtime:
    Vendor: SAP, Build ID: 6.4010.00.0000.20041209081817.0000 (release=630_VAL_REL, buildtime=2004-12-22:22:25:53[UTC], changelist=311488, host=PWDFM026)
    Web Dynpro code generators of DC local/DMSOrderCreation:
    SapDictionaryGenerationCore: 6.4009.00.0000.20041026131628.0000 (release=630_REL, buildtime=2004-11-02:22:13:11[UTC], changelist=295793, host=PWDFM027.wdf.sap.corp)
    SapMetamodelWebDynpro: 6.4009.00.0000.20041026132448.0000 (release=630_REL, buildtime=2004-11-02:22:17:25[UTC], changelist=295810, host=PWDFM027.wdf.sap.corp)
    SapMetamodelCore: 6.4009.00.0000.20040909194107.0000 (release=630_REL, buildtime=2004-11-02:22:06:29[UTC], changelist=280398, host=PWDFM027.wdf.sap.corp)
    SapWebDynproGenerationTemplates: 6.4009.00.0000.20041102105304.0000 (release=630_REL, buildtime=2004-11-02:22:38:28[UTC], changelist=297524, host=PWDFM027)
    SapWebDynproGenerationCTemplates: 6.4009.00.0000.20041102105304.0000 (release=630_REL, buildtime=2004-11-02:22:38:28[UTC], changelist=297524, host=PWDFM027)
    SapGenerationFrameworkCore: 6.4009.00.0000.20041026132141.0000 (release=630_REL, buildtime=2004-11-02:22:05:28[UTC], changelist=295805, host=PWDFM027.wdf.sap.corp)
    SapIdeWebDynproCheckLayer: 6.4009.00.0000.20041026133106.0000 (release=630_REL, buildtime=2004-11-02:22:21:59[UTC], changelist=295820, host=PWDFM027.wdf.sap.corp)
    SapMetamodelDictionary: 6.4009.00.0000.20040805191532.0000 (release=630_REL, buildtime=2004-11-02:22:10:20[UTC], changelist=270520, host=PWDFM027.wdf.sap.corp)
    SapMetamodelCommon: 6.4009.00.0000.20040909194107.0000 (release=630_REL, buildtime=2004-11-02:22:06:42[UTC], changelist=280398, host=PWDFM027.wdf.sap.corp)
    SapWebDynproGenerationCore: 6.4009.00.0000.20041026133106.0000 (release=630_REL, buildtime=2004-11-02:22:22:31[UTC], changelist=295820, host=PWDFM027.wdf.sap.corp)
    SapDictionaryGenerationTemplates: (unknown)
    Web Dynpro code generators of DC sap.com/tcwddispwda:
    No information available
    Web Dynpro code generators of DC sap.com/tcwdcorecomp:
    No information available
    J2EE Engine:
    No information available
    Java VM:
    Java HotSpot(TM) Server VM, version: 1.4.2_09-b05, vendor: Sun Microsystems Inc.
    Operating system:
    Windows 2003, version: 5.2, architecture: x86
    Error stacktrace:
    com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type com.dms.kubota.orders.models.types.Kunnr could not be loaded: com.sap.dictionary.runtime.DdException:
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:205)
         at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.init(AttributeInfo.java:485)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:771)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:756)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:346)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:349)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:599)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:824)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Caused by: com.sap.dictionary.runtime.DdException:
         at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
         at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:587)
         at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:286)
         at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:81)
         at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
         at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:234)
         ... 31 more

    Hi Hans Lauwers,
    I think you have not configured and tested JCO Connection.
    Better you post this Question under WebApplication Server/WebDynpro..Then you 'll get lot of responses.
    Regards,
    Karthick

Maybe you are looking for