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

Similar Messages

Problem in the team calender leave display of other employees

Hello,
I have a problem with the leave request in ESS.
Go to Working Time >> Leave request >> Show Team Calendar >>
and you can see all the members of the team and also if someone has taken leave then that is also highlighted in the calender.
when i keep my mouse pointer near to the highlighted spot, I can see the information like 'date', 'type of leave' and 'approved' messages but if i keep the mouse for the other user then i will get the info as 'date and absent' which is correct and it will not show the type of the leave.
Now the problem is whenever i click on that higlighted spot then, I will get below info.
You have selected the following leave:
type of leave : .............
date : .................
But if i select other team members then it is showing the 'type of leave' but it should show 'absent' as 'type of leave ' when i select other user and it should display actual type of leave when i select for my self.
Now it is displaying the type of leave for all the users. how to avoid this and display as 'absent' ?
The RFC used from the back end is PT_ARQ_REQUEST_PREPARE to get the above detail....
is this the authorization issue? if yes can you tell me how to restrct that ? or if not then what might be the issue ?
Best Regards,
Prashanth J R

Hello Sidharth,
Thank you for the reply but where should i found the below code?
IF value NE <ui_request>-owner-pernr AND value NE approver_pernr .
CLEAR <ui_request>-subtype_description.
<ui_request>-subtype_description = '************'.
ENDIF.

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

Approver not availabale for approving the leave rquest

Hi Guys,
I Had One problem ,
In the leave request work flow ,
When a leave request is raised , if the approver is not available i want to approve that one with out his notification in back ground, for this one is there any std. program or any another process is there.... plz help me with quick responce
Thanks,
Durga Prasad.

Thanks rob,
But I don't want to do like this, is there any another way ?
Why because my project manger is already on vacation , I can't asign substitute for him.
and Oslo all the leave request which are pending and also new request need to be approved in back ground.
Plz advice me
Thanks,,,,
Durga Prasad

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

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 .

Error in the backgrond step for custom leave workflow

Hi,
I have copied the standard workflow for leave module(12300111) and added a method to get the mail id , but when i executed it is giving the error with msg 'Dereferencing of the null reference'.
what do i have to do to avoid the prob
Thanks,
Krish.

Hi Viji,
Yeah u r right, status is not passing because i have change the class name in the binding and put my copied class name, so it is not compatable with the standard class since i have added one custom class to it. so i have chaged the class names in all steps and replaced the standard class name.
Now i am facing the same old problem, workflow is started but showing errors in my custom added step, since it is having my custom class mentioned in the binding and it is not instatiating.
Please tell me how to instatiate the class and get the values from the methods in workflow.
Thanks,
Krish.
Edited by: kishore_krish on Oct 6, 2010 11:15 AM

ESS MSS leave workflow problem when updating IT2001 & IT2006

Dear all,
We have one issue in our production portal leave system. Hospitalization leave was applied for 22.06.2011 to 28.06.2011. Workflow was done properly. I checked workflow log also. It was done properly. But some how Infotypes 2001 and 2006 were not updated at all for the leave applied. I don't understand what could be the problem. I checked the leave table PTREQ_HEADER. I could see the below statuses.
1. SENT
2. APPROVED
3. ERROR
4. POSTED.
I want to know how the update to IT2001 & IT2006 missing. Is there any special program to post the data to IT2001 and IT2006 .
I appreciate your inputs.
Regards,
Venkat.O

