Problem in leave workflow working in ESS

Dear All ,
I ahve modified standard workflow for leave WS12300111 . I have 2 levels of approval . The step which goes to approver is standard task TS12300097 which is calling DUMMY method of CL_PT_REQ_WF_ATTRIBS class .
Now my problem is suppose 100 people have applied for the leave after managers approval it workitem will go to HR . So in HR's UWL he/she will have 100 workitem . Now supose HR clicks on first workitem in by logging in to ESS . when HR clicks on pop-up comes on the top it has one table sort of thing , here all the 100 leave request r getting diplayed .
I want Table to dislay only the Leave request of an employee belonging to That workitem . Please help in this regard . This is very high priority issue .
for further clarification on prolem if any body needs the screen shot please give the email ID I will send the screen shot
Thank you.

hi
can u send me the screen shots .

Similar Messages

Problem in leave approving working when approving through ITS

Hello all
   When we are approving the leave request workflow through R/3 it is working and leave is getting approved .
   when we are trying to approve the leave through ITS from bwsp transaction the leave is not getting approved and when i check in the workflow log it is showing the following message
call back executed from workitem
   In the activity we are using htmlform in workflow

hi
can u send me the screen shots .

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.

Multi Level Leave workflow in ESS MSS

Hi Guys,
This is the first time I am working with ESS MSS and I have to implement 2 level workflow for leave, I have gone through lot of threads and concluded that i have to enhance class CL_PT_REQ_WF_ATTRIBS
with new method where I have to change the status back to SENT after first level of approval and create new background task and attach it to custom workflow which is copy of standard.
Now my problem is I have enhanced the class CL_PT_REQ_WF_ATTRIBS with new method change status but when I am creating the task I canu2019t see that method in drop down list of methods.
Any idea why it not showing.
We are on ECC6. EH4
Atul
Edited by: Atul Dhariwal on Mar 8, 2011 4:56 AM

Hi Atul
You are doing wrong way. You need to use BADI to enhance that for that goto SE18 search with PT_GEN* and get the BADI name and goto se19 and create a implementation for that there you in the desiered method you can code. But remember you cannot add you own need method the BADI. What ever SAP is providing that one only you can use to add additional code not addding new method.
Regards
Vijay

Problem in the Leave workflow

Hi All,
We have a leave workflow attached to a portal. In that one step where if the employee applies for leave the mail notifivation will go to the employees manager. We have coupied the standeard task and we are using. Suddenly this step is not working. The mails are not going to the managers. In this task the class and the mathod we are using are
Object Type CL_PT_REQ_WF_ATTRIBS
Method DUMMY.
Can anybody tell me what is the problem and what to do for solving this.
Thanks & Regards,
Sreelatha Gullapalli.

Hello,
Perhaps this thread will help:
[Question] Leave Request Cannot be Open in SAP Business Workplace
regards
Paultje Bakker
Hanabi Technology

Workflows : Leave Workflow problem in EP

Hi,
I am using the workflow template WS12300111, which gets triggered from EP 6.0.
Well, the workflow is getting triggered when I create a Leave Request using the ESS-Working Time-Leave Request. But we were unable to execute the workitem. The Workitem is not updating the R/3.
I checked the workflow template and I cant find any coding for any step. All the standard steps ..
TS12300097 : Approval Process
TS12300104 : HR Administrator - Check
TS12300116 : Process Leave Request by Employee
are attached to the same method DUMMY of Global class CL_PT_REQ_WF_ATTRIBS.
When I checked that method, I found that there is no codiing attached to this method. So I dont find any coding for this workflow, which calls a BAPI or any transaction to update R/3 as it was earlier in BUSINESS OBJECTS.
Can anyone help me in understanding this new architecture-Class based Workflow Development.
Is there any configuration which had to be done from R/3 side also?
Regards,
<i><b>Raja Sekhar</b></i>

Hi Raja Sekhar,
the dummy entry in the task is there because the tasks should be executed only via the portal UWL and not directly in ECC5.0. In other words, you can't execute it from Business Workplace at all using R/3 functionality.
The config you are missing is most likely in transaction SWFVISU. Here you can define the visualization for a specific task meaning that you can define what gets launched when the work item gets executed in the UWL.
Just add the following entries to the task visualization section and it should work:
- Task TS12300097, visualization type Java WebDynpro
visualization parameters:
    ' Application: LeaveRequestApprover
    ' Package: sap.com/ess~lea
- Task TS12300116, vis type Java WebDynpro
params:
    ' Application: LeaveRequest
    ' Package: sap.com/ess~lea
I haven't tested the HR admin check myself if there is a wd app for it, but the method is the same if you can find one.
So instead of launching the dummy method, the work item launches now the standard web dynpro apps designed for the leave request processing.
Hope this helps,
Mikko

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

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

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.

Testing leave scenario without using ESS & using a copied workflow

Hi all,
How can I create a leave request without using ESS (For testing leave scenario).
If we want to use some copied workflow in place of standard workflow, where can we give that workflow number in IMG settings.
Thnx.

