Fiori My Leave Requests error

Hi,
I try to implement Fiori Leave requests App.
The problem is in this error
But actually I use Leave requests 2 version:
And when I use Gateway client it tells ok 200
But in the browser I see 500 error
I've already cleared cach browser and used SMICM transaction, but no changes.
I would appreciate any suggestions.
Thank you.
Best regards,
Olga
Tags edited by: Michael Appleby

Pls try troubleshooting techniques as described in the blog
SAP Fiori LL11 - Consultants should know about OData troubleshooting.
I would also put an external breakpoint in the MPC classes and check why the Metadata call is failing.
Do you have the right authorizations to make the call?
thanks
A

Similar Messages

Leave Request ERROR

Hi
In ESS when the User is trying to click on Leave request - Error displayed as below :
error displayed as : "A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost. Please contact your system administrator. User HPSAPHR4 does not exist in this period User HPSAPHR4 does not exist in this period: com.sap.pcuigp.xssfpm.java.FPMRuntimeException: User HPSAPHR4 does not exist in this period at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:111) at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:121) at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.initPernr(FcEmployeeServices.java:203) at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.onInit(FcEmployeeServices.java:181) at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServices.onInit(InternalFcEmployeeServices.java:229) at com.sap.pcuigp.xssutils.pernr.FcEmployeeServicesInterface.onInit(FcEmployeeServicesInterface.java:135) at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface.onInit(InternalFcEmployeeServicesInterface.java:183) at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface$External.onInit(InternalFcEmployeeServicesInterface.java:243) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:774) at com.sap.xss.hr.lea.blockcale.VcBlockCale.onInit(VcBlockCale.java:261) at
siri

In addition to checking if employee is active etc,, you need to check that the user is connected to an employee. This happens in Infotype 0105 subtype 0001. The easiest way to check this may be via SE16N. Check table PA0105 and the usernam in field USRID.
BTW - the eror you describe will also happen if the user tries to access own data in portal.
The most usual error is the missing of IT0105 in my experience.
/Kirsten

SAP FIORI : LEAVE REQUEST ERROR in Launchpad.

Hello Everyone,
We have activated required services & RFCs' and they are working fine between NW Gateway Server 2.0 with 740 SP07 and Backend System ECC with latest patch 740 SP07.
While accessing the LEAVE APPLICATION from Launchpad, we are facing following problem :
1. Failed to start App,
2. Service LEAVEREQUEST failed. Contact your system administrator
Cannot call service with URL: /sap/opu/odata/GBHCM/LEAVEREQUEST;v=2
Not sure how to solve this issue.
Error Found at in SAP ;
1.No service found for namespace /GBHCM/, name LEAVEREQUEST, version 0001.
2.No service found for namespace /GBHCM/, name LEAVEREQUEST, version 0002.
3.No service found for namespace /SAP/, name SRA002_TIMESHEET_SRV, version 0001.
4.No service found for namespace /SAP/, name SRA007_BENEFITS_SRV, version 0001.
5.No service found for namespace , name SRA021_SRV, version 0001
Please guys I need help .. Thanks in advance.
Regards,
Gaurav.

Hi Tejas,
Thanks for your reply buddy.
I have checked once again in Transaction : /IWFND/MAINT_SERVICE , Leave Request Service is visible and ICF Nodes are also in green.
Please find below screen for the same.
Also, I mean I am not sure how to populate the metada but I have tried following please find below screens :
A.
B.
Please do reply, where else I can find the solution or check things.
Tejas, do you have any guide that you have made which has the step by step instructions which I can follow once again to check my configuration.
If yes then please do share it with me , that will be great help.
[Removed by Moderator]
Thanks Guys... Please do reply..
Regards,
Gaurav.
Message was edited by: Michael Appleby

Fiori leave request error "Could not start the app due to an internal error"

