Skip to Content
author's profile photo Former Member
Former Member

Unable to Execute the Application

Hi Guys,

I have tried to create the flight example program. But i am continously getting below mentioned error.

1. My JCO Destination for Application server and Message server are working fine in Content Admin.

2. Number of times i have restarted my server.

Can anyone let me know what could have been the reason.

Thanks .,

Kumar

com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type extern:com.sap.tut.wd.flightlist.model.types.FlightModel:com.sap.tut.wd.flightlist.model.types.Bapisfldat could not be loaded: com.sap.dictionary.runtime.DdException: The logical dictionary com.sap.tut.wd.flightlist.model.types.FlightModel does not exist

at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:294)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:659)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:667)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:667)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:667)

at com.sap.tc.webdynpro.progmodel.context.Node.init(Node.java:263)

at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:37)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:181)

at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:392)

at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:333)

at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:361)

at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:137)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:652)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:667)

at com.sap.tc.webdynpro.progmodel.context.Node.init(Node.java:263)

at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:37)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:181)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:529)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:387)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:544)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:411)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:129)

at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:41)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:182)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:136)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:363)

at com.sap.tc.webdynpro.clientserver.task.Task.createApplication(Task.java:181)

at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:494)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:49)

at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:239)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:130)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:92)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:35)

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:373)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:250)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:319)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:297)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:696)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:221)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:146)

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:140)

Caused by: com.sap.dictionary.runtime.DdException: The logical dictionary com.sap.tut.wd.flightlist.model.types.FlightModel does not exist

at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:65)

at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:141)

at com.sap.dictionary.runtime.DdBroker.getStructure(DdBroker.java:172)

at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:292)

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Posted on Dec 06, 2004 at 01:04 PM

    Hi Kumar,

    What is your R/3 version. Actually these BAPI's are present in version 6.20 and higher. That is what i found when i tested these examples at my end.

    You might just want to check whether these BAPI's are present in your system or not.

    Regards

    Sidharth

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 06, 2004 at 02:53 PM

    Hi Sidharth

    Bapi is available at the R3 system. Is that in any other place where in which i could have gone wrong ??

    Thanks,

    Kumar

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Please note that the BAPI is available in the IDES system only.

      Anyway if you have verified the existence of this BAPI, please try to re-execute the WD Application. Do not stop the application loading in your browser. If it is still throwing the error try to execute the application, 10-15 minutes after the application got deployed and couple of times you got the same error.The reason for this error is the time delay the connection takes to read the metadata from the backend system(Make sure that the MetaData JCO connection is working perfectly and Bapisfldat in WD has the same structure as in the Backend system).

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.