ECC 6.0 leave request attendence overview

Please can someone help me how to configure the field "status" in my ESS leave request attendence overview in ECC6.0?
I'm using a leave request scenario without approval and the status of my posted absences in infotype 2001 show the status "informed". From a proces point this status makes no sense.
Already thanks for reading. Hope for a solution.
Robbert Bastiaans

Hello,
I would definitely say for you to have a look at the BADI PT_GEN_REQ. Also verify the implementation of your PT_ABS_REQ.
REgards,
Bentow.

Similar Messages

  • ECC 6.0 - Leave request show duplicate entries one with ERROR status

    Dear All,
    We have implemented standard Leave request process, we are facing the issue as mentioned below, Its not happening for all the time, however we want to what scenario   this problem will arrives.
    Problem description:
    E.g. Staff applied annual leave on 10.06.2010, the leave request will sent for approval , after the approval of the leave ,every 30 min. we have scheduled a job which will execute standard program RPTARQPOST to post a leave request to IT2001.
    After the approval when staff go into ess and see leave request details under "Show Overview of Leave" and its shows as 2 records for the same period one with APPROVED and another one with ERROR.
    Type of Leave   From         TO                    Status                      Used
    Annul

    Hi Annul,
    Please check SAP Note 986003 - ESS LEA: Incorrect ERROR status for records in RPTARQPOST.
    May be relevant for your case.
    Regards,
    Dilek

  • Need to make Leave request delete a single step process on Leave Overview..

    <h5> Hi Guru's, </h5>
    <p>
    My clients requirement is to add a coulumn to the standard LeaveOverview application under SAP ESS Leave application.This coulumn should have a "Delete" button for each row while showing the LeaveOverview records.
    <p>
    On Click of the Delete button the client wants the Leave request to be deleted,without carrying out any further steps as they appear in the standard scenario.
    <p>
    I could add the coulumn by using the provided hidden cutomer field, and added the button as well. Only thing remaining is now the deletion part of it. I am new to WebDynpro java so please help me.
    <p>
    Thanks in advance!
    <p>
    Samir Kulkarni
    9922111479

    Hi Siddharth,
    Thanx for a quick reply!
    I know it can be done with wd java, but I would like a step by step process as being a amature in this domain. I tried few things on standard but in the end it will take me to the review screen only.
    It will really be helpful if you let me know the note number cause I have been searching for the same for long and could only get a note for skipping review screen in the Leave Request process not in the deletion's case from leave overview screen.
    Thanks in advance!
    Regards,
    Samir
    9922111479

  • Leave request projection EP 7.0 ECC 6.0

    Hello experts,
    we are using standard java webdynpro leave application, we have a requirement to project a future leave on end date of leave and allow employee to submit the leave if by the end date of leave they have accrued enough quota for the leave type.
    we have been able to get rid of standard message " not enough quota.." for future leaves by making use of badi calculate_quota, where i have projected the quotas based on the end date of leave and hence in turn allowing the employee to submit leave if enough have been accrued.
    when manager tries to approve such future leave, the system again goes to the same badi and hence projection happens which ensures manager can approve/reject it but manager actually can not see the projected quota amount as time account service displays quota as on current date.
    now we have a requirement to display the projected quota on time accounts service when manager is approving the leave request.
    is there any way by which we can display the projected quota in the time account service on approver screen so that approver is not confused when approving future leaves, which are allowed even if employee dont have enough quota today but will have enough at the end date of the leave( as out code in said badi will ensure it)?
    thanks in advance for your inputs.

    Hi Siddharth,
    thanks for reply.
    I have already changed that badi method so that the fm gets called with the mode suitable to my requirements. so projection is happening for me on quota overview service(which is date driven) and for leave request screen i have used badi PT_QUOTA_DEDUCTION to do projection as on end date of leave and thus getting rid of "not enough quota message" if employee has accrued enough as on end date. problem is we can not make the projection quota balance displayed on the time acc service on leave screen as system makes call to PTaccount with default date as sy-datum, so even though you change mode to 'E' , the results will be based on current date.
    so what we want is to display the quotas on leave approval screen when approver is approving the leave as on the end date of leave. we do not need this display on employee screen but approver needs to see the projected amount as currently quota may not be enough bt in future he has enough thats why employee was able to apply the particular leave.
    now i am not sure how to make the call to Ptaccount fm date driven by the end date of leave as i am not able to find any relation between the call and end date of leave.
    thanks

  • Leave Request - Show or Hide by Country

    Hello to all,
    I have NW2004s EP 7.0, ESS BP 60.2, ECC 5.0.
    I'm implementing the Portal in several languages but I only want to make "Leave Request" available for only a few of them.
    Any ideas?
    Thanks in advance.
    Antonio

    Hi,
    There are two possible ways of doing this:
    This could be possible with the customization of standard business package where in you need to write a piece of code to identify the logged-in user's location (from the backend and not the locale because locale could be deceptive) and thereafter dynamically displaying or hiding the link on overview page.
    Second, go for a federated portal and the implementation would be much easier. You would not need to customize the standard business package. To learn more about federated portal, use this link : http://help.sap.com/saphelp_nw2004s/helpdata/en/89/f9ed428ccd5604e10000000a155106/frameset.htm
    There is no such standard feature available in portal otherwise.
    Hope this helps.
    Cheers,
    Sunil
    PS: Reward points for helpful answers.

  • MSS : Team Calender - Legend colors - Leave Request TOIL

    Hello All,
    We have a scenario where in MSS --> Overview --> Team calender , In one of the legends colors (Leave Request\TOIL), its showing blank, rest of the legend colors seems to be working fine, We tried to look into the badi at the ECC level as well and nothing seems to be missing.
    Could anyone please us know if the there are any personalizations that needs to be done for the in this regard on the portal level? if so , Could anyone let us know the steps for the same ?.
    Regards,
    Ronniee.

    Hi,
    Check the link below:
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/108c31e7-b6a7-2d10-3692-c1a9f7a5c4dc?QuickLink=index&overridelayout=true
    Hope this helps.
    Cheers-
    Pramod

  • Team Calendar in ESS Leave Request (Error)

    Hello,
      we are configuring the Leave request in ESS and MSS in the portal (EP 7.0, ECC 6.0, latest release). The Leave Request process and application, Time accounts and Workflows all working fine and the customizing is done in the IMG.
      Only under ESS -> Leave Request -> Team Calendar we are getting this Error:
    java.lang.Exception: No Views found: Missing customizing
         at com.sap.xss.ser.tecl.fc.FcTeamCalendar._checkData(FcTeamCalendar.java:799)
         at com.sap.xss.ser.tecl.fc.FcTeamCalendar._getData(FcTeamCalendar.java:751)
         at com.sap.xss.ser.tecl.fc.FcTeamCalendar.initialReadData(FcTeamCalendar.java:385)
         at com.sap.xss.ser.tecl.fc.wdp.InternalFcTeamCalendar.initialReadData(InternalFcTeamCalendar.java:319)
         at com.sap.xss.ser.tecl.fc.FcTeamCalendarInterface.initialReadData(FcTeamCalendarInterface ....etc.
    I have maintained the Customzing in IMG for Team Calendar as the following:
    00000001     SAP Standard     01.01.1800     31.12.1999     Approval Mode     View Group (MSS)     MSS_LEA_EE
    00000001     SAP Standard     01.01.1800     31.12.1999     Attendance Overview     View Group (MSS)     MSS_LEA_EE
    00000001     SAP Standard     01.01.1800     31.12.1999     Administrator Mode     View Group (MSS)
    00000001     SAP Standard     01.01.1800     31.12.1999     Request Mode     View Group (MSS)     ESS_LEA_EE
    00000001     SAP Standard     01.01.1800     31.12.1999     Team View Mode     View Group (MSS)
    Would you please help?
    Many Thanks and Regards,
    Nazih

    Hi Bryan,
    1. First of all make sure that the Internet Graphic Server is activated + up and running on your SAP ERP System (see also SAP Note  704604)
    2. Then you have to set the Customizing Parameters for the Team Calendar in IMG (SAP ERP System):
    a. Tcode: PTARQ -> Customizing
    b. Working Time -> Team Calendar
    c. Node Create Rule Group -> Example: 00000001 (SAP Standard)
    d. Node Adjust WEBMO Feature -> Assign all Nodes to your Rue Group
    e. Node Spec. Absecne to be displayed -> Here i assume you have set up the Leave Request Process and WF already, so you only need to assign this to your Rule Group:
    Example.
    00000001     SAP Standard     01     0100     Leave     01.01.1800     31.12.9999
    f. Node Select Employee -->
    Here you need to set the Group of your Employee which should be displayed in the team calendar:
    Example.
    00000001     SAP Standard     01.01.1800     31.12.9999     Approval Mode     View Group (MSS)     MSS_LEA_EE
    00000001     SAP Standard     01.01.1800     31.12.9999     CATS Approval     View Group (MSS)     MSS_LCA_EE
    00000001     SAP Standard     01.01.1800     31.12.9999     Attendance Overview     View Group (MSS)     MSS_LEA_EE     PPOME_P
    00000001     SAP Standard     01.01.1800     31.12.9999     Administrator Mode     View Group (MSS)     MSS_LEA_EE     PPOME_P
    00000001     SAP Standard     01.01.1800     31.12.9999     Request Mode     View Group (MSS)     ESS_LEA_EE
    00000001     SAP Standard     01.01.1800     31.12.9999     Team View Mode     View Group (MSS)     MSS_LEA_EE     PPOME_P
    ---> Tipp: Check all Settings and Leave Types also with an HR Consultant before maintaing these in the ESS Customizing...
    Regards,
    Nazih

  • Error Not enough quota 30 for attendance/absence in ESS Leave Request

    Good Morning
    I am trying to create a "Leave Request" using ESS with  "Floating Days".  It has a cuota manual.  When trying to create the leave request in ECC all works fine, but when trying to create the same leave request in ESS the following error occurs:
    Not enough quota 30 for attendance/absence 0261 on 05.03.2008 for personnel no. 20001140
    Some can help me?
    Best Regards,
    Wilman

    Hi,
    I would suggest the following :
    Step1: Check your IT 2006/IT 2007 for your Absence and Attendance Quotas.
    Step 2: You can also verify the same information using the PT50 transaction ( quota Overview)
    Step 3: By doing the above you ensure that the person has the required quotas.
    Step4: logon to ESS and do the request for leave.if it does not let you, then there is some problem in the config in the ESS. I cannot tell you this from top of my head. We need to look into the portal to see what exactly the problem.
    regards
    Vijay

  • Multiple leave requests on the same day

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

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

  • 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 raising new Leave Request

    Hi guys,
    Some of our users are trying to raise a leave request in ESS and getting an error
    Use the input help to select an approver.
    The only change that has happened is that we recently upgraded from ECC 5.0 to ECC 6.0. Other than that there has been no new development for our ESS/MSS.
    There are only few users that are affected by this problem. The only thing different that I can see about these users is that in our org structure, the position that they're reporting to is not filled (no holder for that position), so they report to the next manager/approver above that position. This has never been a problem in past. ESS was able to get the next approver without any problems before the upgrade but now it seems like SAP only checks one level and since there's no holder of that position it gives this error. For any employees that report to a position that's filled don't have any issues.
    I'm an SAP ABAP developer. Not too familiar with ESS/MSS or SAP config so please help me understand if this is a config issue or there's something else that needs to be done?
    Thanks for your help.
    Edited by: Mohammad Zeeshan on Aug 15, 2011 8:58 PM

    Go to transaction PTARQ and check if you are able to determine the correct approver for these employees.
    Also, from transaction PTARQ - Customizing :
    Employee Self Service - Service Specific Settings - Working time - leave request - Processing Processes - Determine processing processes for each rule group
    There is a configuration for "Determine Next Agent". This should be either "Line Manager" or "Last Agent, then Line Manager" (Refer to the field help for more information)
    Also, you can utilize BADI  PT_GEN_REQ for handling any special cases.
    Thanks,
    Shanti

  • Strange error in Leave request

    Hi Experts,
    I am getting one error in production for the leave request. When one particular employee applies for the leave, he is able to apply for the leave properly. After applying leave, his leave request status changes to sent. when i checked in the report "RPTARQDBVIEW" about that particular employee's leave document, workflow was not attached to that document. This is happening everytime whenever he applies for the leave. Workflow is not getting triggered whenever he applies. Its working fine for the other employees similar to him.  
    Can you help me regarding this. This is becoming critical.
    Thanks
    Sameer
    One thing i found that, its happending for few more employees. and common thing about them is that all are getting error "Unable to send the request with this approver" while applying leave. when they go back and again apply then leave request is going. For all these employees their manager is not belongs to india org unit. And this ESS we have configured for india employees.
    Edited by: sameer dhuke on Jul 17, 2009 7:41 PM

    Hi,
    This comens when the approral is not assign to the User-ID
    Say "A" is the employee and you need set "B" is manager for "A"
    Then folloiwng things you need to do .
    in the PA30 chekh the "Org Assig" for "A".
    The org unit for "A" ( employee ) and "B" ( manager ) should be same .
    then PO10 give the Org Unit and check the following entry .
    19.02.2009     31.12.9999     B     003     Incorporat     S     50006006     056607A     0,00
    19.02.2009     31.12.9999     B     012     Is managed     S     50006006     056607A     0,00
    you can see the "50006006" is the possition ( Is managed )
    Then you need to go PO13 give the possition no and click up on 'Overview"
    19.02.2009     31.12.9999     A     003     Belongs to     O     50129078     New org unit                        0,00
    01.04.2007     31.12.9999     A     008     Holder     P     00001070     (Employee A)     100,00
    01.01.2000     31.12.9999     A     011     Cost cente     K     00002009461000     Financial As     0,00
    19.02.2009     31.12.9999     A     012     Manages...     O     50129078     New org unit     0,00
    01.01.2000     31.12.9999     B     007     Is describ     C     50015243     AdmSup     0,00
    Like this you can set the manager to employee

  • Problem with ESS Leave Request Workflow

    We had configured ESS Leave request, which is working fine with Leave request approval.
    1)     Cancellation of Leave Request using the workflow WS12400005.  
                                  Workflow is not getting triggered when we try to delete the leave request.
    2)     Quota Overview
    While displaying the Casual Leaves (CL) I need to deduct the Paternity leaves (PL) also.
         Remaining CLu2019s = quota CLu2019s u2013 ( used CLu2019s + used PLu2019s).

    hi kishore. how did you resolve the issue of workflow not being triggered?

  • Java.lang.NullPointerException Error in Leave Request tab of ESS in Portal

    Hello All,
    I have configurted ESS/MSS on EP 7.01 SP03, but it is giving error in almost every tab.
    When i navigate in to Employee Self Service < Working Time < Leave Request tab it ends up with error pasted below.
    java.lang.NullPointerException
    Same error appears for other tabs like Employee Self Service < Working Time <Quote Overview/Clocl In/Out Corrections
    Any help to solve this issue will be highly appretiated.
    Thanks
    Vinit

    Full exception chanin from NWA is as below
    Exception occured during processing of Web Dynpro application sap.com/ess~lea/LeaveRequest. The causing exception is nested.
    [EXCEPTION]
    java.lang.NullPointerException
    at com.sap.pcuigp.tracking.BTrackingComp.isValuePackSystem(BTrackingComp.java:290)
    at com.sap.pcuigp.tracking.BTrackingComp.onInit(BTrackingComp.java:206)
    at com.sap.pcuigp.tracking.wdp.InternalBTrackingComp.onInit(InternalBTrackingComp.java:173)
    at com.sap.pcuigp.tracking.BTrackingCompInterface.onInit(BTrackingCompInterface.java:115)
    at com.sap.pcuigp.tracking.wdp.InternalBTrackingCompInterface.onInit(InternalBTrackingCompInterface.java:124)
    at com.sap.pcuigp.tracking.wdp.InternalBTrackingCompInterface$External.onInit(InternalBTrackingCompInterface.java:198)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
    at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.onInit(FcEmployeeServices.java:219)
    at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServices.onInit(InternalFcEmployeeServices.java:273)
    at com.sap.pcuigp.xssutils.pernr.FcEmployeeServicesInterface.onInit(FcEmployeeServicesInterface.java:135)
    at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface.onInit(InternalFcEmployeeServicesInterface.java:198)
    at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface$External.onInit(InternalFcEmployeeServicesInterface.java:258)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
    at com.sap.xss.essceservices.vcceassignmentselection.VcCEAssignmentSelection.onInit(VcCEAssignmentSelection.java:235)
    at com.sap.xss.essceservices.vcceassignmentselection.wdp.InternalVcCEAssignmentSelection.onInit(InternalVcCEAssignmentSelection.java:174)
    at com.sap.xss.essceservices.vcceassignmentselection.VcCEAssignmentSelectionInterface.onInit(VcCEAssignmentSelectionInterface.java:162)
    at com.sap.xss.essceservices.vcceassignmentselection.wdp.InternalVcCEAssignmentSelectionInterface.onInit(InternalVcCEAssignmentSelectionInterface.java:144)
    at com.sap.xss.essceservices.vcceassignmentselection.wdp.InternalVcCEAssignmentSelectionInterface$External.onInit(InternalVcCEAssignmentSelectionInterface.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:754)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289)
    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:1289)
    at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
    at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
    at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:593)
    at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:865)
    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:319)
    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: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:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Edited by: Vinit Soni on Aug 27, 2010 7:59 AM

  • Leave Request SENT but does not show in Worklist (duplicate PTREQ_ACTOR)

    I have a wierd issue in our ESS Leave System.  We are on ECC 6.0 with EP 7.0.  We are using the iView for leave approval and not workflow/UWL.
    The leave system is working great for all users except for one.  The situation is there is one employee in the approvers team that has leave requests that are sent to the approver but they do not show in the approvers worklist.  The requests are visible from the team calendar and the approver can approve them that way.  The approver has other employees in the same team that can send leave requests to the approver and they will show on the worklist with no problems.  We have checked all of the relationships and employee data and all looks OK.
    I have identified that the approver with this issue has 2 records in the PTREQ_ACTOR table.  The requests that are not showing are linked to one ACTOR_ID and the ones that are showing correctly are linked to the other ACTOR_ID.
    1) What caused the employee to have 2 ACTOR_ID records in PTREQ_ACTOR?
    2) How do we cleanup/resolve this issue from happening in the future?

    duplicate can cause  a issue in the system!
    the leave requests should be approved in some timeline and then we can
    delete the table entries which are not used anymore, then The entries which are not used should be deleted, you can write
    a custom program to delete the entries in the system.
    ie
    What we could suggest in your case is to delete one of the
    Actor Ids (the old one or the one which is less used) of the
    manager in question.
    Please identify how many entries are there in the system
    first of all.
    read and apply  the note 1316777.
    You can approve and post via the trans code in PTARQ.