Hi,
I'm getting this error "Could not start the app due to an internal error" when accessing leave request application.
I don't get this error when I login and launch the app for the first time. when I go back to the home screen and select "My Leave Requests" app again, I get this error.
If I close the error message and do a browser refresh, everything is fine again for the first time, if I access the LR app again- same error .
Other apps are working fine.
I don't see any error in gateway or App logs.
below is the Request URI
/sap/opu/odata/UI2/INTEROP/ResolveLink?linkId=%27LeaveRequest-createLeaveRequest%27&shellType=%27FLP%27&formFactor=%27desktop%27
Service call info
Anyone with similar issue? any SAP notes?
we are on
UI2_731        100    0009    SAPK-10009INUI2731        SAP UI2 IMPL. FOR NW 7.31
UI2_FND        100    0009    SAPK-10009INUI2FND        SAP UI2 FOUNDATION
UI2_SRVC    100    0009    SAPK-10009INUI2SRVC        SAP UI INTEGRATION SERVICES
UI5_731        100    0009    SAPK-10009INUI5731        SAP UI5 TEAM PROVIDER ON 731
UISAPUI5    100    0009    SAPK-10009INUISAPUI5    SAP UI5
UI_INFRA    100    0009    SAPK-10009INUIINFRA        SAP UI INTEGRATION INFRASTRUCTURE
UIX01HCM    100    0003    SAPK-10003INUIX01HCM    UI for HCM Application
Tags edited by: Michael Appleby

Hi Masa,
We have required SAP notes now, we are on version 1.22.5.
It is still the same, working the first time I access the App, but subsequent access wont work until i refresh browser.
I've include the response and lpd/tile screens.
Thanks,
Phani

ESS Leave Request error - Processing of the service was terminated.

Dear All,
I am getting the below error on the leave request page in ESS
A critical error has occured. Processing of the service was terminated. Unsaved data has been lost.
Contact your system administrator.
Index: 0, Size: 0
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
let me know what could be the reason for this error?
Thanks

Suresh,
Please search in scn this has been discussed many times
Thanks
Bala Duvvuri

ESS Leave Request - Error while creating a leave record

Hi Friends,
Some of the ESS leave request(not workflow) has gone into error when the system tryies to create a leave record in background. I can view these error request using the report RPTARQDBVIEW. This happens when the background program(PTARQPOST) tries to create a leave record. In some cases the status of the leave request is set to error(the status attribute of the container element(Req) has the value Error),but we are not able to find what is actual error.Is there any log where we can check what is the problem? Please advice.

May be
Internally the pernr might not be locked or some one may be maintaing the pernr for whom you are trying to post.

No Quota for employee in EP- Leave Request error

I am facing an issue with one employee.
This employee is having a lot of quotas for all the absence types in R/3. However in EP when he goes to 'Quota Overview', it shows that the table is empty, and the dropdown list also does not contain any leave.
When he clicks on 'Leave Request' there comes an error
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.     +
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
                at java.util.ArrayList.RangeCheck(ArrayList.java:507)
                at java.util.ArrayList.get(ArrayList.java:324)
                at com.sap.aii.proxy.framework.core.JcoBaseList.get(JcoBaseList.java:268)
                at com.sap.aii.proxy.framework.core.AbstractList.get(AbstractList.java:230)
                at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCList.get(DynamicRFCList.java:281)
                at com.sap.tc.webdynpro.progmodel.context.Node$ModelElementList.getElement(Node.java:2549)
                at com.sap.tc.webdynpro.progmodel.context.Node.getElementAtInternal(Node.java:621)
                at com.sap.tc.webdynpro.progmodel.context.Node.setLeadSelection(Node.java:753)
                at com.sap.xss.hr.lea.form.FcForm.setLeadSelectionForSubtype(FcForm.java:700)
                at com.sap.xss.hr.lea.form.FcForm.setVisibility(FcForm.java:943)
                at com.sap.xss.hr.lea.form.FcForm.prepareCommand(FcForm.java:308)
                at com.sap.xss.hr.lea.form.wdp.InternalFcForm.prepareCommand(InternalFcForm.java:2041)
                at com.sap.xss.hr.lea.form.FcFormInterface.prepareCommand(FcFormInterface.java:116)
                at com.sap.xss.hr.lea.form.wdp.InternalFcFormInterface.prepareCommand(InternalFcFormInterface.java:1887)
                at com.sap.xss.hr.lea.form.wdp.InternalFcFormInterface$External.prepareCommand(InternalFcFormInterface.java:1983)
                at com.sap.xss.hr.lea.form.edit.VcFormEdit.onInit(VcFormEdit.java:299)
                at com.sap.xss.hr.lea.form.edit.wdp.InternalVcFormEdit.onInit(InternalVcFormEdit.java:1084)
                at com.sap.xss.hr.lea.form.edit.VcFormEditInterface.onInit(VcFormEditInterface.java:165)
                at com.sap.xss.hr.lea.form.edit.wdp.InternalVcFormEditInterface.onInit(InternalVcFormEditInterface.java:204)
                at com.sap.xss.hr.lea.form.edit.wdp.InternalVcFormEditInterface$External.onInit(InternalVcFormEditInterface.java:280)
                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:1288)
                at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:355)
                at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:548)
                at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:592)
                at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:864)
                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.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:102)
                at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Any suggestion regarding this?

