ESS Leave Request Workflow Configuration

Hi Experts,
I Have ESS & MSS setup with mySAP ERP 2005 ECC 6.0, i have made the required configuration for absences, i assumed that leave requests should automatically be forwarded to the person with cheif position in the department, Now hwen an employee applies for a leave request i check the MSS UWL and nothing is appearing.
My question is do i have to maintain any configuration in terms of workflow or is it automatically configured if PA & Om integration is active ?
Points will be rewarded for any help..
Regards,
Ahmed Salah

Ok follow this path
Tools --> Business Workflow --> Development --> Tasks/Task Groups --> Change
Task type = Workflow template
Task = 12300111
Click on Change
Click on Workflow Builder.
Click on Process request by Employee.
Click on Task Properties (Agent assignment)
In Maintain Agent assignment,
See for Process Leave Request by Employee , add General Task.
Then click on the Update Index.
Hope this works for you.
Cheers!!!
Sanjay Sharma.

Similar Messages

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

ESS leave request workflow WS04200009...error-u r not one of the possible a

hi all
i m working on ESS leave request workflow WS04200009....but when i create a leave request from user's A/c i got an error at that leave req create screen that's-- u r not one of the possible agent of the task...
pls do help if anyone no solution.
thanks in advance .
Raj

Try making this task a General Task..use tcode PFTC and change the attribute of this task to a general task. That might help solve the issue.

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

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 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 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 : not able to approve request

Hi experts,
When i create leave request, work item for approving request is not coming in the approver's bussiness workplace. I am using std workflow WS12300111. Is there any customization needs to be done ??
please help me
Pointes will be rewarded
Regards,
Sameer

Hi Samee,
Did you select General Task in the steps of workflow you have an agent?
Sónia
You have a chief position on the Organization Unit where you have the employees?
Sometimes it's possible to forget this one:
Transaction SWDD, select the workflow WS12300111 and press CTRL+F8 (Basic Data)
there's another button "Agent assignment for task" (SHIFT+F9)
set task to "General task" with the "Attributes..." Button. (EVERY user can start this task).
And check this to:
Using transaction SWFVISU, check the following entries and correct these where required:
TS12300097 Java WebDynpro APPLICATION LeaveRequestApprover
                 PACKAGE sap.com/ess~lea
TS12300116 Java WebDynpro
                 APPLICATION LeaveRequest
                 PACKAGE sap.com/ess~lea
(check this, because usually you have an error, instead of sap.com you have com.sap)
Register the work items again. Additional information about registering work items is available in the UWL documentation.
After re-register the System Alias again in the UWL - THIS IS VERY IMPORTANT
Edited by: Sonia Santos on Jan 28, 2008 12:49 PM
Edited by: Sonia Santos on Jan 28, 2008 12:51 PM

ESS - Leave Request - Workflow

Our requirement was for the leave request process to be a simple approval process that only includes the option for the employee to u2018changeu2019 or u2018deleteu2019 a request if the manager hasnu2019t approved it yet.
In line with this, we have configured to switched off the u2018changeu2019 and u2018deleteu2019 buttons.
This still allows the u2018changeu2019 and u2018deleteu2019 buttons before a leave request has been approved. (which we wanted)
And these buttons disappear once the leave request has been approved. (which we wanted)
However, for leave requests that have been rejected, we still get these buttons. (which we donu2019t want)
After a Leave Request has been Approved or Rejected by the manager, the "Approve another Absence" link on results page doesn't work. Can we do anything about this?
Also, when a manager is rejecting a leave request he is not forced to enter a rejection reason.Is there a way we can force the manager to enter a rejection reason?
Thanks
WB

Hi
No your right, you shouldn't transport from IDES to DEV, What kind of development system do you have ?
A quick way to check if it exist is to check the HR Tables e.g. HRS1205.
And just to cover the security issue, verify that your not using structural authorization, ar at least that your having full access to the PD Object in question. You can check this in OOSB - If your not using structural authorization you will only have one entry in here - SAP* with full access. If this user is missing in this transaction, or if your user is in the table with less authorization, you wont have access to the workflow templates
Regards
Morten Nielsen

ESS Leave Request Workflow 12300111 not being triggered

Hi Experts,
I am implementing ESS 1.0for ERP05. The Leave Request (EP) is not trigerring the standard wokflow 12300111.
I performed the following steps:
1. Configured inbackend SPRO: Processing process for types of Leave to point to 12300111
2. Changed the taskes under WF12300111 to General Tasks and activated the WF
On submitting the Leave Request (EP), the table PTREQ_HEADER gets updated but theWorflow is still not triggered.
Can someone please help.
Thanks,
Shobhit

Hello Shobhit,
could you solve it ?

ESS leave request

Dear friends
in ESS leave request workflow , in approval process task i am maintaining 10 days deadline , after that by using process control i am making the workitem to be obselete , then same leave request is going to supervisor's supervisor . this is properly working, my problems are
when the first supervisor opens some other leave request still the escalated leave request is showning in the table , still system is allow him approve . and also in the supervisor's supervisor inbox then workitem remains if he opens the workitem there is no any leave for approval in that table , so deadline mointerting is not working propely for ess leave request , and also in supervisor's supervisor inbox workitem is not going out from uwl .
how to do deadline mointering for ESS leave request workflow ,
can any one help on this
reason which i could identify is details are picking from the document database based on the approver .

You should check the forum, I think I saw a thread in the last two days which stated that deadline monitoring is not working for the leave request. (it could be the HCM forum). So this would be why the handling is not working as expected.
The problem of no leave to be approved for the manager could be prevented if you set a terminating event on the task which will be triggered when the leave is approved.
Regards,
Martin

ESS Leave request Visual Parameters for the Tasks

Dear All,
I have a basic dought about ESS Leave request Workflow process.
We have used WS9100004  TS12300097 for this Visual Parameters are
Visual Parameters        Visual Parameter Value
APPLICATION                     LeaveRequestApprover
PACKAGE                    com.sap.xss.hr.lea.appl
For Task TS12300116
Visual Parameters            Visual Parameter Value
APPLICATION                    com.sap.xss.hr.lea.appl
PACKAGE                    LeaveRequest
In the same way I have to use another workflow for canceling the leave request
Workflow number is  WS12400005  in which I have used
TASKS  TS 12400028, TS04200011, TS04200007, TS01000162, TS04200008
For above tasks what are the visual parameters I need to maintain.
Visual Parameters     Visual Parameter Value
APPLICATION              ?
PACKAGE              ?
Please suggest me on this.
Regards,
Kishorekumar.R

Hi Siddharth Rajora,
     With you r help i was able to resolve the issue. Thanks for the information.
Regards,
kishore.

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 Configuration

Similar Messages

Maybe you are looking for