Hi,
Hmmm, clearly there had been some problems due to the ERROR status. Do you know who managed to fix the problem (and how) (for example check the POSTED line in table PTREQ_HEADER and check last changed (or similar) field. Maybe someone tried to manually handle the error and caused the problem. Could you get some more information about the error in PTARQ?
Actually from my point of view this is not a wokflow problem at all. Could you just ask the HR guys to fix it? Isn't it possible to make the infotype entries directly with PA30?
Regards,
Karri

Not able to trigger the Leave Request Workflow from EP

Hi,
There is a problem that I am getting as follows and I need an urgent help :
I am using the Leave Request Workflow WS20000081 in R/3 4.7. The problem that I am getting when I login as "A" who is a boss of "B" and got the mail in inbox in corresponding workflow for Approve or Reject the Leave Request. Now when I "Approve" the Leave Request from R/3 Inbox, then the workflow move for the processing, but if the same Leave Request is to be "Approve" from EP having either the SAP Transaction iView or IAC iView, it doesn't process the Workflow further neither for Approval nor for Rejection. And the workitem remains as such in EP Inbox.
Can someone tell me what to do so that it will trigger from EP too.
Regards
Deep

Hi,
If u have no authorization, even the job log finishes the request won't be deleted.
Once chk the log step by step.....to have some more inf reg authoriations...
Or once goto RSRQ and give the request no there and chk the status of the request whether it is deleted or not?
Atlast try to log-off and refresh the session completely and try.
rgds,

How to read the comment field of the Leave of absence Workflow.

Hi,
I have attached a custom Workflow template to the
Standard class "CL_HRASR00_WF_PROCESS_OBJECT" and event "TRIGGERED" for my Personal leave of absence approval.
During the Workflow step, once the approval goes to the final approval step and it is there in the Benifit Administrator's inbox (Portal) for approval, the Benift Admin is having an option of Withdrawing the process(Withdraw Process button). After filling the comments field, once he clicks this withdraw button the standard class "CL_HRASR00_WF_PROCESS_OBJECT" event "WITHDRAWN" gets triggered and it calls a separate workflow.
I need to capture this comment in the new Workflow but not able to do the same.
Can anyone let me know how can I do this. The event container does have any parameter to pass this value to the workflow container. And since the Step_Object GUID also changes I am unable to read it in the second workflow.
Looking for some real help as this has become critical for the project.
Thanks is andvace.

Hi All,
Thanks for your reply Trevor, but I guess you misunderstood my question. What I am not looking for is not the absence data. Basically I need to capture the comments put in by the Benifit administrator in the Leave of absence application form (Personal or Maternity/child care ), incase when he goes for withdrawing the Application submitted by the Employee.
To elaborate it functionality step by step...
1. An employee logs on to portal and submits a LOA application with a few mandatory field ( Commencing date,Returning Date, Reason).
This kicks of a Workflow say WF1 attached to
ABAP Class- CL_HRASR00_WF_PROCESS_OBJECT, Event- TRIGGERED.
2. Then after executing a few tasks to retrive data it goes to the Manager for approval. Once the manager appoves it goes to the Benifit Administrator.
3. The Benifit Administrator can approve the application or has an option of withdrawing it.
4. In case the Benifit Administrator goes for Withdrawal, after putting some comments in the form, it triggers the Event-WITHDRAWN of ABAP Class-CL_HRASR00_WF_PROCESS_OBJECT.
5. This event in turn starts a new Workflow WF2.
6. In this Workflow WF2 I need to pull in the comments put in by the Benifit Admin.
How can I pull this comment?

Regarding the change status of leave workflow.

hi friends,
i have copied the standard leave worklfow "WS12300111" and customized it just to meet our requirement means for multiple approvers.
everything is working fine in production means if user ID "AIHR01' raise a leave request the workitem will go to "AIHR02" after his approving the workitem will go to the final approver means "AIHR03" after his approval the leave request will be completed and the status in the TC - PTARQ is coming as "APPROVED" means only after the approving of "AIHR03" the status is coming "APPROVED" but in some cases when user id "AIHR02" is approved instead of coming status "SENT" it is coming "APPROVED" in TC-PTARQ and because of this status the workitem is coming blank in UWL of "AIHR03".
I have already incorporated the given below method in the "WORKFLOW" just to change the status from "APPROVED" to "SENT" after the approval of user ID "AIHR02" but in some cases it is not working fine it is giving BUG.
begin_method changestatus changing container.
DATA:request TYPE ptreq_header-request_id,
          wi_id TYPE swwwihead-wi_id.
DATA: request_instance TYPE REF TO if_pt_req_request,
           event   TYPE tim_req_xfer_event VALUE
           cl_pt_req_const=>c_reqtrans_send,
           ex_status TYPE tim_req_status,
           container_wi TYPE swcont OCCURS 0,
           agents TYPE STANDARD TABLE OF swhactor WITH HEADER LINE.
          swc_get_element container 'REQUEST' request.
          swc_get_element container 'Wi_id' wi_id.
DO.
CALL FUNCTION 'ENQUEUE_EPTREQ'
   EXPORTING
    MODE_PTREQ_HEADER       = 'S'
    MANDT                   = SY-MANDT
     request_id              = request
    X_REQUEST_ID            = ' '
    _SCOPE                  = '2'
    _WAIT                   = ' '
    _COLLECT                = ' '
   EXCEPTIONS
     foreign_lock            = 1
      system_failure          = 2
      OTHERS                  = 3
    IF sy-subrc = 0.
      EXIT.
    ENDIF.
    WAIT UP TO 60 SECONDS.
ENDDO.
IF sy-subrc = 0.
    CALL METHOD ca_pt_req_header=>agent->get_request
      EXPORTING
        im_request_id     = request
      IMPORTING
        ex_request        = request_instance
      EXCEPTIONS
        request_not_found = 1
        OTHERS            = 2.
    IF sy-subrc = 0.
      CALL METHOD request_instance->initiate_state_trans
        EXPORTING
          im_transfer_event = event
           im_external_call = 'X'
   im_ret_value      = 0
                 ex_new_status     = ex_status
   ex_ret_code       =
      swc_set_element container 'Ex_Status' ex_status.
    ENDIF.
    CALL FUNCTION 'DEQUEUE_EPTREQ'
     EXPORTING
MODE_PTREQ_HEADER       = 'S'
MANDT                   = SY-MANDT
       request_id              = request
X_REQUEST_ID            = ' '
_SCOPE                  = '3'
_SYNCHRON               = ' '
_COLLECT                = ' '
ENDIF.
swc_create_container container_wi.
swc_set_element container_wi 'WI_ID' wi_id.
agents-otype = 'US'.
agents-objid = sy-uname.
APPEND agents.
CALL FUNCTION 'SWW_WI_START_SIMPLE'
    EXPORTING
      task                         = 'TS90000089'
      called_in_background         = 'X'
    TABLES
      agents                       = agents
      wi_container                 = container_wi
    EXCEPTIONS
      id_not_created               = 1
      read_failed                  = 2
      immediate_start_not_possible = 3
      execution_failed             = 4
      invalid_status               = 5
      OTHERS                       = 6.
end_method.
Request you to plesase help me to solve this issue .why in some cases instead of coming status "SENT" it is coming "APPROVED" after the approval of user id "AIHR02".
BECAUSE of the "APPROVED" staus the same workitem is coming blank in the UWL OF "AIHR03".

solved by own

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?

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,
Raja Sekhar

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

Problem in triggering the correct workflow on AdobeForm submission for PCR

Hi All,
I am facing a problem involving triggering of workflows through Adobe form submission. I have created a scenario for "Employee seperation" in QISRSCENARIO transaction and assigned it to an approval workflow. I have also activated and assigned the BUS7051-Created event in the workflow Basic Data. My workflow also triggers perfectly when i submit the adobe form. Everything is perfect till here.
Now i have to create another scenario for "Request for Transfer" Now for this i had to create a seperate workflow. My problem is since both these workflows are assigned to the same event whenever i submit the "Employee seperation" form both the workflows get triggered. Is there a setting where i can configure the corresponding workflow to be triggered for the respective scenario's alone? How do we handle this situation?

Hi Jocelyn/Raja,
I am trying to use SWB_COND for differentiating between the different workflows. I have created a virtual attribute W_SCENARIO_KEY for this. I tried populating this scenario key by using the following staement,

CALL FUNCTION 'ISR_SPECIAL_DATA_GET'
EXPORTING
 notification_no = object-key-number
IMPORTING
 SCENARIO = w_scenario_key.
SWC_SET_ELEMENT CONTAINER 'W_SCENARIO_KEY' W_SCENARIO_KEY.
When i try to include W_SCENARIO_KEY as a start condition the workflow shows up an express message and fails to trigger. In ST22 i can see that there is an exception "INVALID_NOTIF_NUMBER" raised.
But if i don't set this as a start condition all the workflows activated to BUS7051-CREATED are triggered and in the WF logs i can see the correct value of W_SCENARIO_KEY for the respective notification number.
I am not sure why this happens when i set it as a start condition alone.
I instead used a select statement as shown below,
select * from viqmel into table itab_VIQMEL
 where qmnum = object-key-number.
loop at itab_viqmel where qmnum = object-key-number.
w_scenario_key = itab_viqmel-auswirk.
endloop.
After inserting this statement it works fine without any issues. Any idea on why ISR_SPECIAL_DATA_GET cant be used in the virtual attribute implementation?
The following is the dump i get if i use ISR_SPECIAL_DATA_GET,
Information on where terminated
 The termination occurred in the ABAP program "SAPLQISR9" in
 "ISR_SPECIAL_DATA_GET".
 The main program was "RSWDSTRT ".
The termination occurred in line 39 of the source code of the (Include)
 program "LQISR9U01"
 of the source code of program "LQISR9U01" (when calling the editor 390).
Source Code Extract
Line SourceCde
9 *" EXCEPTIONS
10 *" NO_INTERNAL_SERVICE_REQUEST
 11 *" INVALID_NOTIF_NUMBER
 12 *" INT_SERVICE_REQUEST_NOT_FOUND
 13 *"----
 14
15 * local data
16 DATA: lt_dummy TYPE qisrsgeneral_param.
 17
18 DATA: lr_isr_document TYPE REF TO cl_isr_xml_document.
 19
20 DATA: ls_notif TYPE qmel.
 21
22 * MAIN
23 * try buffer first
 24 CALL FUNCTION 'ISR_SPECIAL_DATA_BUFFER_GET'
 25 IMPORTING
26 ET_SPECIAL_DATA = special_data
 27 ED_SCENARIO = scenario
 28 EXCEPTIONS
 29 BUFFER_EMPTY = 1.
 30
31 IF sy-subrc eq 0.
 32 EXIT.
33 ENDIF.
34
 35 * check notification number
 36 SELECT SINGLE * FROM qmel INTO ls_notif
 37 WHERE qmnum = notification_no.
 38 IF sy-subrc NE 0.
>>>>> RAISE invalid_notif_number.
 40 ELSEIF ls_notif-auswirk IS INITIAL.
 41 RAISE no_internal_service_request.
 42 ENDIF. 
43
44 * set scenario
 45 scenario = ls_notif-auswirk.
 46
47 * read ISR XML document
 48 CALL METHOD cl_isr_xml_document=>read_for_display
 49 EXPORTING id_notif_no = notification_no
 50 IMPORTING er_isr_xml_document = lr_isr_document
 51 EXCEPTIONS bds_error = 1.
 52
53 IF sy-subrc NE 0.
54 RAISE int_service_request_not_found.
55 ENDIF.
56
57 * read data from XML document
58 CALL METHOD lr_isr_document->get_data_from_xml

Problem in the Leave workflow

Similar Messages

Maybe you are looking for