ESS Leave Resquest

Hello Experts,
I am implementing Business Packages ESS 1.0. My problem is in the service leave request at moment verify the absences show me a message ''the infotype not exists''.
help me please, I am new in this forum
Thank

Cagalera,
This issue is not related to portal. I guess it is related to Infotype 2001 in some way. Check with your HR consultant.
Your issue could be addressed in a better way in either of these forums.
[HCM|SAP ERP Human Capital Management (SAP ERP HCM); or [ERP ESS|SAP ERP HCM Employee Self-Service;
Thanks and regards,
Sandeep Tudumu

Similar Messages

  • You are not a receiver of the work item in ESS Leave

    Hi,
    We are using standard ESS leave application in our portal, where employee can raise leave and his manager can approve/reject his leave. But I want in case manager rejects the leave, the rejected leave should not come into MSS UWL of employee, we will send a mail to employee and he can again login to ESS leave application and where he will see the rejected leave and he can re apply/change/delete  the rejected leave. We do not want rejected leave to come in UWL of employee as a work item.
    As of now when manager rejects the leave rejected leave of an employee , it is coming in UWL of the employee which we do not want, so what we did, we went to standard leave work flow template WS12300111, in that we double clicked on Task (TS12300116, Process Request by Employee) and in that  we clicked on agent assignment icon and than we clicked on attribute and we selected General forwarding not allowed radio button, by default general task radio button was selected.
    After selecting General forwarding not allowed radio button, even when manager rejects employee leave, rejected leave is not coming in UWL of employee which we want exactly, but another error is coming when employee goes to ESS leave application again and change or delete this rejected leave he is getting the error You are not a receiver of the work item .
    But if we select general task radio button in agent assignment in work flow , than eveything is working fine but employee is getting rejected leave in his UWL, that we do not want  at all, so why after selecting different radio button this error is coming ?
    Why employee is getting this error, why employee can not reapply/change his rejected leave. Is this portal error OR workflow error OR HR configuration error and  what is the solution for this..

    If you need this option then you need to change the WF Task.
    General Forwarding Not Allowed
    This indicator enables you to determine that work items for this task can only be forwarded to users who are agents for the task.
    If this indicator is not set, a work item for this task can be forwarded to all users.
    The best way to take care of User
    Forwaring authorization is the Task Classification (PFTC -> Additional
    Data -> Classification). Classify tasks with General Forwarding Not
    allowed, will give you the oppotunity to let the user allow to forward
    items JUST to the Possible Agents Assigned to the task
    (Additional Data -> Agent Assingment -> Maintain)...
    Clear that everything depends on How you have developed your workflows
    definitions. In that cases  the best think to do is
    create Different Tasks definition (TSxxxxxx) and let they start
    depending on Company Code (That can be driven via Conditions steps in
    the workjflow definition, for example). This will allow you to define
    Just the responsible Agents per each task, depending on the Companny
    Code. This definitively Resolve the Forwarding frelated Question.

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

  • 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

  • Add a custom button in Ess Leave Request

    Hi Gurus,
    I have requirement, add a custom button in a Standard ESS leave request (Webdynpro Java). When i click the the button it has to call popview(custom view). I am new to webdynpro Java, If possible explain me with step by step preocedures(if possible with screen shots).
    Thanks,
    Mohammed.
    Moderator message: this is the wrong forum, please have a look in the "Web Dynpro Java" forum, but always search for available information before posting.
    Edited by: Thomas Zloch on Jun 17, 2011 9:54 AM

    Hi Gurus,
    I have requirement, add a custom button in a Standard ESS leave request (Webdynpro Java). When i click the the button it has to call popview(custom view). I am new to webdynpro Java, If possible explain me with step by step preocedures(if possible with screen shots).
    Thanks,
    Mohammed.
    Moderator message: this is the wrong forum, please have a look in the "Web Dynpro Java" forum, but always search for available information before posting.
    Edited by: Thomas Zloch on Jun 17, 2011 9:54 AM

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

  • ESS Leave Application - Custom Field - Validation

    Hi,
    We have added two fields that are being shown in ESS Leave. Fields which are added are KEPAU and EXPAU through SPRO.
    We want to do validation on these fields.
    KEPAU is Annual Ticket and EXPAU is Vacation Allowance
    We have implemented BADI PT_ABS_REQ to do validation but in this BADI these fields are not being populated.
    Anyone knows that why these both fields are not appearing in BADI?
    Thanks,

    You need to check in  PT_ARQ_REQUEST_CHECK.
    and also read here
    http://wiki.sdn.sap.com/wiki/display/ERPHCM/ValidationsforESSLeaverequest

  • 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

  • Enhancement in ESS Leave Request

    Hi Gurus,
    I am new to webdynpro Java. I have a requirement to add a custom button in a Standard ESS leave request (Webdynpro Java) view. When i click the the button it has to call popview(not sure is it possible to call a webdynpro abap view).  If possible explain me with step by step preocedures(with screen shots).
    Thanks,
    Mohammed

    Hi,
              Good, you are now able to do modification in Standard ESS package. If you want to navigate to another WDABAP iView from your WDJAVA application, you can use the below code on some button or link action to navigate to another iView.
    Check this link:-
    http://help.sap.com/javadocs/NW04/current/wd/com/sap/tc/webdynpro/clientserver/navigation/api/WDPortalNavigation.html
    public void onActionnavigateToToAbapiView(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
        //@@begin onActionnavigateToAbapiView(ServerEvent)
         try
                        WDPortalNavigation.navigateAbsolute(
                         "ROLES://portal_content/com.demo.DEMO_PCD/com.demo.ESS_SAP/com.demo.iview_ESS/demo.com.java_demo_com_demodc_demo_com_DemoApp",
                         WDPortalNavigationMode.SHOW_INPLACE,
                         "Window Title", WDPortalNavigationHistoryMode.NO_DUPLICATIONS,
                         "Title",
                         "",//ContextURL
                         "param1=10&param2=portalID");          
         catch (Exception e)
              e.printStackTrace();
    You will find your WDAbap PCD location in Content Admin, copy it and repace PCD: with ROLES at start.
    also you can pass parameters between 2-iViews, in the above code snippet you can find that.
    the above code needs to be written in your source iView so as to navigate to destination iView which is mentioned using its PCD location.
    to retrieve the parameters you need to check ABAP syntax to retrieve URL parameters.
    In java we retreive using below syntax:-
    String param1 = WDProtocolAdapter.getProtocolAdapter().getRequestObject().getParameter("param1");
    String loginID = WDProtocolAdapter.getProtocolAdapter().getRequestObject().getParameter("param2");
    to show it as a Pop-Up you need to find some work-around to achieve it, If i get time will do it and let you know, but if you find something for that do share.
    Regards
    Tushar Shinde.

  • ESS leave request two-level workflow

    Hi All,
    We have a requirement for a two-level ESS leave workflow and need to know what would be the approach which can be taken to modify the standard 12300111 workflow.
    The status should be as follows
    STATUS                                                STATUS                                                  STATUS
    (SENT)                      Approves              (PENDING)                 Approves                (APPROVED)
    First Level approver -
    >   Second level approver -
    >
    As we can see, we need to add a new status namely, PENDING to the backend PTREQ tables. Can anyone please provide some kind of leads/info on this.
    Thanks and Regards
    Reshma

    Hi,
    You can take a copy of that standard workflow 12300111 and build your logic accordingly.and give that workflow number in SPRO settings.
    Kind Regards
    Hari SankarM

  • 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

  • FMLA relevant absence Message in ESS Leave Request

    Hi Experts,
    I am on ERP2004, EP6.0SP20.
    I have configured the ESS Leave Request and activated the workflow. When an employee submits a leave request, he sees a message "the requested absence type is an FMLA relevant absence". However, the requested absence type is not a FMLA relevant absence.
    I would like to stop this message coming on to portal. I am not sure whether it is related to Time Management configuration on absence quotas etc. Has any body seen this message?
    your help will be greatly appreciated!

    Messages can be hided in Leave Request through configuration on R/3 side. NWDI customization is not necessary.

  • Ess/Leave Workflow Still In Process(In a specific snario when Escalated )

    Hi Guru's,
    I have a problem with Ess/Leave workflow.
    when the leave is applied from the portal which is triggering workflow and reching to the right agent and when the leave is withdrawn , then which is completing the workflow which is fine.
    Recently i have added Escalation functionality using deadline monitoring which is working fine.
    But when the leave request is escalated and withdrawn from the initiator is not changing the status of the workflow to be completed and still continuing in the Still In Process.
    To complete the workflow ,there is an wait event after the approval process which is waiting for the status change for posted or withdrawn or error and working fine when the work item stayed with the direct manager and no escallation is happend.
    When Escalation happend and the leave is withdrawn the status is changing in the workflow container to withdrawn but the event is not firing in the wokflow which needs to be triggered to complete the workflow which is not happening and the work item keeps on escalating to the other managers.
    Please help me ASAP and let me know if anybody not clear about anything.
    Regards,
    Raj.
    Edited by: rajasekhar bhupathyraju on Sep 6, 2010 11:46 AM

    Helo Every one,
    thanks for your inputs,
    I m not sure that wether i explained properly or not.But i will try to explain more elobrately.
    My leave request workflow is Zworkflow which is working fine in the production.Recently in the last month business request for escalation of leave request when direct manager not approved with in the time frame.
    So i added latest end to the Approve task which uses the ABAP class CL_PT_REQ_WF_ATTRIBS and Method Dummy.
    So the task has 3 outcomes one is deadline reached,process obsolete and processed. and after that i added a loop which will create new work item when escalated.
    When i apply a leave on the portal the workflow is triggering and stopping in the Approve step in the log which is fine and when i with withdrawn the leave without any escallation it is taking one of the brach Processed which i mentioned above and reaching to the event and completing the workflow which is 100%.
    When the direct manager doe'nt approve then it is escallating to the next level manager which is fine.Once the escallation happen and the leave is withdrawn by the Employee(Initiator) then it is not taking any of the 3 paths which i mentioned above and not reacting at all.But the status in the workflow container REQ.STATUS is changing to "WITHDRAWN".
    The same thing is happening for the APPROVE once escallation happens.It keeps on escallating even the leave is approved and posted in the database.
    Please reply me if you are not clear.
    Thanks,
    Raja.

Maybe you are looking for