cancel
Showing results for 
Search instead for 
Did you mean: 

Standard Leave iView of ESS does not work... What to do?

Former Member
0 Kudos

Hi Experts,

We are implementing ESS / MSS. Most of the iViews of ESS are working fine. However, iView of Leave Request is not working.

1) Is it possible that during the portal installation due to some error, some of the components needed for Leave Request has not got installed properly.

2) If yes, can we take the dump / par / WD file of other SAP EP system and import it in my portal.

3) If no, what is the remedy for the solution.

Please suggest. I am getting following message while running application in web dynpro content administration :

An object with ID portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.ess.employee_self_service/com.sap.pct.erp.srvconfig.lea/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.LeaveRequest does not exist.

Regards,

Gary

Accepted Solutions (1)

Accepted Solutions (1)

siddharthrajora
Product and Topic Expert
Product and Topic Expert
0 Kudos

Can you check from the content Admin? If you are able to launch this iview? It should be working if allthe

backend customisation is done in PTARQ

Former Member
0 Kudos

Hi Pinki and Siddharth,

Thanks a lot for the help. I am unable to launch the iView from content admin. (content admin --> portal content ? Content Provided by SAp>End User Content > Employee Self-service> Iviews--> working time)

I am unable to launch the iview from Content Admin> Webdynpro> Deployed content (int he left side panel) >sap.com> sap.com/ess~lea as well.

Now only option left is to re deploy the esslea.sda' and 'esslea~cfg.sda' files from the PCUI_GP files for the Support pack that you are in.

In fact this activity was done by the BASIS person. Can you please let me know the steps to do it. Presently BASIS person is on vacation. I want to do the work on my own.

Regards,

Gary

Former Member
0 Kudos

Hi Gary,

What exactly do you see when you try to launch the iview?

Thanks and Regards,

Pinki

Former Member
0 Kudos

Hi Pinki,

Case 1:

From content admin --> portal content > Content Provided by SAp>End User Content > Employee Self-service> Iviews--> working time I am getting following error message:

iView : The initial exception that caused the request to fail, was:

com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed in WD JNDI lookup. javax.naming.NameNotFoundException: No child found in WebDynproContext with name base

at com.sap.portal.pcm.iview.admin.AdminBaseiView.createAttrSetLayersList(AdminBaseiView.java:357)

at com.sap.portal.pcm.iview.admin.AdminBaseiView.getAttrSetLayersList(AdminBaseiView.java:205)

at com.sap.portal.pcm.iview.admin.AdminBaseiView.getCustomImplementation(AdminBaseiView.java:148)

at com.sap.portal.pcm.admin.PcmAdminBase.getImplementation(PcmAdminBase.java:530)

at com.sapportals.portal.ivs.iviews.IviewServiceObjectFactory.getObjectInstance(IviewServiceObjectFactory.java:442)

... 40 more

Case 2:

From Content Admin> Webdynpro> Deployed content (int he left side panel) >sap.com> sap.com/ess~lea I am getting following error message:

An object with ID portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.ess.employee_self_service/com.sap.pct.erp.srvconfig.lea/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.LeaveRequest does not exist.:

com.sap.xss.config.FPMInconsistentObjectException: An object with ID portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.ess.employee_self_service/com.sap.pct.erp.srvconfig.lea/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.LeaveRequest does not exist.

Thanks

Gary

at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObjectInternal(PcdObjectBroker.java:90)

at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObject(PcdObjectBroker.java:47)

at com.sap.xss.config.domain.PersistentObjectManager.retrieveObjectInternal(PersistentObjectManager.java:106)

at com.sap.xss.config.domain.PersistentObjectManager.retrieveObject(PersistentObjectManager.java:80)

at com.sap.xss.config.FPMRepository.retrieveObjectInternal(FPMRepository.java:83)

at com.sap.xss.config.FPMRepository.retrieveObject(FPMRepository.java:66)

at com.sap.pcuigp.xssutils.ccpcd.FcXssPcd.initializeConfiguration(FcXssPcd.java:816)

