ESS Team Calender not showing approved Leaves.

Hi Friends,
In ESS Team Calender the user is not able to view the approved leaves which was visible untill it was not approved.
what is the ideal functionality ? I want the approved leaves also to be visible.
Please guide.
Regards,

in the table V_PTARQ_TCONSTR, ensure color display is checked for the rule group.
check the notes
1620547
1587357
1165170
1485657
Is this note implemented?
CL_PT_ARQ_REQS_LIST->SEL_REQS_ATTSABS_FOR_OWNER you can check here if this is possible
Edited by: Siddharth Rajora on Oct 13, 2011 4:24 PM

Similar Messages

  • ESS Team Calendar not showing peers list

    Hi,
    When an user logsin with his user id, he is able to see the list of his subordinate from the org. unit of which he is the holder in his ESS Team calendar.
    Rather I have a requirement that his peers should be shown.
    The configuration done is:
    Rule Group     Mode          View Grp.     Group of Organization          Group
    00000001     Approval          u201C     MSS_LEA_EE                    
    00000001     Attendance Over     u201C     MSS_LEA_EE          PPOME_P
    00000001     Administrator     u201C                    MSS_LEA_EE          PPOME_P
    00000001     Request          u201C     MSS_LEA_EE                    
    00000001     Team View           u201C     MSS_LEA_EE          PPOME_P
    In Table V_TWPC_V
    View ESSDIR
    View Name ESS: Direct Employees
    Eval. Path for Root Objects SAP_MANG
    Function Module Root Objects
    Evaluation Path Objects ORGASS
    Function Module Object Set
    Initial Evaluation Depth 0
    Is that I am missing some configuration?
    Thanks,

    In Table V_TWPC_V
    View ESSDIR
    View Name ESS: Direct Employees
    Eval. Path for Root Objects SAP_MANG
    If you use SAP_MANG, only subordinates will be shown
    try using ORGASS or WF_ORGUN or have a custom one developed in T77aw and assign it here where you only see
    peers in this very table

  • ESS tab does not show up after deploying ESS

    We did every configuration step for ESS and we had no issue before for other projects.
    However this time ESS tab does not show up on EP even the roles are assigned.
    ALL Jco tested OK.
    What could be wrong?
    Thanks for your help.

    Jose:
    Thanks!
    I think I miss
    BP_ERP5ESS
    BP_ERP5MSS
    Because I am at ecc6 enhp4, the matrix at Wiki did not specify above BP version.
    Could you tell me what version of
    BP_ERP5ESS
    BP_ERP5MSS
    should be applied to the EP7.01?
    Follow up:
    Jose: I do see the BP at the same Wiki:
    BP ERP05 ESS 1.41 SP04
    BP ERP05 MSS 1.41 SP04
    BP ERP05 COMMON PARTS 1.41 SP04
    I am going to apply them on the portal. Do you agree? Thanks again.
    Thanks!

  • Team Calender only shows 1 week in retropsect

    Hi,
    We use team calender in ESS in our portal, but we are unable to view records in retrospect further than one week.
    I have looked in IMG under ERP, but these options are not available:
    -  Personnel Management ® Employee Self-Service ® Service-Specific Settings ® Working Time ® Team Calendar.
    -  Integration with Other SAP Components ® Business Packages / Functional Packages ® Manager Self-Service (mySAP ERP) ® Working Time ® Team Calendar.
    I then looked at business functions and found that EA-HR isnt turned on (and when attempting activation tells me that it isnt necessary) and HCM_ESS_CI_1 doesnt even seem to exist!!
    Does anyone have any idea what is going wrong?!
    Many thanks

    team calendar customisation comes from this table
    V_PTARQ_TCONSTR., Please check for many months it is specified here
    customisation is possible , please check in trans code ptarq, you ll find all the customisaiton for portal
    Edited by: Siddharth Rajora on Jun 7, 2011 5:40 PM

  • ESS team calender

    Hi All,
    I would like to change in ESS team calendar.
    ESSàworking time à Create leave request à team calendar, only reports on particular org unit employees will be display.
    I would like to change to view direct line manager and any staff in residing  org unit and this need to set to only look down 3 levels.
    Could you please advice how to achieve.

    Hi All,
    Thanks for your reply.
    @ Siddharth, I have gone through as per above but it refering to manager team calender but my requirement was employee team calender.
    For example I have Root org unit A. Under root org unit A, we have 3 employees.
    Like employee1, employee2 and employee3. Employee1 manager for root org unit A.
    Under root org unit A, there are 2 sub org units. under 2 sub org units there are 10 employees.
    Here employee1 who is heading root org unit A, he was able to view all the employees(2+10 = 12 employees).
    But my requirement was employee 2 or employee3 (ESS team calendar are accessed via ESS/Working Time/Create Leave Request/Team Calendar)  from root org unit A need to view employees who are under sub org units.
    Could you please advice.

  • SAP Standard ESS country structure not showing on the iViews

    Hi All,
    Some of the Fields in the SAP Standard Employee Self Service Country structure not showing on the iViews, if we want to bring those fields to iView level, What would be the solution.
    Please suggest.
    Thanks
    PRadeep

    Hi Pradeep
    If these are mandatory fields or legall required in that country and delivered in V_T588M or V_T588MFPROPS then you need to check with SAP why they are not shown in the ESS scenario
    If these are optional or R3 specific fields it could be they are not delivered in V_T588MFPROPS - try inserting
    an overide in V_T588MFPROPC
    If still you cannot get these fields you may need to add a field to the ESS application using NWDI
    and you may also need to change the model so it recognises the new field - this is effectively changing
    the SAP delivery
    Best regards
    Stuart

  • Team calendar not showing after change of Manager

    Hi all,
    we are using the team calendar feature in our organization by filling out the "Manager" attribute in AD and Exchange. Since the old manager left the company and we changed the attribute to the new manager our users can't see the team calendar in
    Outlook anymore.
    I have already checked if the attribute is set properly and all looks fine. I have no idea what to do. I have also recognized that our users don't see the "Show Manager's Team Calendars" option in Outlook since we changed the manager.
    Do you have any ideas what to do now? Maybe there is a option to create the team calendar again?
    We are using Outlook 2010 and Exchange 2010.
    Thanks in advance!
    Regards

    Hi,
    Team Calendar is a feature of Outlook. Once Outlook connects to an Exchange server, Outlook will check the attribute of “Manager”. Then Outlook will create a team calendar according to the value automatically. According to your description, it might
    be that the attribute is not set properly. How do you change the attribute to the new manager in AD?
    What’s the results of the following command for those users?
    Get-AdUser UserName | Fl Manager
    Please open Outlook in online mode to check this issue.
    Best Regards.
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Lynn-Li
    TechNet Community Support

  • Regarding Leave & Team calender

    Hi ESS/EP Gurus,
    We are working SAP ESS/MSS with ECC6.0 and EP7.0,and the patch leave in the portal is SPS13 and we deployed business pakages for  ESS and MSS for 1.0, configured all necessary steps in the backend for leave request its working fine all the services.
      Recently we dployed support package for ESS 1.2 i dont what happent Leave request and team calender not working it throwing some error, can you please help me for this.
    please find the the error messages for bith:
    Leave request::
    java.lang.NullPointerException
        at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.createNewBaseTypeDescriptor(AiiModelClass.java:256)
        at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.descriptor(AiiModelClass.java:222)
        at com.sap.xss.hr.lea.model.Pt_Arq_F4Help_Sickcode_Input.<init>(Pt_Arq_F4Help_Sickcode_Input.java:51)
        at com.sap.xss.hr.lea.form.FcForm.wdDoInit(FcForm.java:143)
        at com.sap.xss.hr.lea.form.wdp.InternalFcForm.wdDoInit(InternalFcForm.java:1994)
        ... 67 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; .NET CLR 2.0.50727)
    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: Wed Dec 05 20:34:49 IST 2007
    J2EE Engine 7.00 patchlevel 109044.44
    Java VM Java HotSpot(TM) Server VM, version:1.4.2_13-b06, vendor: Sun Microsystems Inc.
    Operating system Windows 2003, version: 5.2, architecture: x86
    Session & Other
    Session Locale en
    Time of Failure Thu Feb 07 14:46:36 IST 2008 (Java Time: 1202375796874)
    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
    java.lang.NullPointerException
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.createNewBaseTypeDescriptor(AiiModelClass.java:256)
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.descriptor(AiiModelClass.java:222)
         at com.sap.xss.hr.lea.model.Pt_Arq_F4Help_Sickcode_Input.<init>(Pt_Arq_F4Help_Sickcode_Input.java:51)
         at com.sap.xss.hr.lea.form.FcForm.wdDoInit(FcForm.java:143)
         at com.sap.xss.hr.lea.form.wdp.InternalFcForm.wdDoInit(InternalFcForm.java:1994)
         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.ClientComponent.createComponent(ClientComponent.java:940)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:177)
         at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:149)
         at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:141)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$ComponentUsageManager.createBLCComponentUsage(FPMComponent.java:760)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:919)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:890)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1083)
         at com.sap.xss.hr.lea.blockcale.VcBlockCale.onInit(VcBlockCale.java:254)
         at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCale.onInit(InternalVcBlockCale.java:275)
         at com.sap.xss.hr.lea.blockcale.VcBlockCaleInterface.onInit(VcBlockCaleInterface.java:163)
         at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCaleInterface.onInit(InternalVcBlockCaleInterface.java:144)
         at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCaleInterface$External.onInit(InternalVcBlockCaleInterface.java:220)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java: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)
    Team Calender::
    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: no jcoMetadata found for RFC function 'PT_ARQ_F4HELP_SICKCODE'! Please verify, that your model is consistent with the ABAP backend: 'HR6'.
        at com.sap.tc.webdynpro.modelimpl.dynamicrfc.metadata.DRFCModelInfo.getOrCreateClassInfo(DRFCModelInfo.java:217)
        at com.sap.tc.webdynpro.modelimpl.dynamicrfc.metadata.DRFCModelInfo.<init>(DRFCModelInfo.java:164)
        at com.sap.tc.webdynpro.modelimpl.dynamicrfc.metadata.DRFCModelInfo$Cache.getModelInfo(DRFCModelInfo.java:103)
        at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModel.<init>(DynamicRFCModel.java:112)
        at com.sap.xss.hr.lea.model.LeaveRequestAdaptiveModel.<init>(LeaveRequestAdaptiveModel.java:381)
        ... 79 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; .NET CLR 2.0.50727)
    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: Wed Dec 05 20:34:49 IST 2007
    J2EE Engine 7.00 patchlevel 109044.44
    Java VM Java HotSpot(TM) Server VM, version:1.4.2_13-b06, vendor: Sun Microsystems Inc.
    Operating system Windows 2003, version: 5.2, architecture: x86
    Session & Other
    Session Locale en
    Time of Failure Thu Feb 07 14:50:37 IST 2008 (Java Time: 1202376037482)
    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: failed to create or init instance of model 'com.sap.xss.hr.lea.model.LeaveRequestAdaptiveModel' in scope APPLICATION_SCOPE with instanceId 'null'
         at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getOrCreateModelInstanceFromScopeMaintainer(WDModelFactory.java:341)
         at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getModelInstance(WDModelFactory.java:155)
         at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getModelInstance(WDModelFactory.java:102)
         at com.sap.xss.hr.lea.utils.Utils.getModelInstance(Utils.java:34)
         at com.sap.xss.hr.lea.selectionlist.FcSelectionList.onInit(FcSelectionList.java:223)
         at com.sap.xss.hr.lea.selectionlist.wdp.InternalFcSelectionList.onInit(InternalFcSelectionList.java:382)
         at com.sap.xss.hr.lea.selectionlist.FcSelectionListInterface.onInit(FcSelectionListInterface.java:115)
         at com.sap.xss.hr.lea.selectionlist.wdp.InternalFcSelectionListInterface.onInit(InternalFcSelectionListInterface.java:340)
         at com.sap.xss.hr.lea.selectionlist.wdp.InternalFcSelectionListInterface$External.onInit(InternalFcSelectionListInterface.java:392)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:921)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:890)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1083)
         at com.sap.xss.hr.lea.selectionlist.VcSelectionList.onInit(VcSelectionList.java:219)
         at com.sap.xss.hr.lea.selectionlist.wdp.InternalVcSelectionList.onInit(InternalVcSelectionList.java:330)
         at com.sap.xss.hr.lea.selectionlist.VcSelectionListInterface.onInit(VcSelectionListInterface.java:162)
         at com.sap.xss.hr.lea.selectionlist.wdp.InternalVcSelectionListInterface.onInit(InternalVcSelectionListInterface.java:144)
         at com.sap.xss.hr.lea.selectionlist.wdp.InternalVcSelectionListInterface$External.onInit(InternalVcSelectionListInterface.java:238)
         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: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.wdDoApplicationStateChange(PageBuilder.java:301)
         at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoApplicationStateChange(InternalPageBuilder.java:197)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doApplicationStateChange(DelegatingComponent.java:139)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doApplicationStateChange(ClientComponent.java:667)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doApplicationStateChange(ClientApplication.java:537)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:120)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:313)
         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.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.sap.tc.webdynpro.progmodel.model.api.WDModelException: failed to create instance of model 'com.sap.xss.hr.lea.model.LeaveRequestAdaptiveModel'
         at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getNewModelInstance(WDModelFactory.java:392)
         at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getOrCreateModelInstanceFromScopeMaintainer(WDModelFactory.java:329)
         ... 70 more
    Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: no jcoMetadata found for RFC function 'PT_ARQ_F4HELP_SICKCODE'! Please verify, that your model is consistent with the ABAP backend: 'HR6'.
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.metadata.DRFCModelInfo.getOrCreateClassInfo(DRFCModelInfo.java:217)
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.metadata.DRFCModelInfo.<init>(DRFCModelInfo.java:164)
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.metadata.DRFCModelInfo$Cache.getModelInfo(DRFCModelInfo.java:103)
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModel.<init>(DynamicRFCModel.java:112)
         at com.sap.xss.hr.lea.model.LeaveRequestAdaptiveModel.<init>(LeaveRequestAdaptiveModel.java:381)
         at com.sap.xss.hr.lea.model.LeaveRequestAdaptiveModel.<init>(LeaveRequestAdaptiveModel.java:356)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
         at java.lang.Class.newInstance0(Class.java:308)
         at java.lang.Class.newInstance(Class.java:261)
         at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getNewModelInstance(WDModelFactory.java:386)
         ... 71 more
    Regards,
    Sambaiah.
    Edited by: Sambaiah Muvva on Feb 7, 2008 10:17 AM

    Hi Sambaiah,
    Sorry for the late reply. Did you get a solution for the problem. This defineitely seems to be a compatibilty problem with the frontend (ESS business package, XSS sca files (ess, mss, pcuigp) and backend r3 (EA-HR, SAP-HR).
    As the error clearly points out com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: no jcoMetadata found for RFC function 'PT_ARQ_F4HELP_SICKCODE'! Please verify, that your model is consistent with the ABAP backend: 'HR6'.
    Also, please chek the stack level recommendations for all the components Also, chek note 761266.
    Chuckie,Please let us know if you get a reply from the OSS message, as this might be useful to many more of us who are yet to face this issue
    Best Regards
    Reshma

  • Diff between ESS Team Calendar and MSS Team Calendar

    Hi,
    Can anyone please let me know is there any difference between ESS team calender that employees see in the Leave tab and the Mss team calender that the managers see for their team.
    In our system, it so happens that a user who is a chief sees the org structure in which he is as an employee only ( not manager) in the ESS team calender. However users who have both the ESS and MSS roles see the org structure which is reporting to them in the ESS and as well as the MSS team Calender.
    i already searched SDn and SAPnotes for this and was unable to find anything useful.
    Can anyone please let me know from where does the team Calendar fetch the details from the back-end both in the case of ESS and MSS.
    regards,
    pinki

    ESS Team calendar is meant for the employees to see the other colleagues in their Org unit
    MSS Team calendar is used by the manager to see the
    employees reporting to him directly or indirectly (configuration available)
    All this comes from leave request application, Ie sent leave
    approved status etc, and of course the infotypes 2001
    and 2002.
    Check for team calendar in help.sap.com you ll find very good documentation on this.
    http://help.sap.com/erp2005_ehp_03/helpdata/EN/4d/c19ce6ef2842258283afc35a54172a/frameset.htm

  • Arranging names in team calender in Alphabetical order

    Dear All,
    Please guide me through this if this is possible -
    Can we arrange/sort the names in the ESS team Calendar in Alphabetical order?
    Please guide.
    Regards,
    Poornima

    Hi Siddharth,
    Can you plase explain...
    My requirement is to have the ESS team calender in Alphabatical order..which is not as of now.
    Regards,
    Poornima

  • 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

  • Problem in the team calender leave display of other employees

    Hello,
    I have a problem with the leave request in ESS.
    Go to Working Time >> Leave request >> Show Team Calendar >>
    and you can see all the members of the team and also if someone has taken leave then that is also highlighted in the calender.
    when i keep my mouse pointer near to the highlighted spot, I can see the information like 'date', 'type of leave' and 'approved' messages but if i keep the mouse for the other user then i will get the info as 'date and absent' which is correct and it will not show the type of the leave.
    Now the problem is whenever i click on that higlighted spot then, I will get below info.
    You have selected the following leave:
    type of leave : .............
    date : .................
    But if i select other team members then it is showing the 'type of leave' but it should show 'absent' as 'type of leave ' when i select other user and it should display actual type of leave when i select for my self.
    Now it is displaying the type of leave for all the users. how to avoid this and display as 'absent' ?
    The RFC used from the back end is PT_ARQ_REQUEST_PREPARE to get the above detail....
    is this the authorization issue? if yes can you tell me how to restrct that ? or if not then what might be the issue ?
    Best Regards,
    Prashanth J R

    Hello Sidharth,
    Thank you for the reply but where should i found the below code?
    IF value NE <ui_request>-owner-pernr AND value NE approver_pernr .
    CLEAR <ui_request>-subtype_description.
    <ui_request>-subtype_description = '************'.
    ENDIF.

  • Team Calender in Leave Request Application

    Hi Experts,
    ERP2004 SP17, EP6.0 SP20, ESS/MSS SP17
    I am trying to configure the leave request application. I see a link in the "Show team calender" in the application. I configured according the documentation in spro>personal Management>Employee Self Serivce>service specific settings>working time>leave request.
    the documentation is like this In "layout of web application">select employees for team calender:
    5. Select the employees whose absences you want to display in the team calendar. You first have to enter one of two grouping characteristics in the View/Grp field:
    If you use the Manager Self-Service (MSS) or Employee Self- Service (ESS) components at your enterprise, you will probably use the view groups. They are based on employees organizational assignments.
    If you use the Time Managers Workplace (TMW), you probably use grouping IDs.
    You now have to select the employees whom you want to display in the team calendar. <b>To do so, enter the required view group or grouping ID in the relevant field.</b>
    However I do not know where to create a "GROUPING ID". I have added the view group. but the field "GROUPING ID" is blank in the customization. May be this is required to display employees in team calender.
    Could you help me how to get employees in Team Calender.
    your help will be greatly appreciated.
    Thanks so much!
    Message was edited by:
            minisap g

    Hi Sonia,
    Below is what i see in view TWPC_VG.
    <b>VIEWGROUP</b>           <b>   VIEWID</b>
    APPRAISAL     AP_ALL
    APPRAISAL     AP_DIR
    AP_OVERVIEW     APOV_A
    AP_OVERVIEW     APOV_D
    ATTEND     A_ALL
    ATTEND     A_DIR
    COMMUNICATION     CALL
    COMMUNICATION     CDIR
    DIRECTREPLEVX     TVLEV1
    DIRECTREPLEVX     TVLEV2
    DIRECTREPLEVX     TVLEV3
    DIRECTREPLEVX     TVLEV4
    DIRECTREPLEVX     TVLEV5
    HAP_STATUS     HAPALL
    HAP_STATUS     HAPDIR
    ISR                     ISR1
    ORG                     ORGALL
    ORG                     ORGDIR
    ORG_PROF     O_PROF
    ORG_S                     O_SALL
    ORG_S                     O_SDIR
    PCR                     PCRALL
    PCR                     PCRDIR
    PCR_ERP                     PCRER1
    PCR_ERP                     PCRER2
    PTESS                     ESSDIR
    QP_ORGS_VG     QP_DIR
    REC_OVERVIEW1     RECALL
    REC_OVERVIEW1     RECEXT
    REC_OVERVIEW1     RECSIM
    REC_OVERVIEW2     REC_PA
    REC_OVERVIEW2     REC_PE
    REC_OVERVIEW2     REC_PS
    REPORTING     RPT_KA
    REPORTING     RPT_OA
    REPORTING     RPT_OD
    REPORTING     RPT_PA
    REPORTING     RPT_PD
    VACOV                     RCVAC
    XYLVG1                     XYL1
    ALso let me know the viewgroup you see for the view group "ESS_LEA_EE". May i will try creating these.

  • 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.

  • ESS MSS multiple entry table is not showing up

    Hi All,
    I have a issue in ESS when user applies leave and cancels the leave. When the user clicks on that day again in the calendar
    then unable to see the history of the cancelled leave in ESS Leave application.
    multiple entries are there for that day and in the team calender its not showing light blue color.
    We are using ESS MSS latest package HR Package and US Payroll.
    Swathy

    Hello,
    Is the posting program being run correctly?
    Please check 1104839 - ESS LEA:Wrong Behavior in Change/Delete of Leave
    Rgs,
    Bentow.

Maybe you are looking for