Leave request WS12300111 "ITEMS_TAB"

Hi Friends
Could someone tell me how to use data stored in "ITEMS_TAB" of oject "Req" into my workflow/ task container? I want to retrieve u2018number of days of absenceu2019 to determine how many leaves of approval required.
Thanks
Nash

1. First pass the REQ to a Z BOR method either by using the binding from WF --> TS ---> BO or
WF --> TS ---> By using SWC_ macros's
for example see the belwo lines
swc_get_element container     '_Workitem'          lv_wi_object.
swc_get_property lv_wi_object 'Workitemid'         lv_wiid.
here the first macro is importing the instance of the BOR workitem and the second macro is getting the BOR attribute property workitem ID in the same way.
in your case it will be
SWC_GET_ELEMENT     container 'REQ' lv_req.
SWC_GET_PROPERTY container 'ITEMS_TAB' lv_tab.

Similar Messages

ESS Leave request - steps

Hi,
I would like to know the sequence of steps involved to activate the ESS Leave request WS12300111
in portal .I also come to know that without worflow , using report alone we can process the leave request ?
Is that posssible ?
PT_GEN_REQ - This badi is used for agent assignment ?
Some one who worked on this can help me !
Thanks in advance !
Richard A

Hi Rao,
Go through this link for leave request cofiguration steps.
https://www.sdn.sap.com/irj/scn/wiki?path=/display/erphcm/leave%2brequest%2bconfiguration%2bsteps
Also visit this link for ESS related issue resolution and hints.
https://www.sdn.sap.com/irj/scn/wiki?path=/display/erphcm/commonIssuesandHintsin+ESS
Reagrds,

WS12300111: Leave Request Approval - Multiple Approvals

Hello.
I am part of a project, trying to implement ESS/MSS at a large international NPO Customer, and have encountered a problem.
I plan to use the WS12300111 Workflow for the approval process of Leave Requests, but since the customer in some situations require more than one approval, I have to enhance the workflow. At first glance it seems simple just to repeat the approval process, but since the request will be marked as approved at the first approval step, that will not work.
We are required to keep the implementation as close to SAP Standard as possible, so the portal guys tell me, that it is not really an option to make changes to the approval functions.
I have considered making the first approval a simple workflow task, that doesn't update the request itself, but since a rejection should update the request and trigger the Process Leave Request by Employee task, I really don't see that working either.
Any thoughts on the subject, or maybe even a solution, will be greatly appreciated.
Best regards
Poul Steen Hansen
Denmark

Hi dude,
Well, I might not be able to give you the coding, but I can explain it how to do this. Check the procedure.
Create a new BOR and create a new method - CHANGESTATUS.
Add one and only IMPORT parameter REQUEST of type PTREQ_HEADER-REQUEST_ID.
In the coding part, firstly lock your request using the FM - ENQUEUE_EPTREQ.
Then create an instance using the static method ca_pt_req_header=>agent->get_request which takes the REQUEST number as input and gives us the instance as OUTPUT.
Having the instance in hand, we can use the method initiate_state_transition to change the status of this method. Pass the SEND status as INPUT and get the new updated status as OUTPUT.
Unlock the leave request using the FM - DEQUEUE_EPTREQ.
Implement and release this method in your BOR.
And please make sure that your method is INSTANCE INDEPENDENT METHOD.
In your template create a Standard background task after your first approval step which calls this method.
Regards
<i><b>Raja Sekhar</b></i>

Leave request Workflow ids Ids WS12300111 ,WS12400005

hi
I am on ECC 50 and Portal 7.0. I am using the copy of standard workflows
1) WS12300111 copied to WS90100002 ( Create Leave request)
2) WS12400005 copied to WS 90100003( Cancel leave request)
in ESS.
My questions are as below
1) In Processing process for types of leave in IMG, which worklfows do i enter in each section
a) WF ID of New Request ( i have entered ZWS12300111 )
b) WF ID of Cancellation Request ( i have entered ZWS12400005 )
c) WF ID of Change Request( i dont know what to enter here, should it be same as ZWS12300111 )
2) Secondly the workflow ZWS12400005 does not get triggered when i delete the leave request ( approved, rejected) though i have set up the leave for approvals for cancellation.
3) When i reject the leaves, the work item "Process requeest by employee" comes and sits in UWL. If i click, it open the leave request screen, where in the old values are not present ( like dates for which i had applied leave). If i change the dates and send for approval, the workitem goes to managers inbox, but the work item "process request by employee" still sits in employee inbox. This is happening only in case of rejected leaves when employee uses the same workitem to re apply for leave.
Apprecaite your help
Regards
PN

