Error in leave encashment

Dear Experts,
For some of the employees leave encashment is paying excess for the month of january 2012, we are using Info type 416 for this
Excess amount is as follows
Rs 28.34
Rs 20.59
Rs 12.11
Rs 9.96
Rs 13.99
Rs 5.65
Please let me know the solution
Thanks in advance

Hi
I never worked on +ve TM but how ever try this config may be it may help you
PA - PD - Leave Compensation - V_T556U (give your com test and link to your absence quota)
Copy Wt from MLE0 to custome wt
VV_52D7_B_0416_AL0
In WT Char give days under Timeunit/measure and leave indirect val tab empty
V_T512Z
Go to payroll india - Time quota comp - VV_T556W_A__AL0
Add in PE51 your WT
Go to table v_512w_b and there choose your WT and under cumulation tab give valuatiion base 01,your wt,% Rate 800(i.e 8 Hrs)
Go to pa30 and select 0416 and try giving no.com days and check
This config is i worked in Negative mgt so just try whether will it be usefull for +ve
Thanks

Similar Messages

Portal error for Leave Encashment

Dear All,
We are in EHP6 and 7.31
We are getting error for Leave Encashment.
Regards
Anoku

Hi Anoku,
Please refer to the following thread which talks about the same kind of issue:
ess showing error IRequestDispatcher
Hope this helps!!!
BR,
Anurag

How to Handle Leave Encashment in Oracle Payroll

Dear Friends,
Can any one pls let me Know,How to Handle Leave Encashment in Oracle Payroll.. Pls help me on this..
with regards
Veeru

Hi Vinayaka Prabhu,
Thank you for the information .. Here is the Scenario.. we are implementing HRMS Version12i to an real Estate Company in an Middle east.. Client Requirement is Suppose Annual Leave Entitlement for an employee is 14 days at the end of the year,employee can encash the leave other wise he can carry forward to the next year .. Can you pls help me out on this ..
Note: If you have any setup document can you pls share it with me ([email protected])..
with regards
veeru

Error in Leave Request:ESS

Hi All,
I am getting a error in Leave Request Iview in ESS application.
I am using EP 7.0.
I have done the required settings in R/3.Created Rule group,added applciation parameter in iview,JCos are working.
But still I am getting this error.
If anybody has the idea on how to solve it please help.
The initial exception that caused the request to fail, was:
java.lang.NullPointerException
     at com.sap.xss.hr.lea.blockcale.VcBlockCale.transferFixedBcData(VcBlockCale.java:371)
     at com.sap.xss.hr.lea.blockcale.VcBlockCale.onInit(VcBlockCale.java:262)
     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:756)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
     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:1289)
     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
     at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:193)
     at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
     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:756)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
     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:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     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)
Regards,
Sumangala

Hi,
Please check whether that particular employee having all the necessary authorization or not in ECC side.
Also mention the ECC and ESS version with SP level.
Regards,

Leave Encashment in ESS MSS NWBC

Hi all gurus,
We have implemented Leave request, Travel request, PMS via ESS using standard SAP role SAP_EMPLOYEE_ESS_WDA_3.
Now we got a requirement to do Leave Encashment in ESS MSS through NWBC.
How can I do that.? Is there any standard roles by which I can get Leave Encashment Application in ESS ??
Give me some light to this.
Regards,
Namsheed.

Hi Shankar,
Thanks for the info.
That means it can't be done in NWBC.?
What is the alternative solution for this.?
I am in a bottle neck. Not in India now.
I am in Bhutan for this implementation. In spro also I saw Leave Encashment under India only.
What is the possible solution for this.?
Thanks a lot Shankar for prompt reply.
Namsheed.

The leave encashment exemption

Hi,
the leave encashment exemption has not subtracted from the income .
its coming in /4e7 .
but not reflected in /133
Regards

/130 is update for the month in which leave enchantments entry is there.
like leave enchantments entry in IT0416b is for the month of april and we have to run the payroll of dec.
when we rum the payroll and chcek the log
/130 having the correct value for april month
but its not reflect in dec rt.
Regards

User Exit For Leave encashment

Hi all,
Can i know which is the user exit for leave encashment.
I am new to user exit .Please let me know.
Regards
janhavi

Hi,
User exits allow developers to access and modify program components and data objects in the standard SAP System. On upgrade, each user exit must be checked to ensure that it conforms to the standard system.
There are the following types of user exit:
User exits that use INCLUDEs -
These are customer enhancements that are called directly in the program.
User exits that use tables -
These are used and managed using Customizing.
Please see the link below:
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
Hope this helps.
Reward points if useful.
Regards,
Amit

Workflow for Leave Encashment

