Error in ESS iveiw

Dear All,
I have tried to use the iview provided by SAP for Employee Self Service from portal content area. When i click on all the iview (in ESS), i am getting error as user doesn't exist for this period. can any one help me to resolve this issue?
with Regards,
Balachander

Hi,
Please maintain a user ID in infotype 105 subtype 0001 for an employee.
If u r using user X in EP and u r using Login tickets for authentication, then please use user X in IT 105.
If u r using user mapping, then assign relevant R/3 user ID to the employee.
Cheers!!
Ashutosh

Similar Messages

  • Error in ESS Travel Request iView

    Dear All,
    I am new to HR module of SAP. I have tried to access the ESS iveiw provided by the SAP in the portal. when i access the iveiws (webdynpro/Java) it gives error. can any one tell me how to resolve this error?
    Also when i go through the sap help portal, i read that from ECC 6.0 package 2 they are going to support only ABAP/webdynpro and not JAVA/webdynpro (ESS). Is it correct?
    when i try to query the flight availability through standard SAP travel managment, my system gives error as "Connection error with external reservation system". what could be the cause for this error? can any one help to get rid of this error?
    with Regards,
    Balachander

    Hello Balachander,
    1. if you could give us more infos about the error you receive, we might could help ypu
    2. With Enhancemnet Package 2 (Ramp-Up until Dezember 2007?) the entire ESS Travelmanagement Services are available as Web Dynpro ABAP as well, although the Web Dynpro Java versions ars still there and can be used. You have to manually switch from Java to ABAP. As SAP has only enhanced the WD ABAP version, i would recommand to use those.
    3. If you want to use the Travel Planning functionality you have to connect your SAP-System to a booking system like Amadeus, Galileo etc. This will generate additional costs tho. Check this link for more infos https://websmp210.sap-ag.de/tm-downloads
    regards,
    Markus

  • Error in ESS iview

    Dear All,
    I am new to HR module of SAP. I have tried to access the ESS iveiw provided by the SAP in the portal. when i access the iveiws (webdynpro/Java) it gives error. can any one tell me how to resolve this error?
    with Regards,
    Balachander

    Hi,
    If you would tell which version of ESS you're running and what sort of error you get it would be easier to help. Also you might want to post your issue to ESS dedicated forum:
    SAP ERP HCM Employee Self-Service
    Kind regards,
    Ville

  • Global employees (MGE) error in ESS

    Hi all,
    I am in the process of activating management of global employees in ESS. The leave screens & leave balances work fine for employees with 2 PERNR i.e. i get the pop-up box in ESS.
    The problem i have is with the address and bank screens. I get the following error in ESS: Global Employee scenario: Please refer to the IMG Employee Self-Service -> General Settings -> Concurrent/Global Employee  
    I have activated the address and bank services in IMG node "Assign CE/GE Group Definition Settings to ESS Applications" but its not working like Leave request did.

    Actual message in ESS:
    Critical error.
    Global Employee scenario: Please refer to the IMG Employee Self-Service -> General Settings -> Concurrent/Global Employee:
    com.sap.pcuigp.xssfpm.java.FPMRuntimeException
    at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:112)
         at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:122)
         at com.sap.pcuigp.xssutils.pernr.EmployeeGroupInfo.init(EmployeeGroupInfo.java:140)
         at com.sap.pcuigp.xssutils.pernr.wdp.InternalEmployeeGroupInfo.init(InternalEmployeeGroupInfo.java:183)
         at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.initPernr(FcEmployeeServices.java:270)
         at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.onInit(FcEmployeeServices.java:226)
         at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServices.onInit(InternalFcEmployeeServices.java:273)
         at com.sap.pcuigp.xssutils.pernr.FcEmployeeServicesInterface.onInit(FcEmployeeServicesInterface.java:135)
    The switch HCM_ESS_CE is active, and parts of MGE seem to be working because i can do leave requests for Global employees and i get the assignment pop-up box in ESS for this. I have activated the EMPLOYEE_ADDRESS_nn_SERVICE applications in IMG node "Assign CE/GE Group Definition Settings to ESS Applications"
    I'm wondering if anyone has got address screen working for Global employees?

  • Error in ESS page

    Hi Experts,
    Iam having problem with my ESS page while iam clicking on it its showing error like this please help me in this.
    Overview           
    500   Internal Server Error
    SAP NetWeaver Application Server 7.00/Java AS 7.00
    Failed to process request. Please contact your system administrator.
    [Hide]
    Overview           
    500   Internal Server Error
    SAP NetWeaver Application Server 7.00/Java AS 7.00
    Failed to process request. Please contact your system administrator.
    [Hide]
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: ComponentUsage(FPMConfigurationUsage): Active component must exist when getting interface controller. (Hint: Have you forgotten to create it with createComponent()? Should the lifecycle control of the component usage be "createOnDemand"?
        at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.ensureActiveComponent(ComponentUsage.java:773)
        at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceControllerInternal(ComponentUsage.java:348)
        at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceController(ComponentUsage.java:335)
        at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetFPMConfigurationUsageInterface(InternalFPMComponent.java:245)
        at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.changeToExceptionPerspective(FPMComponent.java:861)
        ... 58 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type     HTML Client
    User agent     Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; InfoPath.1; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30)
    Version     null
    DOM version     null
    Client Type     msie6
    Client Type Profile     ie6
    ActiveX     enabled
    Cookies     enabled
    Frames     enabled
    Java Applets     enabled
    JavaScript     enabled
    Tables     enabled
    VB Script     enabled
    Server
    Web Dynpro Runtime     Vendor: SAP, build ID: 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:13:14[UTC], changelist=455669, host=pwdfm101), build date: Thu May 29 11:29:48 IST 2008
    J2EE Engine     7.00 patchlevel 109044.44
    Java VM     Java HotSpot(TM) 64-Bit Server VM, version:1.4.2 1.4.2.13-070317-20:54-IA64W IA64W, vendor: Hewlett-Packard Company
    Operating system     HP-UX, version: B.11.31, architecture: IA64W
    Session & Other
    Session Locale     en
    Time of Failure     Fri Aug 29 11:57:24 IST 2008 (Java Time: 1219991244104)
    Web Dynpro Code Generation Infos
    sap.com/pb
    SapDictionaryGenerationCore     7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:42[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates     7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:50[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore     7.0013.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:44:42[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer     7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:26[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon     7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:30[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore     7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:23[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary     7.0013.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:54:53[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro     7.0013.20070703112649.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:00:50[UTC], changelist=454024, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates     7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)
    SapWebDynproGenerationCore     7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:37[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates     7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)
    sap.com/tcwddispwda
    No information available     null
    sap.com/pb_api
    SapDictionaryGenerationCore     7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:42[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates     7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:50[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore     7.0013.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:44:42[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer     7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:26[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon     7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:30[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore     7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:23[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary     7.0013.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:54:53[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro     7.0013.20070703112649.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:00:50[UTC], changelist=454024, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates     7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)
    SapWebDynproGenerationCore     7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:37[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates     7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)
    sap.com/tcwdcorecomp
    No information available     null
    Detailed Error Information
    Detailed Exception Chain
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: ComponentUsage(FPMConfigurationUsage): Active component must exist when getting interface controller. (Hint: Have you forgotten to create it with createComponent()? Should the lifecycle control of the component usage be "createOnDemand"?
         at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.ensureActiveComponent(ComponentUsage.java:773)
         at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceControllerInternal(ComponentUsage.java:348)
         at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceController(ComponentUsage.java:335)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetFPMConfigurationUsageInterface(InternalFPMComponent.java:245)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.changeToExceptionPerspective(FPMComponent.java:861)
         at com.sap.pcuigp.xssfpm.java.MessageManager.handleException(MessageManager.java:258)
         at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:103)
         at com.sap.pcuigp.xssfpm.wd.BackendConnections.connectModelInternal(BackendConnections.java:323)
         at com.sap.pcuigp.xssfpm.wd.BackendConnections.initBackend(BackendConnections.java:256)
         at com.sap.pcuigp.xssfpm.wd.BackendConnections.connectModel(BackendConnections.java:154)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalBackendConnections.connectModel(InternalBackendConnections.java:237)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.connectModel(FPMComponent.java:841)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.connectModel(FPMComponent.java:1071)
         at com.sap.pcuigp.xssfpm.wd.BackendConnections.init(BackendConnections.java:141)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalBackendConnections.init(InternalBackendConnections.java:233)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:182)
         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:748)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:283)
         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:149)
         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:313)
         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:149)
         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(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)
                                                                                    Failed to process request. Please contact your system administrator.
    Regards,
    Shilpa.
    Edited by: pasumarthi shilpa on Sep 1, 2008 6:40 AM

    hi Shilpa,
    Please go to transaction SWFVISU and check whether the package name and all is correct or not
    coz u'll see thr sometime package is diff.
    and most of time u need change package name according to ur pkg.
    And
    check whether system object and aliases are properly mapped to the user.
    Expecting your co-operation,If suggession becomes solution or useful to find the solution.
    Thanks
    mahendra

  • Portal Runtime Error in ESS iview

    Hi All,
    I have implemented ESS 50.4 on EP 6.0 SP9. For SAP IAC iviws i am getting following error.
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : pcd:portal_content/AFDB/Role/ESSRole/Office/SAPInbox/SAPInbox
    Component Name : com.sap.portal.appintegrator.sap.IAC
    Error in executing a process for compilation.
    Exception id: 03:10_06/05/06_0031_4156850
    See the details for the exception ID in the log file.
    In the log file i am getting following error message.
    com.sap.engine.services.connector.exceptions.BaseResourceException: "ConnectionManager" is closed. Possible reasons: 1) connector "SAPEPPDB" is stopped or not started, 2) Connector service is stopped or has not been started.
    Please help me to resolve the problem its very urgent.
    Regards,
    Vaishali

    Hi Vaishali,
    Nice to hear from you again.
    Hope you are doing good.
    I am not sure whether the error that you mentioned is the right one for this issue, but if this is the case, just to inform you that a new note has been released in this regard. Please check sap note: 1600085 as well and set the parameters accordingly.
    Usually we need to see what kind of code is using the concerned connection.
    Incase the issue persists, proceed as follows (it wil be better to do this when the value of the number of connections is really high, so that identifying the root cause can be easy.
    1)
    Set the severity of "com.sap.engine.services.connector.jca.ConnectionHashSet" to DEBUG.
    You can change the severity of a location using the guide in the link below:
    http://help.sap.com/saphelp_nwce72/helpdata/en/47/af551efa711503e10000000a42189c/frameset.htm
    2)
    - connect to the AS-JAVA via telnet
    - then execute these commands:
    > add connector
    > switch_debug_mode SAPEPPDB (or the datasource name)
    > jump (to go to the next servernode if you have multiple ones)
    > add connector
    > switch_debug_mode SAPEPPDB
    ... and so on on all the servernodes
    - then wait for a few hours in order to see the connections not being
      released
    - go back to the telnet console and call:
    > list_conn SAPEPPDB -showTrace > server0.txt
    > jump
    > list_conn SAPEPPDB -showTrace > server1.txt
    ... and so on on all the servernodes
    The serverX.txt files will be generated in the ../j2ee/cluster/server directories. Just check them to get more info.
    Thank you!
    Kind Regards,
    Hemanth
    SAP AGS

  • 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

  • Error in ess leave request

    Hi Experts,
    Please find the below error and guide me in this, as the employee has applied leave request and it is approved and posted in 2001 but  the employees has an Option in ess to change his approved leave also but when he is trying to change the leave getting the error
    The leave must not start before 22.04.2009
    please help me in this.
    waiting for your response..
    Regards,
    Shilpa

    Hi,
    GO to SPRO .
    IMG Path:
    Personnel Management  Personnel Administration  Personnel Data  Employee self service  Service Specific settings  Working Times  Leave Request  Processing Process  specify processing process of leaves types
    Select one leave
    in that "Start Date in the Past"
    select 1st RADIO button "Processing Permitted to the recalculation Limit"
    Save ...and check

  • Form 16 error in ESS

    Hi Portal Experts ,
    While trying to view the Form 16 link in Benefits and pay section we are getting the below error . W ehave integrated ESS /MSS 1.41 with EP and in backend able to preview the form 16 .   System connection is working fine and jco also fine.
    error :
    Critical Error
    A critical error has occured. Processing of the service was terminated. Unsaved data has been lost.
    Contact your system administrator.
         Screen output without connection to user.                           , error key: RFC_ERROR_SYSTEM_FAILURE
    com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException:      Screen output without connection to user.                           , error key: RFC_ERROR_SYSTEM_FAILURE
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
         at com.sap.xss.hr.rep.fcrfw.FcRepFramework.callRfcExecAction(FcRepFramework.java:373)
         at com.sap.xss.hr.rep.fcrfw.FcRepFramework.initModel(FcRepFramework.java:292)
         at com.sap.xss.hr.rep.fcrfw.wdp.InternalFcRepFramework.initModel(InternalFcRepFramework.java:256)
         at com.sap.xss.hr.rep.fcrfw.FcRepFrameworkInterface.initModel(FcRepFrameworkInterface.java:136)
         at com.sap.xss.hr.rep.fcrfw.wdp.InternalFcRepFrameworkInterface.initModel(InternalFcRepFrameworkInterface.java:198)
         at com.sap.xss.hr.rep.fcrfw.wdp.InternalFcRepFrameworkInterface$External.initModel(InternalFcRepFrameworkInterface.java:258)
         at com.sap.xss.hr.in.f16.vc.vcf16selection.VcF16Selection.onInit(VcF16Selection.java:237)
         at com.sap.xss.hr.in.f16.vc.vcf16selection.wdp.InternalVcF16Selection.onInit(InternalVcF16Selection.java:235)
         at com.sap.xss.hr.in.f16.vc.vcf16selection.VcF16SelectionInterface.onInit(VcF16SelectionInterface.java:161)
         at com.sap.xss.hr.in.f16.vc.vcf16selection.wdp.InternalVcF16SelectionInterface.onInit(InternalVcF16SelectionInterface.java:144)
         at com.sap.xss.hr.in.f16.vc.vcf16selection.wdp.InternalVcF16SelectionInterface$External.onInit(InternalVcF16SelectionInterface.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:783)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         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:864)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1362)
         at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:355)
         at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
         at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:192)
         at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
         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:783)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
         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.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:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
         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:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Caused by: com.sap.aii.proxy.framework.core.BaseProxyException:      Screen output without connection to user.                           , error key: RFC_ERROR_SYSTEM_FAILURE
         at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
         at com.sap.xss.hr.rep.model.rfwmodel.RfwModel.hrxss_Ser_Rfw_Rfc_Exec_Action(RfwModel.java:184)
         at com.sap.xss.hr.rep.model.rfwmodel.Hrxss_Ser_Rfw_Rfc_Exec_Action_Input.doExecute(Hrxss_Ser_Rfw_Rfc_Exec_Action_Input.java:137)
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
         ... 63 more
    Could you please help  !!!
    regards,
    Sai

    Hi,
    You need to maintain entry in table T7XSS_SER_RFW for XSS_HR_IN_F16.
    You should maintain entry as follows:
    Applid                      classname
    XSS_HR_IN_F16      CL_HRXSS_IN_F16
    This table value is delivered in standard delivery. Because the delivery class is E "Control table, SAP and customer have separate key areas" Kindly compare in your client 000.
    You need to maintain this entry because all applications based on the Generic Reporting Tool (GRT) require a unique application ID. Every application has a class that implements the IF_HRXSS_SER_RFW interface
    and controls the back-end logic.
    To maintain the entry you can proceed through IMG as follows-> SPRO-> Personnel Management-> Employee Self Service-> General Settings-> Generic Reporting tool(GRT)-> Assign Application ID to application class->
    I hope this information will help in resolving the issue.
    Assaf Klieger

  • Portal Runtime Error  in ESS MSS Pages

    Hi All,
    We are getting following run time error from standard ESS transaction page. It is standard ESS iView and data showing correctly but this message is giving in the bottom of the page content area. We are using EP SP12 with 4.6c backend R/3 system.
    Any help or suggestions will be greatly appreciated.
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView
    Cannot assign a java.lang.String object of length 1,342 to host variable 1 which has JDBC type VARCHAR(1,333)..
    Exception id: 10:59_21/08/05_0008_1396450
    See the details for the exception ID in the log file
    Thanks,
    Laxma

    Hi Laxma,
    Change the objectids to something short.
    For now create a new folder structure with Object IDs shorter and move the content in the old folders to the new folders. For each object the name space is too long and is causing the path to exceed the defined limit.
    Regards
    -Venkat Malempati

  • Web Dynpro error in ESS

    Hi experts,
    We are implementing ESS/MSS. There is a problem viewing WebDynpro ABAP program through the DEV Portal. The error is:
    Error when processing your request
    What has happened?
    The URL http://sapbwdev.felhqr.myfelda:8000/sap/bc/webdynpro/SAP/Z_WD_medical_clms// was not called due to an error.
    Note
    The following error text was processed in the system BWD : Password logon no longer possible - too many failed attempts
    The error occurred on the application server sapbwdev_BWD_00 and in the work process 0 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Method: VS_GET_PERNR of program /1BCWDY/1P1UHOV81T1UP0OHPRPS==CP
    Method: VS_GET_PERNR of program /1BCWDY/1P1UHOV81T1UP0OHPRPS==CP
    Method: SUPPLY_ELEMENTS of program CL_WDR_CONTEXT_NODE_VAL=======CP
    Method: IF_WD_CONTEXT_NODE~GET_ELEMENT of program CL_WDR_CONTEXT_NODE_VAL=======CP
    Method: FILL_CLAIMSTYPE of program /1BCWDY/1P1UHOV81T1UP0OHPRPS==CP
    Method: IF_MAIN~FILL_CLAIMSTYPE of program /1BCWDY/1P1UHOV81T1UP0OHPRPS==CP
    Method: WDDOINIT of program /1BCWDY/1P1UHOV81T1UP0OHPRPS==CP
    Method: IF_WDR_VIEW_DELEGATE~WD_DO_INIT of program /1BCWDY/1P1UHOV81T1UP0OHPRPS==CP
    Method: DO_INIT of program CL_WDR_DELEGATING_VIEW========CP
    Method: INIT_CONTROLLER of program CL_WDR_CONTROLLER=============CP
    What can I do?
    If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system BWD in transaction ST22.
    If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server sapbwdev_BWD_00 in transaction SM21.
    If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server sapbwdev_BWD_00 . In some situations, you may also need to analyze the trace files of other work processes.
    If you do not yet have a user ID, contact your system administrator.
    Error code: ICF-IE-http -c: 210 -u: 3600004 -l: E -s: BWD -i: sapbwdev_BWD_00 -w: 0 -d: 20090521 -t: 154452 -v: RABAX_STATE -e: CALL_FUNCTION_REMOTE_ERROR
    HTTP 500 - Internal Server Error
    Your SAP Internet Communication Framework Team
    We have check that the password in not lock. can anybody give me some advice on what to do.
    Thanks,
    Nanie Arianie

    Hi Nanie,
    Have you had a look at the trace using ST22 Tcode.
    Good Luck!
    Sandeep Tudumu

  • ERROR IN ESS AND MSS pages when deleting the superadmin role

    hi all
    According to my clent requirement i have worked with uwl for leave request.....for that i configured uwl and added uwl iview to the standard user role......after i have assigned standard user role to my manager.
    but' after some time they told me that they need attendance overview and Reminder of dates and subordinate information.
    After backend configuration i have assigned Mss role to the Manager,
    i have made the settings for mss role with overview workset
    Again overview contain-workoverview page it contains  1) uwl pabge  2)Attendance Overview   3)reminder of dates
                                            Team-  General information and so on
    now my manager has following roles 1)ESS   2)MSS 3)Home (from the standard user role)   4) Home( by default i think from MSS role)     5) superadmin role
    when ever i am removing the super admin role and standard user role for the manager   i am unable to see the Attendance overview page and Reminder of dates page and i am unable to see the pages in ESS also.
    getting error
    Critical Error
    A critical error has occured. Processing of the service was terminated. Unsaved data has been lost.
    Contact your system administrator.
    Read of object with ID portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.mss/com.sap.pct.erp.srvconfig.rod/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.reminderofdates failed.
    plz ask me if any information is needed for this to solve my problem.
    thankyou in advance.
    if i am keeping that superadmin role(content ,user and system administration) All pages are opening.
    thankyou

    Swapna,
    Pls refer below links,
    Unable to view notofications in MSS
    Re: Critical Error when running MSS Work Overview Page
    Manager Self Service Content are not showing up
    Hope it should work now...
    To give points, select the radio buttons on the left side under the name of the replier.
    Regards,
    Amarnath S

  • Error in ESS App Change Own Data

    Hello!!!
    I am in process of implementing ESS for a middle eat client. For some reason unknown to me the application "Change Own Data" isn't working. When I click on the link to "Change Own Data" it throws the following error:
    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.
      The ASSERT condition was violated., error key: RFC_ERROR_SYSTEM_FAILURE   
      The ASSERT condition was violated., error key: RFC_ERROR_SYSTEM_FAILURE:com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: The ASSERT condition was violated., error key: RFC_ERROR_SYSTEM_FAILURE
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
         at com.sap.xss.hr.cod.FcCodBusinessLogicComp.callRFCReadDetails(FcCodBusinessLogicComp.java:602)
         at com.sap.xss.hr.cod.FcCodBusinessLogicComp.readEmployeeData(FcCodBusinessLogicComp.java:348)
         at com.sap.xss.hr.cod.wdp.InternalFcCodBusinessLogicComp.readEmployeeData(InternalFcCodBusinessLogicComp.java:544)
         at com.sap.xss.hr.cod.FcCodBusinessLogicCompInterface.readEmployeeData(FcCodBusinessLogicCompInterface.java:196)
         at com.sap.xss.hr.cod.wdp.InternalFcCodBusinessLogicCompInterface.readEmployeeData(InternalFcCodBusinessLogicCompInterface.java:179)
         at com.sap.xss.hr.cod.wdp.InternalFcCodBusinessLogicCompInterface$External.readEmployeeData(InternalFcCodBusinessLogicCompInterface.java:259)
         at com.sap.xss.hr.cod.start.VcCodStartComp.onInit(VcCodStartComp.java:198)
         at com.sap.xss.hr.cod.start.wdp.InternalVcCodStartComp.onInit(InternalVcCodStartComp.java:156)
         at com.sap.xss.hr.cod.start.VcCodStartCompInterface.onInit(VcCodStartCompInterface.java:161)
         at com.sap.xss.hr.cod.start.wdp.InternalVcCodStartCompInterface.onInit(InternalVcCodStartCompInterface.java:144)
         at com.sap.xss.hr.cod.start.wdp.InternalVcCodStartCompInterface$External.onInit(InternalVcCodStartCompInterface.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.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)
    Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: The ASSERT condition was violated., error key: RFC_ERROR_SYSTEM_FAILURE
         at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
         at com.sap.xss.hr.cod.model.CodModel.hrxss_Cod_Read(CodModel.java:388)
         at com.sap.xss.hr.cod.model.Hrxss_Cod_Read_Input.doExecute(Hrxss_Cod_Read_Input.java:137)
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
         ... 44 more
      Any assistance will be appreciated.
    Thanks,
    GLM

    Normally this problem occures if there is wrong customizing in the
    tables V_T7XSSPERSUBTYP and V_T591A. Please check this for your used
    infotyp according to the explaination below:
    for
    usecase = A1, A4, B1, B4                     (table V_T7XSSPERSUBTYP)
    you need to have
    zeitb = '1' OR zeitb = '2'                   (table V_T591A)
    for
    usecase = A2, A3, A5, B2, B3, B5
    you need to have
    zeitb = '2'
    for
    usecase = A6, B3
    you need to have
    zeitb = '3'
    Please note that there is a hardcoded setting which is taken if there
    is no entry in table V_T7XSSPERSUBTYP - so if you change the delivered
    customizing in V_T591A it migh be neccessary to create an entry in
    V_T7XSSPERSUBTYP.
    If setting your tables according to this solves your problem kindly
    close this message.

  • Java.lang.NullPointerException  error in ESS Leave Request

    Hi,
       I had configured ESS and i'am trying to apply Leave through Leave Request iview which is available through ESS,i had enterd data into the fields and i had defined Approver in back end system,Now when i click on review button it is throwing me this error
    "The initial exception that caused the request to fail, was:
       java.lang.NullPointerException
        at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.setRelatedModelObject(DelegatorRepositoryModelClass.java:668)
        at com.sap.tc.webdynpro.progmodel.repository.IWDViewUsageInfo$Implementation.setComponentUsageInternal(IWDViewUsageInfo.java:413)
        at com.sap.tc.webdynpro.progmodel.repository.IWDViewUsageInfo$Implementation.setComponentUsage(IWDViewUsageInfo.java:698)
        at com.sap.pcuigp.xssfpm.wd.FPMComponent.buildNextViewAssembly(FPMComponent.java:300)
        at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.buildNextViewAssembly(InternalFPMComponent.java:153)
    java.lang.NullPointerException
    *     at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.setRelatedModelObject(DelegatorRepositoryModelClass.java:668)*
    *     at com.sap.tc.webdynpro.progmodel.repository.IWDViewUsageInfo$Implementation.setComponentUsageInternal(IWDViewUsageInfo.java:413)*
    *     at com.sap.tc.webdynpro.progmodel.repository.IWDViewUsageInfo$Implementation.setComponentUsage(IWDViewUsageInfo.java:698)*
    *     at com.sap.pcuigp.xssfpm.wd.FPMComponent.buildNextViewAssembly(FPMComponent.java:300)*
    *     at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.buildNextViewAssembly(InternalFPMComponent.java:153)*
    *     at com.sap.pcuigp.xssfpm.wd.AssemblyModificationView.onPlugIn(AssemblyModificationView.java:128)*
    *     at com.sap.pcuigp.xssfpm.wd.wdp.InternalAssemblyModificationView.wdInvokeEventHandler(InternalAssemblyModificationView.java:130)*
    *     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)*
    *     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:826)*
    *     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)*
    *     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)*
    *     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)*
    *     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java: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.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.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)*
    *     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1291)*
    *     at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:325)*
    *     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:831)*
    *     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.doApplicationProcessingStandalone(ClientSession.java:711)*
    *     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)*
    *     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)*
    *     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)*
    *     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)*
    *     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)*
    *     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)*
    *     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)*
    *     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java: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)*"
    Please guide me in this issue .
    With Regards
    Praveen

    http://help.sap.com/saphelp_erp2005vp/helpdata/en/f6/263359f8c14ef98384ae7a2becd156/frameset.htm
    complete the configuration from the link.
    Check out the prerequisites section ... you will find the node that u need to configure.
    Cheers!!
    Ashutosh

  • ERROR In ESS WebDynpro with ERP2004  IDES System

    Hi,
    I have installed ERP2004 ECC 5.0 IDES version now i want to use ESS Application on Portal
    i Deployed the JAVA Components for ESS on the WAS 6.40 J2EE Server the componets are succesfully deployed.
    i also cofigure the SLD and JCO destination for ESS which is according to SAP Help.
    now my problem was when i test any of the ESS Webdynpro application using
    http://<host>:<Port>/webdynpro/welcome
    and login into webdynpro content administrator and expanding sap.com
    while running any of the ESS application from deployed content it's gives following common error for all application, no application is works
    error:---
    An error has occurred:
    "Failed to process the request."
    Please contact your system administrator.
    Web Dynpro runtime:
    Vendor: SAP, Build ID: 6.4009.00.0000.20041104173322.0000 (release=630_REL, buildtime=2004-11-18:22:17:10[UTC], changelist=298578, host=PWDFM027)
    Web Dynpro code generators of DC sap.com/essaraddr:
    SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:41[UTC], changelist=280522, <b>host=PWDFM026.wdf.sap.corp</b>)
    SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:28:58[UTC], changelist=280539, <b>host=PWDFM026.wdf.sap.corp</b>)
    SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:03[UTC],
    Error stacktrace:
    com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type com.sap.pcuigp.xssfpm.wd.model.types.Ext_Service could not be loaded: com.sap.dictionary.runtime.DdException:
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:205)
         at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.init(AttributeInfo.java:471)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:771)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:756)
    Caused by: com.sap.dictionary.runtime.DdException:
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:89)
         at com.sap.dictionary.runtime.ProviderFactory.internalResolveLogicalNameToJCODestination(ProviderFactory.java:408)
         at com.sap.dictionary.runtime.ProviderFactory.resolveLogicalNameToJCODestination(ProviderFactory.java:354)
         at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider
    look at the webdynpro application host type it's shows
    PWDFM026.wdf.sap.corp
    i think this host  are taken from R3 Side since the ERP2004 is IDES version, but my host was different
    if there is problem with host how can i changed this host setting
    if enything else i mising than plese help me to solve this
    regards,
    kaushal

    Hi,
    Go to technical landscapes and create a technical landscape for your ECC backend system.
    This should solve the problem.
    Regards
    Bharathwaj.

Maybe you are looking for