Hi
I have the same problem how did you sort it out?
Thanks
Rendani

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

Rejection of a Leave request in MSS - WS12300111

Hi ,
We have a implemented WF WS12300111 for leave request approvals through ESS/MSS.
When a manager rejects a leave , notification is sent to the initiator but the WF status is not CLOSED or COMPLETED .
Can anyone know how to make the status of the WF to COMPLETE , are we missing any step in the portal?
Cheers,
GK.

Hi Pavan,
Yes , i have checked the LOOP exit condition.
Whenever manager rejects the leave , initiator is receiving below notification :
*You submitted a leave request. The request has now been processed. For more information, see the list of your leave requests.*
*To view the list, go to the Web application for leave requests.*
*Once you have processed the request, the work item will automatically be set to "completed."*
Above text says ONCE initiator Process the request workitem will automatically set to Completed.
Do you have any idea from where we have to PROCESS the above request to set the status of the WF to COMPLETE.
Cheers,
GK

Leave Request for ESS Portal WS12300111 Workflow Text

Hello workflow experts
I've been asked to enhance the standard Portal leave request workflow (WS12300111) so that instead of the generic text "General workflow for documents" the SWI2_FREQ transaction can show text with the requester's name to simplify any troubleshooting or auditing issues. For example, have the text show "Carl Robinson's Leave Request".
I've already tried doing this by copying the standard workflow and then placing a workflow container within the text, where the container should have the initiator's name. However, generated worflows do not show any text for this container, just an empty space. For example, current workflows show " 's Leave Request" when I would expect them to show something like "Juan Ramos's Leave Request". When I check the container values in the workflow log, the container does indeed contain the name value.
My suspicion is that since this workflow is not being triggered by an event, but rather through customizing and integration with the Portal, the text is being generated before the containers are populated with values. However, I can't be sure of this since the workflow log shows the containers filled already even when the text shows empty text. Is there a way to test this? Also, would anyone have suggestions on how to fix this issue? Thanks in advance.
Regards and happy holidays,
Juan Ramos

Thank you all for the quick replies.
I followed a similar approach to Maorriyan's suggestion. I created the &NAME& container but it wasn't being populated. Instead I found a similar container under &REQ.INITIATOR.NAME&. This container populated the value correctly as soon as the organizational environment was refreshed.
Thanks all!
Points awarded.
Message was edited by: Juan Ramos Bras

Leave request Workflow WS12300111 not working

Hello All,
We have ESS/MSS portal and ECC6.0. I have started with pilot ESS leave request project
When i create the leave request from ESS, i am getting message ' The leave request has been sent.'
Evne i am able to the see the task in UWL(MSS) in tracking tab. But if log in as a manager to approve the leave request, its not displaying the task. I have checked the workflow, its getting stuck. Then i have checked leave process(test application) in R/3 alone in transaction PTARQ. I have given my person number and mode 'R'. Its throwing error message " No document created : HRTIM_ABS_REQ 124 conflict with absences/relocation (IT2001/0330)
But i have customized workflow properly in 1. SWU3 ; all are green except guided procedures
                                                                      2. Maintained the WS12300111 in workflow template for all
                                                                      3. Request have to approved
                                                                      4. task is generated
                                                                      5. line manager as agent (OM maintained properly)
Kindly help .
Regards,
Venkat

