Leave Encashment in ESS MSS NWBC

Hi all gurus,
We have implemented Leave request, Travel request, PMS via ESS using standard SAP role SAP_EMPLOYEE_ESS_WDA_3.
Now we got a requirement to do Leave Encashment in ESS MSS through NWBC.
How can I do that.? Is there any standard roles by which I can get Leave Encashment Application in ESS ??
Give me some light to this.
Regards,
Namsheed.

Hi Shankar,
Thanks for the info.
That means it can't be done in NWBC.?
What is the alternative solution for this.?
I am in a bottle neck. Not in India now.
I am in Bhutan for this implementation. In spro also I saw Leave Encashment under India only.
What is the possible solution for this.?
Thanks a lot Shankar for prompt reply.
Namsheed.

Similar Messages

  • Configuration steps for leave request in ESS/MSS

    Hi
    I want to configure for leave request approval from ESS/MSS (EP 7.0 and ECC 6.0)
    What are the configuration steps if any doc please send.
    Thanks & Regards

    Hi Rao,
    Go through this link for leave request cofiguration steps.
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/erphcm/leave%2brequest%2bconfiguration%2bsteps
    Also visit this link for ESS related issue resolution and hints.
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/erphcm/commonIssuesandHintsin+ESS
    Reagrds,

  • Multi Level Leave workflow in ESS MSS

    Hi Guys,
    This is the first time I am working with ESS MSS and I have to implement 2 level workflow for leave, I have gone through lot of threads and concluded that i have to enhance class CL_PT_REQ_WF_ATTRIBS
    with new method where I have to change the status back to SENT after first level of approval and create new background task and attach it to custom workflow which is copy of standard.
    Now my problem is I have enhanced the class CL_PT_REQ_WF_ATTRIBS with new method change status but when I am creating the task I canu2019t see that method in drop down list of methods.
    Any idea why it not showing.
    We are on ECC6. EH4
    Atul
    Edited by: Atul Dhariwal on Mar 8, 2011 4:56 AM

    Hi Atul
      You are doing wrong way. You need to use BADI to enhance that for that goto SE18 search with PT_GEN* and get the BADI name and goto se19 and create a implementation for that there you in the desiered method you can code. But remember you cannot add you own need method the BADI. What ever SAP is providing that one only you can use to add additional code not addding new method.
    Regards
    Vijay

  • Error in ESS/MSS application accessing in Portal : URGENT

    Hi Experts ,
    I am getting the following error , when logged in to the portal using one user and click on the Leave request in ESS/MSS.
    Can any body let me know how to resolve this error.
    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: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)
    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:422)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1248)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.proxyLookupLink(PcdProxyContext.java:1353)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.proxyLookup(PcdProxyContext.java:1300)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.lookup(PcdProxyContext.java:1067)
         at com.sapportals.portal.pcd.gl.PcdGlContext.lookup(PcdGlContext.java:68)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.lookup(PcdProxyContext.java:1060)
         at com.sap.xss.config.pcd.PcdObjectBroker.getPcdContext(PcdObjectBroker.java:305)
         at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObjectInternal(PcdObjectBroker.java:53)
         ... 69 more

    Hi ,
    Check the below thread and try options wihtin that.
    all the best as the below thread is not resolved.
    Manager Self Service Content are not showing up
    Koti Reddy

  • TIME on ESS/MSS with the SAP Portal, release ERP2005 ECC6.

    Hello,
    I need to implement TIME (Leave request) on ESS/MSS with the SAP Portal, release ERP2005 ECC6.
    Any informations about the customizing for a proof of concept would be appreciated.
    All the back-end (R/3) as allready been customized.
    Thanks for your responses.
    Olivier

    Hello,
    If you already have all the templates and such configured then its easy. We don't have ESS and only one MSS scenario. However we support the web environment via BSP HAP_DOCUMENT. You can include our list pages in an Iview and assign that to the ESS or MSS scenario in the portal.
    They also run stand alone, so you can test it as well without configuring the portal.
    See also <a href="/people/sap.user72/blog/2007/02/20/objective-setting-appraisals-the-web-environment bloggy</a> on OSA and the web Environment, especially the last part will be of interest for you.
    Regards and Groetjes,
    Maurice

  • ESS/MSS: Approve Leave Request in UWL - not working

    Hi to all,
    we are using web dynpro ESS/ MSS (SAPESS07_12/ SAPMSS07_4) in portal NW04s for mySAP ERP2005 and are using UWL in order to approve leave requests. If employees are creating leave requests, everything works fine. After that the manager opens the leave request in UWL, the web dynpro application is openening succesfully and after some clicks he reaches the buttons to approve or reject the leave request. But by pushing one of them the following messages occures :
    <b>Workitem 000000000000 Cannot be read</b>
    After pushing the button again, another message comes up:
    <b>No Customizing for status typ ARQ, Status approved...</b>
    By the way, the same errors also come up when the employee wants to delete his leave request which is not approved.
    Any ideas, what can be the reason?
    Regards,
    Frank

    Hi Ashutosh,
    I have found the reason. The user <b>WF - Batch</b> in sap erp, which is using the RFC Destination for workflow, was locked. Well, it is a a little bit strange for a cummunication user that he becomes locked. Unlocked him, now all works.
    Thanks for your support.
    Regards,
    Frank

  • ESS/MSS leave approve view is diaplaying as error

    Hi All,
    We are using ESS/MSS for leave request and approval process.
    We did neccessary configuration for the same. I have created leave request in ESS successfully and the same request displayed as item in UWL/Task. When try to approve, by clicking the link, it throws an error.
    The error details are : 503 Service not available
    Error: -6
    Version: 7000
    Component: J2EE Server
    Date/Time: Mon Jan 16 14:31:49 2012
    Module: http_j2ee_mt.c
    Line: 820
    Server: eppilot_KHE_11
    Error Tag:
    Detail: Cannot reach external Application Server on eppilot:51111
    When i try to preview the Iview 'leave reuqest approval' as a stand alone(from Content administration), its shows the approval view perfectly . even i tried to approve from their , its approving perfectly. But the Leave request approval view is not displaying when manager click the link to approve in UWL/Task.
    Kindly help.
    Thanks,
    Venkat

    Hi Andy,
    Thanks for your reply.
    As per the SAP Note 779075,
    I have changed in SWFVISU same as below. 
    TS12300097 WebDynpro Java
                    APPLICATION LeaveRequestApprover
                    DYNPARAM    wi_id=${item.externalId}
                    PACKAGE     sap.com/ess~lea
    TS12300116 WebDynpro Java
                    APPLICATION LeaveRequest
                    DYNPARAM    wi_id=${item.externalId}
                    PACKAGE     sap.com/ess~lea
    The application "LeaveRequestAdmin" is not released. Use transaction SWFVISU to delete the following entry:
    TS12300104 WebDynpro Java
                    APPLICATION LeaveRequestAdmin
                    PACKAGE     sap.com/ess~lea
    1.After that , in Universal Worklist configuration, I have selected the row..system alias 'SAP_WedDYnpro_XSS' Connector type 'Web flow connector, clicked the re-register button.  I got the folowing message :
    Item type registration was successful for the following systems:
    - SAP_WebDynpro_XSS (WebFlowConnector
    2. After that i have cleared the cache.
    But still i am getting the same error message, when i click the leave request item. Kindly help.
    Thanks in advance.

  • ESS/MSS Leave Request Issue

    Hello All Experts
    We have implemented ESS/MSS. Everything is working fine except the Leave Request approval. The approval request comes to the approver's inbox.When we try to open the approval request, the webdynpro application is getting but there is no data in the same. I mean the webdynpro application which is launched is blank.
    Could anyone please try to help me how to make this webdynpro application up and running ?
    We are using EP 7.0 with ECC 5.0
    TIA,
    Vivek

    Hi Chuckie/Ton Groot,
    As mentioned in post by Ton Groot,
    I navigated to System Administration --> System Configuration --> Detailed Navigation --> Universal Worklist Workflow’ à ‘Universal Worklist - Administration’
    I get a list of
    Universal Worklist Systems
    System Alias       Connector Type                       Action            Activate 
    AdHocSystem |   AdHocWorkflowConnector  |                        | Deactivate 
    SAP_ITS_XSS |   WebFlowConnector           |   Re-Register    | Deactivate 
    ActionInbox     |   ActionInboxConnector        |                        | Deactivate
    When I click on Re-Register button under Action, I get the following message
    Item type registration was successful for the following systems:
    - SAP_ITS_XSS (WebFlowConnector)
    I have also cleared the cache by navigating to Cache Administration Page
    Still the issue remains.
    TIA,
    Vivek

  • ESS/MSS Leave Request

    I am working ESS/MSS, we are deployed all the Business packages in the portal and once we open Leave request application
    "There are no Customizing settings for absence type"
         The above Error displayed,is there any configuration is required for R/3. if yes, can any one please help me
    Regards,

    Hi,
    Have you configured the basic settings in TM like Absences, Attendances, AQ types. To achieve the absence types in ESS, you need to configure the absence types in R/3.
    Good Luck
    Om
    Reward it, if u feel helpful.

  • How to Configure NWBC, ESS MSS

    Dear Consultants,
    Can anyone tell how to install ESS MSS servers in the present SAP Server, We want to use NWBC to use.
    Naresh.KM

    Hi Naresh,
    With the limited information you provided, suggestion would be to check below documents to begin your ESS/MSS setup
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/108c31e7-b6a7-2d10-3692-c1a9f7a5c4dc?overridelayout=t…
    How to Configure ESS and MSS in Portal..
    Hope this helps.,
    Regards,
    Deepak Kori

  • ESS/MSS leave reques Enhancement

    Hi,
    I am trying to do some enhancement to ESS/MSS Development Component in the NWDS, but it is not getting reflected. can someone help me out to resolve this issue..??
    Thanks
    Angshuman

    Hi Praveen,
    Extended notifications for SAP Business Workflow notify users by e-mail or SMS about work items that need to be processed. Notifications are sent to the relevant user in the form of messages. At present, e-mail messages (HTML or text-only) and SMS messages are supported.
    Well I would say its not the base for all mails but surely for notifications.You can send mails even without configuring it.You can try it out in dev by creating a simple workflow with mail step.For mails you need to maintain the SCOT settings and evn that is done by BASIS guys so...u need not worry about it.
    Also , for extended notifications i would suggest you to go through this link
    Link:[http://help.sap.com/erp2005_ehp_04/helpdata/DE/d5/581ee8d56f1247bf34cfcd66d16d81/frameset.htm]

  • Error while accessing services of ESS/MSS tabs - URGENT

    Hi,
    When i am accessing the services under ESS, MSS tabs ie, Leave request, My expenses etc.... i am getting the following error. 
    A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.
    Please contact your system administrator.
    User XYZ does not exist in this period:
    com.sap.pcuigp.xssfpm.java.FPMRuntimeException: User XYZ does not exist in this period
         at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:111)
         at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:121)
         at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.initPernr(FcEmployeeServices.java:257)
         at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.onInit(FcEmployeeServices.java:220)
         at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServices.onInit(InternalFcEmployeeServices.java:249)
         at com.sap.pcuigp.xssutils.pernr.FcEmployeeServicesInterface.onInit(FcEmployeeServicesInterface.java:135)
         at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface.onInit(InternalFcEmployeeServicesInterface.java:183)
         at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface$External.onInit(InternalFcEmployeeServicesInterface.java:243)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:920)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:889)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1082)
         at com.sap.xss.tra.fc.utils.FcTraUtils.onInit(FcTraUtils.java:264)
         at com.sap.xss.tra.fc.utils.wdp.InternalFcTraUtils.onInit(InternalFcTraUtils.java:297)
         at com.sap.xss.tra.fc.utils.FcTraUtilsInterface.onInit(FcTraUtilsInterface.java:122)
         at com.sap.xss.tra.fc.utils.wdp.InternalFcTraUtilsInterface.onInit(InternalFcTraUtilsInterface.java:212)
         at com.sap.xss.tra.fc.utils.wdp.InternalFcTraUtilsInterface$External.onInit(InternalFcTraUtilsInterface.java:428)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:920)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:889)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1082)
         at com.sap.xss.tra.fc.allmytrips.FcTraAllMyTrips.onInit(FcTraAllMyTrips.java:247)
         at com.sap.xss.tra.fc.allmytrips.wdp.InternalFcTraAllMyTrips.onInit(InternalFcTraAllMyTrips.java:543)
         at com.sap.xss.tra.fc.allmytrips.FcTraAllMyTripsInterface.onInit(FcTraAllMyTripsInterface.java:115)
         at com.sap.xss.tra.fc.allmytrips.wdp.InternalFcTraAllMyTripsInterface.onInit(InternalFcTraAllMyTripsInterface.java:348)
         at com.sap.xss.tra.fc.allmytrips.wdp.InternalFcTraAllMyTripsInterface$External.onInit(InternalFcTraAllMyTripsInterface.java:420)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:920)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:889)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1082)
         at com.sap.xss.tra.vc.allmytrips.VcTraAllMyTripsInterface.onInit(VcTraAllMyTripsInterface.java:164)
         at com.sap.xss.tra.vc.allmytrips.wdp.InternalVcTraAllMyTripsInterface.onInit(InternalVcTraAllMyTripsInterface.java:205)
         at com.sap.xss.tra.vc.allmytrips.wdp.InternalVcTraAllMyTripsInterface$External.onInit(InternalVcTraAllMyTripsInterface.java:399)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:563)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:437)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:195)
         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:772)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:707)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
         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:1248)
         at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:353)
         at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:551)
         at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:595)
         at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:826)
         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:723)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
         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)
    I am able to access in QAS but not in DEV or Prod.

    VV,
    This could be case when the payroll for the user XYZ has not be updated till the current period, in which you are trying to access the ESS or MSS tabs.
    You can try this.
    1. Go to the transaction - PC00_mxy_CLSTR
    where xy refers to the MOLGA or the country coding for which the payroll is run.
    Observe there till which period for the user XYZ the payroll has been run.
    2. If the payroll has not been run for the current period.
    Go to transaction PC00_mxy_CALC and by entering the parameters, run the payroll and try doing the same.
    Hope this helps!
    Regards.
    Sandeep Tudumu

  • Error  - While changing existing leave request from ESS

    We are trying to use the standard leave request application in ESS/MSS. The basic required standard configurations are done. Since we wanted custom notifications, the related workflow is copied into custom workflow and we have included required custom notifications. The custom workflow is also configured properly.
    Now, the standard functionalities like making leave request, triggering notifications, approving leave request and posting information into backend are working fine from the ESS/MSS.
    When the employee tries to change the existing leave request (before approval) from ESS, at the 2nd step (Review and Send), it is displaying one error message General task: can be edited by all users. But, it still allows submitting the records.
    Once it is submitted, the system throws one java error at the final step (after pressing SEND button) u2013 Failed to process request. Please contact your system administrator. - java.lang.NullPointerException. The complete error information is provided in the attached word document. Even though, it throws error the submitted data is getting saved into the backend.
    Please help to solve this issue.
    Thanks,
    Prabhu
    Edited by: Prabhu T on May 18, 2011 1:53 PM
    Edited by: Prabhu T on May 18, 2011 1:54 PM

    What custom notifications you require in leave request? We have all available in standard using Rptarqemail
    First of all, the WF task should be set as
    General task: can be edited by all users, which you have done presumably under task classification
    Now, for checking purposes, can you check with standard WF in table v_t554s_web for one absence only?
    ie WS12300111.
    Please test this and let us know if you have errors
    Also please check your custom WF whether it is working correctly or not?

  • Objective setting appraisal (OSA) queries related to ESS/MSS

    Hello All,
    I am currently working in OSA. I have few queries related to this.
    My client wants to implement OSA without linking it to the SAP ESS/MSS. They have their own intranet portal which is not a part of SAP. But they are using it for applying leave etc which has been linked to SAP R/3. So they also want to use the the same portal for appraisal also. 
    Hence my query is whether is it possible to link OSA with their own inhouse intranet portal ? And if it is possible then how and will I be able to get all those functionalites which are available in standard ESS/MSS for OSA?
    Please guide.
    Regards,
    Daniel

    Hi Daniel
    If you can call SAP Portal in your local intrenet.
    In one of my clients they were using MOSS as thier frame work (SAP portal is called inside moss)
    Thanks
    Rajdeep

  • Approve link not working in ESS/MSS UWL portal

    Hi experts,
    we are using portal 7.3 with ess/mss.
    in mss when user is approving a leave request, he is not ale to proceed
    after few steps as one link "pprove another request" is not working.
    this i a standrd portal scren in UWL. please suggest.
    Thanks a lot in advance.

    Hello,
    This should be possible with some UWL configuration. Please check the following forum post: http://forums.sdn.sap.com/thread.jspa?threadID=1677777
    Kr,
    Julien

Maybe you are looking for