ESS, Leave Workflow

Hi All,
     We are on ECC6.0, implementing leave workflow with multi level approver (WS12300111). We are using two custom rules to find out the 1st and 2nd level approver. The workitem is going to the UWLs of the correct agents, no problem.
     There is one Approver field on the Leave request form. SAP is pre-populating the field (I think using the standard rule AC00000157, not sure where exactly). Only that agent can see the leave request, whose name is coming to that field. Any other agent is unable to see the leave request even though he receives the workitem.
     I think some configuration needs to be changed, so that any approver can see the leave request and approve. Can anybody please help?
Thanks and Regards,
Abir Kundu

Hi Sagar,
Thanks for your reply. Yes I've noticed that you can disable the Approver field and even you can change way how the next processor would be selected by customizing.
I'll test it today and let you know.
Regards,
Abir.

Similar Messages

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.

How to send mail to portal inbox and user email id in ESS leave workflow ?

Hi
currently i am working on sap ess workflows . i have customized standard workflow (ws12300111) where when manager approvesor rejects the leave in portal, mail has to send to user's portal inbox and email id assigned to user .
in workflow level - i have used 'sendmail' step and given agent as initiator . now mail is going to sap inbox .
can you please guide me (step by step if Posiible) how should i do it.
Regards,
Sreeharsha.
Points will be rewarded.

mail has to send to user's portal inbox and email id assigned to user
Not sure if you want a email or SAP mail. Can you clarify the above statement?
If you want to send a notification mail which needs to be displayed in UWL
Search for keyword SONIC in this forum and blogs section. You will get the solution
If you want to send a notification email to the email id of the user
You need to determine the email id of the user and use the sendmail step to send email (your SCOT settings need to be condigured by your BASIS team)
Thanks,
Prasath N

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

Wait step in leave workflow wait for 20 min

hi friends
I have designed a multilevel ESS leave workflow. After 1st approver the status need to change from approved to sent after that i am using a wait step with condition REQ.STATUS = SENT. This condition is met immediately but it still waits there nearly 15 to 20 min after that only it goes to the next approver. I dont no y its happening even after the condition is met. There is background job SWWCOND is directly related to this wait step. I have scheduled this job for every 3 min. But its long time to execute. If i remove the wait step its shows dump. How to minimize the time of execution of the wait step.
Regards
vijay

Hello,
Let me know if I've understood the problem correctly.
You have a workflow with two wait steps.
These wait steps rely on the running of SWWCOND
to check if the conditions have been satisfied.
The workflow takes 15-20 mins to pass the first condition, even
when already true, but takes little or no time to pass the second
condition.
SWWCOND is scheduled to run every 3 mins and doesn't run for more
than a couple of minutes.
My questions:
- Are you absolutely certain SWWCOND runs every 3 minutes?
Do you see that happening in SM37 while your workflow is waiting?
- You've said that the first condition is REQ.STATUS = SENT,
what is the second condition?
- Is REQ.STATUS a virtual attribute?
- Where is REQ.STATUS set to SENT? Outside of the workflow?
Does it do so without an error? Is a commit work done?
regards
Rick Bakker
Hanabi Technology

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?

How to use EP-ESS Leave Request using Custom Workflow

Hi Experts,
Can I use the EP-ESS Leave Request (ESS 1.0 for ERP05) with a custom workflow which is NOT a copy of the standard workflow 12300111?
Regards,
Shobhit

Please post this question on Business process forum.
U will have to follow the architecture of 12300111 template for ESS leave.
Even though it says u can use ur own wf!!
Cheers!!
Ashutosh

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 SENT. You can get the required coding from APPROVE method of the above mentioned class.
I followed the second method.
I hope this should clear our problem.
Regards
Raja Sekhar

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

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

HELP NEEDED: ESS Sick Leave Workflow