Hi ,
I have changed the pernr ,date and working fine now.Moreover task is also general. But the workflow started but stuck in the step 'Approvel Process.
Its stops at Node number 38 . I have checeked the step history :
Green (Sub)workflow created
Green Background Processing Started
Green Execution started
Green Error Message Created for Admin
Red    Exception occurred Error handling for work item 000000390153
I just want to execute the leave request workflow from PTARQ, keeping as me as requestor and approver. If its success , i want to test with ESS. But now its stuck in R/3 test itself. Please help.
Regards,
Venkat

Issue in Deletion of approved leave request using ws12300111

We are using Std workflow 12300111 and its working fine for new leave request and change leave request but when raise request for deletion of approved leave request the workitem created and info type updated automatically without seeking approval from manager. When you check the workflow log the agent determination happend and updated the info type 2001. This issue is in production system , At the same time if we tested the same scenario in QAS its working fine, ie its asking approval from Manager.
Pl help on this issue.
Regards,
Muthu

This is correct and intended functionality, NO WF IS triggered.
Let me explain, There is no WF triggered when APPROVED (NOT POSTED)
absence is deleted. This is standard, You can trigger a mail
which You had already done so. But there will be no WF triggered.
So if you notice
when the leave request is in status POSTED, it calls the workflow,
but if the leave request is not POSTED yet, it is doesnt call the
workflow.
There is no standard Workflow triggered when the Approved leave request
has been deleted by the employee!
This step should be configured by the customers as when to trigger a
mail to the Admin or Supervisor, when deletion or cancellation happens.
The workflow template is a simple template, You can modify
to suit their needs.

Error while raising leave request

Dear all,
I am getting error while raising Leave request over ESS...Task WS12300111 locked for instantiation.
As well as in MSS manager is not getting requests for approval..can anyone tell me on workflow front what shall be done.
Regards,
Rajasekar.

check the WF is a general task ie PFTC and user has authoriation, Are you using any custom code through badi, then enusre Start_WF method is implemented.

Error - While changing existing leave request from ESS

We are trying to use the standard leave request application in ESS/MSS. The basic required standard configurations are done. Since we wanted custom notifications, the related workflow is copied into custom workflow and we have included required custom notifications. The custom workflow is also configured properly.
Now, the standard functionalities like making leave request, triggering notifications, approving leave request and posting information into backend are working fine from the ESS/MSS.
When the employee tries to change the existing leave request (before approval) from ESS, at the 2nd step (Review and Send), it is displaying one error message General task: can be edited by all users. But, it still allows submitting the records.
Once it is submitted, the system throws one java error at the final step (after pressing SEND button) u2013 Failed to process request. Please contact your system administrator. - java.lang.NullPointerException. The complete error information is provided in the attached word document. Even though, it throws error the submitted data is getting saved into the backend.
Please help to solve this issue.
Thanks,
Prabhu
Edited by: Prabhu T on May 18, 2011 1:53 PM
Edited by: Prabhu T on May 18, 2011 1:54 PM

What custom notifications you require in leave request? We have all available in standard using Rptarqemail
First of all, the WF task should be set as
General task: can be edited by all users, which you have done presumably under task classification
Now, for checking purposes, can you check with standard WF in table v_t554s_web for one absence only?
ie WS12300111.
Please test this and let us know if you have errors
Also please check your custom WF whether it is working correctly or not?

Leave Request two layer approval

Dear Experts,
I'm trying to implement two layer approval leave request workflow by copying and modifying standard workflow WS12300111.
I follow the guide from this link:
http://wiki.sdn.sap.com/wiki/display/ERPHCM/CustomizingtheESSLeaveApprovalusingBusiness+Workflow
My workflow step is as follow:
1. first approver has approve the request
2. reset req object status to SENT
3. set next approver using method if_pt_req_request->set_next_processor
4. send the request to the second approver
I have implement badi PT_GEN_REQ to set first approver (method IF_EX_PT_GEN_REQ~FIND_RESP_AND_DEFAULT_NEXT_PRC) so that the first approver name shown correctly when requestor create the request.
Now there are 3 problems I'm facing:
1. After the FIRST approver approve the request, the note he input is shown twice. I found out this is because the status change create new version of the document. I have tried to clear this note when changing the status using method if_pt_req_request->set_notice. However, the method ignore if the notice is set to blank. Is there anyway to hadle this?
2. When SECOND approver reject the request, I want the request to be revised by the requestor, and then forwared to FIRST approver after that. For this purpose, before send the workitem to requestor back, I put step to set approver back to FIRST approver again using method if_pt_req_request->set_next_processor. But it seems this doesn't work and the request is sent to SECOND approver after revised. The supervisor name that is shown when requestor revise the request also show the SECOND approver name instead the FIRST approver.
3. I find difficulties to create email notification if the request is changed by the requestor during approval process, since there are no event triggered. Is there anyway to trigger this event or is there any workaround?
Thank you.
Regards,
Ponty

