Error in creating leave request

Hi ,
I am new to HR and i am working on Leave management.
When i am trying to crate a leave request workflow, i am getting the below error msg:
'Absence type 100 was not found in Customizing for 21.10.2010'
What could be the reason?\
Thanks,
Krish.

Hello Kishore,
You don't have the absence type created on either one of the two following tables.
T554S - This one is for the Absence creation on the backend in IT2001.
T554S_Web - This one is to show on the frontend framework of the Leave Request.
Regards,
Bentow.

Similar Messages

  • Error message for Leave request (Related to some Old Question)

    Hi Experts,<br />
    <br />
    We are facing an Error when only 1 employee in the company opens his Leave request page, the same page is working for others perfectly.<br />
    <br />
    this Error is the same as the one in the below posts:<br />
    <br />
    1. Link: Re: Error message for Leave request<br />
    <br />
    and I tried going through their solutions such as:<br />
    <br />
    1. Please check if you have the leave config done on ECC side under Personnel Management --&gt; Employee Self services --&gt; Service Specific settings --&gt; Working time --&gt; Leave request .<br />
    2. At the least you should have assign the default rule to your PSG to the standard leave type given. Otherwise create your own rule groups and Specify Processing processes for type of leave set up.<br />
    3. explicitly activate WEBMO Feature although it was activated<br />
    <br />
    But the Error is still coming for this specific Employee, even though his Vacation Quota is created and available for deduction.<br />
    <br />
    Please Help me in solving this issue.<br />
    <br />
    Regards,<br />
    Abdulrahman

    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)
         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)

  • How to configure and test workflow for  Creating Leave Request

    Hi,
    When I select <b>leave request</b> iView in portals I get an R/3 screen titled "Create Leave Request".And when I fill in the details for <b>approver</b> and press<b> send</b> I get this error message <b>"You are not one of the possible agents of the task".</b>
    So help required to configure and test the workflow behind <b>Create leave request iView.</b>
    Regards,
    Pavanmeet.

    Pavanmeet,
    you have to set all activities in the workflow to "general task" as well, not only for WS12300111 itself (doubleclick on each symbol with the "triangle").
    check the status of the sent leave request in transaction PTARQ (Display Documents). Here the "next agent" & the "pers. no" of the next agent is of interest.
    logon with the user, that is saved in infotype 0105 of the above mentioned pers.no. there should be the approve request.
    you can check the status of the workitems with SWI1 (i assume your system is prepared for workflows , check SWU3)
    Message was edited by: Achim Hauck

  • 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 Creating Travel Request ..thru TRIP

    Dear all,
    As I am suppose to creat a travel request thru TRIP but i am geting the below error and the msg no..............
    Error: Trip country IN / trip region do not exist in the system (T702O)
    Message no. PTRA_WEB_INTERFACE031
    As Mr. Paulo Vitoriano suggested me to Define Trip Areas, etc......... but my Trip Areas has already been defined and i have checked it also .... but still the error is same ....... so frnds pls tell me wat else may be the problem....
    I read thred Error while Creating Travel Request ..thru TRIP which is posted by prasanth but what they suggested i maitained already but still i am facing same problem could you pls suggest me where i missed.
    Waiting for Reply.
    Regards,
    Nagaraju

    Hi,
    Please check the following:
    1. Just check have you assigned country India to the trip provision variant you have created.
    2. Just check whether you have assigned the trip provision variant correctly to the respective country.
    Regards,
    S.Srikanth

  • Function Module BAPI_ABSENCE_CREATE for creating leave request.

    Hi Experts,
    I am using FM BAPI_ABSENCE_CREATE for creating leave request. I am passing all the data into this as import parameter. When i am executing this return table gives statement  EPG184Employee/applicant is not locked yet
    Please let me know what i have to follow.
    Thanks And Regards
    Ranjeet Singh

    Use the below function modules in sequence
    1) HR_EMPLOYEE_ENQUEUE'
    2) BAPI_ABSENCE_CREATE
    3) HR_EMPLOYEE_DEQUEUE
    Functionality
    Using this method, an Absences infotype record (2001) can be created.
    Notes
    Messages are returned in the RETURN parameter. The parameter documentation contains the return codes and their meanings.
    The key fields used by this method are described under the parameters.
    This method can only be used if the ENQUEUE method has already been called up for the business object EMPLOYEE. For more information on the ENQUEUE method, please see the documentation on the function module BAPI_EMPLOYEE_ENQUEUE.
    Note: Create absence
    Caution! This API method only writes the Absences infotype (2001). It should no longer be used as it can lead to inconsistent time data. Instead, please use the corresponding 'ManageCreation' API method for business object BUS7007.
    Regards,
    SaiRam

  • Attaching documents in Create Leave Request UI5 application

    Hi,
    We are planning to implement the SAP HR Renewal 2.0 FP1 based HR implementation with ESS/MSS based on the UI5 as well.
    I would like to know if the SAP UI5 application for Create Leave Request has the option to upload the documents or not in the standard delivery.
    Please let me if the attachment facility is available for the Create Leave request application in UI5 based ESS.
    Thanks & Regards,
    Urmi

    Hello Urmi,
    Yes, attachment option is available in Standard Leave Request in UI5.
    Best Regards,
    Deepak.. 

  • Create Leave Request In portal doesn't load  after logging in

    He All,
    we are facing an issue with some of the users of the E portal , after they log in and click on create leave request  the loading icon appear and the portal stuck at that and nothing else happen like in the attached image  , this issue happen with some users not all of the users however it was working with them before.
    Please advice
    Thanks in advance

    Hi Ahmed,
    I didnt suggest a browser issue.
    But using such tool when problem happens can show your the exact request url that hangs.
    Then from this, you can reach to where the problem resides on the server.
    Google chrome contains it already (just click on F12) , you can see all requests:
    When you see a request that doesnt have status 200 or without status, this can give you focus on where is the issue.
    Best regards,
    Tal

  • Create Leave request

    Hi ,
    We have configured ESS/MSS with portal. We have created a Iview Leave request(IAC).
    When we executing this it is displaying R/3 inbox means SWBP insted of showing leave request create view..

    Hi Chuckie,
    Thanks for your response.
    I am trying to create a leve request from my inbox by pressing Create leave request. Earlier it opens a create window. Now a days we are getting SAP R/3 SWBP transation.
    We are using EP-6.

  • Problem with Team Calendar from Create Leave Request

    Hi Expert,
    We are facing following 2 issues with Team Calendar-
    1)     When manager checks Team Calendar from create leave request he gets a warning message 'No team set up for the user in the selection                period.Contact Administrator'
    I know this issue has been reported earlier as well but i didn't find the thread where it has been answered correctly.
    - OADP configuration is correct.
    - Manager is head of org unit.
    - Also IT105 exist for manager as well as employees.
    We are currently checking on authorization side for this.
    2)   Team Calendar is showing leave details only for the current month. If we navigate to previous month it does not show anything even though there exist leave data for the given month. 
    Please suggest if we are missing something.
    Thanks & regards,
    Avinash

    Hi Nagendra,
    I dont remember the exact auth object but ask security team to apply trace for the user id and identify the same.
    Also i would suggest you to check following setting before checking authorizations-
    Get the Group of Organizational Views applicable for rule group in your case  from following path
    SAP Customizing Implementation Guide--> Personnel Management-->Manager Self-Service (Web Dynpro ABAP)--> Service Specific Settings-->Working Time--> Team Calendar--> Select Employees:
    After getting Group of Org View Check the Evaluation path used in OADP configuration.
    Please check if the evaluation path is correct as per your requirement.
    Regards,
    Avinash

  • Component Usage error in MSS Leave Request approval

    Hi All,
    We are getting the below mentioned error only for few users while approving the leave request in MSS.
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: ComponentUsage(FPMConfigurationUsage): Active component must exist when getting interface controller. (Hint: Have you forgotten to create it with createComponent()? Should the lifecycle control of the component usage be "createOnDemand"?
        at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.ensureActiveComponent(ComponentUsage.java:773)
        at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceControllerInternal(ComponentUsage.java:348)
        at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceController(ComponentUsage.java:335)
        at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetFPMConfigurationUsageInterface(InternalFPMComponent.java:245)
        at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.changeToExceptionPerspective(FPMComponent.java:861)
        ... 41 more
    Kindly share your views on the same.
    Thanks and Regards,
    Vivek.

    Hi Anup,
    Please find the complete Trace below.
    System Environment
    Client
    Web Dynpro Client Type     HTML Client
    User agent     Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; MS-RTC LM 8)
    Version     null
    DOM version     null
    Client Type     msie6
    Client Type Profile     ie6
    ActiveX     enabled
    Cookies     enabled
    Frames     enabled
    Java Applets     enabled
    JavaScript     enabled
    Tables     enabled
    VB Script     enabled
    Server
    Web Dynpro Runtime     Vendor: SAP, build ID: 7.0013.20080611120129.0000 (release=NW04S_13_REL, buildtime=2008-09-11:17:05:50[UTC], changelist=42127, host=pwdfm114), build date: Wed Nov 19 19:21:28 CET 2008
    J2EE Engine     7.00 patchlevel 109044.44
    Java VM     IBM J9 VM, version:2.3, vendor: IBM Corporation
    Operating system     AIX, version: 5.3, architecture: ppc64
    Session & Other
    Session Locale     en
    Time of Failure     Sat Jan 02 12:26:56 CET 2010 (Java Time: 1262431616916)
    Web Dynpro Code Generation Infos
    sap.com/ess~lea
    SapDictionaryGenerationCore     7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:43[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates     7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:51[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.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:25[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.0011.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:00:20[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro     7.0011.20061227101814.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:05:13[UTC], changelist=431317, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates     7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
    SapWebDynproGenerationCore     7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:35[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates     7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
    sap.com/pcui_gp~xssutils
    SapDictionaryGenerationCore     7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:43[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates     7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:51[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.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:25[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.0011.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:00:20[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro     7.0011.20061227101814.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:05:13[UTC], changelist=431317, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates     7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
    SapWebDynproGenerationCore     7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:35[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates     7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
    sap.com/tcwddispwda
    No information available     null
    sap.com/pcui_gp~xssfpm
    SapDictionaryGenerationCore     7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:43[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates     7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:51[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.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:25[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.0011.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:00:20[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro     7.0011.20061227101814.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:05:13[UTC], changelist=431317, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates     7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
    SapWebDynproGenerationCore     7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:35[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates     7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
    sap.com/tcwdcorecomp
    No information available     null
    sap.com/pcui_gp~tecl
    SapDictionaryGenerationCore     7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:43[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates     7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:51[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.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:25[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.0011.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:00:20[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro     7.0011.20061227101814.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:05:13[UTC], changelist=431317, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates     7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
    SapWebDynproGenerationCore     7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:35[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates     7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
    Detailed Error Information
    Detailed Exception Chain
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: ComponentUsage(FPMConfigurationUsage): Active component must exist when getting interface controller. (Hint: Have you forgotten to create it with createComponent()? Should the lifecycle control of the component usage be "createOnDemand"?
           at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.ensureActiveComponent(ComponentUsage.java:773)
           at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceControllerInternal(ComponentUsage.java:348)
           at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceController(ComponentUsage.java:335)
           at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetFPMConfigurationUsageInterface(InternalFPMComponent.java:245)
           at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.changeToExceptionPerspective(FPMComponent.java:861)
           at com.sap.pcuigp.xssfpm.java.MessageManager.handleException(MessageManager.java:258)
           at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:103)
           at com.sap.pcuigp.xssfpm.wd.BackendConnections.connectModelInternal(BackendConnections.java:323)
           at com.sap.pcuigp.xssfpm.wd.BackendConnections.initBackend(BackendConnections.java:256)
           at com.sap.pcuigp.xssfpm.wd.BackendConnections.connectModel(BackendConnections.java:154)
           at com.sap.pcuigp.xssfpm.wd.wdp.InternalBackendConnections.connectModel(InternalBackendConnections.java:237)
           at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.connectModel(FPMComponent.java:841)
           at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.connectModel(FPMComponent.java:1071)
           at com.sap.pcuigp.xssfpm.wd.BackendConnections.init(BackendConnections.java:141)
           at com.sap.pcuigp.xssfpm.wd.wdp.InternalBackendConnections.init(InternalBackendConnections.java:233)
           at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:182)
           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.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.doGet(DispatcherServlet.java:46)
           at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
           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(AccessController.java:219)
           at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
           at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Thanks and Regards,
    Vivek.

  • 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 creating Travel request

    Dear All,
    ESS 2005/SP6
        While creating travel request in I am getting following error
    "Errors have been discovered when checking the Expense Report. Please correct them in order to proceed."
    Regards,
    Kamal Rawal

    Hello Kamal
    Did you manage to resolve the issue in relation to "Errors have been discovered when checking the Expense Report."?
    Best Regards
    Roger Earle
    [email protected]

  • Function modules to create leave request?

    Hi experts,
    In my project I need to create a leave request and trigger workflow for approval. Do you know any function modules existed for this purpose? Or shall we need to create workflow and attach it with inserting IT2001 records?
    Thanks a lot.

    Are you going to use standard SAP Portal application for leave or not?
    If yes there are documents available about ESS configuration for the same and you can assign the standard workflow or copy and make the required chnages then assign it in configuration.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/108c31e7-b6a7-2d10-3692-c1a9f7a5c4dc?QuickLink=index&overridelayout=true
    Regards
    Ajay

  • Access Enforcer (error in creating a request)

    Hi All,
    when i am creating a new request in Access Enforcer . After filling alll the details and clicking the submit button it is showing  a error in creating request .Path not found.

    Hello,
    You must have to select at least one condition attribute while creating your initiator. It seems initiator condition not meeting the details you are filling in your request. So it is not able to trigger the workflow initiator.
    For simple scenario, if you are filling your company details in your request then change your initiator condition attribute to "Company".(Don't include more condition attributes for now). Once it works out then change initiator details back to your requirements.
    Please let me know if this will not resolve your issue.
    Thanks
    Himadama

Maybe you are looking for