Problem in initiating Leave Cancelletion workflow

Hi All...
When i try to initiate a Leave cancellation workflow using PT_ARQ_REQUEST_EXECUTE Bapi in webdynpro java,
i get an error as follows
"No Customizing for status type ARQ, status POSTED, and transition event DELETE"
This error occurs only in case of Posted leave requests.
Could anyone please tell me what can i do to resolve this problem.
Thanks in advance
Asha

Hi Anup..
was able to get rid of the previous error..
Thank u very much.
But m facing another error now while executing the same bapi.
Error ID: HRTIM_ABS_REQ
Error message: "Unable to send the request with this approver".
I checked the ORG chart, the approvers are maintained and also there is no
import parameter available for approvers to be set in this bapi.(PT_ARQ_REQUEST_EXECUTE).
is there any setting to be checked?
Could you pls tell me what might the problem?
Regards
Asha

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?

ESS/Leave Reqest Workflow Problem Still in Process when Escallated

Helo Every one,
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.

Hi Raja,
Here is how I can think of, based on your requirement.
I hope you are using modelled deadline. Have the process control step in the deadline branch with function set workitem to obselete. This makes the actual work item to obselete everytime it reaches the deadline and make it create one with an escalated agent. And also keep the dialog task in the loop.
Hope this helps.
Thanks,
Raj

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

Leave approval workflow

people, i have a query ragarding leave approvl workflow. as per standard employee has raised request in ESS, sap will send it to 02, what will happen if position of 002 (reports to) is vacant ? does it automatically and immediately goes to 012 (chief)? what is the chief position is vacant.? does it goes to the O-O and then chief of that org unit?
can the approver forward it to other person in the org strucure by selecting his pernr in MSS.
need help

Hi Manoj,
Check if you are using structure authorizations. If this is the case the substitution will not be able to process the workitem. Otherwise it still could be an authorization problem. Compare the HR authorizations, i suspect the problem will be in there.
Regards,
Martin

ESS Leave Request Workflow Issue

Hi Every one,
Our client is using ESS/Portal Leave Request workflow(ZWorkflow template which is configured to the portal) which is working fine up to the last month.Recently i developed 3 level Escalation functionaly which is working fine and we tested and finally transported to production in the last month .And recently i got an issue when the leave request is aproved after escallation is not setting the workflow status completed and keep on escalating to the next levels.
Note:When the 1st manager approves the leave request without escallation the workflow status is going to be completed which is fine and only there is an issue when escallated and approved the status of that specific leave request is approved but the workflow is not going to the status completed and keep on escalating to the next levels.
i checked the log and found there is condition based wait event step which have a condition when
Req.status = Approved&
Req.status = Withdrawn&
Req.status = Error.
must raise the event and complete the workflow only working fine when the escalation does'nt takes place and the direct manager reacted without escalating to another manager.
Please help e what might be the problem is.
Thanks,
Raja.

Hi,
Where is this event called? And more over is it an AND condition between those statements?
regards
Krishna

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

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,

Leave management workflow in HR

Hi,
Is there any standard workflow for leave approval process in HR? If it is there will it take care of creation of 2001 record as well. Is that workflow equipped with leave encasement process as well?
I found WS12300111 as leave management workflow, is this a correct one?
Please guide me on this regard.
Regards,
Babu

Hi,
My user want to use R/3 only for leave management section. we have no portal.
will this workflow would work fine in this case? if so how do i proceed to get it configured?
Thanks in Advance.
Regards,
Babu

ESS Leave Request workflow customization

Hi Guys,
We are trying to customize the standard Leave Request Workflow WS12300111 in the ESS application for ECC6. The standard workflow passes the data to the workflow via the object REQ of type CL_PT_REQ_WF_ATTRIBS. I need to extract the leave information from the object.
I tried creating an enhancement implementation for the Class CL_PT_REQ_WF_ATTRIBS and added my own method. But I can't see this method when I create a workflow task.
I also tried copying the whole class and adding my code, but am not sure how to instantiate the new class in workflow. Pls help .

