ESS FI-TV workflow

Hi all,
I'm using the Business Package for Employee Self-Service (mySAP ERP) 1.0 on Enterprise Portal.
I can´t find a way to activate FI-TV workflows.
Can anyone help me?
Best regards,
Luis Cruz

I guess there are 3 workflows in Travel. One is approve trip,approve travel plan and approve travel request. Pls check if you have the appropriate workflow activated.
Workflow is started by an event that is created when a trip is saved.
The Approve Travel Plan workflow is started each time a travel plan is saved/posted.
The Approve Travel Request workflow is started when a trip is saved with the travel request/to be accounted status.
The Approve Trip workflow is started when a trip is saved with the trip completed/to be accounted status.
Are u creating a travel request or a plan ?
Regards
jayesh
Edited by: Jayesh Ghodge on Feb 7, 2008 12:33 PM

Similar Messages

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.

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

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

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

ESS Leave Request Workflow Configuration

Hi Experts,
I Have ESS & MSS setup with mySAP ERP 2005 ECC 6.0, i have made the required configuration for absences, i assumed that leave requests should automatically be forwarded to the person with cheif position in the department, Now hwen an employee applies for a leave request i check the MSS UWL and nothing is appearing.
My question is do i have to maintain any configuration in terms of workflow or is it automatically configured if PA & Om integration is active ?
Points will be rewarded for any help..
Regards,
Ahmed Salah

Ok follow this path
Tools --> Business Workflow --> Development --> Tasks/Task Groups --> Change
Task type = Workflow template
Task = 12300111
Click on Change
Click on Workflow Builder.
Click on Process request by Employee.
Click on Task Properties (Agent assignment)
In Maintain Agent assignment,
See for Process Leave Request by Employee , add General Task.
Then click on the Update Index.
Hope this works for you.
Cheers!!!
Sanjay Sharma.

Third party address validation in ESS pages using workflows

Can anyone help out in giving some ideas for solutioning the following.
Address entered in the page "Main Address: Enter New Address" of
Employee Self Service needs to be validated using third party PL/SQL API. This PL/SQL API is available in the same schema where HRMS objects are available. After the validating the address, user can be shown recommended or invalid address message when address entered is not valid. User can accept the recommended address or reject it in which case the original user entered address would be saved.
ESS pages are using workflows. What is the best design to call the third party address validation from the workflow and show the page with recommended address/invalid address message with "Accept" and "Reject" options. Can anyone help out on what are the technical possibilities to implement this address validation in the ESS page?.

After the validation, user is shown a page with "Ok" and "Cancel" options ( please note as said earlier we are not going with "Accept" or "Reject") along with recommended address if the address needs to be corrected. If user clicks "Ok", user will be in the Address update page and can edit the address with the recommded address. If user clicks "Cancel", control goes to next page by saving the address what ever is entered intially.
After passing through the validation logic in the work flow process and based on the result returned, can a OAF page be invoked which can show recommended address with OK and Cancel buttons?

ESS W2 Reprint workflow Rule HR Administrator

Hi,
I am using std . workflow WS01000090 for W2 reprint.I have a requirement -
the notification of request for w2 should go to two diffrerent transaction centers via email and not the HR Administrator. How do I modify the the standard rule 60100010 (HR Administrator) ? Please help me with valuable suggestions.
R/3 system is 4.7 and ESS BP version is 50.1
Thanks
-Apparao

Hi
The best suggestion is to use a custom Function module in the Rule (60100010) to call the email IDs of the users / administrators.
Pl do reward if this helps.
Narasimha

Custom ESS Advance Claim Workflow

Hi,
1. I have a scenario in ESS: Advance Claims, where in we need to n-level Approval.
Could any one throw some light on this ?
2.As of now I have activated the standard wf template, WS18900023, for one-level approval, and it is getting triggered.
But, when the approver approves the request, the status shown in the Request Creator's inbox is:
Request Phase : In-Process
Request Status : Partially Approved
But, if a request is rejected, the status is :
Request Phase : Completed
Request Status : Rejected
I have implemented a BADI: HRPBSIN_NEXT_APPROVER with the logic, just to determine the
method IF_AC_NEXT_APPROVER~GET_NEXT_APPROVER.
IFD_ALGRP = 'NLE5'.
EFD_APERN = '969'.
EFD_APGRP = 'DEFAULT_GROUP'.
IFD_ALGRP = 'NLE5'.
EFD_APERN = '6601'.
EFD_APGRP = 'DEFAULT_GROUP'.
endmethod.
3. Can any one tell me, where the workflow template (WS18900023) is being retrieved from, when the claim request is created?
I mean, by means of any configuration or std code ?
Thanks,
Sai.

Dear Vivek,
Thanks for your response.
Actually, the workflow is being triggered. So, why do we need to call this RFC function module ?
Also, even, if we call this RFC function module, what parameters do we pass to the wf template?
One of the wf container element in the std wf template - WS18900023 -Request ( ZAMCLASS ) whose type ' CL ABAP Class ' does not exist in the system.
So, how do we populate this container element?
Thanks

ESS Travel Request Workflow issue.