Hi ESS/MSS Gurus,
Good day!
I am a newbie workflow consultant currently working on enabling ESS-MSS for a client. In summary, here are their requirements:
1. Leave Requests and Clock In/Out Corrections - Upon initiation of employee request, the work item is sent to the manager for approval. Regardless of the decision (either approve or reject), the employee will be notified via an email notification
2. Sick Leave Requests - upon initiation of employee request, the work item is sent to the company doctor for approval. Regardless of the decision (either approve or reject), both the employee and his/her immediate manager will be notified via an email notification
Here are some details regarding how I went about it:
1. Leave Requests and Clock In/Out Corrections - Created a copy of workflow WS12300111 and included send mail steps after TS12300097 (Approval Process) to notify the work item initiators.
2. Sick Leave Request - Created a copy of workflow WS12300111 and included send mail steps after TS12300097 (Approval Process). The approval process is pointed to the Position Company Doctor. After which a step was inserted after the approval process which uses a customized method (using FM SWX_GET_MANAGER) to determine the employee's manager. Then send mail steps are executed for the employee and the manager
3. Clock Corrections and Sick Leave/Leave Requests belong to the same Rule Group
During testing in our sandbox client I was able to successfully test all of the workflows. However, when I migrated the changes into our pseudo-QA system, I cannot launch the Sick Leave workflow from ESS. I encountered the following errors in PTARQ (standard leave request and clock in/out correction are ok):
1. Scenario 1: applied leave coincides with the working time of the employee
   "Document created with information: P2 848: Absence encompasses planned work time
2. Scenario 2: when only the total nmber of hours is entered for the applied sick leave date
   "No document created: HRTIM_ABS_REQ 094 Indentical clock times were adjusted, Check the entries"
3. Scenario 3: applied leavedoues not coincide with the working time
   "Document created with warning" HRTIM00BLPRETRO 001 Time entry triggers retroactive accounting in payroll"
For all cases, no work item was created in the back end.
I would like to tap unto your wealth of knowledge and experience on how to address such errors. I need to determine if this is a misstep in the workflow, HCM, or ESS/MSS configuration to better isolate the errors.
Your immediate response is highly appreciated.
Regards,

you dont need a custom WF first of all, You can directly use standard one cause we have a standard mail program
called rptarqemail
ie
The mails will be directly triggered to the mail address once you run rptarqemail.
Please check if you are running the report using the option since last
run. The procedure is usually this :
1. Create a Leave Request
2. Execute the report RPTARQEMAIL.
3. Approve the Leave Request.
4. Execute the report RPTARQPOST.
5. Execute the report RPTARQEMAIL.
Now to determine different approvers for different types of leave you can use the option of badi PT_GEN_REQ
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.
also note that
Standard Leave request application offers the following options to
determine the Next agent. This specifies whether and how the next agent
of a leave request is to be determined.
Last Agent: The system reads from the database the last agent to have
had requests from this employee.
Line Manager: The system uses the organizational model to determine the
agent.
Last Agent, Then Line Manager: If no agent is entered in the database,
the system then uses the organizational model to determine the agent.
No Calculation/Manual Entry: The system does not determine a next agent.
Employees can enter an agent manually.
However if the customer has a different requirement, the BADI PT_GET_REQ
method FIND_RESP_AND_DEFAULT_NEXT_PRC is provided for this purpose.
the message you get is correct and its a information message which will not stop leave request, they depend upon customisation which can be hidden too
check here
http://wiki.sdn.sap.com/wiki/display/ERPHCM/LeaveRequestCustom+Messages

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 - How to use a custom Leave Workflow?

Hi Experts,
I am implementing ESS 1.0 for mySAP ERP05. I have a custom workflow for Leave Request which I want to use for the ESS Leave Request. Can someone tell me what are the configuration steps required for this?
I have already performed the following activity:
SPRO --> Personnel Information --> ESS --> Service Specific Settings --> Working Time --> Leave Request --> Specify Processing Processes for Types of Leave
Here I have defined the WF ID of New Request as the custom Workflow ID.
Now when I trigger the Leave Request from EP-ESS, the message comes that the request was sent successfully.
But in the backend no workflow gets triggered. I even tried to write an implementation for the BADI PT_ABS_REQ to trigger the custom workflow event, but still no activity in the ECC workflow upon submitting thwe portal request.
Can some one please advise.
Thanks,
Shobhit

Ohh.. So the standard WF also doesnt get triggered??
Are you sure u have done SWU3 config??
If u have, Try using SWU_OBUF to refersh the workflow buffer.
Try swi1 to check what is happening with ur WF.
Try login to requesters login ... SBWP ... check the outbox. Is there a WF with Error here.
Cheers!!
Ashutosh

ESS, Leave Workflow

Similar Messages

Maybe you are looking for