MSS Portal performance Team calender

Hi All,
While accessing the Team Calender by MSS Portal , its taking much time , even when we are accessing Team calender in Production portal, its taking so much time.
Can any one help me in this regard.Whay its taking so much time how we can increase performenc of the Team calender accees.
Thanks

Is this issue only with team calender or all the services in MSS including team viewer.
If this is only with team calender where manger views attendance of employee then debug the application and specifically look at the RFC timing.
This can be an issue with respect to sizing of system if all the mss applications are resulting in poor response otherwise as suggested raise an OSS.

Similar Messages

  • 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

  • In MSS- ServiceMap- Team- Team Calender update rate? .

    Hi,
            In  MSS->ServiceMap->Team-> there is Team Calender .Can anyone tell me -wheather this Team calender is updated day 2 day basis  or monthly basis ? Can any one please reply ASAP.
    Thanks
    Rizwan

    Hi All,
    Actually the scenario is that the some employees ae moved from one manager to another onn 16th of a month say oct.
    These employees are still displayed in the team calender of the old (previous) manager for that month(oct).
    We wanted to verify if this is the correct behaviour or since the employees are no longer reporting to the manager, these should not be displayed in the team calendar of the manager?
    Urgent assistance would be appreciated.
    Best Regards,
    Kanika

  • MSS team calender

    Hi All,
    When I access MSS team calender MSS --> team. I could view my direct subordinate and team members but I would like my name(manager name) to be displayed in team calender. How could be acheive this. Could please advice.

    Hi Jwala,
    I could view my team members names but my issue was I would like to view my name in team calender.

  • MSS Team calender problem  - Manager's Assistant

    Hi
    I am putting together an MSS role for Personal Assistants of managers....ie instead of using chief positions as standard I'm creating new OADP entries and assigning them to iViews (eg attendanceoverview)....all good until I came to the Team Calendar.
    The Team Calendar properties doesn't have a entry for the organizational structure view. Instead it is configured in the IMG and the config doesn't seem conducive to doing this. 
    Anyone done this and able to share the info....Or anyone with some good ideas.....I can workround it by just creating new entries in the dropdown list in the Team Calendar iView but both Manager and Assistant will see each others entries....
    TIA
    Stu

    No.  Unfortunatley not
    We just worked around it and put 4 entries into the Team Calender drop down ....
    - Direct Reports
    - All Employees
    - Direct Reports (Mgr Assistant)
    - All Employees (Mgr Assistant)
    Not a v good solution.... if anyone can point out how to configure it differently I'd be gr8ful

  • MSS Team calender in acting position

    Hi Gurus,
    this is regarding MSS team calender, an employee with his actual position X , if he acts in a acting position Y and if he logs in MSS then he should be able to see all the subordinates under position Y, but presently he cannot see any team under position Y,
    can any one please let me know where can be the problem is?
    Thanks in advance,
    Sud.

    Dear Raphael,
    Now I checked team view in MSS. Manager is able to see all the employees & their leave + travel in separate colours.
    But in attendance overview, nothing is getting display.
    So functionality of  Team Calendar is only to get information to manager who are on leave & who are present in each month.
    Is there any more functionality available in Team Calendar.
    Thanks,
    Namsheed.

  • 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

  • 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

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

  • Attendance (IT 2002) - to display in team calender

    Dear All,
    Once a maanger has approved the over time in MSS, he no longer has access to view the approved records. I went through the documentation where i read that team calender supports both IT 2001 & IT 2002. Right now in the team calender only IT 2001 is getting updated. Please guide me on how should I proceed so that the manager is able to view the overtime that he has approved
    Regards
    Minal

    Hi
    Records exist in the backend. the problem is the team calender is not reflecting the data. As of now only approved leaves getting reflected in team calender.
    Regards
    Minal

  • Insert team calender to tasks view in UWL

    Hi All,
    I am trying to configure the UWL:
    The Task iView for an MSS user should have a link to the team calender (like in the MSS team overview).
    Like ->show team calender
    Any idea on how to do that?
    I tried the iView properties but haven't found any clue.
    Maybe the problem lies more in the workitem?

    Hi,
    I would probably configure a new custom action (=new button") for the work item that would be displayed in the work item details (similarly than you have for example the "Launch web dynpro" or "Open task" buttons (or whatever you have visible there). This action would launch the team calendar application.
    This requires a bit of UWL XML configuration (for your workflow task(s)). I am not sure if you are familiar with it. If you are, then the above explanation should give you the starting point.
    Regards,
    Karri
    Edited by: Karri Kemppi on Apr 27, 2010 1:52 PM

  • Portal Performance is Very Slow..Pls Help

    Hi to all.
    Our machine is Sun280R - Sun Solaris 8..
    Using Oracle 9iAS 9.0.2.0.1..
    Our portal is 9.0.2.0.1 Release 2.
    All installed in one machine (infs/apps)
    We have difficulties with the Portal performance.
    It takes slow time to login, and view the pages.
    and when we click the Customize button, it will be more slower (50 sec)...
    Can anybody help?
    How to check what is wrong here?
    Pls..this is urgent..
    Thanks.

    you need to type in the name of a valid tablespace in the database where you are trying to install the owa_perf tables.
    Like it says in the setup guide (readme.htm) that comes with the scripts..
    "During the installation process, you will be asked for three tablespace destinations for:
    * the log tables
    * the log indices
    * the log materialized views
    It is recommended, though not mandatory, that you create and specify individual tablespaces for the storage of these elements. You cannot use DEFAULT as a valid tablespace for these responses."
    ...so you need to type in the name for a valid tablespace for each entry, you can type the same name but it asks you for three choices because each one can get large when your logs are large, asking for them separately would allow you to place them on separate disks or tablespaces that you could drop independently of other data.

  • MSS-Portal link with R/3

    Hi folks,
    We have a QA environment or the MSS-Portal running, linked to our R/3 QA system. It's working fine. Since we are preparing some tests for an SAP Upgrade phase, we need to link the MSS-Portal to a new R/3 server.
    The basis guys created a new Portal connector, but it seems that additional settings are required since the iViews are still showing information from the original R/3 system. Also, if I create an ISR, the information is shown through IQS8 in the original R/3, not the new one.
    Help on "what" and "how" to configure/change settings will be appreciated.
    Thanks!!

    Andrey :
    You may also want to check 'Jco Destination' to make sure the connection is actually linked to the new SAP R3 system instead of the old one.
    Rgds.

  • Portal performance monitoring scripts : (Unable to generate reports)  HELP

    Hi,
    Using 10.1.2.0.0
    I followed README.html document to load the logs files to generate reports for Portal Performance.
    First of all while running loadlogs.pl I keep getting the following error. I even tried adding -nodirect but still gets the same error. Don't know why. But it looks like there is some data loaded in OWA_LOGGER table
    C:\ORACLE_PRODUCTS\PORTAL_AS\portal\admin\plsql\perf\loader>perl loadlogs.pl -logical_host localhost -connection owa_perf/owa_perf@orcl -http_logfile C:\ORACLE_PRODUCTS\PORTAL_AS\Apache\Apache\logs\error_log.1130457600 -webcache_logfile C:\ORACLE_PRODUCTS\PORTAL_AS\webcache\logs\access_log -oc4j_logfile C:\ORACLE_PRODUCTS\PORTAL_AS\j2ee\OC4J_Portal\application-deployments\portal\OC4J_Portal_default_island_1\application -nodirect
    25-Oct-05 13:20:17, Copying abc:C:\ORACLE_PRODUCTS\PORTAL_AS\Apache\Apache\logs
    \error_log.1130241600
    25-Oct-05 13:20:17, Loading C:\DOCUME~1\whitesox\LOCALS~1\Temp\abc_error_log.1130
    241600.20051025.132017
    25-Oct-05 13:20:21, Copying abc:C:\ORACLE_PRODUCTS\PORTAL_AS\j2ee\OC4J_Portal\a
    pplication-deployments\portal\OC4J_Portal_default_island_1\application
    25-Oct-05 13:20:21, Loading C:\DOCUME~1\whitesox\LOCALS~1\Temp\abc_application.20
    051025.132021 -nodirect
    SQL*Loader-350: Syntax error at line 127.
    Token longer than max allowable length of 258 chars
             end",
            ^
    25-Oct-05 13:20:22, Copying abc:C:\ORACLE_PRODUCTS\PORTAL_AS\webcache\logs\acce
    ss_log
    25-Oct-05 13:20:31, Loading C:\DOCUME~1\whitesox\LOCALS~1\Temp\abc_access_log.200
    51025.132022Then I ran reports.sql but I don't see any reports being generated, but running this script did populate some other tables. I tried running some other scripts also but somehow I don't see any reports being generated as opposed to what is said in the README.HTML document i.e. "A sample web page (reports.html) is included which provides links to the generated reports.". How really I get to see the reports, where are the reports generated, is it something else that I am missing. No matter what script I run I don't see any report being generated. The document is not so clear. Can someone please help me out here. Thanks

    Hi!
    You have to change to directory
    ORACLE_HOME$/portal/admin/plsql/perf/scripts
    (you can find reports.sql in it) before you run reports.sql script!
    It will produce several .txt files.
    After running the script just open reports.html, that will point the generated files.
    A better place to ask questions like this:
    Portal Performance and Scalability
    http://forums.oracle.com/forums/forum.jspa?forumID=15

  • Portal performance report

    Hi Portal GURUs,
    We have configured Portal Activity Reports for monitoring hits but we required to monitor Portal Performance.
    Please suggest me if there is any in built features to get these reports?
    Regards
    Kiran

    Hi,
    you can monitor the portal performance by using  CCMS (and GRMG).
    Below link will also help you.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/48fead90-0201-0010-6e83-b43f5dd4d338https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3ba6a290-0201-0010-d684-c94b1c765ae9
    Raghu

Maybe you are looking for