MSS Team Calander Critical error "There is no processing process for absence type XXXX, rule group ZXXXXXX (40 XXXXXXXX)"

[Former Member]

Dear Guru's,

I have a peculiar issue where manager tries to click on team calander, he gets below error depicting 1 employee.

There is no processing process for absence type XXXX, rule group ZXXXXXXX (40 XXXXXXXX). this employee was a call center employee with ESG as XX with rule group say ZXXXXXXX now he is salaried employee with ESG YY with rule group ZYYYYYYYY.

Normally we traced these kind of issues with a WF reports PTARQDBVIEW and sort the issue related to absences by deleting the work items.

In the above case i am not finding any work item with improper status to delete also the rule group validity is 31.12.9999.

Also no discrepancy found in IT2006 also

Request your help.

Thanks,

PR

[Former Member]

Critical Error

A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.

Please contact your system administrator.

		There is no processing process for absence type 0105, rule group Z4000001 (40 00017481)
		There is no processing process for absence type 0105, rule group Z4000001 (40 00017481):com.sap.pcuigp.xssfpm.java.FPMRuntimeException: There is no processing process for absence type 0105, rule group Z4000001 (40 00017481) at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:112)  at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:136)  at com.sap.xss.ser.tecl.fc.FcTeamCalendar._addMessages(FcTeamCalendar.java:702)  at com.sap.xss.ser.tecl.fc.FcTeamCalendar._getData(FcTeamCalendar.java:769) at com.sap.xss.ser.tecl.fc.FcTeamCalendar.gotoPage(FcTeamCalendar.java:371) at com.sap.xss.ser.tecl.fc.wdp.InternalFcTeamCalendar.gotoPage(InternalFcTeamCalendar.java:315)  at com.sap.xss.ser.tecl.fc.FcTeamCalendarInterface.gotoPage(FcTeamCalendarInterface.java:219)  at com.sap.xss.ser.tecl.fc.wdp.InternalFcTeamCalendarInterface.gotoPage(InternalFcTeamCalendarInterface.java:290)  at com.sap.xss.ser.tecl.fc.wdp.InternalFcTeamCalendarInterface$External.gotoPage(InternalFcTeamCalendarInterface.java:378)  at com.sap.xss.ser.tecl.vc.VcTeamCalendarInterface.gotoPage(VcTeamCalendarInterface.java:352)  at com.sap.xss.ser.tecl.vc.wdp.InternalVcTeamCalendarInterface.gotoPage(InternalVcTeamCalendarInterface.java:323)  at com.sap.xss.ser.tecl.vc.VcTeamCalendarView.onActionGotoPage(VcTeamCalendarView.java:426)  at com.sap.xss.ser.tecl.vc.wdp.InternalVcTeamCalendarView.wdInvokeEventHandler(InternalVcTeamCalendarView.java:411)  at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)  at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)  at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)  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:333)  at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)  at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)  at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)  at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:192)  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:864)  at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)  at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1374) at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:326)  at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:872) 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:333)  at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)  at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)  at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)  at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:192)  at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)  at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)  at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)  at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)  at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)  at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)  at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)  at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)  at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)  at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)  at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)  at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)  at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

[former_member443899]

I know this is a year old, but just in case. Have you gone to table V_T554S_WEB which is used in Leave Request and Team Calendar areas of the IMG.

In V_T554S_WEB it sounds like you just have to make sure there is a rule group z400001 with an try for absense type 0105 whatever that is in your system for the approrpriate PSGrouping.  Without seeing the system I'd be guessing about what (40 00017481) means but would assume 40 is the ps grouping.

Good luck hope this was fixed a year ago.