Hi,
Can you tell me the requirement.
Do you want to change the Agent using a BADI ??
or you want to send the leave request for another approval ??
If you want to send the leave for another approval then just reset the status of the leave to SENT again using same class and using following code
CALL METHOD cl_pt_req_badi=>initiate_state_transition
    EXPORTING
      im_request    = request
      im_event      = 'SENT'
   IM_RET_VALUE = 0
    IMPORTING
      ex_new_status = me->status.
After this, u can send this workitem to another processor..
Another scenario could be:
U want to determine a new agent for your workitem.
In this case, u will have to implement BADI "PT_GEN_REQ"
Read the documentation of this BADI.. this might help.
And please tell me the requirement once again.. what you want to achieve.
Regards
Ashutosh

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.

Reg: EP based Leave request workflow

Hi Experts
We are implementing ECC 6.0 and EP .
My requirement is I have copied standard leave request no 12300111 and i have modifield according to client requirment .
When i create the leave request wokflow from EP frent end its working fine and leave details are appearing in superviser in box ( IN EP inbox) .
Supervisor is approving fine .
1 . After approving leave reqeuest data is not updating in 2001 infotype.
2. In this workflow there is no BOR ( Business Object ) but still the data is appearing in supervisor inbox after create a leave from employee .
How can i see the request data in workflow becouse i need configure mail format aslo .
Once leave is created i need send main notification to employee as well as manager with leave request details.
Please help me how do i get leave data in workflow container .
Thanks
RameshG

There is no BO for the standard SAP leave req workflow. It is handled by a class CL_PT_REQ_WF_ATTRIBS. So you can forget everything about creating a sub-business object and delegating it to the standard one.
You can create your own custom (ABAP class) method which you can use to get the needed details of the leave request into your workflow container (which you can then use in your notifications). Check Jocelyn Dart's blogs about WF and ABAP OO. In your case everything should be quite clear if you just create one static method (you don't need to implemenet the LPOR-methods). This is of course the simpliest way to achieve your requirement - there are also some other more fancy ways.
Regards,
Karri

Do we face any problem if initial download is done again and again

Hi to all,
Do we face any problem if initial download is done again and again.
Is there any impact on the server?
please help me.
Regards,
divya

Divya,
Yes, definately there will be a impact on server. Whenever we do intial download, some logs like archiving logs gets filled in database level. This logs stores all the processing and actions and results happened during download. Once this logs is full, download will stop. SO it is always recommended to involve some BASIS or database administrator while doing download, just to monitor the logs and performanace of server. If log is full, delete the log.
I have face this problem many time...
If it helps, please credit the points.
REgards
Pankaj

Problem to trigger PO Release Workflow

Hello experts,
I am working in a workflow to release PO.For this I have copied the standard workflow template wf_po_rel(20000075).
In my custom workflow I have used RELEASESTEPCREATED
of BUS2012 object as triggring event(as like the standard workflow).
Now when I am creating a new PO the workflow is not being triggred.But I am receiving a message in my workspace inbox with title:Error in event receiver.
And the body is as given below.
Error processing following event linkage:
BUS2012 RELEASESTEPCREATED WS99900005
Following error occurred:
SWF_RUN 594
Message text:
Import container contains errors (are any obligatory elements missing?)
Event container appended as attachment.
Event linkage with errors deactivated.
Can anyone suggest what to do to recover the problem and successfully trigger the workflow.
Thanks & Regards
Manas
Edited by: Manas Santra on Feb 13, 2008 7:55 AM

Hi JMB,
I have gone to SWE2 transaction in 200 client.
There I saw that the corresponding type linkage was unchecked.I double click the row and check the Linkage Activated check box and save that.After that I check the start event tab of my workflow template and that is active now.
But when I create a new PO in 200 client the workflow has not been triggred.But a message has been received in my inbox from Workflow-System...
Title:Workflow 388121 set to status ERROR
and the body like as given below..
Please repair the suspended workflow
Context Information:
ID: 388121
Work Item Text: Workflow for PO release
User: WF-BATCH
Language: E
Press 'Execute' to display the workflow that has errors.
Regards,
Manas

Problem in initiating Leave Cancelletion workflow

Similar Messages

Maybe you are looking for