Hi Ponty,
I am trying to implement two layer approval for leave request, too.
I took a copy of standard WS12300111 as you did.
I followed the guide, you mentioned. For one level approval this works nearly out of the box.
But I don't understand the second half of the guide.
For me it will be the first time to implement a BAdI. I never did this before.
Can you please explain me, how to do it and how you enhanced the workflow for two layer approval?
Some screenshots might be useful. Eventually you can enhance the guide you mentioned.
Regarding the numerous questions on multi level approval, these hints might be useful for a large number of users.
I would be very happy, If somebody can help me, becaus I didn't know any workflow experts who can help me implementing the BAdI.
Thank you.

Auto Approval Workflow for leave request Management.

Hi Guru's,
I am working on leave request Workflow i.e WS12300111.
Now i have to implement the auto approval of workitem if the approver doesnt take any action in 3days.
1. i have implemented deadline monitoring i.e in Latest end tab
refer date/time :- Expression Date : %DATUM% Time : %UZEIT% 3 days Action : Modeled Display test
Outcome : Reminder Mail
In outcome tab i have activated Processing obsolete.
i have created an activity if the deadline is reached so that it should auto approve the workitem.
in that activity i have created a copy of class CL_PT_REQ_WF_ATTRIBS created 1 method auto_approve. and used function module PT_ARQ_REQUEST_EXECUTE so that it will change the status from SENT to APPROVE.
But when i apply leave in portal , workflow starts but it doesnt reach to branch auto approve after the deadline is reached.
Please suggest is the deadline monitoring implemented correctly or not .
whether the auto approve method used is correct or not
or there is another solution to this
I have checked the SWU3 setting and it is green.
Please Advise
Thanks in Advance
chitis

Hi Rick ,
Thanks for the Reply.
But is there something wrong in deadline monitoring i have maintained for the task.
could you please share the procedure for implementing deadline monitoring specific to auto approval of the workitem.
thanks in advance
chitis

ESS leave request workflow : not able to approve request

Hi experts,
When i create leave request, work item for approving request is not coming in the approver's bussiness workplace. I am using std workflow WS12300111. Is there any customization needs to be done ??
please help me
Pointes will be rewarded
Regards,
Sameer

Hi Samee,
Did you select General Task in the steps of workflow you have an agent?
Sónia
You have a chief position on the Organization Unit where you have the employees?
Sometimes it's possible to forget this one:
Transaction SWDD, select the workflow WS12300111 and press CTRL+F8 (Basic Data)
there's another button "Agent assignment for task" (SHIFT+F9)
set task to "General task" with the "Attributes..." Button. (EVERY user can start this task).
And check this to:
Using transaction SWFVISU, check the following entries and correct these where required:
TS12300097 Java WebDynpro APPLICATION LeaveRequestApprover
                 PACKAGE sap.com/ess~lea
TS12300116 Java WebDynpro
                 APPLICATION LeaveRequest
                 PACKAGE sap.com/ess~lea
(check this, because usually you have an error, instead of sap.com you have com.sap)
Register the work items again. Additional information about registering work items is available in the UWL documentation.
After re-register the System Alias again in the UWL - THIS IS VERY IMPORTANT
Edited by: Sonia Santos on Jan 28, 2008 12:49 PM
Edited by: Sonia Santos on Jan 28, 2008 12:51 PM

Leave request WS12300111 "ITEMS_TAB"

Similar Messages

Maybe you are looking for