Absence Request Workflow

Hello fellow Sap'ers.
I have an issue in a client which is the following. Due to an error in customizing for a few days, the absence requests created in ESS did not initiate the workflow for the request. We were able to find out the problem and fix it, but the problem is that meanwhile all absence requests created in this interval of days are "stuck" and don't appear in the task list for the aprovers. I have checked and the requests are created (PTREQ* tables) are all ok, the request is created with the status SENT and only has the version 1 record.
So my question is, how can i replicate the natural process, creating the workflow process for these requests ? I have tried with FM SAP_WAPI_START_WORKFLOW but i think i'm missing something in the containers, has i get an error.
The task we are using is WS90200027 which is probably a copy of the standard task for the Absence requests.
Thanks for all the help in advance.
Cheers.

Thanks for the reply, but we have solved this in another way. Using the program RPTARQUIATEST as a working base, i was able to find out that due to customizing when a request is in SENT status, a new send won't iniciate a workflow process, so i needed to reset the status to NEW and generate a EXECUTE_SEND event for these requests. Thanks for the help anyway.

Similar Messages

  • Absence request workflow does not start

    Hello, I have created a workflow for absence request and I configured it in transaction PTARQ for my absence type.
    I tried several times making an absence request from portal but the workflow does not start. I have also seen in transaction PTARQ that the request was really made and has status SENT but has no workflow associated.
    Any help?
    Thanks

    Hi Mário,
    Check using transaction SWIA to see if the workflow is actually started by the leave creation (if not could be a problem with the event trigger)? If it is started, you should see in SWIA where the workflow stops/breaks down, normally this is due to missing container elements or bindings.
    Good luck!
    Gareth

  • ESS deleting an Absence request before approving it.

    Hello,
    I have problems stopping the ESS Absence Request workflow after the user deletes it before the manager approves.
    Reproduction scenario:
    - The requestor creates an Absence request.
      ... the workflow (a copy of WS12300111) is instantiated
      ... the manager of the requestor gets a work item
    Now the requestor decides to delete the absence request...
    - Requestor deletes the absence request.
      The user now gets the information message:
      ... the ESS application now tries to complete (FM: <b>SAP_WAPI_WORKITEM_COMPLETE</b>)  the Work item of the manager.
      No administrator found for the task
      (By debugging, I found out that this was message 5W 141.)
    The <b>result</b> is that the request document is ended with <b>status WITHDRAWN</b>, which is correct, however the workflow has still a READY work item for the manager which he cannot start anymore.
    Analysis:
    The error message is a little bit weird, because it actually ment that the requestor is not an agent for the work item of the manager.
    I could solve this problem by giving the requestors more authorization. When I added SAP_ALL to the requestor, the error does not occur.
    The transition table determines:
    Documentstatus: SENT
    Status transition: DELETE
    Workflow control: CONTINUE Continue Workflow
    ...that's why it start FM: SAP_WAPI_WORKITEM_COMPLETE
    I hope you have an answer to my problem.
    Kind regards,
    Alwin van de Put
    (I expected that ESS would make use of events for terminating work items in stead of using SAP_WAPI_WORKITEM_COMPLETE.)

    Hello Ravi,
    Thank you for answering.
    The standard task is a General Task.
    The main problem is, that the agent determined in the step (in my case: Expression: &AGENT_0001.AGENTS&) is not the one who will complete the task.
    This is the case when the Requester deletes (withdraw) the absence request, than the ESS function module tries to complete the work item of the Manager with the user of the Requester.
    We could solve this problem by giving all requesters the following rights:
    S_CODE id TCD field SWIA.
    But we don't want to give all users rights to transaction SWIA.
    Kind regards,
    Alwin.

  • 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

  • Cancelling a absence request haas not changed the status by the user

    Hi experts,
    An absence request has been cancelled,. Looking in Status Monitor, i will see that the reuest has been cancelled, but the user see the status stay on "Pendig For Approval". Normally the user will see the Absence Category set to Cancelled, but not "Pending For Approval". The reason is unknown to me. Thus i need your support.
    Thanks in advance
    Mehdi

    Just to confirm my understanding, are you saying that:
    1) Employee requested an Absence through SSHR Leave of Absence
    2) An administrator queried the absence in the Workflow Status Monitor and Cancelled it
    3) Now that absence is showing to the Employee as 'Pending Approval'
    Is that right? You mention 'Normally the user will see...'. When you say 'normally' what is the behaviour you expect?
    If I've understood you correct this is the behaviour I would expect: cancelling a workflow does not change the status from 'Pending For Approval' and it definitely does not change the Absence Category on the absence. Cancelling an absence via this route isn't really recommended because - as you are seeing - it gets stuck. It's best to get the approver to reject the absence instead.
    To remove this cancelled absence, take a look at these Oracle Support articles:
    Unable To Remove Cancelled Workflow Item Related To LOA Transaction [ID 1123714.1]
    How to Purge Obsolete Workflow Runtime Data (FNDWFPR) for HR Workflow Completed Processes [ID 237564.1]
    How to Run the HR Workflow Cleanup Process (HRWFDFCT) [ID 237524.1]

  • Leave request Workflow  WS12300111 not working

    Hello All,
    We have ESS/MSS portal and ECC6.0. I have started with pilot ESS leave request project
    When i create the leave request from ESS, i am getting message '  The leave request has been sent.'
    Evne i am able to the see the task in UWL(MSS) in tracking tab. But if log in as a manager to approve the leave request, its not displaying the task. I have checked the workflow, its getting stuck. Then i have checked leave process(test application) in R/3 alone in transaction PTARQ. I have given my person number and mode 'R'. Its throwing error message " No document created : HRTIM_ABS_REQ 124 conflict with absences/relocation (IT2001/0330)
    But i have customized workflow properly in 1. SWU3 ; all are green except guided procedures
                                                                          2. Maintained the WS12300111 in workflow template for all
                                                                          3. Request have to approved
                                                                          4. task is generated
                                                                          5. line manager as agent (OM maintained properly)
    Kindly help .
    Regards,
    Venkat

    Hi ,
    I have changed the pernr ,date and working fine now.Moreover task is  also general. But the workflow started but stuck in the step 'Approvel Process.
    Its stops at Node number 38 . I have checeked the step history :
    Green  (Sub)workflow created
    Green  Background Processing Started
    Green Execution started
    Green Error Message Created for Admin
    Red    Exception occurred  Error handling for work item 000000390153
    I just want to execute the leave request workflow  from PTARQ, keeping as me as requestor and approver. If its success , i want to test with ESS. But now its stuck in R/3 test itself. Please help.
    Regards,
    Venkat

  • Mitigation assignment approval in Access Request Workflow

    Hi Guys,
    I am currently implementing GRC for one of the clients. I have a question with respect to Mitigation assignment approval in Access Request Workflow.
    Below is the Scenario,
    1) User Submits the request
    2) Manager Approves
    3) Role Owner runs the SOD & finds SOD violations. Role Owner assigns the mitigation controls & approves the request
    Clarification:
    Once the role owner approves , depending on the mitigation controls assigned , can this request be routed to the mitigation control owner for approval in next stage? is this configurable with out custom BRF+ rules ? I know there is a workflow separately  (SAP_GRAC_CONTROL_ASGN) for approval of assignment which I suppose is out side of the Access request workflow.
    Please suggest.

    Pavan,
    more or less - as the control assignment workflow is independent the access request doens't wait. So if the role owner set a mitigation the control workflow starts. If you allow the role owner to approve the access request with risks, means if the risk isn't mitigated, then the role owner can proceed.
    To have your scenario working you must set the following in Access Request workflow: Role Owners are not allowed to approve as long as there are risks. All risks must either be remediated or mitigated before approval. That means if the role owner sets a mitigation the assignment workflow starts. As soon as the mitigation is valid (final approval) the access request can be approved.
    Technically both workflows are independent and don't have a relation to each other. But with some settings you can combine them.
    Does this answer your question?
    Regards,
    Alessandro

  • Replace AR Credit Memo Request Workflow with a new Custom Workflow

    Hello friends,
    We have a business requirement to replace the AR Credit Memo Request Workflow with a new Custom Workflow whenever an Invoice is disputed (Oracle Advanced Collections).
    The Credit Memo Request workflow is being launched within the Oracle API arw_cmreq_cover. We thought of an approach wherein the Oracle form IEXINDTL.fmb can be renamed and the Custom workflow to be called in the WHEN-BUTTON-PRESSED trigger on Dispute Button instead of calling the program Unit IEXINDTL_CONTROL.DISPUTE (as in standard form) which inturn calls several API's and hence the AR Credit Memo Request Workflow. But this would override the other standard processes being carried out in these API's. Our requirement is to only replace the AR Credit Memo Request Workflow and not to override the other standard processes.
    Does anyone have come across the similar requirement? Please let us know your inputs.
    Thanks in Advance !

    I ran across the same error today. Since it's been over a month, I assume you've fixed it already or decided you didn't need it at all? What was your fix?
    For me, I noted that in the sample directory, a similar "createView" call (in End User Anonymous Enrollment) also includes this argument:
    <Argument name='viewId' value='User'/>
    When I added that to my createView call, the "Missing view id" error went away, and the user are gets created.
    I'm not entirely comfortable with the value specified, though; seems like view IDs should be more unique. I would have thought it should have been something like this instead:
    <Argument name='viewId' value='User:$(accountId)'/>

  • Functional Specification for Travel Request Workflow

    Dear All,
    EHP6 and 7.3
    The standard travel request workflow( WS20000050) is not supporting for my business process.
    So we are developing custom Workflow.
    I want write Functional specification.
    Please provide some information to write functional specification for Travel request.
    Advance thanks.............
    Regards
    Somu

    Are you kidding ?
    Do you want us to do your work ? ^^

  • ESS Absence request  Error : Lock Exception

    Hi,
         When a user is trying the absence request application , she is getting the following error, she is the only user getting the error.
    We did a server restart but that didn't solve the problem.Please suggest
    #2#sap.com/pb/PageBuilder#com.sap.tc.webdynpro.services.session.LockException: Thread SAPEngine_Application_Thread[impl:3]_36 failed to acquire exclusive lock on client session ClientSession(id=(J2EE258694500)ID0000822451DB11319429603123595159End_1457644797). Existing locks: LockingManager(ThreadName:SAPEngine_Application_Thread[impl:3]_36, exclusive client session lock: ClientSessionLock(SAPEngine_Application_Thread[impl:3]_35), shared client session locks: ClientSessionSharedLockManager([]), app session locks: ApplicationSessionLockManager([]), current request: sap.com/pb/PageBuilder).Hint: Take a thread dump of the server node to find the blocking thread that causes the problem.
         at com.sap.tc.webdynpro.clientserver.session.ClientSession$LockingManager.lock(ClientSession.java:1511)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:233)
         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.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: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)

    Hi,
        Have you deleted the locks from system administration->Monitoring and under portal check object locking. see if there are any locks and see if you could delete the locks.
    If the system is hanged you can restart the server0 (or server<n>) node to resolve the issue, but the issue may recur. Permanent solution is described in the note 1234847. There is a ppt attached to the note, you can proceed as described there.
    Cheers!!!
    Umang

  • Absence request update inconsistency in ME/CE

    Hi Friends,
    Recently we have implemented the ME/CE (Multiple/Concurrent employment ) for one of our
    customer. While testing the scenario's we have observed that absence record updating in
    IT2001 is not consistency such as when we create the absence request via PA30 its updating to all personnel assignments of personnel
    ID ,second when we creating the absence request via PTMW for same personnel ID its updating for selected personnel assignment in IT2001
    ,similarly third when we create the leave request from ESS system its updating updating for leave request created personnel assignment IT2001.
    Here bit confused what would be correct process in ME/CE ,and how should we keep the same process from PA30,PTMW,ESS
    Your inputs would be appreciated .
    We are in SAP ECC 6 .
    Regards,
    Syedr.

    Hi Siddharth ,
    We are in EHP6 ,we have enabled the CE for leave management .
    My questions is when update the leave from R/3 its copying for all assignments but when we posted the leave data from portal its not coping to all personnel assignment .
    So here I am looking is there any concept of make it copy the leave to all personnel assignment when we post the leave from portal.
    Regards,
    Syedr.

  • Validation during request workflow

    Hello,
    During the request workflow, we would like to make comments mandatory when rejecting a request.
    I added the validation :
              <Validation>
                   <cond>
                  <notnull><ref>:variables.comments</ref></notnull>
                  <null/>
                  <s>A comment is mandatory when rejecting a request.</s>
                  </cond>
              </Validation>This validation is checked only when pushing the "Reject" button, meaning that when a person approves a request (by pushing the "Approve" button), the validation is by-passed. Do you know why the validation code is executed only when rejecting the form ?
    Second question : when the user is on the "Awaiting approvals" form, he can check the boxes of the approvals he wants to reject or approve without going through the approval form. This way, the check we have added on the comments when rejected is not done. Is there a way to disable the mean to approve/reject directly ?

    Yes, you can use a RequestDataValidator (implemented as a plugin and configured in the Request Dataset) to perform validation on a request. If in that code you throw a InvalidRequestDataException it will reject the request with an error displayed. See metalink artilce [ID 1317087.1].

  • ESS Leave Request workflow customization

    Hi Guys,
    We are trying to customize the standard Leave Request Workflow WS12300111 in the ESS application for ECC6. The standard workflow passes the data to the workflow via the object REQ of type CL_PT_REQ_WF_ATTRIBS. I need to extract the leave information from the object.
    I tried creating an enhancement implementation for the Class CL_PT_REQ_WF_ATTRIBS and added my own method. But I can't see this method when I create a workflow task.
    I also tried copying the whole class and adding my code, but am not sure how to instantiate the new class in workflow. Pls help .

    Hi,
    Can you tell me the requirement.
    Do you want to change the Agent using a BADI ??
    or you want to send the leave request for another approval ??
    If you want to send the leave for another approval then just reset the status of the leave to SENT again using same class and using following code
    CALL METHOD cl_pt_req_badi=>initiate_state_transition
        EXPORTING
          im_request    = request
          im_event      = 'SENT'
       IM_RET_VALUE  = 0
        IMPORTING
          ex_new_status = me->status.
    After this, u can send this workitem to another processor..
    Another scenario could be:
    U want to determine a new agent for your workitem.
    In this case, u will have to implement BADI "PT_GEN_REQ"
    Read the documentation of this BADI.. this might help.
    And please tell me the requirement once again.. what you want to achieve.
    Regards
    Ashutosh

  • ESS Leave Request  Workflow Issue

    Hi Every one,
    Our client is using ESS/Portal Leave Request workflow(ZWorkflow template which is configured to the portal) which is working fine up to the last month.Recently i developed  3 level  Escalation functionaly which is working fine and we tested and finally transported to production in the last month .And recently i got an issue when the leave request is aproved after escallation is not setting the workflow status completed and keep on escalating to the next levels.
    Note:When the 1st manager approves the leave request without escallation the workflow status is going to be completed which is fine and only there is an issue when escallated and approved the status of that specific leave request is approved but the workflow is not going to the status completed and keep on escalating to the next levels.
    i checked the log and found there is condition based wait event step which have a condition when
    Req.status = Approved&
    Req.status = Withdrawn&
    Req.status = Error.
    must raise the event and complete the workflow only working fine when the escalation does'nt takes place and the direct manager reacted without escalating to another manager.
    Please help e what might be the problem is.
    Thanks,
    Raja.

    Hi,
    Where is this event called? And more over is it an AND condition between those statements?
    regards
    Krishna

  • ESS leave request workflow -WS12300111

    Hello Experts
    I need to develop ESS leave request workflow by making copy from WS12300111. We are using SAP 4.7 and EP 6.0. And ESS and MSS is not yet deployed in EP.I tried to open this workflow in Workflow builder. Its saying that the task 12300111 does not exist. I have seen this workflow in ECC 6.0.
    Is WS12300111 not available in SAP 4.7? or after deploying ESS,will it be available in SAP 4.7?
    Please help me out...
    Thanks&Regards,
    Hemalatha

    hi Hemalatha
    I think in 4.7 you can't get that workflow. In ECC6 you can see the workflow. In EP you can't the visual see the workflow like that ECC6. i have developed multileve ESS workflow. take the copy of the standard workflow ws12300111 and do the customization according to your need. Check with the support pack with the portal and basis team. ESS will support only more that sp18 i guess. check with your basis team.
    Regards
    vijay

Maybe you are looking for