at com.sap.pcuigp.xssutils.ccpcd.FcXssPcd.loadConfiguration(FcXssPcd.java:250)

at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcd.loadConfiguration(InternalFcXssPcd.java:178)

at com.sap.pcuigp.xssutils.ccpcd.FcXssPcdInterface.loadConfiguration(FcXssPcdInterface.java:138)

at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcdInterface.loadConfiguration(InternalFcXssPcdInterface.java:148)

at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcdInterface$External.loadConfiguration(InternalFcXssPcdInterface.java:240)

at com.sap.pcuigp.xssutils.ccpcd.CcXssPcd.loadConfiguration(CcXssPcd.java:282)

at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcd.loadConfiguration(InternalCcXssPcd.java:184)

at com.sap.pcuigp.xssutils.ccpcd.CcXssPcdInterface.loadConfiguration(CcXssPcdInterface.java:115)

at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcdInterface.loadConfiguration(InternalCcXssPcdInterface.java:124)

at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcdInterface$External.loadConfiguration(InternalCcXssPcdInterface.java:184)

at com.sap.xss.essservices.cc.ccesspcd.CcEssPcd.loadConfiguration(CcEssPcd.java:268)

at com.sap.xss.essservices.cc.ccesspcd.wdp.InternalCcEssPcd.loadConfiguration(InternalCcEssPcd.java:169)

at com.sap.xss.essservices.cc.ccesspcd.CcEssPcdInterface.loadConfiguration(CcEssPcdInterface.java:115)

at com.sap.xss.essservices.cc.ccesspcd.wdp.InternalCcEssPcdInterface.loadConfiguration(InternalCcEssPcdInterface.java:124)

at com.sap.xss.essservices.cc.ccesspcd.wdp.InternalCcEssPcdInterface$External.loadConfiguration(InternalCcEssPcdInterface.java:202)

at com.sap.pcuigp.xssutils.ccxss.CcXss.loadConfiguration(CcXss.java:209)

at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXss.loadConfiguration(InternalCcXss.java:153)

at com.sap.pcuigp.xssutils.ccxss.CcXssInterface.loadConfiguration(CcXssInterface.java:112)

at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface.loadConfiguration(InternalCcXssInterface.java:124)

at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface$External.loadConfiguration(InternalCcXssInterface.java:184)

at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:187)

at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)

at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)

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

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)

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

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:756)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)

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

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

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

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

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

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

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

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

Former Member
0 Kudos

com.sap.xss.config.FPMInconsistentObjectException: An object with ID portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.ess.employee_self_service/com.sap.pct.erp.srvconfig.lea/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.LeaveRequest does not exist.

....

Well this definitely means you need to deploy missing components, will be with redeploying whole ESS since you might not have made any changes so far.

Check with BASIS and get relevant ESS and required components redeployed on server.

Rgds

Answers (2)

Answers (2)

siddharthrajora
Product and Topic Expert
Product and Topic Expert
0 Kudos

yes that means SDA files have missed leave request files, Now you have to undeploy first and then deploy it, There are steps given in help.sap.com

Former Member
0 Kudos

Hi Gary,

What do you mean when you say that the leave request ivew is not working?

Please try previewing the iviews from the content provided by SAP (content admin --> portal content ? Content Provided by SAp>End User Content > Employee Self-service> Iviews--> working time) and see whether you are able to view it from there. if you are able to preview from there, then the problem is with the configuration in the SPRO (check check the url of the pcd provide) and also try previewing it directly from the ESS role in the portal.

If you are not able to preview the iviews present in the content provided by SAP, also check from Content Admin> Webdynpro> Deployed content (int he left side panel) >sap.com> sap.com/esslea. Expand the node and try running the application from there and check. If it does not work, then, you will have to re - deploy the esslea.sda' and 'essleacfg.sda' files from the PCUI_GP files for the Support pack that you are in.

if you any more queries, please let me know.

Regards,

Pinki