When Quotas table is empty then customisation is missing for his ESG AND PSG in v_t556a_web
check his groupings from It2006 overview and maintain those in above for his rule group
java dump :
Please can you check if the Pernr used
has correct information like It0105 etc, also the rules are
correctly defined.
For the Employee, First of all check the Period Work Schedule also
the Quotas of the pernr needs to maintained in 2006, Please do
this customisation and it should solve the issue.
Maintain the absence quota in the IT2006 and then try once.
Also make sure that the Settings in Webmo and PTARQ etc all is done
The pernr belongs to the a Rule and have absences defined for him.

ESS Leave Request error when launched from the portal

Hi guys
When i try to launch the Leave request from ESS tab in portal i am getting the following error
I have checked the backend and i can process a leave request from there. It is failing on the portal side.
A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.
Please contact your system administrator.
Index: 0, Size: 0
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
     at java.util.ArrayList.RangeCheck(ArrayList.java:507)
     at java.util.ArrayList.get(ArrayList.java:324)
     at com.sap.aii.proxy.framework.core.JcoBaseList.get(JcoBaseList.java:268)
     at com.sap.aii.proxy.framework.core.AbstractList.get(AbstractList.java:230)
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCList.get(DynamicRFCList.java:281)
     at com.sap.tc.webdynpro.progmodel.context.Node$ModelElementList.getElement(Node.java:2549)
     at com.sap.tc.webdynpro.progmodel.context.Node.getElementAtInternal(Node.java:621)
     at com.sap.tc.webdynpro.progmodel.context.Node.setLeadSelection(Node.java:753)
     at com.sap.xss.hr.lea.form.FcForm.setLeadSelectionForSubtype(FcForm.java:700)
     at com.sap.xss.hr.lea.form.FcForm.setVisibility(FcForm.java:943)
     at com.sap.xss.hr.lea.form.FcForm.prepareCommand(FcForm.java:308)
     at com.sap.xss.hr.lea.form.wdp.InternalFcForm.prepareCommand(InternalFcForm.java:2041)
     at com.sap.xss.hr.lea.form.FcFormInterface.prepareCommand(FcFormInterface.java:116)
     at com.sap.xss.hr.lea.form.wdp.InternalFcFormInterface.prepareCommand(InternalFcFormInterface.java:1887)
     at com.sap.xss.hr.lea.form.wdp.InternalFcFormInterface$External.prepareCommand(InternalFcFormInterface.java:1983)
     at com.sap.xss.hr.lea.form.edit.VcFormEdit.onInit(VcFormEdit.java:299)
     at com.sap.xss.hr.lea.form.edit.wdp.InternalVcFormEdit.onInit(InternalVcFormEdit.java:1084)
     at com.sap.xss.hr.lea.form.edit.VcFormEditInterface.onInit(VcFormEditInterface.java:165)
     at com.sap.xss.hr.lea.form.edit.wdp.InternalVcFormEditInterface.onInit(InternalVcFormEditInterface.java:204)
     at com.sap.xss.hr.lea.form.edit.wdp.InternalVcFormEditInterface$External.onInit(InternalVcFormEditInterface.java:280)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)

This error occurs due to the following customisaton, Please
check this :
Check the Feature WEBMO is activated or not?
Is the pernr assigned correctly?
Please can you check if the Pernr used
has correct information like It0105 etc, also the rules are
correctly defined.
For the Employee, First of all check the Period Work Schedule also
the Quotas of the pernr needs to maintained in 2006, Please do
this customisation and it should solve the issue.
Maintain the absence quota in the IT2006 and then try once.
Also make sure that the Settings in Webmo and PTARQ etc all is done
The pernr belongs to the a Rule and have absences defined for him.

Leave request Error in ESS

