Issue in customize leave workflow

Hi Guru,
i have developed a customize workflow which have 2 approvers and one initiator. when initiator create a leave workflow then he sends to the first approver . once the first approver approve the the leave request and sends it to the second approver .when second approver recieves a mail , and click the link in uwl, system open the webdynpro application but did not contain any leave request due to which second approver can not find approve / reject button .
As it is an urgent please help me out ASAP.
Edited by: Sadia Kamal on Nov 25, 2011 12:48 AM

Are you using the standard approval task TS12300097? If yes, then you need to take care that in the first approval step, the leave status is not getting changed to 'APPROVED'. If the document status gets changed to APPROVED after the first approval step, the posting report will post the leave document and hence the workflow will get completed. In such a case, the second approver will not get any item in his approval list.
Hope this helps

Similar Messages

Issue with muliti level custom Leave Workflow

Hi,
   our Leave Workflow is multi level Approvals based on Absence codes.
   Say for Example : Case 1: For casual leave 2 Level Approval,
                              Case 2: For Sick Leave 1 Level Approval,
                              Case 3: For Maternity leave 3 Level Approval.
The Workflow is working fine for Case 1 and Case 2. Workflow is Getting Completed. No issues at all here.
The Issue is with Maternity Leave there are 3 level of approvals Manager 1, Manager 2, Manager 3.
   First 2 Managers are able to approve it from portal and for third level approval the work item is going to Manager 3's UWL.
   But when we click on work item it is showing the message like your Work list is Empty.
   Even we have forwarded the work item to Manager 2 and Manager 1 using SWIA. From their UWL also we are getting this same message
   your Work list is Empty.
   Observations:
      Request status is in SENT status.
       Visualization parameters are fine.
       Agent is Ready.
       In R3 Level we are not able to see the worklist details in Approval mode in PTARQ tcode for Manager 3,
      For Manager 1 & Manager 2 it is fine there we had approved in PTARQ.
Here are the Screen shots.
     What Could be the issues? Are we missing something?
     Ideas and Suggestions are welcome
     Regards,
     Arun

Hi Arun
Can you please give a screen shot of the technical workflow log with the step history selected for this step? (ensure that you have tried executing it once from UWL and rcd the same message), then get to the backend WF log).
Also, is the same Workflow task sent to all three levels in a loop or is it a different task at level 3?
Is there any deadline monitoring assigned to the task (for third level)?
Regards,
Modak

Leave Workflow not getting Completed

Hi,
I have a custom leave workflow which is a copy of the standard one. I added two more levels for the workflow and that's the change that I made to this. Now the issue which I am facing is that even after the Final approver approves, the leave, the workflow is not getting completed . The workitem is getting completed and the data is saved in the infotype. What could be the reason for workflow still in Started status? Please do help.
Regards,
Jubish

Hi AK,
But, what is the terminating event for Leave? Could you please tell that? The thing is that, if the terminating event is not working fine, then the same issue will be there in for standard leave workflow also right?
Regards,
Jubish

Standard Leave Workflow

Hi,
We are using a copy of standard leave workflow 12300111. It is working perfectly. But sometimes for few Pernrs the agents were not picked up correctly.
I saw the BOR AAGENT and also the class CL_WFD_ADHOC_PROPERTY_DB but not able to decide on anything.
I saw the Agents tab in the workflow container in SWIA it has only US value to it. If i check the GUID, that particular GUID does not have the Agent assigned to it instead it has only US value in the table SWDAAGNTS.
The workflow in in Started status.
Please let me know what could be the issue.
Thanks,
Sri

Hi ,
check for pernr if it has multiple users assigned / or relevant authorisations are provided.
Hope this helps.
If not , provide more information , so that the community can contribute further.
Best Regards
Saujanya

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

Leave workflow in ECC 6.0 using business object ABSENCE

Hi Friends,
I want to develop leave workflow in ECC 6.0. The BO event which is getting triggered when a leave request is created from PA30(Leave request will be locked when it is created) is ABSENCE.REQUESTED.But If i check the BO ABSENCE all the methods in that BO are obsolete. Even there is a SAP note(731260) which says that ABSENCE should not be used and use BUS7007 should be used, but BUS7007 does not have any event. In this case how should I proceed. Please advice.
Regards,

