Change default approver name in ESS leave request

Hi,
Please help me..
I am creating leave request Workflow.
When i go to ESS and try to create Leave Request, ESS already defaults the Approver, and its in display mode only.
I see the F4 help in Approver field and when i try to select from F4 help, it does not take new value. It's still the same value as it was default to initially.
How can i use F4 help and change the default approver name?
Can anyone please help me...I dont know where the things are missing.
Thanks in Advance
Shipra

Thank you all for your reply..
When i changed the configuration, now its allowing me to change the approver while submitting the leave request.
But now it also allows me to enter my user id itself to approve the request
Is there a way that system allows you to enter only your immediate supervisor or supervisor of the supervisor and so on?
Please help thanks.
.shipra

Similar Messages

  • 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.

  • 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 in Time calculation without changing work schedu

    Hi All,
    We are implementing a ESS Leave Request in EP6 with backend HR ECC5.0.
    The time calculation is taken  from the Work schedule rule in
    HR backend which is 24*7.
    For example if the leave taken is for 2 days-systems calculates as 24*2=48 hrs
    but in actual the requirement is to calculate 2*8 =16 hrs without changing
    the Work Schedule in 2001 infotype in HR Backend.
    Can we do this change through
    1.Validation in portal itself
    2.Changing the RFC PT_ARQ_REQUEST_CHECK
    3.Changing the Absence Types
    Regards
    Anand.

    Hello,
    Please use:
    programming
    but without the spaces before and after } and {
    Testing:
    programming
    regards
    Rick Bakker
    Hanabi Technology

  • ESS Leave Request - Customer fields default function not working

    Hi,
    a. SAP version being discussed
    SAP ECC6.0
    EP7.0
    ESS/MSS
    b. Here is the scenario
    1. We are using ESS Leave Request application for employees to request leave. We are using the standard web dynpro java leave request application delivered by SAP.
    2. Lately there has been a need to provide a customer field on the request form which will have a calculated value showing up when the employee opens the request
    3.We used one customer field called customer01 as per configuration steps.
    4. This field appears on the request form when it is opened.
    5. Our need is to display a value in that field when the form is opened.
    6. SAP/s documentation states that we can use BADI PT_ABS_ARQ to default a value to this field on the form. This value is calculated during runtime dynamically.
    7. We have used the method IF_EX_PT_ABS_REQ~SIMULATE_VIA_BLOP for this purpose
    8. After activating and coding this implementation, the system does not default anything on the request form when it is opened up.
    9. Once the employee hits the review button, this field gets its defaulted value but this is not what we want. We want the system to display this when the form is OPENED, that means at the prepare stage. For this field to appear after hitting the review button is meaningless as the employee needs to make a decision based on the value in this field before hitting the review button.
    It almost seems like this BADI is called when the review button is hit and not when the form is opened up. We may be wrong and missing something obvious which one of you can immediately point out, Hence this post.
    10. I did go thru the forum at great length and seen that there has been discusion surrounding the need to populate R3 from a value entered into this field. My problem is different wherein, I wish to populate this upfront as display information when the form is opened and then send it back to R3, once the employee submits the request.
    Would be grateful if anybody on this forum could point me in the right direction.
    Thank you,
    Rajesh

    Please, can I take this question a little further.
    Is it possible to add more fields to the leave request form on the ESS portal. For example, our customer wants additional fields like reason for leave, contact residential and telephone number during leave, Require leave entitlements (Yes/No).
    Would appreciate if a reply can be given on if it is possible or not and what to be done if it is possible.
    Cheers

  • 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.

  • ESS Leave Request - Set Workflow status to Completed

    Hi,
    We are on ECC 5.0 and we are using ESS to process Leave Requests. We have a custom Workflow based on the standard Workflow template WS12300111 for approval of Leave Requests.
    Whenever an employee creates a Leave Request via ESS the Workflow is started. When the employee deletes the request the Workflow has to be stopped/completed. For this we have put a Wait for Event step in a parallel branch to the Approval Process. In the Wait for Event step we wait till a condition ( Request.status = DELETED ) is met.
    But when an employee deletes a Leave Request the request is deleted from the list but it gives a message as "Specify a class name".
    Can anybody please help us on this( how to complete the workflow whenever the Request is deleted ) and let us know what is the procedure to do this.
    Thanks in advance.
    Regards
    Immanuel

    Hi Prashanth
    Thanks for your quick reply. But that would not solve my problem. My Workflow looks something like this
                               WF-started by entries in configuration tables
                             Some activity in background
                         A fork with 2 parallel processes
                        Approval     Wait for an exception condition using Wait for event step
                          process          (wait till an attribute of a object has a specific value)
                              Workflow completed
    The wait step waits for the status of the object to change to DELETED.  The Workflow should get completed either if the Approval process is over or the condition specified in the Wait step is satisfied.
    But in the case of ESS Leave Request this doesn't work. Is there anything that we need to do to set the status of the Workflow to Completed if the Leave Request is deleted.
    Thanks
    Immanuel

  • ESS Leave request workflow : ws12300111 : Customizing

    Dear experts,
    I need to customoze ESS leave request workflow WS12300111.
    Can you please tell me do I need to Copy this to a NEW workflow generating a new WF no or can I simply generate a new version for this only ? What is ideal ?
    1. Can anyone tell me step by step process(config) in ESS leave application workflow?.(SWFVISU????)
    2. Is workflow WS12300111, the only workflow that I need to look for leave application ?.
    3. If it is WS12300111 I don’t see any start event for this workflow. So how is it getting triggered?
    4. For the approval task TS12300097, agent determination is done by expression ‘&Agent_0001.Agents&’. How does it interact with Org.Structure.
    5. In my scenario, approver should be supervisor of the employee applying for leave. If it is pending with this approver for 5 days it should go to the next up level manager.
    For identifying first level approver is ‘&Agent_0001.Agents&’ enough.? For identifying 2nd level approval do I need to write a rule ?
    Kindly help.

    Hi Sourav,
    Try this step by step process(config) in ESS leave application workflow.
    ESS Scenario
    Workflow Process 20000081 u2013 Create Leave Request with HTML
    Steps for triggering the workflow:
    1) The employee logs with his user name in the ESS web page.
    2) The employee creates a leave request with an optional note and sends it to the appropriate approver (usually his supervisor). The approveru2019s name is automatically displayed in the leave request form and the employee can replace him with another if such a change is needed.
    3) The approver (us approver) logs on to sap system or to ESS
    web pages and reads his mails in the SAP Business Workplace. The employeeu2019s leave request form appears in the workflow inbox with approve and reject options.
    A) If the us approver approves the leave request, he pushes the
    button approve from his mailbox (processing status A with
    approve). A screen is appeared with a box (Table entry: 0001)
    and the approver must push the button continue in order that
    the workflow is continued. Then the form is sent to the
    employeeu2019s mailbox in Sap. When the employee opens his mails, he receives a note in his inbox that u201Cthe absence from u2026. To u2026..has been approved byu2026.u201D.After that the absence is
    automatically created in the sap system. Then the approver gets a mail (notification of completion & Return u2026u2026).
    B) When the approver cancels a leave request, he pushes the
    button reject and the processing status changes to u201CRu201D.
    Then the same form appears
    Realative OSS Notes:588262, 480103, 717560, 452841, 359197, 321439, 428394, 321439, 693368, 451998 (ITS), 197746 (ITS), 419297 (ITS)
    ITS - ESS stand-alone solution for 4.7
    This solution allows customers to schedule the 4.6C or 470
    install / upgrade independently from the Enterprise Portal or
    mySAP Workplace implementation and will be supported at least as long as SAP R/3 4.6C and R/3 Enterprise is supported.
    This ESS stand-alone menu is intended solely to allow independent scheduling of the 4.6C or 470 upgrade and the Enterprise Portal / mySAP Workplace installation. To use this solution, you have to take the following steps:
    1. If you do not already have R/3 4.6C, HR support package 8,
    please import HR support packages to at least this level. From
    HR support package 8 and above, the correct services are
    implemented. For 470, the corresponding recommended HR SP is 16 (See note 621589)
    2. Verify that the ITS you want to use does not contain a service or service-related files (HTML templates, MIME files) for the services PZLE, PZM3 or PZM3_start. If you find these files,
    delete them.
    3. Publish the services PZLE, PZM3 and PZM3_start from your R/3 4.6C system (or R/3 470 system whichever is the case) to your ITS using the SAP@Web Studio or the IACOR service.
    4. Maintain the username-employeenumber assignment in your system by customizing Infotype 0105, Subtype 0001 of those employees, who should be able to use ESS.
    5. Verify that your users have proper authorizations for
    executing RFCs (that is, authorization object S_RFC) from the
    function group EH08. If you run into problems, this is most
    likely due to missing RFC authorizations to start the service
    PZM3.
    6. Your users should now be able to access ESS by starting the service PZM3. They can do this by entering a URL like
    http://<ITS server>:<http port>/scripts/wgate/pzm3/!
    (the ! at the end is essential).
    7. ESS 4.70 Unicode System ITS 6.10 patch level 29 and above (With IE and Netscape). ITS 6.20, patch level 6 and above (With IE only).
    The ESS development tested these ITS versions.
    8. For Release 4.6C, ESS has the same browser requirements as the HTML (see also note 178788) and the mySAP Workplace 2.11 (if ESS is accessed through the mySAP Workplace 2.11).
    Hope it helps.Do award points if found helpful.
    Regards,
    Gourav

  • Issue with ESS Leave request workflow - Deleting a leave request

    Hi friends,
      This is my scenario: An employee has created a leave request from ESS - Leave Request Workflow(Copy of  WS12300111) gets triggered and work item gets created in manager's UWL. After that the employee realizes he has created a wrong leave request so he deletes that leave request from ESS. In this case the workflow instance which got triggered when he created the leave request is under process and the work item stays in the Manager's UWL( there is no terminating event or wait for event step in the approval step of workflow WS12300111), when the Manger opens that work item it shows a blank column, ideally speaking when the leave request is deleted by the employee the work item in the manger's UWL should be logically deleted and the workflow should complete, but this part is not handled in the standard workflow WS12300111as well. How to handle this case. I can put a wait for event or a condition to complete a work item at the approval step but i would like to know how the standard ESS leave request framework works in this case. Please advice.

    Hi sapient
      This is not handled in std. You have clear the next processor in your in method then only the work item will get vanished from the UWL.  For clearting the next processor either you can create a method in your BOR and get the request id. For the request id get the max version and clear the next processor or in the BADI you have wirte your own logic when the change happens what you have to do. This logic has to be written in you BADI.  I thing BADI will start with PT_ check with that name in se18
       You cannot use wait for event or terminating event since its not R/3 workflow its ESS workflow you cannot use ternminating event or wait step.
    Regards
    vijay

  • ESS leave request 2 level workflow??

    Hi friends,
    Does anyone know how to create a 2 level workflow in ESS leave request?? im not able to find any solution for this.
    looking forward for your reply...
    thanks in advance
    sudhir

    Hi Sudhir,
    You dont have to create a new status for such scenarios. The Java WD Leave Application lists all the Leave Requests that are in SENT status. So after the first approval is done, the status is set to APPROVED in case if it is approved. Now, we have to reset it to the status SENT if you have one more level of approval.
    This can be achieved in 2 ways.
    1) Changing your Standard Class's coding as suggested by SAP in the above thread.
    2) You create one custom BOR with one method - RESETSTATUS - Which resets the status of the Leave Request back to <b>SENT</b>. You can get the required coding from <i>APPROVE</i> method of the above mentioned class.
    I followed the second method.
    I hope this should clear our problem.
    Regards
    <i><b>Raja Sekhar</b></i>

  • Advanced search in ESS leave request scenario

    Dear experts,
    we want to use the leave request scenario for ESS. The employees should choose the ap-prover with the search help (or advanced search which pops up when the user clicked the symbol at the edge of the approver field). Is there any way to customize the advanced search so that the result only lists employees in a specific role and not all of them? Where can I see the code from the advanced search und where can I change this?
    I am thankful for any hints and tips!
    Many thanks
    Diana Natanegara

    Re: Advanced search in ESS leave request scenario

  • How to add new fields for ESS leave request

    Hi friends,
    Can u please help me with my issue.......
    My issue is to add new fields in ess/leave request i.e...
    The component needs to be Checked-out through Net Weaver Development Infrastructure, make the necessary enhancements, and finally Check-it-in back to NWDI.
    Custom Function Modules are to be invoked apart from the standard ones that are already available in the Leave Request component – ess~lea inorder to accommodate the extra absence-type logic.
    can u please sujjest me where should i make changes in the given 14 components
    means in which view i have to add these fields.................
    Regards
    Rajesh

    Hi Rajesh ,
    Check whether u are able to find the ess dc's under inactive dc's in webdynpro
    If ur not able to find it then Check the landscape configurator in CMS and also the transport studio and confirm that ess packages are imported fine
    Ganesh ,
               for creating a DTR client u need to open the DTR perspective right click and "create clients" before that go to windows ->preferences of the NWDS and check the development infrastructure URL is gven correctly ...try pinging it once...
    Do check ur SLD is up or not!!!
    Regards
    Krishna
    Message was edited by:
            krishnagopal Mukundan

  • Problem with ESS Leave Request Workflow

    We had configured ESS Leave request, which is working fine with Leave request approval.
    1)     Cancellation of Leave Request using the workflow WS12400005.  
                                  Workflow is not getting triggered when we try to delete the leave request.
    2)     Quota Overview
    While displaying the Casual Leaves (CL) I need to deduct the Paternity leaves (PL) also.
         Remaining CLu2019s = quota CLu2019s u2013 ( used CLu2019s + used PLu2019s).

    hi kishore. how did you resolve the issue of workflow not being triggered?

  • ESS leave request, additional field

    I need to add three additional fields in ESS leave request (HR). I was told i can do that using web dynpro. I like to know how can I do it.
    Thanks

    hi Jeroen,
    Can u please help me with my issue.......
    My issue is to add new fields in ess/leave request i.e...
    The component needs to be Checked-out through Net Weaver Development Infrastructure, make the necessary enhancements, and finally Check-it-in back to NWDI.
    Custom Function Modules are to be invoked apart from the standard ones that are already available in the Leave Request component – ess~lea inorder to accommodate the extra absence-type logic.
    can u please sujjest me where should i make changes in the given 14 components
    means in which view i have to add these fields.................

  • How to craete a 'annual leave 1/2day-AM'  in ESS  leave request

    Hi ,
    I have created 2001- subtype 670 : "annual leave 1/2day-AM".
    I wanted to see "annual leave 1/2day-AM" in the ESS leave request list down box ( already we have few ) ... please let me know what are the steps i need to follow ...
    thanks,
    sunitha
    Edited by: Sunitha Reddy on Sep 19, 2008 9:27 AM

    Hi,
    Your ABAPer will be the best person to let you know the table name or some experts here who have come across this situation will guide you. Also check where other types of leaves are populated in SAP and your new value is there or not.
    Thanks,
    Preetham

Maybe you are looking for