Hi Experts,
Greetings !!
One of our user is facing a weird issue while he is trying to apply for a leave through ESS.
He is applying for a leave for absence type ABC for which he is having enough quota, an error message is coming while he is submitting the leave as below:
"No absence quota type 1/01/20 on 17.06.2014" - This error is of absence type XYZ,
More information about this issue:
- Employee has enough quota for which he is trying to apply for leave
- The error message which is showing as error (absence type XYZ 1/01/20) is a different absence type and this absence type is delimited on 31.12.2010.
- Though the leave type is delimited, it is coming as error message for only one employee while he is applying for leave of a different absence type.
Can some one help me providing solution how to fix this issue. Thanks in advance.

In leave request we consider all open requests of absences for validating current request and not necessarily current request that's the reason you get error message for an absence which is not related to the one you are applying read here the concept http://scn.sap.com/thread/2068984 http://scn.sap.com/thread/3508890 Read note 1070831 which explains how quota deduction is done both in leave request and TMW which are based on same technology. So to summarize Absences are picked up for the quota deduction , they are picked in the ascending order of the begin date of the absences \In the standard TMW framework, when the data is simulated it first backtracks the PA2001 record and based on the ascending order the quota is deducted, therefore the first quota is deducted by the simulated requests and the Infotype 2001 record is deducted from the second Infotype 2006 record. so check for this user if he has any open request ie in sent/approved not yet posted status which ll also account for quota!! and will sorted again in ascending order and all requests will be considered for quota deduction if they are open!

Team Calendar in ESS Leave Request (Error)

