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

Similar Messages

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.

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

Display residual leave in team calender

Hi,
when clicking in the team calender on a certain absence details will be shown below.
The detail data does not include the residual leave although we have a screenshot where
the residual leave is shown.
Does anyone know how to make the residual leave to be displayed?
Thanks in advance!
Regards
Chris

Chris,
you may check these badis
PT_ABS_REQ
PT_GEN_REQ
Thanks
Bala Duvvuri

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

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. To do so, enter the required view group or grouping ID in the relevant field.
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.
VIEWGROUP VIEWID
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

Team calender - change of colour

Hi
The team calender is refelecting both IT 2001 & 2002 in the same colour. Is there any way i can change the colour code of the display.
Please help me.
Regards
Minal

Hi,
Have you looked at the BADI: BAdI PT_ABS_REQ
It can be reached from the customizing for the TeamCalendar.
<Integration with Other mySAP.com Components ->Manager Self-Service (mySAP ERP) -> Working Time -> Team Calendar -> BAdI: Control Processing of Leave Requests>.
Best regards,
Lars

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.

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

Team Calender Error.

Dear All,
EHP6 and 7.31
SP21
I have configured Team Calender (Rule group and all required tables).
There is an error in Team Calender.
500 SAP Internal Server Error
ERROR: Exception condition "COMMUNICATION_ERROR" raised. (termination: RABAX_STATE)
Regards
Somu

Hello Somu,
You would be getting the dump in R/3 also, please attach the same here.
Could you update IGS to the latest version and config IGS as described
in the notes below:
896400    Upgrade your integrated IGS 7.x installation
844669    Profile parameter of IGS as of Version 7.x
454042    IGS: Installing and Configuring the IGS
You can check your patch level as follows:
- Start transaction SA38 (or SE38)
- Run the report GRAPHICS_IGS_ADMIN
- Choose the RFC destination, IGS_RFC_DEST should be the default
- Select Status
This page shows the versions of the IGS components. The number before
the last number shows the patch level. We recommend to update it to
the latest available if not done so yet, based on the practice it
solves number of issues (and according to SAP note 514841, step 1).
Best Regards,
Deepak Kumar Sharma
Active Globol Support..

Errors in the team calender

Hi,
We are facing two problems in the Team Calender(Leave Approval) application:
1. We want active employees to be displayed only, but seperated employees are also there.
2. The calender shows Leave details of current month and future months only. Not showing previous months leave details.
Reagrds
Anumit

check in the table V_PTARQ_TCONSTR
options available
Start of Period
Display of Leave
Definition of Start of Period
Specifies the way in which a period is calculated.
Use
You can specify the period for which absences are displayed in one of the following ways:
As of Current Date:
The period you enter applies as of the current system date.
As of Start of Current Calendar Period:
The period you enter is calculated as of the start of the specified unit, for example, as of the start of the current week or month.
As of Start of Current Period
The specified number of periods is calculated as of the start of the specified payroll period.
The time frame starts as of the current date in each case.
for terminated employee, please check his infotypes i m surprised he is being shown stil in team calendar!!

Display data (dropdown for years) in Team Calender

Hi,
Presently, in the dropdown menu of the Display data of team calender 3 years are populated "2007, 2008, 2009". Can anyone pelase let me know how to configure this to display dropdown to display till 2011?
regards,
pinki

Hi Siddharth,
Which code..can you please let me know that?
regards,
pinki

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

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.

Regarding Leave & Team calender

Similar Messages

Maybe you are looking for