Hi,
I have to know is there any standard workflows or tasks for leave encashment.if no how should i proceed for this requirement.
please tell me the Business Object for Leave Encashment

Hi
pls find very useful links to HR & Cross Apps work flows.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMPA/BCBMTWFMPA.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMCA/BCBMTWFMCA.pdf
good luck!

Error During Leaving Action.

hi Gurus,
While doing leaving action for an UK employee, the system throws following error.
" The object currency of CTR CARK/3000250306 is USD and not GBP".
please guide me what to do.

Hi
IT0105 is infotype, under this u can create the no. of subtype if 10 is not exesting means there is no date in types of communication pls check it once
Regards
suresh

Error in Leave Approval Workflow

Hello Experts,
I'm Using Standard Workflow WS0040077 for Leave Approval . I Activated the Event Linkage in SWEL .Did General Task in Agent Assignment . But when i run transaction PA30 . i get this error in SAP Inbox.
Following error occurred:
00 341
RFC_NO_AUTHORITY
Message text:
Runtime error RFC_NO_AUTHORITY has occurred
SAP System: EDV
Client: 100
Event container appended as attachment.
Event linkage not changed.
Event stored temporarily.
Events can be redelivered via event queue
administration (transaction SWEQADM).
so what should i do to solve this problem.

Hi,
Have you checked the workflow config in SWU3? It sounds like there may be a problem with the LOCAL RFC destination used by workflow. Click the 'Start Verification Workflow' button in SWU3 as a health check.
Also, are you testing this in the right client?
cheers
Paul Bakker

Run time error iview 'Leave Overview' in ESS - Pl Help

Hi Gurus ,
We are getting run time error when we
click the 'Leave Overview' in
ESS.
when emloyee applies for leave he may
need to wait for aproval during
that time he cannot access the 'leave
overview' screen he will be
facing run time error .
because of this run time error system
performance become very slow .
please help me .i will give points for valid answers .
:-Suneetha reddy
Edited by: Sunitha Reddy on Mar 26, 2008 9:47 AM

Hi ,
I am soory for late reply ,
I changed the runtime parameter to 1200 and monitaring the system .
Now there is no Run time error but still Leave overview is taking time .
Please help
Thanks,
Sunitha

Strange error in Leave request

Hi Experts,
I am getting one error in production for the leave request. When one particular employee applies for the leave, he is able to apply for the leave properly. After applying leave, his leave request status changes to sent. when i checked in the report "RPTARQDBVIEW" about that particular employee's leave document, workflow was not attached to that document. This is happening everytime whenever he applies for the leave. Workflow is not getting triggered whenever he applies. Its working fine for the other employees similar to him.
Can you help me regarding this. This is becoming critical.
Thanks
Sameer
One thing i found that, its happending for few more employees. and common thing about them is that all are getting error "Unable to send the request with this approver" while applying leave. when they go back and again apply then leave request is going. For all these employees their manager is not belongs to india org unit. And this ESS we have configured for india employees.
Edited by: sameer dhuke on Jul 17, 2009 7:41 PM

Hi,
This comens when the approral is not assign to the User-ID
Say "A" is the employee and you need set "B" is manager for "A"
Then folloiwng things you need to do .
in the PA30 chekh the "Org Assig" for "A".
The org unit for "A" ( employee ) and "B" ( manager ) should be same .
then PO10 give the Org Unit and check the following entry .
19.02.2009     31.12.9999     B     003     Incorporat     S     50006006     056607A     0,00
19.02.2009     31.12.9999     B     012     Is managed     S     50006006     056607A     0,00
you can see the "50006006" is the possition ( Is managed )
Then you need to go PO13 give the possition no and click up on 'Overview"
19.02.2009     31.12.9999     A     003     Belongs to     O     50129078     New org unit                        0,00
01.04.2007     31.12.9999     A     008     Holder     P     00001070     (Employee A)     100,00
01.01.2000     31.12.9999     A     011     Cost cente     K     00002009461000     Financial As     0,00
19.02.2009     31.12.9999     A     012     Manages...     O     50129078     New org unit     0,00
01.01.2000     31.12.9999     B     007     Is describ     C     50015243     AdmSup     0,00
Like this you can set the manager to employee

Java.lang.NullPointerException Error in Leave Request tab of ESS in Portal

Hello All,
I have configurted ESS/MSS on EP 7.01 SP03, but it is giving error in almost every tab.
When i navigate in to Employee Self Service < Working Time < Leave Request tab it ends up with error pasted below.
java.lang.NullPointerException
Same error appears for other tabs like Employee Self Service < Working Time <Quote Overview/Clocl In/Out Corrections
Any help to solve this issue will be highly appretiated.
Thanks
Vinit