Hello,
we are configuring the Leave request in ESS and MSS in the portal (EP 7.0, ECC 6.0, latest release). The Leave Request process and application, Time accounts and Workflows all working fine and the customizing is done in the IMG.
Only under ESS -> Leave Request -> Team Calendar we are getting this Error:
java.lang.Exception: No Views found: Missing customizing
     at com.sap.xss.ser.tecl.fc.FcTeamCalendar._checkData(FcTeamCalendar.java:799)
     at com.sap.xss.ser.tecl.fc.FcTeamCalendar._getData(FcTeamCalendar.java:751)
     at com.sap.xss.ser.tecl.fc.FcTeamCalendar.initialReadData(FcTeamCalendar.java:385)
     at com.sap.xss.ser.tecl.fc.wdp.InternalFcTeamCalendar.initialReadData(InternalFcTeamCalendar.java:319)
     at com.sap.xss.ser.tecl.fc.FcTeamCalendarInterface.initialReadData(FcTeamCalendarInterface ....etc.
I have maintained the Customzing in IMG for Team Calendar as the following:
00000001     SAP Standard     01.01.1800     31.12.1999     Approval Mode     View Group (MSS)     MSS_LEA_EE
00000001     SAP Standard     01.01.1800     31.12.1999     Attendance Overview     View Group (MSS)     MSS_LEA_EE
00000001     SAP Standard     01.01.1800     31.12.1999     Administrator Mode     View Group (MSS)
00000001     SAP Standard     01.01.1800     31.12.1999     Request Mode     View Group (MSS)     ESS_LEA_EE
00000001     SAP Standard     01.01.1800     31.12.1999     Team View Mode     View Group (MSS)
Would you please help?
Many Thanks and Regards,
Nazih

Hi Bryan,
1. First of all make sure that the Internet Graphic Server is activated + up and running on your SAP ERP System (see also SAP Note 704604)
2. Then you have to set the Customizing Parameters for the Team Calendar in IMG (SAP ERP System):
a. Tcode: PTARQ -> Customizing
b. Working Time -> Team Calendar
c. Node Create Rule Group -> Example: 00000001 (SAP Standard)
d. Node Adjust WEBMO Feature -> Assign all Nodes to your Rue Group
e. Node Spec. Absecne to be displayed -> Here i assume you have set up the Leave Request Process and WF already, so you only need to assign this to your Rule Group:
Example.
00000001     SAP Standard     01     0100     Leave     01.01.1800     31.12.9999
f. Node Select Employee -->
Here you need to set the Group of your Employee which should be displayed in the team calendar:
Example.
00000001     SAP Standard     01.01.1800     31.12.9999     Approval Mode     View Group (MSS)     MSS_LEA_EE
00000001     SAP Standard     01.01.1800     31.12.9999     CATS Approval     View Group (MSS)     MSS_LCA_EE
00000001     SAP Standard     01.01.1800     31.12.9999     Attendance Overview     View Group (MSS)     MSS_LEA_EE     PPOME_P
00000001     SAP Standard     01.01.1800     31.12.9999     Administrator Mode     View Group (MSS)     MSS_LEA_EE     PPOME_P
00000001     SAP Standard     01.01.1800     31.12.9999     Request Mode     View Group (MSS)     ESS_LEA_EE
00000001     SAP Standard     01.01.1800     31.12.9999     Team View Mode     View Group (MSS)     MSS_LEA_EE     PPOME_P
---> Tipp: Check all Settings and Leave Types also with an HR Consultant before maintaing these in the ESS Customizing...
Regards,
Nazih

ESS Leave Request Error

Hi Experts,
We have implemented ESS in our organisation.
In the leave request view i am getting the following error.
For ex : If the leave request pending is 10.
If i approved 1 it should reduce to 9 .....Its getting refreshed as 9 in R/3end but in the portal page its remains the same(Showing pending request : 10)
Can anyone pls throw some light on this issue.
Thanks in Advance,
Dharani

Hello,
Please, I have the same issue!
How did you resolve this problem?
Thanks in advance

Fiori - Approval for Timesheet & Leave Request

Hello Friends,
I am currently working on SAP Fiori Timesheet & Leave request approval. The application is working fine and going to manager for approval.
I have a concern here, the approval to manager happens only if I maintain relationship "A012" Managed by, then subordinates who are in that respective Org Unit submits timesheet/Leave request goes to manager for approval.
If I maintain One-on-One relationship "A002", then it is not showing up in manager's id for approval. When I checked in t-code "SWIA" to check with whom it is pending it shows the correct manager maintained in One-on-One relationship.
In my current project, there is only One-on-One relationship "A002", and we don't have relationship "A012". Please let me know whether the approval scenario will work or not.
We cannot ask the client to change the relationship now from "A002" to "A012".
Thanks & Regards,
S.Srikanth
Tags edited by: Michael Appleby

Hi Srikanth,
Can you please share the evaluation path rules for the Root and Navigation Objects that you used to solve? I'm having the exact same problem pulling in the B002 relationships.
Using SAP_MANG for the root:
10
B
008
Holder
S
20
S
A
012
Manages...
O
30
US
A
208
Is identical to
P
By adding the B002 Relationship to a rule based on MSSDIREC (Line 25)
10
O
B
900
Manager under manager
S
20
O
B
900
Manager under manager
O
25
S
B
002
Is line supervisor of
S
30
S
A
008
Holder
P
40
S
A
008
Holder
US
I got RHSTRU00 to show the correct Evaluation, but Fiori doesn't pull in B002's yet. Do I need to adjust the Root one as well? Thanks for any ideas!
Scott

Error while approving Leave request

Hi,
I am facing an issue while approving the attendance request of an employee via MSS. The error message comes for the leave request further in the queue.
Error Message : No read authorization for infotype 2001/5006(Annual Leave) for employee number between 07.06.2010 and 07.06.2010
Hoping for the early response.
Thanks!

I guess there is problem with the managers ID and the authorizations.
Try to check in SU53 and speak to security team to run the trace and provide the necessary authorizations

Error while raising leave request

Dear all,
I am getting error while raising Leave request over ESS...Task WS12300111 locked for instantiation.
As well as in MSS manager is not getting requests for approval..can anyone tell me on workflow front what shall be done.
Regards,
Rajasekar.

check the WF is a general task ie PFTC and user has authoriation, Are you using any custom code through badi, then enusre Start_WF method is implemented.

Error while trying to delete leave request

Dear All,
When trying to delete a leave request via ESS Portal, system is displaying the following error message:
"No Customizing for status type ARQ, status Posted and transition event Delete."
In the workflow log, Document Status is POSTED and Workflow Status is COMPLETED.
Kindly let me know if any other information is required.
Any pointers to resolve the above issue will be highly appreciated.
Regards,
Rahul

Hi Rahul,
Please check the below threads which may help you.
Re: Cancellation Leave request
Re: Leave request deletion problem
Thanks & Regards,
Sandip Biswas.

Fiori My Leave Requests error

Similar Messages

Maybe you are looking for