ESS Loan Request Approver side validations

Dear All,
I am using standard ess loan request service.Here I have to perform certail validations at MSS side(Loan Request Approver IView).
Here manager can edit the values of Granted Amount,payment date,payment amount and payment type.But without entering these values also the loan request is getting approved by clicking on Review button.
I want to validate the above mentioned fields in case any of thefields left blank and also I have to validate the granted amount(should not be greater than requested amount).
As we know we have following BADI's available thru which we can perform validations when employee is applying for a loan.
1.Eligibility check
2.Custom Validations
3.Determine Approver.
Is there any BADIs available to perform validations at MSS part(Loan Request Approver)
Please give some input!
Thanks,
Reddy.

Dear Roy,
Thanks for your response.
According to your reply I understand that I need to write my validations in the approval task(TS18900024).In the workflow Approval task there is a standard class CL_HRPBSIN_LOAN_REPAY_WF available.I cannot create a method under it since this is a standard class.Do I need to take a copy of it and create a method?
But how can I Import the parameters from approver screen like Granted amount,payment amount,payment date and payment type.
Please clarify...

Similar Messages

  • Error while accessing ESS Loan Request.

    Hi Experts,
    While accessing ESS Loan request for Country grouping 40 India am getting below mentioned error saying that 500 Internal Server Error.
    I have maintained the settings for Leave request and maintained Infotype 45 Loans for employee.
    But it is giving the below mentioned error.
    500   Internal Server Error
      SAP NetWeaver Application Server 7.00/Java AS 7.00 
    Failed to process request. Please contact your system administrator.
    [Hide]
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       com.sap.dictionary.runtime.DdException: Type com.sap.model.loan.types.Extdl does not exist
        at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
        at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:596)
        at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:296)
        at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:94)
        at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
        ... 74 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2)
    Version null
    DOM version null
    Client Type msie8
    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.0205.20100813133935.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:28:44[UTC], changelist=91834, host=pwdfm256), build date: Fri Feb 11 16:31:03 IST 2011
    J2EE Engine 7.02 PatchLevel 91789.
    Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_28-b03, vendor: Sun Microsystems Inc.
    Operating system Windows Server 2008 R2, version: 6.1, architecture: amd64
    Session & Other
    Session Locale en_US
    Time of Failure Fri Feb 18 11:17:24 IST 2011 (Java Time: 1298008044828)
    Web Dynpro Code Generation Infos
    sap.com/pb
    SapDictionaryGenerationCore 7.0205.20100813133727.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:18:36[UTC], changelist=91776, host=PWDFM256.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0205.20100813133727.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:18:40[UTC], changelist=91776, host=PWDFM256.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0205.20100813133737.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:08:53[UTC], changelist=91781, host=PWDFM256.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0205.20100813133926.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:22:53[UTC], changelist=91832, host=PWDFM256.wdf.sap.corp)
    SapMetamodelCommon 7.0205.20100813133815.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:09:28[UTC], changelist=91800, host=PWDFM256.wdf.sap.corp)
    SapMetamodelCore 7.0205.20100813133815.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:09:25[UTC], changelist=91800, host=PWDFM256.wdf.sap.corp)
    SapMetamodelDictionary 7.0205.20100813133729.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:16:20[UTC], changelist=91777, host=PWDFM256.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0205.20100813133929.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:20:37[UTC], changelist=91833, host=PWDFM256.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0205.20100813133935.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:30:09[UTC], changelist=91834, host=pwdfm256)
    SapWebDynproGenerationCore 7.0205.20100813133926.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:22:57[UTC], changelist=91832, host=PWDFM256.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0205.20100813133935.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:30:09[UTC], changelist=91834, host=pwdfm256)
    Detailed Error Information
    Detailed Exception Chain
    com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.sap.model.loan.types.Extdl could not be loaded: com.sap.dictionary.runtime.DdException: Type com.sap.model.loan.types.Extdl does not exist
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:268)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:231)
         at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:687)
         at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:940)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:177)
         at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:149)
         at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:141)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$ComponentUsageManager.createBLCComponentUsage(FPMComponent.java:761)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:920)
         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.ess.in.loan.overview.VcOverviewESS.onInit(VcOverviewESS.java:244)
         at com.sap.ess.in.loan.overview.wdp.InternalVcOverviewESS.onInit(InternalVcOverviewESS.java:611)
         at com.sap.ess.in.loan.overview.VcOverviewESSInterface.onInit(VcOverviewESSInterface.java:162)
         at com.sap.ess.in.loan.overview.wdp.InternalVcOverviewESSInterface.onInit(InternalVcOverviewESSInterface.java:144)
         at com.sap.ess.in.loan.overview.wdp.InternalVcOverviewESSInterface$External.onInit(InternalVcOverviewESSInterface.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:783)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java: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:876)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:222)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1355)
         at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:357)
         at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:551)
         at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:597)
         at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:870)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
         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)
    Caused by: com.sap.dictionary.runtime.DdException: Type com.sap.model.loan.types.Extdl does not exist
         at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
         at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:596)
         at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:296)
         at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:94)
         at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
         at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:260)
         ... 72 more
    Please suggest me the solution for this.
    Regards,
    Ksanj.

    Please   check that the ESS/ERP packages fit together according to
    the page
    https://wiki.sdn.sap.com/wiki/display/ERPHCM/HOWTOGETRIDOFSPSTACK+
    MISMATCH+ISSUES
    Please check again the componentinfo and the SPlevels of the testlandsca
    pe, that the same level is used on the prod landscape.
    So ensure you are on correct levels!

  • Loan Request Approved but it is not updating in R/3 IT 0045.

    Dear All,
    Loan approval process is completed. But it is not getting update in R/3. Are there any back ground programs needs to run to update the record? Or else where I can check the completed requests in R/3?
    Thanks in Advance.
    Potru.

    Hi Siddharth,
    Thanks for your reply..
    600 SP17 (SAP_ESS) and sap.com/SAP-JEE - 7.02 SP5.
    HRPBSIN_LOANUPDINFTY - I run this T-code but system is giving message "There is no loan or repayment request for updating in infotype 0045".
    Regards,
    Potru.

  • ESS portal request approval thru blackberry

    Hi,
    I have a requirement of sending a request for approval on Blackberry as soon as a requisition is raised from ESS. The requisitions are Z-development and connected to a workflow which triggers once the requisition is raised. I want a approval request to be flashed on black berry of the approver. Does any one know a Bapi which fits well.
    Regards,
    Dhiraj Mehta

    HI,
    Check if u have activated the workflow and agent assignments are done. If it is done then
    Login to approvers ID and see if he has got the work item in SBWP. If not, go to requesters SBWP in R/3, open outbox -> started workflows. Check the log for the workflow.
    Cheers!!
    Ashutosh

  • ESS Leave Request Approval Not working

    Hi All,
    We here have ESS1.0, ECC 6 and EP 7 on NW2004s.
    Problem which i am facing is in Leave Request.
    An employee enter his leave details and send it to its boss.
    and the boss check the same in his UWL uptil this its working fine.
    But when the boss click on the Leave request in UWL to approve or reject the same then error comes.
    The error is "<u><b>Application error occurred during request processing.
    Details:       com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Wrong WebDynpro-URL: no application name specified
    Exception id: [001125C556F8005400000500000B2052000432CAF4C7A0CF]</b></u>"
    Kindly help me out on how can i resolve this issue.
    Regards,
    Sidhartha Chatterjee

    Hi Sidhartha,
    proove, if you use the following things:
    In the portal under "Universal Worklist - Administration" you must fill out the parameter "Web dynpro launch system" for the binded ECC system you use. Use a portal system (the alias name for the portal system you have created) which links to the Web Application Server where you have deployed(!) your application (if web application server and portal is the same you also must create a portal system with the local web application data). In general, you create and named a portal system like SAP_WebDynpro_XSS and bind it as parameter.
    If you do not use this system the Web Dynpro for Approve/ Reject leave request generates a wrong URL with the Web application data from ECC, not for web dynpro.
    More information:
    Configuring The Business Package For Employee Self Service (ESS)-mySAP ERP 2004
    (to create the system SAP_WebDynpro_XSS)
    http://help.sap.com/saphelp_nw04/helpdata/en/92/a88931f2dd4631b9e8d530697d89c9/content.htm
    (to bind it into UWL)
    Hope that helps,
    Regards,
    Frank

  • Loan request - ESS - Error on eligiblity

    Hi
    Loans are configured in R/3 and working fine .... I configured the same for ESS ( Benefits and Payments - > Loan Requests ) when i try to raise a request for a loan type in ESS , i get en error saying " The Experience of employee 00000022 is less than eligibile experience for loan" , even though i have given "null (0) " in the node - Maintain loans Eligiblity checks and limits ... have any of you come across something like this..... inputs on how to solve this would be highly appreciated.....
    Cheers
    Sang

    Hi Sai Sree
    Thanks for the reply
    Even with the BADI activated, i get the same error in ESS..
    In the ESS - Loan Request screen, the "Reference No." field is grayed out with '000000000000" , though i have given the number range in SPRO for the same...
    Can you please let me know whether you get the reference number field correctly filled??
    Thanks in advance
    Cheers
    Sangeetha

  • Loan Request iView(ESS)

    Hello,
    When executing Loan Request iView(ESS) I get the following error:
    type com.sap.model.loan.types.Pin_Status could not be loaded: com.sap.dictionary.runtime.DdException: Type com.sap.model.loan.types.Pin_Status does not exist
    Please, do you know how can I resolve it?
    Isabel

    Hi Sai Sree
    Thanks for the reply
    Even with the BADI activated, i get the same error in ESS..
    In the ESS - Loan Request screen, the "Reference No." field is grayed out with '000000000000" , though i have given the number range in SPRO for the same...
    Can you please let me know whether you get the reference number field correctly filled??
    Thanks in advance
    Cheers
    Sangeetha

  • Loan Auto approval while requesting in ESS

    Hai all,
    I am having a requirement that while applying a loan req in ESS that request should not go to the manager for approval.
    It should be approved when it is applied. So that the status should be approved when applying itself.\
    So when i run the report it will post the request in infotype 45.
    what is the necessary setting needs to be done so that the request will be approved when sending itself.
    Kindly give some suggestions.
    Thanks,
    Nalla B.

    Hai all,
    Thanks for ur valuable response. There is a small twist in this. Am having three type of loans in which two required approval one does not required any approval.
    Am using the standard Wd 18900041and  using the BADI   HRPBSINGET_APPROVER to find the approver and sending the request to approval through WF.
    So how can I achieve the auto approval functionality for that one type of loan alone???
    Can I follow the following steps
    1) Deactivate the WF in config.
    2) Restricting the BADI to find approver only for the other two type of loans.
    Pls give some suggestions.
    Thnks in advance,
    Nalla B.

  • ESS Claim Advance Approval screen showing incomplete list of requests.

    Hi Friends,
    In ESS Claim Advance Approval screen we are facing this issue.
    When approver opens the screen for approving the request.
    The list of requests appear but its not the complete list.
    There are also 2 sucess messages that get displayed.
    112 records found for the selection
    Only 10 of 112 records loaded which meet the selection criteria
    Users are able to see the rest of the request at r/3,
    also if they approve the first 10 request then they are able to view the next slot of requests.
    Any guidance as where the configuration for this could be checked.
    Regards.
    Edited by: SAP Portal Deve on Sep 20, 2011 2:41 PM

    you mean number of requests in UWL?
    Please specify
    http://help.sap.com/saphelp_afs64/helpdata/en/56/15681955744ec8877931c56607ec35/frameset.htm
    Edited by: Siddharth Rajora on Sep 20, 2011 8:08 PM

  • Error after second level approval in ESS leave request

    Hi Experts
    I am using custom workflow for Ess Leave request process which is copied from WS21500001.
    I have added custom class methods to change status from approved to sent.
    Then another method i have set next appovaer.
    The problem i m facing is that I am getting an error on portal after second approval approves the request.
    i.e Field syomol has not been assigned yet.
    from st22 i found its generating from
    Include LPT_ARQ_REQUEST_UIAF06  - Form   execute_approver_update
    By debugging i found that Its not getting next approval with status T as there is only first approval with status 'A'
    This results in unassigned field symbol. and then error.
    Please help me resolve this issue.
    Please confirm why next approver is not found in method.

    Hi All
    Thanks for your reply.
    I checked why it was giving a dump.
    This execute_approver_update subroutine takes approval data from table ptreq_approver .
    I filled this with resp actor id after request is approved and status is changed to sent.
    For every emp its unique actor id is saved in ptreq_actor table agaist his pernr.
       SELECT SINGLE actor_id FROM PTREQ_ACTOR INTO actor_id WHERE objid = nextApprover_pernr.
        wa_appr-mandt = sy-mandt.
        wa_appr-request_id = Request_ID. "Req.requestID ( from Workflow )
        wa_appr-version_no = version_no. "Req.Version ( from Workflow )
        wa_appr-seqnr = seqnr. "Same as version no but in char
        wa_appr-approver_ins = actor_id. "Employee actor id from ptreq_actor
        wa_appr-status = 'T'. "Manual
        append wa_appr to it_appr.
        INSERT PTREQ_APPROVER FROM TABLE it_appr .
        commit work and wait.
    This resolved my issue.
    Thanks

  • ESS leave request - Change Approver

    Hi,
    We have a situation in which a employees dotted line manager will approve the leave request instead of a direct manager. We have a custom relationship to establish the dotted line manager. Now, In the ESS leave request there is a Approver field which shows the Employees direct manager. Can we customize the logic using a BADI or User exit to show the dotted manager?.  Please let me know which enhancement is to be used for this requirement.
    Thanks in Advance for your assistance.
    Ramesh

    in the customizing for the definition of the processes per rule group
    you set the selection for the next processor to "Manual Entry".
    or for the BADI
    Another way is to use the BAdI Control Processing Processes for Time
    Management Web Applications (PT_GEN_REQ) and implement the methode
    IF_EX_PT_GEN_REQ~FIND_RESP_AND_DEFAULT_NEXT_PRC.
    Method FIND_RESP_AND_DEFAULT_NEXT_PRC of badi
    PT_GET_REQ  might be utilised here.
    Please have a look at the  method
    CL_PT_REQ_SEARCH_NEXT_P~SEARCH_NEXT_PROCESSOR.
    If you are implementing the badi then make sure you copy all the methods
    and implement the one, as mentioned.

  • Next level approver in ESS leave request

    hi friends
    Am working in ESS leave request workflow. In my scenerio there are 4 level approver. I have function module SWX_GET_MANAGER  i have copied and customized to ZSWX_GET_MANAGER with my logic to get the next level approvers. If i entered the PERNR it return all the approver for that employee. How do the workflow know he is the 2nd level approver, he is the 3rd level approver. How can i achieve it. kindly help me...
    Regards
    vijay

    Hi Vijay,
    I think you will need to use a loop and a counter so you know the approval level. You can use this to get the manager who belongs to the level.
    Regards,
    Martin
    PS I hope you will show in the thread which solution you got so others will benefit. This forum is about sharing knowledge and one way is to give the solution in your thread, or value the appropriate answers.

  • How to create iView for Leave Request Approval for ESS Tab in Portal

    Hello ,
    I am new to  Enterprise portal. I got a requirement for creating iViews.
    How to create iView for Leave Request Approval for ESS Tab in Portal.??
    Please give me clearly or provide any document.
    Thanks
    Risha

    Hi Risha,
    is it customized application ?
    If so in SWFVISU transaction maintaain the entry .
    Use transaction SWFVISU to prepare standard setting for your Workitem in the UWL. --Parameters for Work Item Visualization in the UWL.
    Have a look at below link
    http://help.sap.com/saphelp_nw2004s/helpdata/en/59/d516690e854c7090ae15bf492a869f/content.htm

  • Team Calendar in Read-Only Mode in Leave Request Approver Screen

    Hi,
      After lots of interaction and inputs in my previous thread,
      Customization Done for 2 level approval of leave in ESS but Facing Problems
           Our Team had decided to make the Team Calendar in Leave Request Approval Screen in Read-Only Mode (more precisely modus=TeamView)
           My question is, is it possible to achieve the same, because instead of adding custom validations using Custom RFC, If it is possible to make the Team Calendar as Read-Only than it will help us to achieve our goals. Please do let us know that is it possible? and, if Yes, How to achieve it?
          On leave request approval screen, we want Approver to take any action via "Show Worklist" and No User Action allowed on Team Calendar (Disabled but not InVisible).
      Thanks,
    Regards,
    Tushar Shinde.

    This is the note 1484853 but as i said you cant see it unless you raise a Message for SAP , We have to add yout company to the note.
    these are the steps
    Symptom
    In LeaveRequestApprover application, a higher level manager can
    approve/reject a leave though he/she is not the owner of the approval
    workitem (TS12300097). It happens when a higher level manager clicks on
    the leave in the TeamCalendar launched from the LeaveRequestApprover
    application.
    Other terms
    LeaveRequestApprover, TS12300097, prepare_select, WorkList,
    LPT_ARQ_REQUEST_UIAF07
    Reason and Prerequisites
    Reason:- This is caused because the approve/reject button were not
    restricted based on the logged in user.
    Prerequisites:- IT105 entries for the backend PERNRs should be correctly
    maintained.
    You can check here
    Object REPS LPT_ARQ_REQUEST_UIAF07
    Object Header FUGR PT_ARQ_REQUEST_UIA
    FORM PREPARE_SELECT
    the note is meant for few customers only

  • ESS Claims - Requested value Rs. 20000 is greater than balance eligibility

    Dear All,
    While Approving the ESS claims request getting a error message Requested value Rs. 20000 is greater than balance eligibility value 0.00.
    Help in solving this issue.
    Regards,
    Potru.

    Hi,
    This is a correct error. Please check the balance amount in infty 45 for the particular loan type. The loan request should not exceed that.
    Hope this helps
    Regards
    Roy

Maybe you are looking for