Failed to create deployable object 'local/Calendar' since it not a WD objec

Hi
I created a calendar application in Web dynpro,There iam getting this error .will any one please help me how to avoid this.
com.sap.tc.webdynpro.services.sal.core.DispatcherException: The requested deployable object 'local/Calendar' and application 'CalendarApp' are not deployed on the server. Please check the used URL for typos.
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.getApplicationDeployableObjectPart(RequestManager.java:383)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.initTask(RequestManager.java:317)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:143)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
     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: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.services.exceptions.WDRuntimeException: Failed to create deployable object 'local/Calendar' since it is not a Web Dynpro object.
     at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObject.<init>(AbstractDeployableObject.java:106)
     at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.<init>(DeployableObject.java:56)
     at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObject(DeployableObjectFactory.java:95)
     at com.sap.tc.webdynpro.services.sal.deployment.core.DeployableObjectInternal.getDeployableObjectInternal(DeployableObjectInternal.java:34)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.getApplicationDeployableObjectPart(RequestManager.java:380)
     ... 20 more

Hi Sushma,
                 lot of new features have been added in CE EHP1 version .for more information refer this [link|http://help.sap.com/saphelp_nwce711/helpdata/en/26/b7fa511a964597a5d8c1b778508936/content.htm] and search in SDN for new features in EHP1 version.
in CE EHP1, local web dynpro projects cannot be used as it is deprecated in this version.
i believe this calendar is a local standalone project created in CE 7.1 version and conert this local project to development component.
right click on ur local project --> Development component -->Convert Project to Development Component.
After this, go ur NWDI --> select ur component --> right click --> Create project (& Sync ysed Dcs) ..
finally deploy and run ur component .
Hope this helps.
Thanks and Regards

Similar Messages

  • Failed to create deployable object 'virsa/ccappcomp' since it is not a Web

    Hi All,
    As per 999858  I download VIRCC09_0-20001854.SAR and depolyed ( this is  fresh installation of Virsa Compliance Calibrator) it directly since in java stack you do not have to go incremental way  as per Virsa Compliance Calibratoru2122 Version 5.2 for SAP WAS 700  installation guide.
    Here are the components which I have deployed using SDM
    1. sap.comgrcccxsysdb.sda
    2. virsalib.sda
    3. sap.com~ccume.sda
    4. sap.comgrcccxsysbe
    5. sap.comgrcccxsysbehr
    6. sap.comgrcccappcomp
    7. sap.comgrcccxsysws 
    8. sap.comgrcccxsysbgear
    But when I take http://hostname:50200/webdynpro/dispatcher/virsa/ccappcomp/
    I am getting following error.
    Root Cause
    The initial exception that caused the request to fail, was:
       com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create deployable object 'virsa/ccappcomp' since it is not a Web Dynpro object.
        at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObject.<init>(AbstractDeployableObject.java:106)
        at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.<init>(DeployableObject.java:56)
        at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObject(DeployableObjectFactory.java:95)
        at com.sap.tc.webdynpro.services.sal.deployment.core.DeployableObjectInternal.getDeployableObjectInternal(DeployableObjectInternal.java:34)
        at com.sap.tc.webdynpro.clientserver.session.RequestManager.getApplicationDeployableObjectPart(RequestManager.java:407)
        ... 20 more
    But I did deployed sap.comgrcccappcomp and still getting error tthat it is not deployed
    com.sap.tc.webdynpro.services.sal.core.DispatcherException: The requested deployable object 'virsa/ccappcomp' and application '' are not deployed on the server. Please check the used URL for typos.
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.getApplicationDeployableObjectPart(RequestManager.java:410)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.initTask(RequestManager.java:344)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:145)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
         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:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
         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.services.exceptions.WDRuntimeException: Failed to create deployable object 'virsa/ccappcomp' since it is not a Web Dynpro object.
         at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObject.<init>(AbstractDeployableObject.java:106)
         at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.<init>(DeployableObject.java:56)
         at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObject(DeployableObjectFactory.java:95)
         at com.sap.tc.webdynpro.services.sal.deployment.core.DeployableObjectInternal.getDeployableObjectInternal(DeployableObjectInternal.java:34)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.getApplicationDeployableObjectPart(RequestManager.java:407)
         ... 20 more
    But I am able to take the debug  window
    http://hostname:50200/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?debug=1
    Do you have any tips?

    Yes, try the correct URL for calling CC
    http://hostname:50200/webdynpro/dispatcher/sap.com/grc~ccappcomp/ComplianceCalibrator
    This is the URL since CC 5.2 SP05, before it was
    http://hostname:50200/webdynpro/dispatcher/virsa/ccappcomp/ComplianceCalibrator
    The first one should apply to you.
    Kind regards,
    Daniela

  • Failed to create deployable object '********' since it is not a Web Dynpro object - Migration from 7.0 to 7.4

    I have installed NWDS 7.30 EHP1 SP 14 PAT000   with JVM 6 SAP AG
    to   migrate wedynpro development components from 7.0 to
    NW7.4 WAS SAP AG 1.6.0_85 on Windows Server 2008 R2 6.1  SP09 PAT000
    In track imported below SCAs of version  7.31 SP14 .
    Could able to migrate and build in NWDS, getting deployment errors.
    Followed   
    http://scn.sap.com/docs/DOC-55584 
    and   
    http://scn.sap.com/community/nwdi/blog/2014/03/26/nwdi-vs-nwdi-content 
    COMP_BUILDT
    ECM-CORE
    ENGFACADE
    ENGINEAPI
    ESCONF_BUILDT
    FRAMEWORK
    MOIN_BUILDT
    SAP_BUILDT
    WD-RUNTIME
    Deployment Errors:-
    com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
    Reason: ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] failed
        at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:862)
        at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
        at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:105)
        at com.sap.ide.tools.services.dc.EngineDcDeployService.deployFiles(EngineDcDeployService.java:257)
        at com.sap.ide.tools.services.dc.EngineDcDeployService.deploy(EngineDcDeployService.java:135)
        at com.sap.ide.dii05.ui.internal.actions.dc.DcDeployAction$5$1.run(DcDeployAction.java:282)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] failed
        at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:246)
        at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:67)
        at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:282)
        at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
        at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:100)
        at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
        at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
        at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
        at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Caused by: com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] Operation [update] of [sdu id: [XXXXXXX.com_home~chgemail]
    sdu file path: [E:\usr\sap\SN3\J00\j2ee\cluster\server0\temp\tc~bl~deploy_controller\archives\111\XXXXXXX.com~home~chgemail.ear]
    version status: [HIGHER]
    deployment status: [Admitted]
    description: []
    ] failed
        at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:100)
        at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:141)
        at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
        at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:213)
        ... 8 more
    Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: ASJ.dpl_ds.006193 Operation [update] of [E:\usr\sap\SN3\J00\j2ee\cluster\server0\temp\tc~bl~deploy_controller\archives\111\XXXXXXX.com~home~chgemail.ear] failed
        at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:3370)
        at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:489)
        at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:74)
        ... 11 more
    Caused by: com.sap.engine.services.servlets_jsp.webcontainer_api.exceptions.WebContainerExtensionDeploymentException: Error during deployment of application {0}
        at com.sap.engine.services.webdynpro.WebDynproDeploymentHook.onDeploy(WebDynproDeploymentHook.java:52)
        at com.sap.engine.services.webdynpro.webcontainer.extension.ExtensionHandler.onDeployInternal(ExtensionHandler.java:169)
        at com.sap.engine.services.webdynpro.webcontainer.extension.ExtensionHandler.onDeploy(ExtensionHandler.java:129)
        at com.sap.engine.services.servlets_jsp.server.deploy.impl.WebContainerProvider.deploy(WebContainerProvider.java:334)
        at com.sap.engine.services.servlets_jsp.server.deploy.DeployAction.deploy(DeployAction.java:360)
        at com.sap.engine.services.servlets_jsp.server.deploy.UpdateAction.makeUpdate(UpdateAction.java:327)
        at com.sap.engine.services.servlets_jsp.server.deploy.WebContainer.makeUpdate(WebContainer.java:446)
        at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.makeUpdate(ContainerWrapper.java:409)
        at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:478)
        at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:183)
        at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:234)
        at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:421)
        at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:473)
        at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:1836)
        at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:582)
        at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:487)
        ... 12 more
    Caused by: com.sap.tc.webdynpro.services.sal.deployment.core.DeploymentException: Failed to deploy application 'XXXXXXX.com/home~chgemail'.
        at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.notifyOnDeploy(DeployableObjectFactory.java:324)
        at com.sap.tc.webdynpro.services.sal.deployment.core.DeployableObjectInternal.notifyOnDeploy(DeployableObjectInternal.java:122)
        at com.sap.engine.services.webdynpro.WebDynproDeploymentHook.onDeploy(WebDynproDeploymentHook.java:49)
        ... 27 more
    Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create deployable object 'XXXXXXX.com/home~chgemail' since it is not a Web Dynpro object.
        at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObject(DeployableObjectFactory.java:79)
        at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObjectFactory$1.getDeployableObject(AbstractDeployableObjectFactory.java:87)
        at com.sap.tc.webdynpro.services.sal.deployment.api.WDDeployableObject.getDeployableObject(WDDeployableObject.java:43)
        at com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook.calculateVMOsOfDeployableObject(RepositoryContainerHook.java:264)
        at com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook.onDeploy(RepositoryContainerHook.java:181)
        at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.notifyOnDeploy(DeployableObjectFactory.java:297)
        ... 29 more
    Caused by: com.sap.tc.webdynpro.spi.WebDynproRuntimeException: No Web Dynpro application (deployable object) with name XXXXXXX.com/home~chgemail exists.
        at com.sap.engine.services.webdynpro.WebDynproRuntimeServiceImpl.getDeployableObject(WebDynproRuntimeServiceImpl.java:228)
        at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObject(DeployableObjectFactory.java:77)
        ... 34 more
    Deployment Items status: [
    ----- Sorted Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
    ----- Deployment Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            Description:'1. Failed to create deployable object 'XXXXXXX.com/home~chgemail' since it is not a Web Dynpro object.
             -> No Web Dynpro application (deployable object) with name XXXXXXX.com/home~chgemail exists.'.
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
            Time statistics( ms ):
                1.Check version:XXXXXXX.com_home~chgemail : 4
                2.validate : -1
                    2.1.Resolve dependencies : 3
                    2.2.deployment : 7055
                        2.2.1.Notify:Event triggered : 203
                        2.2.2.Bulk deployment : 6839
                            2.2.2.1.Stop : 73
                            2.2.2.2.Perform delivery : 6765
                                2.2.2.2.1.Application Deployer : 6615
                        2.2.3.Notify:Event performed : 9
                    2.3.Post process : 10
                        2.3.1.Starting : 9
    ]      [Error: com.sap.engine.services.tc~bl~deploy~api  Thread[Worker-444,5,main]]
    Deployment Items status: [
    ----- Sorted Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
    ----- Deployment Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            Description:'1. Failed to create deployable object 'XXXXXXX.com/home~chgemail' since it is not a Web Dynpro object.
             -> No Web Dynpro application (deployable object) with name XXXXXXX.com/home~chgemail exists.'.
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
            Time statistics( ms ):
                1.Check version:XXXXXXX.com_home~chgemail : 4
                2.validate : -1
                    2.1.Resolve dependencies : 3
                    2.2.deployment : 7055
                        2.2.1.Notify:Event triggered : 203
                        2.2.2.Bulk deployment : 6839
                            2.2.2.1.Stop : 73
                            2.2.2.2.Perform delivery : 6765
                                2.2.2.2.1.Application Deployer : 6615
                        2.2.3.Notify:Event performed : 9
                    2.3.Post process : 10
                        2.3.1.Starting : 9
    ]      [Error: com.sap.engine.services.tc~bl~deploy~api  Thread[Worker-444,5,main]]
    [#6]: Deployment Items status: [
    ----- Sorted Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
    ----- Deployment Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            Description:'1. Failed to create deployable object 'XXXXXXX.com/home~chgemail' since it is not a Web Dynpro object.
             -> No Web Dynpro application (deployable object) with name XXXXXXX.com/home~chgemail exists.'.
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
            Time statistics( ms ):
                1.Check version:XXXXXXX.com_home~chgemail : 4
                2.validate : -1
                    2.1.Resolve dependencies : 3
                    2.2.deployment : 7055
                        2.2.1.Notify:Event triggered : 203
                        2.2.2.Bulk deployment : 6839
                            2.2.2.1.Stop : 73
                            2.2.2.2.Perform delivery : 6765
                                2.2.2.2.1.Application Deployer : 6615
                        2.2.3.Notify:Event performed : 9
                    2.3.Post process : 10
                        2.3.1.Starting : 9
    ]      [Error: com.sap.ide.eclipse.deployer.dc.DVLog  Thread[Worker-444,5,main]]
    [#6]: Deployment Items status: [
    ----- Sorted Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
    ----- Deployment Items -----
        1. Client path 'C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear'
            Deploy status is 'Aborted'
            Description:'1. Failed to create deployable object 'XXXXXXX.com/home~chgemail' since it is not a Web Dynpro object.
             -> No Web Dynpro application (deployable object) with name XXXXXXX.com/home~chgemail exists.'.
            SDA : name 'home~chgemail', vendor 'XXXXXXX.com', location 'SN3_MDTRJS_D', version '20150312060513', software type ('J2EE', sub type ''), csn component '', dependencies :[( name 'tc~aii~base~offline~facade', vendor 'sap.com') , ( name 'tc~ddic~runtime~facade', vendor 'sap.com') , ( name 'tc~bl~logging~api', vendor 'sap.com') , ( name 'tc~bl~exception~lib', vendor 'sap.com') , ( name 'tc~wd~api', vendor 'sap.com') , ( name 'tc~cmi', vendor 'sap.com') , ( name 'tc~bl~jco~api', vendor 'sap.com') ]
            Time statistics( ms ):
                1.Check version:XXXXXXX.com_home~chgemail : 4
                2.validate : -1
                    2.1.Resolve dependencies : 3
                    2.2.deployment : 7055
                        2.2.1.Notify:Event triggered : 203
                        2.2.2.Bulk deployment : 6839
                            2.2.2.1.Stop : 73
                            2.2.2.2.Perform delivery : 6765
                                2.2.2.2.1.Application Deployer : 6615
                        2.2.3.Notify:Event performed : 9
                    2.3.Post process : 10
                        2.3.1.Starting : 9
    ]      [Error: com.sap.ide.eclipse.deployer.dc.DVLog  Thread[Worker-444,5,main]]
    Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] failed]      [Error: com.sap.engine.services.tc~bl~deploy~api  Thread[Worker-444,5,main]]
    Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] failed]      [Error: com.sap.engine.services.tc~bl~deploy~api  Thread[Worker-444,5,main]]
    [#6]: Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] failed]      [Error: com.sap.ide.eclipse.deployer.dc.DVLog  Thread[Worker-444,5,main]]
    [#6]: Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [XXXXXXX.com_home~chgemail] failed]      [Error: com.sap.ide.eclipse.deployer.dc.DVLog  Thread[Worker-444,5,main]]

    C:\nwds-extsoa-7.3-EHP1-SP14-PAT0000-win32\eclipse\workspace.jdi\1\DCs\XXXXXXX.com\home\chgemail\_comp\gen\default\deploy\XXXXXXX.com~home~chgemail.ear
    can you find this ear in your local drive?

  • Failed to create deployable object

    Hello All,
    We have upgraded my portal,web as and developer stuido from SP14 to SP12. All the web dynrpo applications on the portal pages have stopped functioning. I cannot click on any of the web dynpro application controls nor do these applications show
    images in caption fields. All the other portal components are working fine. The web dynpro application too work fine when I try to test them off the Web AS.Please advice.
    The error message i get is
    Failed to create deployable object resources/sap.com since it is not a webdynpro object
    Thanks

    HI Vijay,
    I guess when you upgraded your WAS server from SP14 to SP12 then you need to rebuild your all applications in NWDS SP12 and then deploy once again.
    Error says that those applications are not deployed on the server at this time. So, it means, when you have upgraded server all deployed applications were deleted.
    Just check in deploy service of visual administrator.
    Regards,
    Bhavik

  • Failed to create Salience object and java.lang.NoClassDefFoundError

    We are getting the below error while trying to use the text enrichment component in Endeca integrator clover server.
    2015-01-26 10:11:59,880 INFO 1343495 [pool-7-thread-1] Creating new Salience object from data paths: '/app/oracle/ofm/TextEnrichment/salience-5.1.1.7349/data'.
    2015-01-26 10:11:59,881 ERROR 1343495 [pool-7-thread-1] Failed to get Salience object from factory
    java.lang.NoClassDefFoundError: com/lexalytics/salience/Salience
      at com.endeca.clover.adapters.salience.SalienceFactory.createSalience(SalienceFactory.java:101)
      at com.endeca.clover.adapters.salience.SalienceFactory.getSalienceInstance(SalienceFactory.java:41)
      at com.endeca.clover.adapters.salience.SalienceRunnable.run(SalienceRunnable.java:92)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
      at java.lang.Thread.run(Thread.java:680)
    2015-01-26 10:11:59,891 ERROR 1343495 [WatchDog_1343495] Component [Customer Background:CUSTOMER_BACKGROUND] finished with status ERROR.
    Failed to create Salience object.
    2015-01-26 10:11:59,891 ERROR 1343495 [WatchDog_1343495] Error details:
    org.jetel.exception.JetelRuntimeException: Component [Customer Background:CUSTOMER_BACKGROUND] finished with status ERROR.
      at org.jetel.graph.Node.createNodeException(Node.java:535)
      at org.jetel.graph.Node.run(Node.java:514)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
      at java.lang.Thread.run(Thread.java:680)
    Caused by: java.lang.RuntimeException: Failed to create Salience object.
      at com.endeca.clover.adapters.salience.SalienceComponent.execute(SalienceComponent.java:166)
      at org.jetel.graph.Node.run(Node.java:485)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
      ... 1 more
    2015-01-26 10:11:59,930 INFO 1343495 [WatchDog_1343495] Execution of phase [0] finished with error - elapsed time(sec): 0
    2015-01-26 10:11:59,930 ERROR 1343495 [WatchDog_1343495] !!! Phase finished with error - stopping graph run !!!
    2015-01-26 10:11:59,930 INFO 1343495 [WatchDog_1343495] Post-execute finalization of connection:
    2015-01-26 10:11:59,930 INFO 1343495 [WatchDog_1343495] DBConnection driver[org.jetel.connection.jdbc.driver.JdbcDriverImpl@103cdbdc]:jndi[null]:url[jdbc:oracle:thin:@gitvm000212.us.oracle.com:1521:upslstg]:user[upsell_winref] ... OK
    2015-01-26 10:11:59,930 INFO 1343495 [WatchDog_1343495] -----------------------** Summary of Phases execution **---------------------
    2015-01-26 10:11:59,931 INFO 1343495 [WatchDog_1343495] Phase# Finished Status RunTime(sec) MemoryAllocation(KB)
    2015-01-26 10:11:59,930 INFO 1343495 [JobFinalizer_1343495] Finalisation
    2015-01-26 10:11:59,931 INFO 1343495 [WatchDog_1343495] 0 ERROR 0 139976
    2015-01-26 10:11:59,931 INFO 1343495 [WatchDog_1343495] ------------------------------** End of Summary **---------------------------
    2015-01-26 10:11:59,931 INFO 1343495 [WatchDog_1343495] WatchDog thread finished - total execution time: 0 (sec)
    2015-01-26 10:11:59,935 INFO 1343495 [JobFinalizer_1343495] RunTime: 296 ms
    2015-01-26 10:11:59,935 ERROR 1343495 [JobFinalizer_1343495]
    --------------------------------- Error details ----------------------------------
      Component [Customer Background:CUSTOMER_BACKGROUND] finished with status ERROR.
      Failed to create Salience object.
    2015-01-26 10:11:59,935 INFO 1343495 [JobFinalizer_1343495] Finished Status: ERROR
    This happens only on our stage and production instances. On our dev instance it works without problems. All 3 instances are setup the same, although our dev instance was created long time before the stage and prod instances. However, we cannot detect any differences between the machines.
    I've tried the solutions mentioned in the other similar thread: Failed to create Salience object but this doesnt solve the issue since the directory and variables were already correct.
    Anyone can help?

    Given that you are running this in Clover Server, one thing I can recommend is to shut that server down, move/truncate the logs, restart and retest, then look at the first error message you get when attempting to run the graph.  Java classloaders sometimes cache failed class clinit and report future attempts to load that class as a simple NoClassDefFoundError, masking the original/actual root cause.  With any luck you might find another, clearer error - maybe the native binary libraries are not being located.

  • Failed to load deployable object part 'AmendAgrmntApp', type 'Application'

    hi,
    I have deployed a DC on server. I can run the application indepemdently. But when I try to create the URL of this application using WDURLGenerator.getApplicationURL (as I want to call this application from another application), i get the following exception
    com.sap.tc.webdynpro.services.sal.deployment.api.WDDeploymentException: Failed to load deployable object part 'AmendAgrmntApp', type 'Application' of deployable object 'aramco.com/itcaesaleswebamndagrmnt'.
    Failed to generate URL to deployable object 'aramco.com/itcaesaleswebamndagrmnt', application 'AmendAgrmntApp'
    Please suggest a solution
    Thanks !
    seventyros

    According to the API at http://help.sap.com/javadocs/NW04S/SPS09/wd/com/sap/tc/webdynpro/services/sal/url/api/WDURLGenerator.html
    There must be a deployable object part of type WDDeployableObjectPartType.APPLICATION with the given applicationPartName within the deployable object with name deployableObjectName

  • Failed to start deployable object

    Hello friends!
    I get the following error very often after migrating from 7.1 sp5 to 7.1.1 Ehp1 sp4 NWDS.
    (Never faced this issue in 7.1 sp5 NWDS.)
    "Application error occured during the request processing
    com.sap.tc.webdynpro.services.sal.core.DispatcherException: Failed to start deployable object....."
    This Webdynpro Application goes down time and again when other application are working fine.
    On the NWA side : It says Webdynpro has implicilty stoped and EJB application failed to start.
    Please help.
    Regards
    Poornima

    Following is the entire stack trace
    com.sap.tc.webdynpro.services.sal.core.DispatcherException: Failed to start deployable object abcd.com/esswd.
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.initApplicationDeployableObjectPart(RequestManager.java:589)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.initTask(RequestManager.java:505)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doInitWdEnvironment(RequestManager.java:170)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:231)
         at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:202)
         at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
         at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
         at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
         at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToDispatcherContext(ExecutionContextDispatcher.java:146)
         at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:92)
         at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:104)
         at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
         at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:61)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
         at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:486)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
         at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:243)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
         at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
         at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    Caused by: com.sap.tc.webdynpro.services.sal.deployment.core.StartStopException: Failed to start the deployable object 'abcd.com/esswd'.
         at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.start(DeployableObject.java:226)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.initApplicationDeployableObjectPart(RequestManager.java:583)
         ... 50 more
    Caused by: com.sap.tc.webdynpro.spi.WebDynproRuntimeException: Cannot start application abcd.com/esswd
         at com.sap.engine.services.webdynpro.WebDynproRuntimeServiceImpl.start(WebDynproRuntimeServiceImpl.java:473)
         at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.start(DeployableObject.java:224)
         ... 51 more
    Caused by: com.sap.engine.services.servlets_jsp.server.deploy.impl.exceptions.WCEApplicationNotStartedException: Failed explicit start for application [abcd.com/esswd].
         at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.start(ApplicationManager.java:190)
         at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.analyseAppStatusMode(ApplicationManager.java:293)
         at com.sap.engine.services.servlets_jsp.server.deploy.impl.WebContainerExtensionContext.getWebModuleContext(WebContainerExtensionContext.java:181)
         at com.sap.engine.services.webdynpro.WebDynproRuntimeServiceImpl.start(WebDynproRuntimeServiceImpl.java:471)
         ... 52 more
    Caused by: java.rmi.RemoteException: [ERROR CODE DPL.DS.6309] Error occurred while starting application in whole cluster and wait.; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: [server ID 4651950:Problem in appclient deployment. Cannot create application client environment into naming. Application "abcd.com/essappl" will not be deployed because of NamingException.
               -> Path to object does not exist at appclient-environment, the whole lookup name is appclient-environment/abcd.com/essappl/jxl.
    server ID 4651950:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5035] Application [abcd.com/esswd] cannot be started. Reason: it has hard reference to resource [essappl] with type [application], which is not active on the server.
    Hint: 1) Is referred resource deployed? 2) Is referred resource able to start?
         at com.sap.engine.services.deploy.server.ReferenceResolver.checkApplicationStatus(ReferenceResolver.java:870)
         at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:847)
         at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:574)
         at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:488)
         at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:195)
         at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:160)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483)
         at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:587)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:213)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:374)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3430)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3416)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:551)
         at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.start(ApplicationManager.java:183)
         at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.analyseAppStatusMode(ApplicationManager.java:293)
         at com.sap.engine.services.servlets_jsp.server.deploy.impl.WebContainerExtensionContext.getWebModuleContext(WebContainerExtensionContext.java:181)
         at com.sap.engine.services.webdynpro.WebDynproRuntimeServiceImpl.start(WebDynproRuntimeServiceImpl.java:471)
         at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.start(DeployableObject.java:224)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.initApplicationDeployableObjectPart(RequestManager.java:583)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.initTask(RequestManager.java:505)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doInitWdEnvironment(RequestManager.java:170)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:231)
         at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:202)
         at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
         at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
         at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
         at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToDispatcherContext(ExecutionContextDispatcher.java:146)
         at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:92)
         at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:104)
         at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
         at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:61)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
         at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:486)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
         at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:243)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
         at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
         at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)

  • Web Dynpro Java : Failed to get deployable object part info for component

    Currently we have a web dynpro java project which connects to the ABAP backend with Web Services. Everything seems fine, and when we transport to the production server via NWDI, we have the following error. Everytime we try to access the application , the error is occurred.
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to get deployable object part info for component com.sie.attachmentcomp.AttachmentComp
        at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.getComponentDeploymentDescription(ClientComponent.java:784)
        at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:934)
        at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:177)
        at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:149)
        at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:116)
    It is working properly in our development , and testing environment. Only production has this error. And one weird thing is that this particular error occurred only sometimes to some user. For example; I could not access to the application with this error yesterday but my friend can access. Today, I can access in the morning but my friend cannot. For another friend , Yesterday he can access by using IE but not by Firefox. But today Firefox is fine but not with IE. It seems crazy.
    For more information, in our J2EE engine for the production server, we have 3 server nodes (clusters). And we are not sure it is the source of the problem. Is there any solution , and any way to know from the application that we are on which server?
    We also go and check from the Content Administrator in Web Dynpro Console. Under our project name, in the list of Components, sometimes we can see AttachmentComp but sometimes not.
    Please help us as our project is about to go-live next week.
    Thanks,
    Yu

    Hi Meenge,
    Please check below document for finding root cause for "Failed to start deployable object part info for <development component> and application <application name>"
    http://help.sap.com/saphelp_nwce711core/helpdata/en/44/7716e1633a12d1e10000000a422035/frameset.htm
    OR http://help.sap.com/saphelp_nw04/helpdata/EN/f4/1a1041a0f6f16fe10000000a1550b0/frameset.htm
    Hope it helps
    Regards
    Arun

  • Cisco Bars - Web Error : Failed to create ASP object

    I have installed ;
    Win2003
    framework ASP .net2
    IIS
    MSDE 2000 serveur
    Cisco BARS Version 4.0.12
    When I go to http://IP/BARS
    It ask for password, then I see the usual interface, but then I go and choose a backup option and I allways have this error
    Windows Internet explorer
    Failed to create ASP Object for : _RemoteScripts/rs_BARSconfig.asp
    Firefox show that error :
    Error:
    Cannot locate proxy which supports Remote Scripting.
    Was RSEnableRemoteScripting method invoked?
    Second popup :
    Failed to create ASP object for : _RemoteScripts/rs_BARSconfig.asp

    thanks a lot, it fix my problem verry well.
    Another little one :)
    have any idea of this one here ?
    Webpage error details
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
    Timestamp: Sat, 4 Jul 2009 03:06:10 UTC
    Message: Object doesn't support this property or method
    Line: 269
    Char: 3
    Code: 0
    URI: http://localhost/BARS/_ScriptLibrary/rs.htm
    Message: 'rsConfig' is null or not an object
    Line: 199
    Char: 3
    Code: 0
    URI: http://localhost/BARS/BARSserverConfig.asp

  • Failed to get deployable object part info for component

    We are getting the given error while accessing the leave request/approve application in the ESS overview page.
    The initial exception that caused the request to fail, was:
       com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to get deployable object part info for component com.sap.pcuigp.xssfpm.wd.FPMComponent
        at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.getComponentDeploymentDescription(ClientComponent.java:682)
        at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.<init>(ClientComponent.java:707)
        at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.<init>(ClientApplication.java:298)
        at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.createApplication(ClientApplication.java:285)
        at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.createApplication(WebDynproMainTask.java:748)
        ... 22 more

    HI saket jha,
    Refer the following thread
    Error in "Who is Who" search
    ESS Timesheet Error
    Regards,
    Manivannan P

  • List data validation failed when creating a new list item but does not fail when editing an existing item

    Dear SharePoint Experts,
    Please help.
    Why does my simple formula work in Excel but not-work in SharePoint?
    Why does this formula...
    =IF([Request Type]="Review",(IF(ISBLANK([Request Date]),FALSE,TRUE)),TRUE)
    ...work in Excel but fail when I try to use it in SharePoint?
    The intent of this formula is the following...
    If the field "Request Type" has the value "Review" and the field "Request Data" is blank then show FALSE, otherwise show TRUE.
    SharePoint saves the formula, but when a list item is saved where the formula is implemented, (under List Settings, List Validation), SharePoint does not, say anything other than that the formula failed.
    Note that the "list data validation failed" error only happens when I am creating a new item-- the formula above works just fine when one is trying to Save on the edit form. 
    Can you help?
    Thanks.
    -- Mark Kamoski

    Dear Jason,
    I appreciate your efforts.
    However, it seems to me that this statement of yours is not correct...
    "If it meet the validation formula, then you can new or edit the item, otherwise, it will throw the 'list data validation failed' error, it is by design".
    I believe this is NOT the answer for the following reasons.
    When I create a new item and click Save, the validation error is "list data validation failed".
    When I edit an existing item and click Save, the validation error is "my custom error message" and this is, I believe, the way it needs to work each time.
    I think, at the core, the error my formula does not handle some condition of null or blank or other default value.
    I tried a forumla that casts the date back to a string, and then checked the string for a default value, but that did not work.
    I tried looking up the Correlation ID in the ULS when "list data validation failed" occurs, but that gave no useful information because, even though logging was set to Verbose, the stack trace in the error log was truncated and did not given any
    good details.
    However, it seems to me that SharePoint 2013 is not well-suited for complex validation rules, because...
    SharePoint 2013 list-level validation (NOT column-level validation) allows only 1 input for all the multi-field validation formulas in a given list-- so, if I had more than 1 multi-field validation rule to implement on a given list, it would need to be packed
    into that single-line-of-code forumla style, like Excel does. That is not practice to write, debug, or maintain.
    SharePoint 2013 list-level validation only allows 1 block of text for all such multi-field validation rules. So that will not work because I would have something like "Validation failed for one or more of the following reasons-- withdrawal cannot exceed
    available balance, date-of-birth cannot be after date-of-death,... etc". That will not work for me.
    The real and awesome solution would simply be enhancing SP 2013 so that column-level validation forumlas are able to reference other columns.
    But, for now, my workaround solution is to use JavaScript and jQuery, hook the onclick handler on the Save button, and that works good. The only problem, is that the jQuery validation rules run before any of the column-level rules created  with OOTB
    SP 2013. So, in some cases, there is an extra click for the enduser.
    Thanks,
    Mark Kamoski
    -- Mark Kamoski

  • How to create local calendar?

    At times of Snow Leopard I had a local calendar and several calendars from my Exchange account.
    At that time I created Automator-based processes and entered them to my local calendar to be executed at specific intervals.
    After first syncing with MobileMe and then migrating to iCloud, my local calendar dissappeared and the "process" schedules have been moved to MobileMe and then iCloud.
    However, those process schedules can only be executed on my iMac and I DONT WANT them to be synced to my other devices (MacBook, iPhone).
    So I need my local calendar back.
    How can I create a local calendar on my iMac?
    Thanks for all hints...
    Matt

    Roger, you made my day!
    I did miss the command "New Calendar" in the "File" menu (or however those menus are called in english. have a german OS).
    Instead, I always tried to create a new local calendar via the  "Account" settings - which was absolutely stupid!
    However, when exporting those Automator based entries and trying to re-import them into my local calendar, the "possibly dangerous" Automator actions have been removed.
    But I could open those (recurring) entry in edit mode and just "switch" it to my local calendar without losing any information.
    Thank you so much for your hint, which lead me to the right way!
    Matt

  • Sender channel. Details: MQJMS2005: failed to create MQQueueManager for loc

    Hi Friends,
    when i amdoing the jms to file scenario i got the following error "Sender channel. Details: MQJMS2005: failed to create MQQueueManager for 'local host:SAPQM'". please help me to resolve this issue.

    hi uday,
    check the below threads with the similar issue
    configuration of JMS  adapter Using WebSphereMQ
    Adapter Engine Error
    Receiver determination error
    <removed by moderator>
    regards
    kummari
    Edited by: Mike Pokraka on Jul 24, 2008 12:46 PM

  • Create the object - not correct data in the file ?

    I have the text file, then I parse and create objects MyDocument (one row = one document). If row is corect then I create object MyDocument. But what I must do when row is not correct. The row can have 3 type of errors:
    1.Not correct length of row
    2.Not filled required fields in row
    3.Field are filled by not correct data
    Is a good to throw exception when I get one of this errors. Do I need to store this errors on separate class (MyObjectErrors extends Exception)?
    So when row is correct I create the object MyDocument. Otherwise I NOT create object MyDocument and throw exception. Is this a good solution?

    One question These 3 error you want together or what let me know i ll do that code n give you

  • Create SOFM object instance from PDF

    Hi All,
    I am using 4.6 version of SAP where FM 'sap_wapi_attachment_add' is does not exit. My query is to create an attachment (SMARTFORM coverted in PDF) in ABAP progam which i have to send as attachment with a Decision Task in the workflow.
    I am able to send attachment with mail but to send attachment with decision task i need to create an instance of SOFM object. Please suggest an alternative method to do so instead of FM 'sap_wapi_attachment_add' .

    Hi Taran,
    I had put my code in workflow task. You can find the task method code below:
    *Data declaration
    DATA: GITAB     TYPE SOLIX_TAB,                     
          GSTAB     LIKE LINE OF GITAB,                 
          SOFM_KEY  TYPE SOFMK,                         
          GIT_LINES TYPE SOLI_TAB.                      
    DATA: LREF_DOCUMENT_BCS  TYPE REF TO CL_DOCUMENT_BCS,
          LREF_IM_DOCUMENT   TYPE REF TO IF_DOCUMENT_BCS.
    Generate Smartform*
    CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
        EXPORTING
          FORMNAME                 = C_FORM
    *      VARIANT                  = ' '
    *      DIRECT_CALL              = ' '
        IMPORTING
          FM_NAME                  = GV_FM
        EXCEPTIONS
          NO_FORM                  = 1
          NO_FUNCTION_MODULE       = 2
          OTHERS                   = 3.
      IF SY-SUBRC <> 0.
    *    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *       WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      CALL FUNCTION 'SSF_GET_DEVICE_TYPE'
        EXPORTING
          I_LANGUAGE                   = SY-LANGU
    *      I_APPLICATION                = 'SAPDEFAULT'
        IMPORTING
          E_DEVTYPE                    = GV_OUTPUT_OPTIONS-TDPRINTER
        EXCEPTIONS
          NO_LANGUAGE                  = 1
          LANGUAGE_NOT_INSTALLED       = 2
          NO_DEVTYPE_FOUND             = 3
          SYSTEM_ERROR                 = 4
          OTHERS                       = 5.
      IF SY-SUBRC <> 0.
    *    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *       WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      GV_OUTPUT_OPTIONS-TDNOPREV = 'X'.
      GV_CONTROL_PARAMETERS-GETOTF = 'X'.
      GV_CONTROL_PARAMETERS-NO_DIALOG = 'X'.
      CALL FUNCTION GV_FM
        EXPORTING
    *      ARCHIVE_INDEX              =
    *      ARCHIVE_INDEX_TAB          =
    *      ARCHIVE_PARAMETERS         =
          CONTROL_PARAMETERS         = GV_CONTROL_PARAMETERS
    *      MAIL_APPL_OBJ              =
    *      MAIL_RECIPIENT             =
    *      MAIL_SENDER                =
          OUTPUT_OPTIONS             = GV_OUTPUT_OPTIONS
          USER_SETTINGS              = 'X'
          GV_ENAME                   = GV_ENAME
          GV_PERNR                   = GV_PERNR
          GV_PERSK                   = GV_PERSK
          GV_ZZ_LEVEL                = GV_ZZ_LEVEL
          GV_BTRTX                   = GV_BTRTX
          GV_GBDAT                   = GV_GBDAT
          GV_JOIN_DATE               = GV_JOIN_DATE
          GV_RESIN_DATE              = GV_RESIN_DATE
        IMPORTING
          DOCUMENT_OUTPUT_INFO       = GV_DOCUMENT_OUTPUT_INFO
          JOB_OUTPUT_INFO            = GV_JOB_OUTPUT_INFO
          JOB_OUTPUT_OPTIONS         = GV_JOB_OUTPUT_OPTIONS
        EXCEPTIONS
          FORMATTING_ERROR           = 1
          INTERNAL_ERROR             = 2
          SEND_ERROR                 = 3
          USER_CANCELED              = 4
          OTHERS                     = 5.
      IF SY-SUBRC <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      CALL FUNCTION 'CONVERT_OTF_2_PDF'
    *    EXPORTING
    *      USE_OTF_MC_CMD               = 'X'
    *      ARCHIVE_INDEX                =
        IMPORTING
          BIN_FILESIZE                 = GV_BIN_FILESIZE
        TABLES
          OTF                          = GV_JOB_OUTPUT_INFO-OTFDATA
          DOCTAB_ARCHIVE               = GIT_DOCS
          LINES                        = GIT_LINES_TEMP
        EXCEPTIONS
          ERR_CONV_NOT_POSSIBLE        = 1
          ERR_OTF_MC_NOENDMARKER       = 2
          OTHERS                       = 3.
      IF SY-SUBRC <> 0.
    *    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *       WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      CALL FUNCTION 'SX_TABLE_LINE_WIDTH_CHANGE'
        TABLES
          CONTENT_IN  = GIT_LINES_TEMP
          CONTENT_OUT = GIT_LINES.
      IF SY-SUBRC <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      CALL FUNCTION 'SO_SOLITAB_TO_SOLIXTAB'
        EXPORTING
          IP_SOLITAB  = GIT_LINES   "GIT_LINES_TEMP1
        IMPORTING
          EP_SOLIXTAB = GITAB.
    *Create SOFM object from smartform PDF
    IF NOT GITAB IS INITIAL.                    
          TRY.                                                        
              CALL METHOD CL_DOCUMENT_BCS=>CREATE_DOCUMENT            
                EXPORTING                                             
                  I_TYPE          = 'BIN'                             
                  I_SUBJECT       = 'NOTICE PAY WAIVER FORM'          
    *          I_LENGTH        =                                      
    *          I_LANGUAGE      = SPACE                                
    *          I_IMPORTANCE    =                                      
    *          I_SENSITIVITY   =                                      
    *          I_TEXT          =                                      
                  I_HEX           = GITAB                             
    *          I_HEADER        =                                      
    *          I_SENDER        =                                      
                RECEIVING                                             
                  RESULT          = LREF_DOCUMENT_BCS.                
            CATCH CX_DOCUMENT_BCS .                                   
          ENDTRY.                                                                               
    LREF_IM_DOCUMENT = LREF_DOCUMENT_BCS.                                                                               
    TRY.                                                        
              CALL METHOD LREF_DOCUMENT_BCS->ADD_DOCUMENT_AS_ATTACHMENT
                EXPORTING                                             
                  IM_DOCUMENT = LREF_IM_DOCUMENT.                     
            CATCH CX_DOCUMENT_BCS .                   
          ENDTRY.                                                                               
    TRY.                                        
              CALL METHOD LREF_DOCUMENT_BCS->GET_DOCTP
                RECEIVING                             
                  RESULT = SOFM_KEY-DOCTP.            
            CATCH CX_OS_OBJECT_NOT_FOUND .            
          ENDTRY.                                                                               
    TRY.                                        
              CALL METHOD LREF_DOCUMENT_BCS->GET_DOCYR
                RECEIVING                             
                  RESULT = SOFM_KEY-DOCYR.            
            CATCH CX_OS_OBJECT_NOT_FOUND .            
          ENDTRY.                                                                               
    TRY.                                        
              CALL METHOD LREF_DOCUMENT_BCS->GET_DOCNO
                RECEIVING                             
                  RESULT = SOFM_KEY-DOCNO.            
            CATCH CX_OS_OBJECT_NOT_FOUND .            
          ENDTRY.                                                                               
    SWC_CREATE_OBJECT NOTICE_PAY_WAIVER_FORM 'SOFM' SOFM_KEY.
          SWC_SET_ELEMENT CONTAINER 'NOTICE_PAY_WAIVER_FORM'      
                                     NOTICE_PAY_WAIVER_FORM.      
        ENDIF.
    The object instance thus created will be visible along with other  object instances in the workitem display. Provide this object in binding of decision step as you provise any other obect instance and not as ATTACH_OBJECT       
    Regards,
    Neha

Maybe you are looking for

  • A way to search System Files and by File Name as default?

    Hello. Is there a way I can make the default search both include searching by File Name and searching System Files? I know I can make a saved search, but this just is one extra step. I'd like to the default behavior of the Finder be to search system

  • DVR to DVD

    I was wondering if anyone out there could point me in the right direction. I am looking for an appliance that I can plug into my DVR that allows me to move those programs I love onto my computer so I can can then put them on dvd. any advice would be

  • Getting calendar events from exchange 2003

    Hi All, We have a requirement of getting the calendar items from exchange server 2003 using web dav , jakarta slide initially we made a connection and retrieve the mail items from server we use search method of org.webdav.lib.httpclient.method.search

  • Soundbooth CS4 will not record files

    I am having an issue with Soundbooth CS4 not recording a file. I can open the record box and select my audio source (Alesis USB mixer in this case) but when I hit record nothing records. The record button does highlight however no audio is record or

  • Is there a limit to how many apps we can reserve?

    Since iTunes Connect doesnt allow us to delete an app without at least one approved version. So is there any limit to how many apps we can reserve? Can we just check the name availability without reserving it?