Error building/creating WD Callable Object

Hello guys,
Pardon for reposting - I did post on the WD Java thread - and I think this is the more appropriate area to ask this question since its GP Callable Objects related.
While creating a WD Callable Object: I
I added Used DC: caf/eu/gp/api/wd to the WD DC. And added IGPWebdynproCO on the Implemented Interface. Afterwards, after building the DC, I got the following errors:
This compilation unit indirectly references the missing type com.sap.caf.eu.gp.co.api.IGPTechnicalDescription (typically some required class file is referencing a type outside the classpath)
The project was not built since its classpath is incomplete. Cannot find the class file for com.sap.caf.eu.gp.co.api.IGPTechnicalDescription. Fix the classpath then try rebuilding this project.
I tried repair and rebuild - and restared NWDS (and even restarted my PC).
Issue not resolved.
What else should I do?
Thanks!
Regards,
Jan

I solve this including DC from caf/eu/gp/api (external public part) as show
http://help.sap.com/saphelp_nw70/helpdata/en/43/e085d6421a4d9de10000000a155369/content.htm
Later the method getDescription throws error because not return anything, while I return null
Regards,

Similar Messages

  • Error while creating a callable object - User Interface

    Hello,
    When i'm trying to create a callable object - User Interface in the guided procedure design time. i'm getting an error. An internal server error. This is happening while i'm trying to create a guided procedure with webdynpro's.
    Is there any body who allready had somthing like this.
    Greetings
    Kurt

    Hi Raja Akella,
    I allready had the roles and my portal version is upgraded until SP8 and all the possible patches.
    I get an internal server error when i want to create a callable object. specially when i want to create a webdynpro ( ABAP / JAVA).
    In the visual administrator i get the following  errors.
    <b>Error 1</b>
    Exception occured during processing of a Web Dynpro application: "com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.".
    [EXCEPTION]
    com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.
         at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:640)
         at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponentInternal(IWDApplicationInfo.java:286)
         at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponent(IWDApplicationInfo.java:270)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.addWdappsElement(COConfigWDApp.java:646)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readWebDynproApps(COConfigWDApp.java:631)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readApplications(COConfigWDApp.java:308)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalCOConfigWDApp.readApplications(InternalCOConfigWDApp.java:190)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.initCreate(VSelect.java:306)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.onPlugFromDispatch(VSelect.java:174)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalVSelect.wdInvokeEventHandler(InternalVSelect.java:168)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:826)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:330)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)
         at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:178)
         at com.sap.tc.webdynpro.repository.persistence.xml.XMLPersistence.doReadVMO(XMLPersistence.java:126)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.readVMO(RepositoryPersistence.java:356)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.doFindRepositoryObject(RepositoryPersistence.java:598)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.findRepositoryObject(RepositoryPersistence.java:170)
         at com.sap.tc.webdynpro.repository.model.Repository.findRepositoryObjectInternal(Repository.java:590)
         at com.sap.tc.webdynpro.repository.model.RepositoryObjectRelation$XMLGuidWrapper.getModelObject(RepositoryObjectRelation.java:462)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.getCurrentLayerObject(RepositoryPersistence.java:702)
         at com.sap.tc.webdynpro.repository.model.Repository.getCurrentLayerObject(Repository.java:1483)
         at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.doMergeInheritedTarget(NonSharedRelationToOne.java:85)
         at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.mergeInheritedTargets(NonSharedRelationToOne.java:49)
         at com.sap.tc.webdynpro.repository.model.RelationToOne.getTarget(RelationToOne.java:93)
         at com.sap.tc.webdynpro.repository.model.AbstractRepositoryModelClass.getRelatedModelObject(AbstractRepositoryModelClass.java:234)
         at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:636)
         ... 39 more
    Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)(:main:, row=1, col=491) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
         at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:148)
         at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:166)
         ... 52 more
    Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
         at com.sap.engine.lib.xml.parser.XMLParser.scanAttList(XMLParser.java:1566)
         at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1687)
         at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2792)
         at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:227)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:141)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:156)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:259)
         at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:278)
         at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:340)
         at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
         ... 53 more
    <b>error 2</b>
    Processing HTTP request to servlet [dispatcher] finished with error. The error is: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.
         at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:640)
         at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponentInternal(IWDApplicationInfo.java:286)
         at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponent(IWDApplicationInfo.java:270)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.addWdappsElement(COConfigWDApp.java:646)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readWebDynproApps(COConfigWDApp.java:631)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readApplications(COConfigWDApp.java:308)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalCOConfigWDApp.readApplications(InternalCOConfigWDApp.java:190)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.initCreate(VSelect.java:306)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.onPlugFromDispatch(VSelect.java:174)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalVSelect.wdInvokeEventHandler(InternalVSelect.java:168)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:826)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:330)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)
         at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:178)
         at com.sap.tc.webdynpro.repository.persistence.xml.XMLPersistence.doReadVMO(XMLPersistence.java:126)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.readVMO(RepositoryPersistence.java:356)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.doFindRepositoryObject(RepositoryPersistence.java:598)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.findRepositoryObject(RepositoryPersistence.java:170)
         at com.sap.tc.webdynpro.repository.model.Repository.findRepositoryObjectInternal(Repository.java:590)
         at com.sap.tc.webdynpro.repository.model.RepositoryObjectRelation$XMLGuidWrapper.getModelObject(RepositoryObjectRelation.java:462)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.getCurrentLayerObject(RepositoryPersistence.java:702)
         at com.sap.tc.webdynpro.repository.model.Repository.getCurrentLayerObject(Repository.java:1483)
         at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.doMergeInheritedTarget(NonSharedRelationToOne.java:85)
         at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.mergeInheritedTargets(NonSharedRelationToOne.java:49)
         at com.sap.tc.webdynpro.repository.model.RelationToOne.getTarget(RelationToOne.java:93)
         at com.sap.tc.webdynpro.repository.model.AbstractRepositoryModelClass.getRelatedModelObject(AbstractRepositoryModelClass.java:234)
         at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:636)
         ... 39 more
    Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)(:main:, row=1, col=491) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
         at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:148)
         at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:166)
         ... 52 more
    Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
         at com.sap.engine.lib.xml.parser.XMLParser.scanAttList(XMLParser.java:1566)
         at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1687)
         at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2792)
         at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:227)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:141)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:156)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:259)
         at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:278)
         at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:340)
         at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
         ... 53 more
    <b>error 3</b>
    Processing HTTP request to servlet [dispatcher] finished with error.
    The error is: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.
    Exception id: [00505691431B006F0000003E00000FE800041B45B87F7617]
    thanks in advance
    Kurt

  • Error testing Web Dynpro Callable Object (GP Interface)

    With reference to thread:
    Interactive form as  Callable object error on testing the object.
    FYI, I'm running NW04s, EP 7.0 SPS 13, JDK 1.4.2_14, Unix OS
    Hi All,
    I have created a Web Dynpro App with a Adobe Form as the frontend. I have included the caf/eu/gp/api as a DC and implemented the IGPWebDynproCO interface. Next I created a Web Dynpro Callable object in GP and ran a test and received the following error:
    Result: Technical Exception
    Details: Could not create web dynpro callable object component
    Output Parameters
    Callable object implementation did not return  output parameters
    Can anyone help me resolve this? Do I have to make a manual entry in the HOST file? If so, what is that entry? Are there alternatives?
    Thanks
    Kunal.

    Hi,
    For creating WD callable object you need to add following three DC in your WD DC project.
    In the Web Dynpro Explorer of the Web Dynpro Perspective, expand the node DC MetaData -> DC Definition, and select Used DCs.
    a.      To create a DC dependency, open the context menu and choose Add Used DC.
      b.      Select Local Development  -> SAP-EU  -> caf/eu/gp/api/wd  -> DC MetaData  -> Public Parts  -> GPWebDynproCO. For Dependency Type, select Build Time, Design Time, and Run Time. Choose weak from the dropdown list.
      c.      Repeat the previous step to define a dependency to DCs SAP-EU-> caf/eu/gp/api (public part external) and SAP-JEE -> com.sap.security.api.sda (public part default).
    You need to do one more thing like bellow.
    Select your Web Dynpro project and open its context menu. Choose Properties.
    1. Choose Web Dynpro References -> Library References.
    2.  Add a reference for library caf/eu/gp/api.
    I think this will help you.
    Thanks
    Chandan

  • Problem in creating a callable object of type Business Logic

    Hi SDN,
    I am trying to create a callable object of type Business Logic in CE.
    When I give all information and click Next, I get this error message.
    Error while loading configuration dialog: Failed to create delegate for component com.sap.caf.eu.gp.ui.co.CExpConfig. (Hint: Is the corresponding DC deployed correctly? Does the DC contain the component?)
    Can anybody help me out with this problem.
    Regards,
    Sumangala

    Hi.
    I'm having the same problem as Senthil in NW2004s SP15 with my application service and methods not showing up in the Callable Object wizard for Composite Application Services after I choose the Endpoint.  The only application name that shows up in the wizard is caf.tc, and the only service names that show up for it are LDDataAccessor, Metadata, and PropPermissionService.
    My IDE is on one machine and the application server I deploy to is located on a different machine.  My endpoint to the remote application server looks to be correctly configured.  The Composite Application Service seems to be deployed properly as I'm able to see it and test that it works in the Web Services Navigator <http://remotehost:50000/wsnavigator/>
    My deployed application service is a remote enabled service and is also web services enabled as well.
    I'm not sure if this is relevant, but I noticed that the generated Java code does not create any remote EJB interfaces (only home and local interfaces were generated).
    Something else I noticed is that when I proceed to the External Service Configuration -> Business Entities screen <http://remotehost:50000/webdynpro/dispatcher/sap.com/cafUIconfiguration>, I only see three business entities displayed, and the following error message is displayed: "Corrupt metadata has been detected. This may prevent some objects from being displayed. Check the server log for more details."  I was unable to find anything in the instance log files.  Is the error message indicative of the problem?
    I am developing locally without a NetWeaver Development Infrastructure (NWDI) in place.
    I'm wondering if the credentials specified in the endpoint require any special roles or privileges.
    Senthil, do any of these additional descriptions apply to you as well?
    Edited by: Ric Leeds on Jun 20, 2008 4:37 PM

  • "cannot find this class" erro while creating Background Callable Object.

    Hi All,
    I am facing "cannot find this class" while creating Background Callable Object.
    I followed the following document for Creating Background Callable Object.
    [Creating Callable Objects for Background Execution|http://help.sap.com/saphelp_nwce10/helpdata/en/53/cde385301f4aa3b8e77a92cd46bff3/frameset.htm]
    After giving the fully qualified java class name in the Implementation Class Name when i press next i am getting the error.
    Please suggets me in solving this issue.
    Regards,
    S.V.Satish Kumar
    Edited by: Sathish Kumar SV on Apr 4, 2009 10:34 AM

    Hi, kavita.
    First, make sure you choosed the correct container when you created the background CO.
    Second, make sure your package name was "com.examples.bckgco" and class name was "UserDetailsCallableObject". The exception  which you got just means you entered incorrect name.
    It doesn`t relate to your program.
    Best Regards.
    Louis Huang.

  • I am not able to create a callable object of my web Dynpro application

    Hi,  
      I have my Portal server installed with NW2004S and with other components as follows.    
    ·WAS 7.0 SP9  
    ·EP7.0 SP9  
    ·CAF 7.0 SP9  
    ·VC 7.0 SP9  
    But now my webdynpro application is not reflecting in web Dynpro Component(GP Interface) during the design time, when I am trying to create a callable object.    
    So please can you suggest what is the problem and how I will get it corrected.  
    Regards,  
    Paresh.

    Hi Aliaksei,
    I had created a complete CAF application which was working fine. Then the server got crashed and i lost everything.So then i again installed the server and upgraded it to SP7.But than i was not able to see my web dynpro application while creating callable object. So i created another instance in the server at the base level(SP4) and i was able to create callable object.
    There is no problem in the webdynpro application.I have added runtime library referece to my project : sap.com/cafeugp~api and also implemented the Interface IGPWebDynproCO in my component.
    So i dont know where i am going wrong while i am upgrading the server.
    Regards,
    Paresh.

  • Error while creating Vacancy requisition object (NB) after upgrading EHP4

    Hi All,
    We had alreay E-Rec system with EHP2 and using last 1 year. Now based on Client requirement, we have upgrdaed to EHP4. After completing EHP4 upgradation, we are getting error while creating vacancy requisition object after all level of approval.
    Can any body help how to resolve this issue?
    Thanks in advance.
    Regards,
    Sreelatha

    Hi
    Hope SAP Note 1241014 will be useful to you.
    Best Regards
    Reddy

  • Unable to create a callable object

    Hi All,
    Try making a Web Dynpro application for CAF GP using this article:
    [https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/composition/caf/how%20to%20integrate%20two%20web%20dynpro%20applications%20using%20composite%20application%20framework%20guided%20procedures.pdf]
    I have been able to deploy the application successfully. But when i run the Process, the first Callable Object (CO1) is fine and the second Callable Object (CO2) is showing error:
    /System/UserInterface#Plain###Unable to create web dynpro callable object implementation.
    com.sap.tc.webdynpro.progmodel.context.ContextException: NodeElement(CallableObject2Interface.0): unknown attribute firstName
         at com.sap.tc.webdynpro.progmodel.context.NodeElement.wdGetAttributeInfo(NodeElement.java:380)
         at com.sap.tc.webdynpro.progmodel.context.NodeElement.setAttributeValue(NodeElement.java:883)
         at com.tcs.bhel.co2.CallableObject2Interface.execute(CallableObject2Interface.java:166)
         at com.tcs.bhel.co2.wdp.InternalCallableObject2Interface.execute(InternalCallableObject2Interface.java:132)
         at com.tcs.bhel.co2.wdp.InternalCallableObject2Interface$External.execute(InternalCallableObject2Interface.java:182)
         at com.sap.caf.eu.gp.ui.co.exec.wd.COExecWD.execute(COExecWD.java:303)
         at com.sap.caf.eu.gp.ui.co.exec.wd.wdp.InternalCOExecWD.execute(InternalCOExecWD.java:171)
         at com.sap.caf.eu.gp.ui.co.exec.wd.COExecWDInterface.execute(COExecWDInterface.java:122)
         at com.sap.caf.eu.gp.ui.co.exec.wd.wdp.InternalCOExecWDInterface.execute(InternalCOExecWDInterface.java:134)
         at com.sap.caf.eu.gp.ui.co.exec.wd.wdp.InternalCOExecWDInterface$External.execute(InternalCOExecWDInterface.java:249)
    Thanks
    Ash

    hi Ash,
    Make sure that you have done this step for callable object2
    Select entry Web Dynpro References
    - Select tab page Library References
    - Choose Add
    - Enter the reference caf/eu/gp/api
    Thanks and regards,
    Arun

  • Error while creating a system object for R3 in portal

    Hi,
    I am getting error while trying to create a system object in portal.
    Following are the details I used :
    Under WAS...
    Web AS Host Name :<XXXX>:8001
    Web AS path: /sap/bc/bsp/sap/
    Web AS protocol : http
    Under User management:
    Authentication Ticket Type : SAP Logon Ticket
    Logon Method :SAPLOGONTICKET
    User Mapping Type : admin,user
    Under Connector:
    SAP Client : <Client NO>
    SAP System ID : <System ID>
    SAP System No : <System No>
    System Type : SAP_R3
    While trying with connection test... I am getting like this:
    SAP Web AS Connection
      Test Details:
    The test consists of the following steps:
    1. Checks the validity of system ID in the system object.
    2. Checks if the system can be retrieved from the PCD.
    3. Check whether a SAP system is defined in the system object
    4. Validate the following parameters: WAS protocol; WAS host name
    5. Checks if the host name of the server can be resolved.
    6. Pings the server to see if it is alive.
    7. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
    8. Checks HTTP/S connectivity to the defined back-end application
      Results
    1. The system ID is valid
    2. The system was retrieved.
    3. The system object represents an SAP system
    4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (<FQDN server name>:8001)
    5. The host name <FQDN Server Name> was resolved successfully.
    6. The server sapdwh01 could not be pinged successfully.
    Test Connection with Connector
      Test Details:
    The test consists of the following steps:
    1. Retrieve the default alias of the system
    2. Check the connection to the backend application using the connector defined in this system object
      Results
    Retrieval of default alias successful
    Connection failed. Make sure that Single Sign-On is configured correctly
    It seems that the portal is not able to ping to R3 system. I tried to ping to R3 server from portal server by command prompt. I am able to ping. Also under SICF, I can see ping service as in activated state.
    Kindly help.
    Regards,
    Niraj
    Edited by: Niraj Kumar on Dec 11, 2008 10:41 AM

    I created a SAP Transactional iView for transaction SE80.
    Also, I tried from under System Administration -> Support -> SAP Transaction. It is not working.
    Got portal Runtime error :
    Portal Runtime Error
    An exception occurred while processing your request
    Exception id: 12:57_11/12/08_0003_2795650
    See the details for the exception ID in the log file.
    Regards,
    Niraj

  • Error while creating new entity object.

    Hi all
    I'm using Jdev 11.1.1.3. I want to create an entity object and Jdev issues an information error saying "Either this is not a valid name or an object with that name already exists."
    I found that if the package I'm targeting for the new entity is called "com.test.model.whatever" I cannot create a EO called "Whatever".
    I can't find any reference in the fusion developer guide that constraints the entity names to be allowed.
    Is there a way to circumvent this issue or is this the way it should be?

    Sudipto and Suresh, thank you very much for your replies.
    I know that changing the package or entity name would work, but was expecting some other kind of workaround, something like giving a full qualified name on some xml or something to avoid the name clash or whatever the problem is.
    I do not like packing all the entities together as it goes against my best practice of packing things that change together on the same package. Also I don't like suffix or prefix class names as it goes against my best practice of short descriptive names.
    So well, I will have to tinker the names some more and meet you guys half way.
    I will now mark this thread as answered, thanks again.

  • Error while creating the proxy object to connect to a third party tool.

    Hi,
    I tried creating a proxy object with the wsdl file. I even created a HTTP connection to the third party tool. but when I try to execute the whole proxy object, I am getting the below error. Can anyone help me on this?
    "Proxy-Generierung: Fehler aufgetreten"
    "Incorrect value: Entity "<<document>>"(92 /3788 ). end tag 'ul' does not match begin tag 'p'"
    Thanks & Regards,
    Veerabhadra Rao A.

    do a check on the wsdl file and how you are passing values in the proxy. The tags for XML are not correct. Open the WSDL in IE and see there must be an error. Or probably when passing the actual values to the XML generated each element is not closed properly. Error says tags dont match.
    Edited by: Kshamatha Eda on Mar 5, 2010 10:54 AM

  • GP Background callable object. Error while making a Callable object

    Hi,
    I have implemented a Background callable object and deployed it to the server.
    When I try to make a Callable object of this from the Design Time tab in GP, i get the following error msg.
    *Class does not correctly implement the required interface*
    The detailed error msg is as follows
    Full Message Text
    Unable to load the required classes. Check all the references to other modules, especially the GP API
    com.sap.caf.eu.gp.base.exception.EngineException: Unable to load the required classes. Check all the references to other modules, especially the GP API
    at com.sap.caf.eu.gp.model.svc.impl.EngineClassloaderImpl.isClassAvailable(EngineClassloaderImpl.java:101)
    at com.sap.caf.eu.gp.ui.co.config.bkgd.COCfgSelect.OnCanLeaveScreen(COCfgSelect.java:293)
    Pls help.
    Tx in advance

    The problem was resolved after retrying many times. Code was checked again and redeployed. Server restarted as well. GP objects deleted and steps repeated. It worked in the end.

  • Error when creating a Proxy Object from WSDL

    Hi,
    when creating a proxy object in abap based on the [WSDL|http://download.mapandguide.com/EN/dev/xserver/XLocate-1.6.0.3.wsdl] i get the error 'Incorrect value: Unknown Type Referencens0:ArrayOfString'.
    1- Is there a conflict with the type 'String' that's also a type in ABAP
    <complexType name="ArrayOfString">
      <sequence>
      <element name="String" type="xsd:string" minOccurs="0" maxOccurs="unbounded" nillable="true" />
      </sequence>
      </complexType>
    2- Is it a name space problem?
    xmlns:ns0="http://types.xlocate.xserver.ptvag.com"
    type="ns0:ArrayOfString"
    3- Something else?
    Please Help!
    Thank
    Fouad

    Hi Isaias,
    we are working with this versions:
    SAP_BASIS     700     0015     SAPKB70015     SAP Basiskomponente
    SAP_AP                     700     0013     SAPKNA7013     SAP Application Platform
    We are not working with developer studio, only with the regular tools of the abap development workbench Transaction SE80.
    Thanks,
    Fouad

  • Error when creating a ReportDocument object in ver 11.5.3300.0

    When I try to create a new ReportDocument from .NET the application exists with no other information. There is an event log entry similar to this one:
    Faulting application CrystalTest1.vshost.exe, version 9.0.21022.8, time stamp 0x47316898, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x04525da0, process id 0x10fc, application start time 0x01c9c2d6d624913d.
    Investigating more I tracked down that the error happens when I try to create various COM objects from Crystal Reports (for example by running the following vbscript: Set o = CreateObject("CrystalClientDoc.ReportClientDocument")). The error is always an Access Violation in cachemanager.dll on address 3f8691b5:
    3F869172 push ebx
    3F869173 push esi
    3F869174 push edi
    3F869175 push 3F873464h
    3F86917A call dword ptr ds:3F86C04Ch
    3F869180 mov ebx,dword ptr esp+10h
    3F869184 mov esi,eax
    3F869186 mov eax,dword ptr esi
    3F869188 mov ecx,esi
    3F86918A mov dword ptr esi+4,ebx
    3F86918D call dword ptr eax+8
    3F869190 push esi
    3F869191 lea edi,esi+14h
    3F869194 push eax
    3F869195 mov ecx,edi
    3F869197 call 3F8690EE
    3F86919C mov edi,dword ptr edi
    3F86919E push edi
    3F86919F push 0FFFFFFFCh
    3F8691A1 push ebx
    3F8691A2 call dword ptr ds:3F86C254h
    3F8691A8 push dword ptr esp+1Ch
    3F8691AC push dword ptr esp+1Ch
    3F8691B0 push dword ptr esp+1Ch
    3F8691B4 push ebx
    3F8691B5 call edi
    3F8691B7 pop edi
    3F8691B8 pop esi
    3F8691B9 pop ebx
    3F8691BA ret 10h
    The full stack trace is:
    00455B60()
    cachemanager.dll!3f8691b7()
    http://Frames below may be incorrect and/or missing, no symbols loaded for cachemanager.dll
    user32.dll!7735f8d2()
    user32.dll!7735f794()
    user32.dll!7735f73d()
    user32.dll!77360817()
    user32.dll!773539f7()
    ntdll.dll!771f99ce()
    user32.dll!77353cf7()
    user32.dll!77353b94()
    user32.dll!77353cc3()
    atl71.dll!7c12c51d()
    atl71.dll!7c12c633()
    atl71.dll!7c121653()
    user32.dll!77353d9a()
    cachemanager.dll!3f86922f()
    cachemanager.dll!3f86949e()
    cachemanager.dll!3f869600()
    cachemanager.dll!3f868aec()
    msvcr71.dll!7c349565()
    kernel32.dll!760e4911()
    ntdll.dll!771de4b6()
    ntdll.dll!771de489()
    The address called at 3f8691b5 seem to always contain the following data in my case:
    00455B51 00 00 add byte ptr eax,al
    00455B53 00 00 add byte ptr eax,al
    00455B55 00 00 add byte ptr eax,al
    00455B57 00 DA add dl,bl
    00455B59 44 inc esp
    00455B5A 44 inc esp
    00455B5B 3A 00 cmp al,byte ptr eax
    00455B5D 00 00 add byte ptr eax,al
    00455B5F 8B db 8bh
    00455B60 C7 44 24 04 70 1F F4 01 mov dword ptr esp+4,1F41F70h
    00455B68 E9 4E 39 41 3F jmp 3F8694BB
    00455B6D 00 00 add byte ptr eax,al
    00455B6F 00 DF add bh,bl
    00455B71 44 inc esp
    00455B72 44 inc esp
    00455B73 3A 00 cmp al,byte ptr eax
    00455B75 00 00 add byte ptr eax,al
    00455B77 88 E0 mov al,ah
    00455B79 66 45 inc bp
    00455B7B 00 90 5B 45 00 B8 add byte ptr eax-47FFBAA5h,dl
    The data and the address seem to be always the same in my case.
    I am running 32-bit Vista Ultimate on a dual core Intel Centrino CPU. I have a Crystal Reports Deployment suite installed. The cachemanager.dll is 106,496 bytes and the file version is 11.5.8.998
    Pelase help!

    Hi Ludek,
    Thanks for looking into this.
    > What version of .NET are you using?
    I have all version of .NET installed but please note that .NET is not required to reproduce the problem. Please read again my initial post. The error can be reproduced with this single line of VB Script and there is no .NET involved:
    Set o = CreateObject("CrystalClientDoc.ReportClientDocument")
    The same can be reproduced by creating a new ReportDocument object from .NET in any type of .NET application.
    > What CR Service Pack are you on?
    I haven't installed any additional service packs. Please see the versions of the files I have on my system to figure out the service pack:
    Crystaldecisions.Crystalreports.Engine.dll file version = 11.5.9708.998
    cachemanager.dll file version = 11.5.8.998
    clientdoc.dll file version = 11.5.8.998
    The other computers where all works good have the same versions installed.
    > What .NET Service Pack are you on?
    All latest service packs and updates from Microsoft are installed
    > What is the version of the CR assembly crystaldecisions.Crystalreports.engine.dll referenced in your application?
    The assembly version is 11.5.3700.0, file version: 11.5.9708.998, file size: 393,216 bytes
    > Is this a web or a win app?
    The error happens in btoh web and windows forms applications as well as by simply trying to create the Crystal COM object directly from VB Script without involving any .NET. So the same error will occur if CR are used from VB6 for example.
    > What OS are you on?
    Again as per my original post I am using a 32-bit Vista Ultimate on a dual core Intel Centrino CPU
    > What happens if you try to run an existing application?
    I get a crash in unmanaged code in cachemanager.dll at 0x3f8691b7. All the details are in my original post (scroll up). When this happens in a .NET application, the process is terminated and Vista shows a message that the program has stoped working. There is an error in the event log (see my original post)
    > There are different ways of instantiating a report. The sample app vbnet_win_simplepreview has all of these. Running the app with the different options may give us a clue... Was Crystal Reports installed before .NET or after?
    Crystal Reports Basic for Visual Studio 2008 was installed with VS 2008. After that I installed Crystal Reports Server Deployment
    > Have you tried to reinstall Crystal Reports?
    Yes I did reinstall both Crystal Reports Basic for Visual Studio 2008 and Crystal Reports Server Deployment in reverse order (i.e. the server deployment first and then the basics)

  • Error Dump Creating a Transformation Object

    Hi all:
    I have NW2004s  in my box.
    I have the following error when trying to create a Tranformation Object (function "Create Transformation"  on a Data Source).:
    "Make sure that the OCXs ICDataFlow.ocx and wdbdadpt.ocx are installed on your computer....".
    Installation went ok, with no errors, so I don't know why the system is asking for additional files.
    If so, what should I do?...What should I check?
    Thanks in advance.

    You don't have access to :
    http://service.sap.com/notes
    or SAP Notes through CSS ?
    Then, it will be difficult as some notes have corrections that need to be implemented and you do need the access.
    Best Regards,
    Snehal

Maybe you are looking for

  • Installation issue on opensuse 11

    Hey All,<br /><br />Im a Windows guy still struggling with Linux set-upsso take it easy on me! :)  and Im having a hard time getting blaze installed and running.<br /><br />This is what Ive done so far.  I've successfully set-up the latest copy of op

  • To write data as an IDOC for EDI 858 (bill of lading) through reports.

    Hey everybody, I need serious help about this. I am back to my question that I asked before. I don't understand still how to write out the data as an IDOC when we are not doing EDI through a VAN but dumping the file onto both application and presenta

  • BPM or Java/Db for this requirement

    Hi, Here's the requirement: A user creates a document (using webcenter portal UI) and he has a provision to add 'n' number of reviewers both sequential and parallel reviews are needed and also a combination is needed, which the user will add through

  • Installation of Introscope Agent

    Hi! I would like to install Introscope Agent. Neither the manual installation nor the installation via Setup Introscope Agent was succesfull. case a) automatic installation via SMD Wizard The erros of installation with SMD Wizard (Setup Introscope Ag

  • Disabling printer selection screen

    Hi All, I have developed a smartform which will be printed throug a normal report. When i am executing the report, i am getting the pop up screen for selecting the output device, etc...i want to disable this screen, so that after executing the report