Leave Request Webdynpro

Dear All,
We are on ECC 6 and EP 7 SP9 with business package 9. When i try to browse the leave request webdynpro page. It give me some error message like
Index: 0, Size: 0  
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.RangeCheck(ArrayList.java:507)
at java.util.ArrayList.get(ArrayList.java:324)
at com.sap.aii.proxy.framework.core.JcoBaseList.get
and etc.
This suppose to be a standard leave page and do i need any configuration?
Anyone know whats wrong with this page?
Thanks
Regards,
Bryan

Hi
Yah some configuration is required to access the leave request page in the portal even it is the standard page of ECC.
first you have to create JCO connection from portal to ECC thru content admin->webdynpro->create JCO connection
once you have to create JCO connection then you can test the connection.
before that also u have to create the ECC system object in portal and assign this system alias to the properties of the webdynpro ivew where you want to access leave request page
in portal.
if u want then you can map this ECC system to any user thru Usermapping of SSO.
Regards
Sunil
[points are helpful]

Similar Messages

  • Who can tell me how to find the leave request Webdynpro for ABAP iview

    Hi,Expert,
    As I know Portal only has Webdynpro for java iview for leave request iview in the past.
    but someone tell me SAP portal has delivered some new standard WebDynpro for ABAP iview.
    I have a requirement to create a employee role for new Leave Request service created by WD ABAP . Under Content Provided by SAP in Content Administration, I couldn't find the iView assocated to the leave request except the Java one. Is there have any Employee Self-Service Web Dynpro ABAP workset ?
    thanks
    Olivia

    The business package for ESS based on Webdynpro for ABAP is available only for ECC 6.0 EHP5.
    If you are on EHP5, you may choose to use this version of the BP.
    http://help.sap.com/erp2005_ehp_05/helpdata/EN/25/340b0507434193adbfe3f8fc8896c7/frameset.htm
    Leave Request application:
    http://help.sap.com/erp2005_ehp_05/helpdata/EN/1f/a073be62744fcca7e1fae9942f0031/frameset.htm
    Thanks,
    Shanti

  • Webdynpro leave request page

    Dear All,
    We are on ECC 6 and EP 7 SP9 with business package 9. When i try to browse the leave request webdynpro page. It give me some error message like
    Index: 0, Size: 0  
    java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
    at java.util.ArrayList.RangeCheck(ArrayList.java:507)
    at java.util.ArrayList.get(ArrayList.java:324)
    at com.sap.aii.proxy.framework.core.JcoBaseList.get
    and etc.
    This suppose to be a standard leave page and do i need any configuration?
    Anyone know whats wrong with this page?
    Thanks
    Regards,
    Bryan

    i guess you need to apply note 1134874 to fix this issue
    Regards
    Shridhar Gowda

  • Add a custom button in Ess Leave Request

    Hi Gurus,
    I have requirement, add a custom button in a Standard ESS leave request (Webdynpro Java). When i click the the button it has to call popview(custom view). I am new to webdynpro Java, If possible explain me with step by step preocedures(if possible with screen shots).
    Thanks,
    Mohammed.
    Moderator message: this is the wrong forum, please have a look in the "Web Dynpro Java" forum, but always search for available information before posting.
    Edited by: Thomas Zloch on Jun 17, 2011 9:54 AM

    Hi Gurus,
    I have requirement, add a custom button in a Standard ESS leave request (Webdynpro Java). When i click the the button it has to call popview(custom view). I am new to webdynpro Java, If possible explain me with step by step preocedures(if possible with screen shots).
    Thanks,
    Mohammed.
    Moderator message: this is the wrong forum, please have a look in the "Web Dynpro Java" forum, but always search for available information before posting.
    Edited by: Thomas Zloch on Jun 17, 2011 9:54 AM

  • ERP 2005 ESS Leave Request

    Hi,
    We are planning to use the new Leave request module. We want to bring in 9 new fields in to the Leave module. We found the way of adding customised fields in to the Webdynpro screens. But i want to add dropdown list or provide a search button to provide value selection for the customer fields. We scanned through the BADI's, but it seems not possible. Have anybody tried on the same and any suggestion or solution is really vluable.
    Best Regards
    Sundar / Rahul

    Hi Shamsul,
    if you only need one single dropdown box, you can possibly misuse the UMSKD field. This field provides the "sickness description" from table T572B in a dropdown menu. You can see this, when you activate the customer field "description of sickness" (technical name: UMSKD  (PTARQ_ATTABS_TIMEDATA_STRUC)) in your IMG.
    Then you may modify the function PT_ARQ_F4HELP_SICKCODE. which determines the sickness description and its code and assigns it to the customer field on the leave request webdynpro application.
    My problem is, that i need to pass an additional approver to the workflow. Unfortunately the key-field UMSKD has just a length of 6 chars. so i cant use it for the personell number...
    Hope this helps on!
    Matthias

  • Enhancement in ESS Leave Request

    Hi Gurus,
    I am new to webdynpro Java. I have a requirement to add a custom button in a Standard ESS leave request (Webdynpro Java) view. When i click the the button it has to call popview(not sure is it possible to call a webdynpro abap view).  If possible explain me with step by step preocedures(with screen shots).
    Thanks,
    Mohammed

    Hi,
              Good, you are now able to do modification in Standard ESS package. If you want to navigate to another WDABAP iView from your WDJAVA application, you can use the below code on some button or link action to navigate to another iView.
    Check this link:-
    http://help.sap.com/javadocs/NW04/current/wd/com/sap/tc/webdynpro/clientserver/navigation/api/WDPortalNavigation.html
    public void onActionnavigateToToAbapiView(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
        //@@begin onActionnavigateToAbapiView(ServerEvent)
         try
                        WDPortalNavigation.navigateAbsolute(
                         "ROLES://portal_content/com.demo.DEMO_PCD/com.demo.ESS_SAP/com.demo.iview_ESS/demo.com.java_demo_com_demodc_demo_com_DemoApp",
                         WDPortalNavigationMode.SHOW_INPLACE,
                         "Window Title", WDPortalNavigationHistoryMode.NO_DUPLICATIONS,
                         "Title",
                         "",//ContextURL
                         "param1=10&param2=portalID");          
         catch (Exception e)
              e.printStackTrace();
    You will find your WDAbap PCD location in Content Admin, copy it and repace PCD: with ROLES at start.
    also you can pass parameters between 2-iViews, in the above code snippet you can find that.
    the above code needs to be written in your source iView so as to navigate to destination iView which is mentioned using its PCD location.
    to retrieve the parameters you need to check ABAP syntax to retrieve URL parameters.
    In java we retreive using below syntax:-
    String param1 = WDProtocolAdapter.getProtocolAdapter().getRequestObject().getParameter("param1");
    String loginID = WDProtocolAdapter.getProtocolAdapter().getRequestObject().getParameter("param2");
    to show it as a Pop-Up you need to find some work-around to achieve it, If i get time will do it and let you know, but if you find something for that do share.
    Regards
    Tushar Shinde.

  • How to find the leave request layout in standard Webdynpro ESS business pac

    Hi Gurus,
    How to find the Intial leave request layout from the standard webdynpro ESS business package.
    Can you tell me the exact component that i need to look for this particular layout.
    Its a urgent requirement can you guys send me the answers ASAP
    Higher points will be rewarded for the useful inputs.
    Thanks in Advance,
    Dharani

    look for ess~lea dc
    reward points if helpful

  • Webdynpro - Leave Request Approval

    Hi Colleagues,
    We have implemented the mysaperp2005 ESS business package on EP7. Portal is working, leave request is working, workflows trigger and open in UWL, UWL looks OK.
    However the button to execute the workflow, "Launch Webdynpro", launches the wrong URL for Leave Approval.
    It gets the Port wrong using 8032
    http://ourserver.com:8032/webdynpro/dispatcher/sap.com/ess~lea/LeaveRequestApprover
    Should be port 53300
    http://ourserver.com:53300/webdynpro/dispatcher/sap.com/ess~lea/LeaveRequestApprover
    Cannot find where 8032 is comming from, can can't find any config for this in the LeaveRequestApprover iView properties or anywhere else. Checked every property of the LeaveRequestApprover versus LevaeRequest iView: identical.
    Regards,
    Jimmy.

    Thanks Sebastian,
    icm/server_port_0 is not set up.
    I have only icm/server_port_<xx>
    Do you thing I should I set up icm/server_port_0?
    Regards,
    Jimmy.
    Param. Name
    icm/server_port_<xx>
    Short description(Engl)   ICM server specification
    Appl. area                Internet Communication Manager
    ParameterTyp              Character String
    Changes allowed           Change permitted
    Valid for oper. system    All operating systems
    DynamicallySwitchable
    Same on all servers
    Dflt value
    ProfileVal
    Current value

  • Difference in ITS Leave request and WebDynpro Leave request

    Hello,
    Whats the difference between ITS based leave request and webdynpro based leave request.
    I read that in webdynpro based leave request there is a need for new workflow, other than what is being used in ITS based leave request. If for some period of time both are in place then will it create some kind of problem ?
    Can anybody help me on this. Thanks in adv.

    HI
    GOOD
    GO THROUGH THESE LINKS
    http://www.sapdesignguild.org/editions/edition3/gen_iview.asp
    http://www.sapdesignguild.org/editions/edition2/line_m.asp
    http://www.sap.info/public/INT/int/index/Category-12613c61affe7a5bc-int/8/articlesVersions-11651438ad87bac9ad
    THANKS
    MRUTYUN

  • BAPI: IT2006,  IT0014  in Webdynpro leave request scenario

    Hope someone can help me with our new WEBDYNPRO leave request scenario where we want to create via workflow in our back-end R/3 system:
    Infotype 2006 absence quotas.
    Infotype 0014 recurring payments/deductions.
    Does anyone know if there are any standard BAPI's / object type methods available to create the above infotypes?
    If not available hope someone can tell me if it is a real challenge to create such a BAPI from scratch on for a medior ABAP programmer? Myself i am a functional HR consultant with little ABAP skills who likes to know how much ABAP days i need for my client in this last "from scratch on" case.
    Thanks for reading and maybe replying,
    Robbert Bastiaans

    >> if it is a real challenge to create such a BAPI from scratch on for a medior ABAP programmer?
    Not really.. you can use HR_INFOTYPE_OPERATION to create the infotypes.. but this function module is not RFC enabled.. what you will have to do is create a custom RFC & wrap it around the above function module..
    ~Suresh

  • Webdynpro leave request standard workflow

    Dear Expert,
    I am on EP 7 with ECC 6 backend. As for my leave request, i am able to trigger using the workflow (WS12300111) and the approver able to appprove it.
    The problem is when the approver reject the request, it will send back a notification the the requester UWL for resubmition and not matter how many times the requester resubmit the leave. The notification still in the UWL. Anyway to get rid of it.
    My second question is, is there any standard workflow for cancellation leave and change leave request?
    Thanks in advance....
    Regards,
    Bryan

    Dear Richard,
    Thanks for your reply. My situation is as below.
    1) The requester request for a leave and submit the application.
    2) The leave application reach the approver UWL.
    3) The approver REJECT the leave application.
    4) The workflow (WS12300111) went to the resubmission flow
        and trigger TS12300116.
    5) The requester receive an item "Process Leave Request by 
        Employee" in his UWL.
    6) The requester click on the item and it looks similar to the leave application screen. The requester then try to re-submit a new leave from there and send to request. However even after the requester send resubmit the leave, the item still remain in the requester UWL.
    My first question is why the item still remain in the requester UWL even after the requester execute it by re-submit a new leave application. Any way to remove it or it is the workflow error
    Second question is if the requester decide not to resubmit the leave application after being rejected. What is the procedure to remove the item from the requester UWL?
    Thanks,
    Regards,
    Bryan

  • Multiple leave requests on the same day

    We would like to enforce a check so that multiple leave requests of the same type cannot be submitted for the same day on ESS.
    How can this be achieved ? We are on EP 7.0 and ECC 6.0 and are using webdynpro java version of the ESS applications.
    Any configuration available for this or does this require a BADI implementation ?
    Thanks in advance.
    Thank You,
    Raj

    http://wiki.sdn.sap.com/wiki/display/ERPHCM/ValidationsforESSLeaverequest
    read here, it requies a badi implementation only, no config is available!
    You have to call backend exits from the badi of leave request
    Edited by: Siddharth Rajora on Aug 2, 2011 7:48 AM

  • In ESS-Leave Request -A critical error has occured.

    In ESS when tried to enter the Leave which is under Leave request the below error occured:
    Critical Error
    A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.
    Please contact your system administrator.
    CREATE OBJECT: The class  was not found., error key: RFC_ERROR_SYSTEM_FAILURE  
    com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: CREATE OBJECT: The class  was not found., error key: RFC_ERROR_SYSTEM_FAILURE
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
         at com.sap.xss.hr.lea.blockcale.FcBlockCale.getBcData(FcBlockCale.java:232)
         at com.sap.xss.hr.lea.blockcale.wdp.InternalFcBlockCale.getBcData(InternalFcBlockCale.java:250)
         at com.sap.xss.hr.lea.blockcale.FcBlockCaleInterface.getBcData(FcBlockCaleInterface.java:135)
         at com.sap.xss.hr.lea.blockcale.wdp.InternalFcBlockCaleInterface.getBcData(InternalFcBlockCaleInterface.java:224)
         at com.sap.xss.hr.lea.blockcale.wdp.InternalFcBlockCaleInterface$External.getBcData(InternalFcBlockCaleInterface.java:276)
         at com.sap.xss.hr.lea.blockcale.VcBlockCale.onInit(VcBlockCale.java:261)
         at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCale.onInit(InternalVcBlockCale.java:275)
         at com.sap.xss.hr.lea.blockcale.VcBlockCaleInterface.onInit(VcBlockCaleInterface.java:163)
         at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCaleInterface.onInit(InternalVcBlockCaleInterface.java:144)
         at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCaleInterface$External.onInit(InternalVcBlockCaleInterface.java:220)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
         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.doApplicationProcessingPortal(ClientSession.java:733)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
         at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1246)
         at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:354)
         at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:547)
         at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:591)
         at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:822)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:684)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
         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: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: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(AccessController.java:219)
         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.aii.proxy.framework.core.BaseProxyException: CREATE OBJECT: The class  was not found., error key: RFC_ERROR_SYSTEM_FAILURE
         at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
         at com.sap.xss.hr.lea.model.LeaveRequestAdaptiveModel.pt_Arq_Eecale_Get(LeaveRequestAdaptiveModel.java:434)
         at com.sap.xss.hr.lea.model.Pt_Arq_Eecale_Get_Input.doExecute(Pt_Arq_Eecale_Get_Input.java:137)
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
         ... 60 more

    I found out the solution and solved this issue.
    Deleted the leave request which was created with error i.e: from the custom table zxx_vacr noted down the id initiater ( which had error) and in the Test Environment for Leave request (PTARQ) gave the PERNR and deleted the documents ( gave the id iniater in the document status ).
    To check the error work flow go to SWIA and check for that Workflow (Leave) raised by the PERNR at that duration ( check in IT2001 for the duration) and give it here.
    After deleting it check in the portal for the leave request.

  • Error in ESS while Accessing Leave Request

    Dear All,
      We are having the ESS in EP 7.0 and ECC 6.0, We have deployed the ESS components. Everything working fine for one User only,But for other users we are facing problem Leave Request. This is the error we are getting:::
    com.sap.xss.config.FPMConfigurationException: Read of 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 failed.
    *     at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObjectInternal(PcdObjectBroker.java:92)*
    *     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.pcuigp.xssutils.ccxss.CcXss.loadConfiguration(CcXss.java:205)*
    *     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:172)*
    *     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:429)*
    *     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)*
    *     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)*
    *     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)*
    *     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:731)*
    *     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:667)*
    *     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.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)*
    *     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:879)*
    *     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:222)*
    *     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1280)*
    *     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:354)*
    *     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:552)*
    *     at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:596)*
    *     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:827)*
    *     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)*
    *     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)*
    *     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)*
    *     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)*
    *     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.doApplicationProcessing(ClientSession.java:683)*
    *     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.sapportals.portal.pcd.gl.PermissionControlException: Access denied (Object(s): 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)
    *     at com.sapportals.portal.pcd.gl.PcdFilterContext.filterLookup(PcdFilterContext.java:421)*
    *     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1177)*
    *     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1183)*
    *     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1183)*
    *     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1183)*
    *     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1183)*
    *     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1183)*
    *     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1183)*
    *     at com.sapportals.portal.pcd.gl.PcdProxyContext.proxyLookupLink(PcdProxyContext.java:1282)*
    *     at com.sapportals.portal.pcd.gl.PcdProxyContext.proxyLookup(PcdProxyContext.java:1229)*
    *     at com.sapportals.portal.pcd.gl.PcdProxyContext.lookup(PcdProxyContext.java:996)*
    *     at com.sapportals.portal.pcd.gl.PcdGlContext.lookup(PcdGlContext.java:68)*
    *     at com.sapportals.portal.pcd.gl.PcdProxyContext.lookup(PcdProxyContext.java:989)*
    *     at com.sap.xss.config.pcd.PcdObjectBroker.getPcdContext(PcdObjectBroker.java:305)*
    *     at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObjectInternal(PcdObjectBroker.java:53)*
    *     ... 69 more*
    Please let me know what might be the problem, and y its not working for other ESS users.
    Expecting solution and Ideas as soon as possible as its very are in crucial time.
    Thanks
    Ravi.S

    This is a permission issue.
    Please go to Content Admin> Portal C D> ...Provided by SAP> End User C> ESS> you will see the ESS object> Right click on it and select Permission and you will see the roles present on the right hand side.
    Check it and save it.
    Regards
    Prashant

  • 500 internal error while approving leave request

    Hi All,
    One of my user when trying to approve leave request, he is getting the following error. it was working previously but suddenly thsi error has come
    500 internal server error
    Application error occurred during request processing
    Details: com.sap.tc.webdynpro.services.sal.core.Dispatcher exception: The requested deployable object 'sap.com/ess~lea' and application 'leaverequestapprove' are not deployed
    Can anyone advise on this error please!!!
    Thanks!
    Swarnaprakash

    Dear Swarnaprakash,
    Hope you are doing good.
    Do make sure that all ESS related applications/services are running.
    Please try to restart the applications this way:
    1. start the telnet admin tool
       telnet <hostname> 5<instnum>08
    2. logon using the J2EE Admnistrator user
    3. lsc (to list the available servernodes)
    4. jump <servernode> (usually jump 0)
    5. add deploy
    6. start_app -all
    Please have a look at the below for more information:
    [http://wiki.sdn.sap.com/wiki/display/TechTSG/(JSTSG)(Telnet)DeployController+Commands]
    and
    [http://help.sap.com/saphelp_nwpi711/helpdata/en/45/0ad8e787652d6ae10000000a11466f/frameset.htm]
    If the issue still persists, please check if all the SDAs have been deployed for ESS (SCA->SAP ESS and Business packages)
    Thank you and have a nice day :).
    Kind Regards,
    Hemanth

Maybe you are looking for

  • I made some changes to my header, I did not like the results, so I changed them back and now I cannot edit the content of the page.  It is all grayed out..

    I was making some changes to my header file.  I did not like the results of the changes, so I changed them back.  When I did make the change back, I lost the ability to edit the page.

  • Monitor looks red

    monitor looks all red, I tried another monitor before and that one looked yellow, do i have a problem with my videocard? I went to system preferences and tried all; also I tried the PRAM RESET but didn't work? the monitors seems to work fine in a min

  • Mail and Keychain Problem

    I would like to refer to the problem of Mail asking multiple (50 plus) a day for the passwords for POP accounts. The question has been posted a couple of times here and a dozens of times in other forums. Nobody was able to give an answer. If nobody h

  • Satellite A665-S6094 BIOS Instability with 4GB of RAM

    I recently upgraded the RAM in my Sattelite A665-S6094 laptop to 8GB, and I was cheerfully greeted with frequent memory-related bluescreens and an inability to use the sleep function. The laptop works perfectly with the original 2x 2Gb modules instal

  • Automatic update does not work

    On my both computers (Windows 7, Window 8), the automatic update does not work at all, although it is activated in the options. All I get in the Firefox info box is that an update is available, with a link that I have to follow to download the instal