Thnx Sudhir
I have one doubt.
Approver will get sms for all employees who have applied for leave and when the approver will approve/reject the application how can we identify for which employee he has approved/rejected the leave. As we don't have anything in sms to keep track of the employee. So we need 2 pass something, like unique workflow ID with the sms so that it will return to that particular WF and complete it.
Can you tell me the way. how I can do this. Is there something like WF id n how can I get this... Is thr any RFC to get the same?
Thnx n Regards.
Edited by: Shailly on Dec 31, 2008 8:31 AM

Problem in standard workflow of claims in ESS

Hi ,
I am functional consultant and I am facing problem in standard workflow of claims WS18900023 .
When approver clicks on approve button it gives message that ' Validation is succesful 'and it does not get approved.
When approver clicks on Approve button it should say that request has been approved and that workiten should go from his inbox but this is not happening .That workitem still shows in his inbox with same status of to be approved .
Kinldy help in resolving this issue .
Thanks in advance
Archana

Hi Archana,
I assue that you have activated the BADI GET_NEXT_APPROVER.
Follow these steps.
=> Request for claims from portal.
=> Then in SAP run the T-code HRPBSIN_AC_ACRP and check the request status. It should show as To Be Approved.
=> Then logon as manager and approve the request from UWL.
=> Now agian in SAP run the T-code HRPBSIN_AC_ACRP and check the request status. It should show as Approved. ( If your maintaining Multi level approval process status will be Partially Approved).
=> Once it shows status Approved, Run the T-code HRPBSIN_AC_INFU, it will show the list of requests to be update in IT0015.
Regards,
Shankar.

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

Leave Workflow Not triggered

Hi All,
         We configured the Leaves through ESS and it was working fine, but abruptly, the Leave Workflow stopped executing. I have maintained the following settings:
1. In the leave settings in SPRO, "Process Request Using Workflow" option is checked and the WF Id is 12300111 for all the three entries.
2. Display field for next Agent is checked. In ESS, the manager's name is displayed in the leave app.
3. Request has to be approved option is checked.
4. In SWFVISU, TS1230097 is maintained as
     APPLICATION        LeaveRequestApprover
     DYNPARAM          wi_id=${item.externalId}
     PACKAGE            sap.com/ess~lea
5. The task TS1230097 is maintained as a General task .
I tested the application through PTARQ & through ESS, the leave is applied, but the Workflow is not triggered. I checked the WF Tasks in SWIA, but No Workitem exist there. There's no entry in SWEL.
Can you please suggest, where are we missing to trigger the workflow.
Cheers!!!
Umang

Hi Umang,
I do not see any problem with your workflow configuration.
Most probably the problem is with your rule group configuration.
As advised before, using WEBMO feature, find out what is the right rule group for the test employee (for whom you are applying leave). Then ensure that in the SPRO "Personnel Management -> Employee Self-Service->Service specific settings -> Working Time -> Leave Request -> Processing Processes--> define Absences/Processing Processes" there is an entry for the Rule group and the leave type you are applying for.
View that entry and ensure that you have all the WF settings as told before.
Thanks
Krishna

Leave Request work items are not showing in SBWP TCODE under OUTBOX .

Hi
Friends
I used work flow 12300111 for leave request process and I activated that work flow.
I applied leave through ESS from portal(Employee login)employee sends a leave request sends good,
and I got Leave request(work items) Managers in box(uwl in Manager Login in portal).
Manger Approve the leave request has been approved successfully.
can I check whether leave request is processed in R/3.
in tcode se38-RPTARQDBVIEW - UNDER leave request(Leave)->STATUS>COMPLETED,
But in r/3 i execute the Tcode SBWP...
here is no work items are not showing in outbox..
Please help me
Rafi Shaik

it wont be shown in outbox of SBWP
you need to check via SWIA or rptarqdbview or SWI5 for the user
these are java based tasks so will be done in UWL. you can see only the tasks but after approval they are disappeared.
The outbox shows the last 30 days by default. This default cannot be
changed. This 30 days selection period is always set when you enter
the outbox. However, the user can change the selection period by
clicking the button 'Change selection period' on top of the grid
control but this as you know will be reset once you log out.
This is how the mapping from the
backend workplace folders to the UWL tabs should work:
UWL tab                        Backend folder
Notifications                  Deadline Messages
Tasks-> Completed Tasks        Outbox -> Workitems executed by me
Tracking -> My Requests        Outbox -> Started Workflows
Tracking -> Forwarded          Outbox -> Forwarded workitems
Edited by: Siddharth Rajora on Aug 5, 2011 10:04 AM

Problem in Leave Request

Hi,
We are using EP 7.0 , ECC 6.0.
when an employee is requesting leave, the request is not going to the substitute but it is going to the manager who is in leave.
I haven't worked on ESS/MSS. How and where can i check for the problem? and how to resolve it.
Thanks,
Vila.

any answers please......

Problem in leave workflow working in ESS

Similar Messages

Maybe you are looking for