Hello All,
I have copied Standard Workflow WS20000050. and using this Workflow for ESS.
when Approver Send it to Initiator for Changes .
when initiator want t do change in ESS by Executing Workitem.
there is no any Button for Save the Changes. it is Only showing 'Approve' button .
is ther is any Solution for this.
Please revert back to me.
Thank You.

i suspected if manager can actually change original travel request submitted by Employee.... and guess what , i was right about it.
http://help.sap.com/saphelp_erp60/helpdata/en/d5/202038541ec006e10000009b38f8cf/frameset.htm
Standard service only allows manager to approve/reject with comments..
Hope this helps,
Cheers

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

HELP NEEDED: ESS Sick Leave Workflow

Hi ESS/MSS Gurus,
Good day!
I am a newbie workflow consultant currently working on enabling ESS-MSS for a client. In summary, here are their requirements:
1. Leave Requests and Clock In/Out Corrections - Upon initiation of employee request, the work item is sent to the manager for approval. Regardless of the decision (either approve or reject), the employee will be notified via an email notification
2. Sick Leave Requests - upon initiation of employee request, the work item is sent to the company doctor for approval. Regardless of the decision (either approve or reject), both the employee and his/her immediate manager will be notified via an email notification
Here are some details regarding how I went about it:
1. Leave Requests and Clock In/Out Corrections - Created a copy of workflow WS12300111 and included send mail steps after TS12300097 (Approval Process) to notify the work item initiators.
2. Sick Leave Request - Created a copy of workflow WS12300111 and included send mail steps after TS12300097 (Approval Process). The approval process is pointed to the Position Company Doctor. After which a step was inserted after the approval process which uses a customized method (using FM SWX_GET_MANAGER) to determine the employee's manager. Then send mail steps are executed for the employee and the manager
3. Clock Corrections and Sick Leave/Leave Requests belong to the same Rule Group
During testing in our sandbox client I was able to successfully test all of the workflows. However, when I migrated the changes into our pseudo-QA system, I cannot launch the Sick Leave workflow from ESS. I encountered the following errors in PTARQ (standard leave request and clock in/out correction are ok):
1. Scenario 1: applied leave coincides with the working time of the employee
   "Document created with information: P2 848: Absence encompasses planned work time
2. Scenario 2: when only the total nmber of hours is entered for the applied sick leave date
   "No document created: HRTIM_ABS_REQ 094 Indentical clock times were adjusted, Check the entries"
3. Scenario 3: applied leavedoues not coincide with the working time
   "Document created with warning" HRTIM00BLPRETRO 001 Time entry triggers retroactive accounting in payroll"
For all cases, no work item was created in the back end.
I would like to tap unto your wealth of knowledge and experience on how to address such errors. I need to determine if this is a misstep in the workflow, HCM, or ESS/MSS configuration to better isolate the errors.
Your immediate response is highly appreciated.
Regards,

you dont need a custom WF first of all, You can directly use standard one cause we have a standard mail program
called rptarqemail
ie
The mails will be directly triggered to the mail address once you run rptarqemail.
Please check if you are running the report using the option since last
run. The procedure is usually this :
1. Create a Leave Request
2. Execute the report RPTARQEMAIL.
3. Approve the Leave Request.
4. Execute the report RPTARQPOST.
5. Execute the report RPTARQEMAIL.
Now to determine different approvers for different types of leave you can use the option of badi PT_GEN_REQ
IF_EX_PT_GEN_REQ~FIND_RESP_AND_DEFAULT_NEXT_PRC.
Method FIND_RESP_AND_DEFAULT_NEXT_PRC of badi
PT_GET_REQ might be utilised here.
Please have a look at the method
CL_PT_REQ_SEARCH_NEXT_P~SEARCH_NEXT_PROCESSOR.
If you are implementing the badi then make sure you copy all the methods
and implement the one, as mentioned.
also note that
Standard Leave request application offers the following options to
determine the Next agent. This specifies whether and how the next agent
of a leave request is to be determined.
Last Agent: The system reads from the database the last agent to have
had requests from this employee.
Line Manager: The system uses the organizational model to determine the
agent.
Last Agent, Then Line Manager: If no agent is entered in the database,
the system then uses the organizational model to determine the agent.
No Calculation/Manual Entry: The system does not determine a next agent.
Employees can enter an agent manually.
However if the customer has a different requirement, the BADI PT_GET_REQ
method FIND_RESP_AND_DEFAULT_NEXT_PRC is provided for this purpose.
the message you get is correct and its a information message which will not stop leave request, they depend upon customisation which can be hidden too
check here
http://wiki.sdn.sap.com/wiki/display/ERPHCM/LeaveRequestCustom+Messages

Ess personal information workflow

Hi
We have requirement that when ever a employess edits his/her personal informations in ESS, a workflow should route the changed information to a reviewer to approve the changes. Once it is approved, informations should be moved to backend system.
Can someone tell me how to achieve it?
Thanks
Nash

I think you have to identify whether any event is triggered when you are changing the Employee Information.
Check with SWEL Tcode.
Thanks
Arghadip

ESS FI-TV workflow

Similar Messages

Maybe you are looking for