Full exception chanin from NWA is as below
Exception occured during processing of Web Dynpro application sap.com/ess~lea/LeaveRequest. The causing exception is nested.
[EXCEPTION]
java.lang.NullPointerException
at com.sap.pcuigp.tracking.BTrackingComp.isValuePackSystem(BTrackingComp.java:290)
at com.sap.pcuigp.tracking.BTrackingComp.onInit(BTrackingComp.java:206)
at com.sap.pcuigp.tracking.wdp.InternalBTrackingComp.onInit(InternalBTrackingComp.java:173)
at com.sap.pcuigp.tracking.BTrackingCompInterface.onInit(BTrackingCompInterface.java:115)
at com.sap.pcuigp.tracking.wdp.InternalBTrackingCompInterface.onInit(InternalBTrackingCompInterface.java:124)
at com.sap.pcuigp.tracking.wdp.InternalBTrackingCompInterface$External.onInit(InternalBTrackingCompInterface.java:198)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.onInit(FcEmployeeServices.java:219)
at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServices.onInit(InternalFcEmployeeServices.java:273)
at com.sap.pcuigp.xssutils.pernr.FcEmployeeServicesInterface.onInit(FcEmployeeServicesInterface.java:135)
at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface.onInit(InternalFcEmployeeServicesInterface.java:198)
at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface$External.onInit(InternalFcEmployeeServicesInterface.java:258)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
at com.sap.xss.essceservices.vcceassignmentselection.VcCEAssignmentSelection.onInit(VcCEAssignmentSelection.java:235)
at com.sap.xss.essceservices.vcceassignmentselection.wdp.InternalVcCEAssignmentSelection.onInit(InternalVcCEAssignmentSelection.java:174)
at com.sap.xss.essceservices.vcceassignmentselection.VcCEAssignmentSelectionInterface.onInit(VcCEAssignmentSelectionInterface.java:162)
at com.sap.xss.essceservices.vcceassignmentselection.wdp.InternalVcCEAssignmentSelectionInterface.onInit(InternalVcCEAssignmentSelectionInterface.java:144)
at com.sap.xss.essceservices.vcceassignmentselection.wdp.InternalVcCEAssignmentSelectionInterface$External.onInit(InternalVcCEAssignmentSelectionInterface.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:754)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289)
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:1289)
at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:593)
at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:865)
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:319)
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:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
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)
Edited by: Vinit Soni on Aug 27, 2010 7:59 AM

Critical error in leave request

Dear All,
Following error is getting only for some users when they click on Leave request link in E-portal. We have EP 7.
I have searched previously posted threads for this type of issue & checked for points suggested in those threads. But everything seem to be ok.
1. Leave request config is proper
2. WEBMO maintained is ok.
3. Infotype 0105 subtype 0001 is maintained & ESS role is assigned using Tcode HRUSER.
4. Leave quota is updated in 2006.
Error I am getting
Critical Error
A critical error has occured. Processing of the service was terminated. Unsaved data has been lost.
Contact your system administrator.
       User does not exist in this period                                 , error key: RFC_ERROR_SYSTEM_FAILURE
       User does not exist in this period                                 , error key:
RFC_ERROR_SYSTEM_FAILURE:com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException:      User does not exist in this period                                 , error key: RFC_ERROR_SYSTEM_FAILURE
For other users entire leave request & leave approval process is happening properly. leaves are also getting updated in 2001. Then why the error is for only few users?system has gone live & people are not able to apply leaves
Please help.
Thanks & Regards,
Swapnali
Edited by: Swapnali Kamerkar on Sep 14, 2010 2:28 PM

Hi Siddharth & Jiggar,
Thanks for your immediate response.
Yes, I had already checked this scenario giving SAP_ALL authorization, same error is coming & I don't think so authorization would be the problem cause for other users entire leave request & leave approval is happening properly with assigned ESS Role.
Also respective user Id was already created in R/3 & maintained in infotype 0105 subtype 0001 using HRUSER Transaction. Same user ID was created in portal & employee is logging-in with that Id. Validity period is also proper.
Also I want to put one more point here that whenever I don't maintained user Id in 0105 subtype 0001 for a particular employee & if he is logging-in with that ID, Error coming is only 'User 'XY' doesn't exist in this period'. where XY is user ID.
But for the case in qustion even if Id is maintained in 0105, error coming is 'User doesn't exist in this period ...RFC_ERROR_SYSTEM_FAILURE'.
Also all other applications like time account,payslips, personal information are working fine for that user.
Waiting for your replies.
Thanks & Regards,
Swapnali
Edited by: Swapnali Kamerkar on Sep 15, 2010 8:36 AM

