Attendance regularisation in ESS
Hi All,
We have a requirement from business which alows the employee to regularise attendance in case they are out of office on officail work. In this case the employee will come back and log his regularisation request which will go to superior for approval.
On approval the resp Atendance infotype will be updated.
Is ther a standard workflow, service available in ESS . We are working on BP 50.4 and ECC 5.0.
Your help is highly appreciated.
Regards
PN
hi Ryan,
Thanks for the reply. I had a look at Record working times iview .
Record working times has a relation to Time management rite ? Do we have to implement Time management for the same ?
Also would the entry in record wokring times update 2002 infotype ( attendance ) .
Appreciate your help
Regards
PN
Similar Messages
-
Error Not enough quota 30 for attendance/absence in ESS Leave Request
Good Morning
I am trying to create a "Leave Request" using ESS with "Floating Days". It has a cuota manual. When trying to create the leave request in ECC all works fine, but when trying to create the same leave request in ESS the following error occurs:
Not enough quota 30 for attendance/absence 0261 on 05.03.2008 for personnel no. 20001140
Some can help me?
Best Regards,
WilmanHi,
I would suggest the following :
Step1: Check your IT 2006/IT 2007 for your Absence and Attendance Quotas.
Step 2: You can also verify the same information using the PT50 transaction ( quota Overview)
Step 3: By doing the above you ensure that the person has the required quotas.
Step4: logon to ESS and do the request for leave.if it does not let you, then there is some problem in the config in the ESS. I cannot tell you this from top of my head. We need to look into the portal to see what exactly the problem.
regards
Vijay -
TEM Workflow for "Approval of Employee's attendance booking"
Dear All,
Is there any special configuration point, which I may be missing on, in order to trigger the standard workflow " Approval of Employee's Attendance Booking" thru ESS (t-code: PV7I)
The problem that I am facing is that the workflow is not getting triggered and direct attendance booking happens when I click on Book Business Event Tab thru t-code PV7I
Please advise if there is any special authorization required for the same?
Regards,
ReemaAnd also
same table (T77S0)
SEMIN REQUE 1
May I know what is the error? -
Hi Gurus,
I am new to ESS-MSS, my client is implementign this module. Can any one please tell me what r the steps to active Work Flows to trigger mails for "Absence/Attendance application in ESS" by employee and for CATS Time sheet filling & its approvals by the manager inMSS& the related tasks.
r there any standard Work Flows to be called in R/3, if so , can any one tell me the path.
In Personnel Time Management -> Web Applications -> Leave Request
do we need to active the Work Flow templet and what input need to be given in fiends New requet____, Cancellation Request_____, & Change Request_____.
we are usign ECC6 in R/3.
Please help,
Thanks for all the help in advance.
Regards
PrasadHi Siddharth,
Thanks for the replay, but
System is asking for three Work Flow Teplets they are
Path: Personnel Time Management -> Web Applications -> Leave Request ->Link Absence Type & Workflow Teplets
WF ID of New Requst:
WF ID of Cancellation Request:
WF ID of Change Request:
Pleae let me know are there any standard Templets for this & also apart from this node is there any whare else we need to asign the WF Templets.
Regards
Prasad -
Java.lang.NullPointerException on ESS/MSS Team Calendar
Hi,
Whenever we try to access the Team Calendar or Attendance Overview in ESS or MSS, we get the error below.
IGS has been configured, and appears to be working fine from the HTTP administration. I have also tried pointing the portal to an IGS that I know works for Team Calendar, and still get the same error.
Many thanks in advance for any suggestions.
Regards
Jane
Error:
java.lang.NullPointerException
at java.io.Reader.<init>(Reader.java:61)
at java.io.InputStreamReader.<init>(InputStreamReader.java:55)
at com.sap.tc.graphics.igs.CallIgs.handleNonOk(CallIgs.java:276)
at com.sap.tc.graphics.igs.CallIgs.execute(CallIgs.java:321)
at com.sap.tc.graphics.igs.IgsComponent.callIgs(IgsComponent.java:86)
at com.sap.tc.graphics.igs.IgsComponent.callIgsIfNecessary(IgsComponent.java:104)
at com.sap.tc.graphics.igs.IgsImageComponent.getImageAsByteArray(IgsImageComponent.java:153)
at com.sap.tc.webdynpro.clientserver.uielib.graphics.impl.BusinessGraphics.createImage(BusinessGraphics.java:756)
at com.sap.tc.webdynpro.clientserver.uielib.graphics.uradapter.BusinessGraphicsAdapter$Image.getSrc(BusinessGraphicsAdapter.java:2148)
at com.sap.tc.ur.renderer.ie6.ImageRenderer.render(ImageRenderer.java:63)
at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
at com.sap.tc.ur.renderer.ie6.GridLayoutRenderer.renderGridLayoutCellFragment(GridLayoutRenderer.java:826)
at com.sap.tc.ur.renderer.ie6.GridLayoutRenderer.renderGridLayoutRowFragment(GridLayoutRenderer.java:424)
at com.sap.tc.ur.renderer.ie6.GridLayoutRenderer.renderGridLayoutFragment(GridLayoutRenderer.java:336)
at com.sap.tc.ur.renderer.ie6.GridLayoutRenderer.render(GridLayoutRenderer.java:79)
at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
at com.sap.tc.ur.renderer.ie6.GroupRenderer.renderGroupFragment(GroupRenderer.java:1194)
at com.sap.tc.ur.renderer.ie6.GroupRenderer.render(GroupRenderer.java:74)
at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
at com.sap.tc.ur.renderer.ie6.GridLayoutRenderer.renderGridLayoutCellFragment(GridLayoutRenderer.java:826)
at com.sap.tc.ur.renderer.ie6.GridLayoutRenderer.renderGridLayoutRowFragment(GridLayoutRenderer.java:424)
at com.sap.tc.ur.renderer.ie6.GridLayoutRenderer.renderGridLayoutFragment(GridLayoutRenderer.java:336)
at com.sap.tc.ur.renderer.ie6.GridLayoutRenderer.render(GridLayoutRenderer.java:79)
at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
at com.sap.tc.ur.renderer.ie6.ScrollContainerRenderer.renderScrollContainerFragment(ScrollContainerRenderer.java:619)
at com.sap.tc.ur.renderer.ie6.ScrollContainerRenderer.render(ScrollContainerRenderer.java:74)
at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
at com.sap.tc.ur.renderer.ie6.ViewContainerRenderer.renderViewContainerFragment(ViewContainerRenderer.java:134)
at com.sap.tc.ur.renderer.ie6.ViewContainerRenderer.render(ViewContainerRenderer.java:49)
at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
at com.sap.tc.ur.renderer.ie6.ViewContainerRenderer.renderViewContainerFragment(ViewContainerRenderer.java:134)
at com.sap.tc.ur.renderer.ie6.ViewContainerRenderer.render(ViewContainerRenderer.java:49)
at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
at com.sap.tc.ur.renderer.ie6.FlowLayoutRenderer.renderFlowLayoutItemFragment(FlowLayoutRenderer.java:596)
at com.sap.tc.ur.renderer.ie6.FlowLayoutRenderer.renderFlowLayoutFragment(FlowLayoutRenderer.java:244)
at com.sap.tc.ur.renderer.ie6.FlowLayoutRenderer.render(FlowLayoutRenderer.java:49)
at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
at com.sap.tc.ur.renderer.ie6.SingleColumnLayoutRenderer.renderSingleColumnLayoutCellFragment(SingleColumnLayoutRenderer.java:679)
at com.sap.tc.ur.renderer.ie6.SingleColumnLayoutRenderer.renderSingleColumnLayoutFragment(SingleColumnLayoutRenderer.java:253)
at com.sap.tc.ur.renderer.ie6.SingleColumnLayoutRenderer.render(SingleColumnLayoutRenderer.java:74)
at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
at com.sap.tc.ur.renderer.ie6.ScrollContainerRenderer.renderScrollContainerFragment(ScrollContainerRenderer.java:619)
at com.sap.tc.ur.renderer.ie6.ScrollContainerRenderer.render(ScrollContainerRenderer.java:74)
at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.UiWindowRenderer.render(UiWindowRenderer.java:52)
at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:434)
at com.sap.tc.webdynpro.clientimpl.html.renderer.uielements.base.RenderManager.render(RenderManager.java:133)
at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.sendHtml(HtmlClient.java:1055)
at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.fillDynamicTemplateContext(HtmlClient.java:455)
at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.sendResponse(HtmlClient.java:1240)
at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.retrieveData(HtmlClient.java:252)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doRetrieveData(WindowPhaseModel.java:595)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:156)
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:321)
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:150)
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.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1257)
at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:325)
at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:826)
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:321)
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:150)
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)Hi Jane Tooke,
Where as i got bit different issue with Team Calender like " Graphics Rendering Problem ", i was un able to see the Team Calendar. To resolve this issue have gone through the note : 704604. And finally we got it working. Try to go with this note.
Regards,
Kishore -
500 internal server error when using attendance in ESS
Hi All,
when the user clicks on attendance & its related activities in ESS, the following error is displaying frequently and after sometime it is working properly. why it is giving error frequently and how to avoid this error permanently?
Related Activities
500 Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
[Hide]
Error Summary
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.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 0, 0, 0(:main:, row:1, col:3)
at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2785)
at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
... 69 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)
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.0010.20061016112122.0000 (release=645_VAL_REL, buildtime=2006-10-21:16:12:34[UTC], changelist=421181, host=pwdfm101), build date: Tue Oct 16 13:15:01 BST 2007
J2EE Engine 7.00 patchlevel
Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_13-b06, vendor: Sun Microsystems Inc.
Operating system Windows 2003, version: 5.2, architecture: amd64
Session & Other
Session Locale en_GB
Time of Failure Thu Jan 24 11:58:41 GMT 2008 (Java Time: 1201175921417)
Web Dynpro Code Generation Infos
sap.com/pb
SapDictionaryGenerationCore 7.0010.20061002105236.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:52:59[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0010.20061002105236.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:53:17[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0010.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:40:44[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0010.20061002110128.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:58:51[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:39[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:32[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0010.20060719095619.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:50:36[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0010.20061002110156.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:55:32[UTC], changelist=419397, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0010.20061016112122.0000 (release=645_VAL_REL, buildtime=2006-10-21:16:19:13[UTC], changelist=421181, host=pwdfm101)
SapWebDynproGenerationCore 7.0010.20061002110128.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:59:00[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0010.20061016112122.0000 (release=645_VAL_REL, buildtime=2006-10-21:16:19:13[UTC], changelist=421181, host=pwdfm101)
sap.com/tcwddispwda
No information available null
sap.com/pb_api
SapDictionaryGenerationCore 7.0010.20061002105236.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:52:59[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0010.20061002105236.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:53:17[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0010.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:40:44[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0010.20061002110128.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:58:51[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:39[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:32[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0010.20060719095619.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:50:36[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0010.20061002110156.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:55:32[UTC], changelist=419397, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0010.20061016112122.0000 (release=645_VAL_REL, buildtime=2006-10-21:16:19:13[UTC], changelist=421181, host=pwdfm101)
SapWebDynproGenerationCore 7.0010.20061002110128.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:59:00[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0010.20061016112122.0000 (release=645_VAL_REL, buildtime=2006-10-21:16:19:13[UTC], changelist=421181, host=pwdfm101)
sap.com/tcwdcorecomp
No information available null
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to read deployment descriptor.
at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObject.initializeDeployableObjectParts(AbstractDeployableObject.java:297)
at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObject.getPart(AbstractDeployableObject.java:214)
at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObjectPart(DeployableObjectFactory.java:113)
at com.sap.tc.webdynpro.services.sal.deployment.api.WDDeployableObject.getDeployableObjectPart(WDDeployableObject.java:62)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:921)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:176)
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.createVACComponentUsage(FPMComponent.java:745)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:562)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:437)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:195)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:429)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:772)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:707)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
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:1248)
at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:353)
at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:551)
at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:595)
at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:826)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:723)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
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:160)
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.services.exceptions.WDRuntimeException: Failed to find deployment descriptor '.\temp\webdynpro\public\sap.com\msseeproarchiveddocuments\webdynpro\portalapp.xml' on the file system. Please check if the application 'sap.com/msseeproarchiveddocuments' is deployed correctly.
at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.getDeploymentDescriptor(DeployableObject.java:278)
at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObject.initializeDeployableObjectParts(AbstractDeployableObject.java:259)
... 58 more
Caused by: com.sap.tc.webdynpro.spi.WebDynproRuntimeException: Unexpected IO exception on GET<sap.com/msseeproarchiveddocuments>
at com.sap.engine.services.webdynpro.WebDynproContainer.getDeployableObject(WebDynproContainer.java:209)
at com.sap.engine.services.webdynpro.WebDynproRuntimeServiceImpl.getDeploymentDescriptor(WebDynproRuntimeServiceImpl.java:354)
at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.getDeploymentDescriptor(DeployableObject.java:274)
... 59 more
Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 0, 0, 0(:main:, row:1, col:3)(:main:, row=1, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 0, 0, 0(:main:, row:1, col:3)
at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:139)
at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:76)
at com.sap.engine.services.webdynpro.PApplication.load(PApplication.java:142)
at com.sap.engine.services.webdynpro.WebDynproContainer.getDeployableObject(WebDynproContainer.java:204)
... 61 more
Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 0, 0, 0(:main:, row:1, col:3)
at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2785)
at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
... 65 more
Thanks in advance,
vHi,
We were also having the same problem; but we couldnt find a specific solution for that problem.
But when we upgraded the ESS support packages to SP13 for some other reason this issue was also got resolved.
May be helpful i guess.
Regards,
Vijay -
Ess Time Sheet and Attendance Web Dynpro - ABAP or JAVA
We are determining the resources we will be needing for the HR - ESS Time Sheet and Attendance Module.
What is this module written in. ABAP Web Dynpro or Java Web Dynpro.
Many thanks,
Multiple replies welcome.
KenThe ESSTimeSheet is now called Record Working Time & for now it is still in WebDynpro JAVA.. looking at how complex the whole application is, it will really take some beating to rewrite the same in WDA.
~Suresh -
ESS attendance/absecen category code display only
Hello,
We need to displays only the attendance code only with no textual description when recording time.
When recording time for the employee through MSS (historically known as "ESS in MSS") using Java iview Approve Working Times in Business Package for Manager Self-Service (SAP ERP) 1.4. works OK we can see it displays the attendance code only with no texttual description.
But is not the same case when recording time directly from ESS using iwiew CATS regular/Record Working Time in Business Package for Employee Self-Service 1.41 is not OK beacise it shows code + textual description.
Is there a way in configuration or user-exit could change the ESS recording time displays the attendance code?
Thaniks in adavance.
Abel.Problem solved with an implicit enhacement at the end of function modue HRXSS_CAT_WD_RECORD:
ENHANCEMENT 2 ZENH_HRXSS_CAT_WD_RECORD. "active version
field-SYMBOLS: <FS_ST_FIELDLIST_TIMESHEET> TYPE HRXSS_CAT_RFC_FIELDLIST_DATA,
<fs_f4_value> type hrxss_cat_rfc_f4_values.
CONSTANTS: c_tec_name_awart type string value 'AWART'.
read table ET_FIELDLIST_TIMESHEET ASSIGNING <FS_ST_FIELDLIST_TIMESHEET>
with key tec_name = c_tec_name_awart.
check sy-subrc = 0.
loop at <FS_ST_FIELDLIST_TIMESHEET>-f4_values ASSIGNING <fs_f4_value>.
clear <fs_f4_value>-text.
endloop.
ENDENHANCEMENT. -
Hello,
I want to know what are all the standard applications that can be used to record the attendance of the employee on ESS. Further i wanted to know if any application can be built on ESS that can record the employee's attendance?
Thanks.
Regards,Hi,
Employees usually do not enter their attendances using ESS even though CATS can be used to record them. This is in negative time recording. But if the company wants to have a positive time recording there are various methods to record the attendances like swipe card systems (barcode cards, magnetic cards) (many SAP vendors sell the machines), bio-metric systems etc.
Once the data thus captured can be taken to various attendance infotypes and processed. -
ESS for Infotype 2002-Attendance
Infotype 2002-Attendance is not getting automatically updated from ESS, As we are making any entries or corrections in attendance from portal the changes are not automatically updating in Infotype 2002-Attendance. Please suggest a solution it is very urgent.
Hi go to T Code PTARQ and click on Psot deocuments which is report RPTARQPOST. First run the test run and check the documents are displayed or not.
You can check the ESS record is createed or not in the PTARQ --> Display document it will display the ESS records with status. -
Hi all
I am using ESS on SAP Portal.
I wonder if there is any standard iview I can use to wirte on infotype 2007. We use infotype 2007 to authorize overtime, but I didn't find any possibility to show and manage this infotype through the portal as for Absence 2001 or attendance 2002.
It seems that only display in available for 2007 infotype and not any update
thanks
andreaHi Friends ,
Please let me know implementing ESS/MSS Interview questions. Immediately.
Detail response will be highly appreciated.
Very Respectfully,
Sameer.
Pages: 1 -
HI,
can anybody suggest how to make ESS report based on clock in ,clock out , sick leave, RH etc with time management for a particular duration period in ABAP i.e.
If employee comes very late and goes very earily then i should count that day as a half day.
Regards,
AlokHi Alok,
please refer to tcode-PTARQ
kindly refer this threads and link for reference
http://www.sap-img.com/workflow/ptarq-tcode-not-available.htm
T-code PTARQ
Hope it helps
No Worries
KG -
Hi All,
I am getting an error message displayed on the portal in ESS business package whenever I enter the working time hours (that comes under Record Working Time application in Attendance workset) in the wrong format. Can anybody suggest me where do I go and change this error message.
Thanks,
Tomtom,
go to SPRO / Personnel Management / Employee Self Services / Service-Specific Settings / Working Time / Clock-In/Out Corrections / Processing Processes / Configure Output of Messages
(or maintain View V_HRWEB_TRS_MESS directly in SM30)
the SPRO Help gives you hints how to do that.
otherwise you can maintain MODIFY_APPLICATION_MESSAGES method of the PT_GEN_REQ Business Add-In
kr, achim -
Not able to get a link to the fron-end portal(ess) with back-end sap R\3 AB
Hi,
In the back-end i.e sap abap-hr , the required data (leave types) are available.But on front-end Portal(ESS) ,the drop-down menu in personal LOA forms shows only two leave types(personal & self-funded leave).i got struck in how to make few in remaining also viewable in the drop-down list.Can anyone help me on this?Bottom line,
to configure the Leaves on your portal you have to do.
1. Configure the Leave Types and all the customizing on T554S.
opc. If you want to have quota deduction, and everything else you should check V_T559L, T556C, T556A as well.
2. Configure the Leaves on the Portal. This is done on the IMG path colleague replied:
>Personnel Management
>Employee Self-Service
>Service-Specific Settings
>Working Time
>Leave Request
>Processing Processes
a. Create the Rule Groups - this step you just create them.
b. Adjust feature WEBMO - The feature WEBMO is used to select the rule group. Most of the times based on MOLGA and Ctrl. Center.
c. Define Processing Processes for Each Rule Group - define the processes such as how to record partial day leaves, details on to check PTREQ_HEADER tables for unposted leaves, and how to determine workflow's next agent (more info press F1 on each of these fields)
d. Specify Processing Processes for Types of Leave - Associate the Leaves from T554S that you want to show on the portal. This includes Absences and ATtendances. Here you define data such as if you are allowed to create leaves on the past, present and future; field customizing, and other details.
Since Time Management is an old part of SAP the F1 documentation is very complete so I really advise you to check.
Also, check http://wiki.sdn.sap.com/wiki/display/ERPHCM/LeaveRequestCustom+Messages
for how to have custom warning messages to show on your leaves.
I hope I have clarified.
Kind Regards,
Bentow. -
ERROR IN ESS AND MSS pages when deleting the superadmin role
hi all
According to my clent requirement i have worked with uwl for leave request.....for that i configured uwl and added uwl iview to the standard user role......after i have assigned standard user role to my manager.
but' after some time they told me that they need attendance overview and Reminder of dates and subordinate information.
After backend configuration i have assigned Mss role to the Manager,
i have made the settings for mss role with overview workset
Again overview contain-workoverview page it contains 1) uwl pabge 2)Attendance Overview 3)reminder of dates
Team- General information and so on
now my manager has following roles 1)ESS 2)MSS 3)Home (from the standard user role) 4) Home( by default i think from MSS role) 5) superadmin role
when ever i am removing the super admin role and standard user role for the manager i am unable to see the Attendance overview page and Reminder of dates page and i am unable to see the pages in ESS also.
getting error
Critical Error
A critical error has occured. Processing of the service was terminated. Unsaved data has been lost.
Contact your system administrator.
Read of object with ID portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.mss/com.sap.pct.erp.srvconfig.rod/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.reminderofdates failed.
plz ask me if any information is needed for this to solve my problem.
thankyou in advance.
if i am keeping that superadmin role(content ,user and system administration) All pages are opening.
thankyouSwapna,
Pls refer below links,
Unable to view notofications in MSS
Re: Critical Error when running MSS Work Overview Page
Manager Self Service Content are not showing up
Hope it should work now...
To give points, select the radio buttons on the left side under the name of the replier.
Regards,
Amarnath S
Maybe you are looking for
-
I've transferred my Itunes Media Library to a NAS drive, and pointed Itunes (using the advanced preferences tab) to the relevant folder on the NAS drive. I have done this to free up disk space on a computer I primarily use for work but which I use bo
-
How to zip a folder containing subfolders with files and download the zip file in silverlght 4
private void hbtnDownloadReceipt_Click(object sender, RoutedEventArgs e) try string Docpath = "ClaimsDetails/" + "20tech" + "/" + PaymentAdviceUNo; string dd = "ClaimsDetails/"; Uri uri = new
-
Why does my Illustrator logo look ragged/pixelated when I import into ID?
I have designed a logo in Illustrator, and when I place it into my ID document, it looks all ragged. When I use the magnifier tool to get a better look, sure enough, it is all pixelated and ragged. Does anyone know why this is so? Thanks!
-
While creating the SWCV we have the field production state.It is having the options like planned,started...etc.what is the difference between them. How it will effect in the design,config and transport? Thank you, regards, kar
-
KM - Portal Runtime Error - iView not found
Hi, When we try access the KM Documents, We are facing the following error Portal Runtime Error An exception occurred while processing a request for : iView : N/A Component Name : N/A iView not found: pcd:portal_content/every_user/general/eu_role/com