Hi Sapient,
Below are my thoughts.
Per Information I collected methods of BO ABSENCE are marked as Obsolate because the underlying BAPIs are discourged by SAP as they may create data Inconsistancies. and have suggested new BAPIs
bapi_ptmgrattabs_mngdelete
bapi_ptmgrattabs_mngcreation
bapi_ptmgrattabs_mngchange
instead of one used in BO ABSENCE.
bapi_absence_delete
bapi_absence_create
bapi_absence_approve
bapi_absence_request
bapi_absence_change
See the BO Documentation for more information. Methods of BUS7007 are doing exactly the same.
So I think we you can keep using the Events of ABSENCE and Methods of BUS7007.
Regards
Shital

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

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.

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

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.

Can we customize standard workflows.

Can we customize standard workflows.I am not asking about configuring the std workflows.I am asking whether can we change the standard workflows.Please Reply.

Hi,
If there is a need for adopting a standard workflow, copy the same and customize it according to the scenario. Let the standard workflow remain isolated.
Rgds

Leave Workflow item from Personnel no. of an employee

Dear All,
I just wanted to know that is there any transaction or report which displays leave workflow items for particular employee.
Thanks in Advance
Regards,
Bharat

Hello,
You can use tx SWI6
as input use the businessobject and the key. This will give you an overview of all workitems which worked whith this object instance.
Kind regards,
Peter

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

Customize iRec Workflow

Hello!
I have to customize the iRec Workflow (IRC_WF).
Within this workflow there are 3 Versions of one Prozess.
I have to customize "iRecruitment New Vacancy", "iRecruitment New Vacancy V2" and "iRecruitment New Vacancy V3".
Within HR there is the Function IRC_CM_HOME which starts the iRecruitment Home Page. But there is no connection between the Function IRC_CM_HOME and the Workflow IRC_WF.
I found out, that the function "IRC_VAC_NEW_LAUNCH_WF" starts the IRC_WF.IRC_VACANCY_NEW_V3 process via
OA.jsp?akRegionCode=IRC_REQUISITION_LAUNCH_WF&akRegionApplicationId=800&WFItemType=IRC_WF&WFProcess=IRC_VACANCY_NEW_V3
But where is "IRC_VACANCY_NEW" and "IRC_VACANCY_NEW_V2" started?
did the following:
First, i copied the Process IRC_VACANCY_NEW to XXSONY_IRC_VACANCY_NEW
Then i copied IRC_VACANCY_NEW_V2 to XXSONY_IRC_VACANCY_NEW_V2 and also V3.
Afterwards, i customized the XXSONY_ Processes.
Then i changed the IRC_VAC_NEW_LAUNCH_WF function to do the following HTML call: OA.jsp?akRegionCode=IRC_REQUISITION_LAUNCH_WF&akRegionApplicationId=800&WFItemType=IRC_WF&WFProcess=XXSONY_IRC_VACANCY_NEW_V3
But i don't know, where IRC_VACANCY_NEW and V2 are started. There is no function for these 2 processes.
Do you know where the processes IRC_VACANCY_NEW and IRC_VACANCY_NEW_V2 are started so that i can replace the call to hit XXSONY_IRC_VACANCY_NEW and XXSONY_IRC_VACANCY_NEW_V2?
Or should i customize IRC_VACANCY_NEW and IRC_VACANCY_NEW_V2.
But in that case i'm afraid that an standard Oracle update overwrites my customization.
What is the best way to implement my customized version of this workflow?
Thank you for your help!
Best regards,
Thomas

chances are that the previous versions are not used anymore. If you want to be sure, just customize them by adding a division by zero, so it errors out.
if you just have to change the approval flow, i would opt for AME, so you don't customize the workflow, but configure the approval scheme.

Leave Workflow escalation

Hi Experts
My client is having one requirement regarding the escalations of the leave workflow after the certain period of time. I am using the standard leave workflow WS12300111.
For e.g.
Employee applies the leave for 27.02.2009- 28.02.2009 and his reporting officer will not take any action till 26.02.2009 so, automatically the leave request should escalate to the managers' manager for approval.
Please help me in this regard
Thanks & Best Regards
Sheetal Gupta

Dear Kumar
Can you please let me know the point on which I can fix the no. of days in WF.
Thanks & Best Regards
Sheetal Gupta

Issue in customize leave workflow

Similar Messages

Maybe you are looking for