Maybe you are looking for

  • Missing Waveform Monitors - New Install, Most Recent Premiere CC 2014

    Hi, I recently downloaded and installed Premiere Pro CC and related apps with a cloud subscription on a new Mac Pro tower. I connected by working RAIDs and opened a PPro project originated on my previous edit system, an iMac.  Right away I noticed so

  • When I try to access my att mail I get a message 404 not found nginx/0.6.32, but I can get mail through inertent explorer

    If I go To Internet explore I can open my mail but not on firefox. this started a couple of weeks ago. I downloaded a program suggested by my ban. Some how I ended up with bing on my computer a finally got rid of it . Downloaded the new 4. fireox but

  • Displaying a cachedRowSetImpl in a jsp! :-(

    I am new to servlets and jsps. I have a problem with cachedRowSetImpl and jsps. I have a sevrlet (userDisplay) that populates a cachedRowSetImpl object (called crs) and then stores this in a bean called userDisplayBean. I then want to access this bea

  • Skip Selection screen

    Hi Friends, I need to run a report and before the report is generated i need to run a Extract program. So the screen sequence is goe like this. 1. The initial selection screen is the selection criteria for the report. 2. Once the criteria is given an

  • Error in importing idoc cremas03

    Dear all,   I am trying to import an idoc cremas.cremas03 in XI but it is giving following messages   " import started"   " Idoc type cremas03 contains error(unable to read segments)   "  idoc import failed with 1 error " i have tried to import 4 to