Problem using workflow with ess leave requests

Hello, I have been experiencing some problems using wf for approval with leave request in ess.
I customized ws12300111 for request approval and it is working fine. But when we try to cancel a request in ess, there are strange things happening:
- If the request is in status sent: the workflow gets in error.
- If the request is already in db: it starts a new workflow (ws12300111).
We don't want this because we have customized ws12300111 only for new requests. I have tried to customize absences in SPRO so that onlu new requests start the WS12300111, Onlu new requests have the workflow field filled with 12300111, but even like that, the WS12300111 starts whenever that is a cancelling or modification of a request.
I have also tried using a different workflow for canceliing (WS12400007), but in this case there is an error in ess when we try to submit.
This is really annoying, I have tried everything...

Hello,
"If the request is in status sent: the workflow gets in error."
Please always say what the error is.
" If the request is already in db: it starts a new workflow (ws12300111"
You first have to find out how this is done. Look in SWEL, it's probably via some sort of CHANGED event.
regards
Rick Bakker
hanabi technology

Similar Messages

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?

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

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

Error after second level approval in ESS leave request

Hi Experts
I am using custom workflow for Ess Leave request process which is copied from WS21500001.
I have added custom class methods to change status from approved to sent.
Then another method i have set next appovaer.
The problem i m facing is that I am getting an error on portal after second approval approves the request.
i.e Field syomol has not been assigned yet.
from st22 i found its generating from
Include LPT_ARQ_REQUEST_UIAF06 - Form   execute_approver_update
By debugging i found that Its not getting next approval with status T as there is only first approval with status 'A'
This results in unassigned field symbol. and then error.
Please help me resolve this issue.
Please confirm why next approver is not found in method.

Hi All
Thanks for your reply.
I checked why it was giving a dump.
This execute_approver_update subroutine takes approval data from table ptreq_approver .
I filled this with resp actor id after request is approved and status is changed to sent.
For every emp its unique actor id is saved in ptreq_actor table agaist his pernr.
   SELECT SINGLE actor_id FROM PTREQ_ACTOR INTO actor_id WHERE objid = nextApprover_pernr.
    wa_appr-mandt = sy-mandt.
    wa_appr-request_id = Request_ID. "Req.requestID ( from Workflow )
    wa_appr-version_no = version_no. "Req.Version ( from Workflow )
    wa_appr-seqnr = seqnr. "Same as version no but in char
    wa_appr-approver_ins = actor_id. "Employee actor id from ptreq_actor
    wa_appr-status = 'T'. "Manual
    append wa_appr to it_appr.
    INSERT PTREQ_APPROVER FROM TABLE it_appr .
    commit work and wait.
This resolved my issue.
Thanks

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

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.

Problem with chage leave request

Hi Experts,
                  In ESS leave request application is working fine. But the customer's requirement is that while changing leave request employee should able to change only Leave start and end dates. He should not able to change leave type . So is this requirement is possible in SAP.
Please give me suggestions ASAP.
Thanks
Sameer

Hi Sameer
Yes. It can be achieved by changing the webdynpro code.
Project: ess/lea
Component Controller: VcFormEdit
View Controller: EditView
Steps:
1. Add a Value Attribute, of type 'boolean', to EditView's Context (eg: ReadOnlyLeaveType).
2. Assign this attribute to the 'readOnly' property of 'Type of Leave' dropdown (id = awartDropDownField) on the EditView's Layout.
3. Now to change the value of the above attribute, according to the requirement needed, add relevant code inside 'wdModifyView()' method from the EditView's Implementation.
Following is a code sample added to restrict user from changing the Leave Type ONLY for the approved leaves:
String status = wdContext.currentPrepare_Ex_RequestElement().getStatus_Text();
if (status.equals("Approved")) {
     wdContext.currentContextElement().setReadOnlyLeaveType(true);
} else {
     wdContext.currentContextElement().setReadOnlyLeaveType(false);
This should answer your question.

ESS Leave Request - Error while creating a leave record

Hi Friends,
Some of the ESS leave request(not workflow) has gone into error when the system tryies to create a leave record in background. I can view these error request using the report RPTARQDBVIEW. This happens when the background program(PTARQPOST) tries to create a leave record. In some cases the status of the leave request is set to error(the status attribute of the container element(Req) has the value Error),but we are not able to find what is actual error.Is there any log where we can check what is the problem? Please advice.

May be
Internally the pernr might not be locked or some one may be maintaing the pernr for whom you are trying to post.

HCM ESS Leave request : Intimation mail or Approval mail is not going

Dear Experts,
We have an Ep 7.0 system with ECC 6.0 is connected at backend. Currently we have a requirement : whenever an employee will request for a leave from ESS(EP 7.0) the approver should get an intimation mail and similarly when the request is apporved or rejected the requestor should get a mail about this.
Now we have already a customize workflow for this leave request process. We have checked and scheduled background work procesess for the following reports
1. RPTARQEMAIL
2. RPTARQPOST
3. RSWWTHEX
4. RSWWERRE
5. RSWWCLEAR
6. RSWWCOND
Please note that an approval mail is being sent to the applicant after approval of his leave. We need to make the following adjustments:
1. The body of the approval mail that is being sent now needs to be changed and must include details of the leave request. How to do this?
2. No intimation mail is being sent to approver after a leave request has been raised. As per RPTARQEMAIL approver should also get notified about the leave request.
3. Apart from RPTARQEMAIL if we use the work item "SEND MAIL" in the workflow to implement this, we are getting the approval mail and notification mail in the inbox of our business workspace(SBWP). However the mail is not being redirected to the mail id maintained i.e in outlook inbox.
Regards
Partha

My sincere advise is to do some thing like this,
1. First take a copy of the standard leave workflow template WS12300111
2.Create a ZBOR (in SWO1 txn) in which you define a method which handles mail sending process by using the standard SAP FM SO_DOCUMENT_SEND_API1
3. Create a Text element in SO10 transaction.After this as I said you will creating a ZBOR-method in that itself you determine the agents and email addresses before calling the FM
SO_DOCUMENT_SEND_API1.
4. To get the lines of the mail content (from SO10) you hvae to use the FM READ_TEXT
if the above is done then fixing your issues is a simple thing
Q1. You need to change the content of the mail type.
A1. You can chage the mail content in the TExt element.
Q2.No intimation mail is being sent to approver after a leave request has been raised?
A2. You hvae two options over here either you can make use of the tab notification of the decision step or by using the program RSWUWFML2 you can schedule a background job, for help see the Documentation of the rep.
Q3.Mail Sedning to outlook
A3. SCOT settings, SMTP---> Internet ---> addresses ---> maintain the address or by using the SWNCONFIG you can even aceheive this.

ESS leave request

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

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

Problem using workflow with ess leave requests

Similar Messages

Maybe you are looking for