Error in Leave Request

Hi,
We are using the standard Leave application -- HRESS_A_PTARQ_LEAVREQ_APPL and the application is working fine except for one employee. Seems like Basis issue but it must be for all the employees. PERNR is mapped and all the master data is correct, Payroll area not locked, user is also not locked. Unable to find out the issue. reply will be appreciated.
Regards,
Abdullah khan

Hi,
There is no issue of authorizations as i have checked by assigning SAP_ALL.
Category               ABAP Programming Error
Runtime Errors         TIME_OUT
ABAP Program           CL_PT_REQ_ATTABS_ITEM_SELECTORCP
Application Component PT
Date and Time          28.03.2014 16:34:37
|Short text                                                                                        |
|    Time limit exceeded.                                                                          |
|What happened?                                                                                    |
|    The program "CL_PT_REQ_ATTABS_ITEM_SELECTORCP" has exceeded the maximum                       |
|     permitted runtime without                                                                    |
|    interruption and has therefore been terminated.                                               |
|                                                                                                  |
|What can you do?                                                                                  |
|    Note down which actions and inputs caused the error.                                          |
|                                                                                                  |
|                                                                                                  |
|    To process the problem further, contact you SAP system                                        |
|    administrator.                                                                                |
|                                                                                                  |
|    Using Transaction ST22 for ABAP Dump Analysis, you can look                                   |
|    at and manage termination messages, and you can also                                          |
|    keep them for a long time.                                                                    |
|Error analysis                                                                                    |
|    After a specific time, the program is terminated to make the work area                        |
|    available to other users who may be waiting.                                                  |
|    This is to prevent a work area being blocked unnecessarily long by, for                       |
|    example:                                                                                      |
|    - Endless loops (DO, WHILE, ...),                                                             |
|    - Database accesses with a large result set                                                   |
|    - Database accesses without a suitable index (full table scan)                                |
|                                                                                                  |
|    The maximum runtime of a program is limited by the system profile                             |
|    parameter "rdisp/max_wprun_time". The current setting is 600 seconds. If this                 |
|     time limit is                                                                                |
|    exceeded, the system attempts to cancel any running SQL statement or                          |
|    signals the ABAP processor to stop the running program. Then the system                       |
|    waits another 60 seconds maximum. If the program is then still active,                        |
|    the work process is restarted.                                                                |
|How to correct the error                                                                          |
|    Programs with long runtime should generally be started as background                          |
|    jobs. If this is not possible, you can increase the system profile                            |
|    parameter "rdisp/max_wprun_time".                                                             |
|                                                                                                  |
|    Depending on the cause of the error, you may have to take one of the                          |
|    following measures:                                                                           |
|    - Endless loop: Correct program;                                                              |
|    - Dataset resulting from database access is too large:                                        |
|      Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table                      |
|      (for example);                                                                              |
|    - Database has unsuitable index: Check index generation.                                      |
|                                                                                                  |
|    If the error occures in a non-modified SAP program, you may be able to                        |
|    find an interim solution in an SAP Note.                                                      |
|    If you have access to SAP Notes, carry out a search with the following                        |
|    keywords:                                                                                     |
|                                                                                                  |
|    "TIME_OUT" " "                                                                                |
|    "CL_PT_REQ_ATTABS_ITEM_SELECTORCP" or "CL_PT_REQ_ATTABS_ITEM_SELECTORCM008"                   |
|    "SEL_REQS_BY_INFOTYPE_DATA"                                                                   |
|                                                                                                  |
|    If you cannot solve the problem yourself and want to send an error                            |
|    notification to SAP, include the following information:                                       |
|                                                                                                  |
|    1. The description of the current problem (short dump)                                        |
|                                                                                                  |
|       To save the description, choose "System->List->Save->Local File                            |
|    (Unconverted)".                                                                               |
|                                                                                                  |
|    2. Corresponding system log                                                                   |
|                                                                                                  |
|       Display the system log by calling transaction SM21.                                        |
|       Restrict the time interval to 10 minutes before and five minutes                           |
|    after the short dump. Then choose "System->List->Save->Local File                             |
|    (Unconverted)".                                                                               |
|                                                                                                  |
|    3. If the problem occurs in a problem of your own or a modified SAP                           |
|    program: The source code of the program                                                       |
|       In the editor, choose "Utilities->More                                                     |
|    Utilities->Upload/Download->Download".                                                        |
|                                                                                                  |
|    4. Details about the conditions under which the error occurred or which                       |
|    actions and input led to the error.

Error in leave encashment

Similar Messages

Maybe you are looking for