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

Similar Messages

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

Unable to evaluate workflow rule - Value too long for field

Need help with a workflow error for a record update before the record is saved. There are 3 calculations that would be done in a particular order - all on number fields. Each time, I am overwriting existing values. The individual numbers could have up to 6 decimal spaces. When I try to update one or more fields that contain the calculation, I get an error message saying that the system is unable to evaluate the workflow rule - value too long for field (zNum6).
This same calculation is fine when a new record is entered and the calculation is done as a default field value.
Any ideas?

I actually had to use a ToChar function at the beginning of the calculation and #### to indicate the number of digits to make this work. Oracle Help Desk provided the answer - quickly.

Create opportunity using workflow rule

Hi,
Is there a way to create an opportunity record using a workflow rule.
We want to be able to create a service opportunity to be triggered automatically by the sales person by either updating a flag or check box which inturn triggers
a workflow rule that can create an opportunity.
I am aware of using a web link to copy an existing opportunity.
Any ideas ?
Thanks
Swami

At this time this is possible by using Integration Events and using web services. CRMOD does not support Workflows that will automatically create an opportunity using a workflow

Workflow rules doesn't work for existing record!!?!?!?

Hi all,
I've created one workflow rule to update value from one filed to another. Here is my expression:
[<QuickSearch1>] <> [<plStatus_ITAG>]
and my action is
field name = "*Status" (QuickSearch1)
Value = <plStatus_ITAG>
and I tick on the Overwrite the existing value
This is work for new record, but for the existing one the field value doesn't chnage. Any suggestion??
Thanks
Note

The syntax should be: PRE('< QuickSearch1>') <> [<QuickSearch1>] for the condition.

Help writing a workflow rule

Hello Experts!!!
I need help writing a workflow rule condition to trigger the workflow. What I am aiming for is an email to be sent out when an opportunity is marked Closed/Won. But it can only be of a certain opportunity type (we use three options) and opportunity sub-type (we use two options) (these are custom fields we use)
Below are the fields that need to be used:
[<SalesStage>] = Closed/Won
[<OpportunityType>] = Acute
[<plOpportunity_SubType_ITAG>] = Tech
Thanks Again!!

Hi
Try:
[<SalesStage>] = Closed/Won AND [<OpportunityType>] = Acute AND [<plOpportunity_SubType_ITAG>] ='Tech'
Note that in case of picklists it is recomended to use the lookup value and not static text like 'Tech', but both will work.
Good luck
Guy

How to write workflow rules/expressions/SQL

Hi all.
We are recent users of CRM onDemand, we would like to write some workflow rules but cannot seem to find any information on how to do this. The help section is limited in answers, and some of the questions here are also not specific to what we would like to do.
Does anyone have any advice on books, web sites, etc. on where to find the knowledge we need on how to write the workflow rules and use SQL and expressions in CRM on Demand?
Thanks in advance!!

For your first case:
1. You cannot create a workflow in r15 for activity but in R16 you can
Create new to create a workflow
Name: Auto email send
record type: activity
trigger: when new record saved
rules: put your rules by clicking on the fx icon i.e this is where you are entering the rule saying the owner is different from the person who is creating the activity or the delegated field is filled (another way of looking at it)
then save the workflow
In the actions section
choose the action "Create Email Notification"
In the To: Section choose "Relative User on Record" and Choose "Activity Owner"
Save it. Make sure both the workflow and activity are marked active.
2. In your second scenario:
How do you expect to create an account and automatically populate the Sales rep's name - not sure
But you can create an opportunity and auto fill with the Account Owner's name by using this in the field validation (you do not need the workflow), you can use the FieldValueJoin function.
Hope this helps - btb there is no book you can go thro the help and you will find some directions

Workflow Rule Condition : impact of the "LookupValue"

Hello,
I would like to know something about he "LookupValue" (eg.1) impact in the "workflow rule condition". What is exactly the role of the "LookupValue"? Does it have an impact if I decide to delete it and just write the value needed (eg. 2) ?
eg.1 : ... =LookupValue("OCC_CUST_LOV_OPTY_4", "Value Needed")
eg.2 : ... =("Value Needed")
Could someone help me?
Thanks and regards.
Edited by: user5840933 on 5 mars 2009 03:44

Hi !
The lookupValue function is very useful. Imagine you created 10 workflows with a condition such as : PICKLIST="Value".
Then imagine you have to modify the "Value" of this picklist in "Value2" for example. This means you will have to update your 10 workflows to put "Value2" instead of "Value".
Using the LookupValue function, it will automatically get the picklist value based on the code corresponding to the value.
LookupValue(PICKLIST, "A") will return the value corresponding to the code "A", no matter what the value is.
In the expression builder, after chosing the field in the picklist, click on the link "Get acceptable values". Then click on a value and the LookupValue function will appear in your expression.
Hope this will help, feel free to ask more !
Max
[See Mike L announcement|http://forums.oracle.com/forums/ann.jspa?annID=883]

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.

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

Help with applescript/workflow/rule that would unflag mail when read (...)

Here's my scenario:
I have quite many mail.app rules that automatically filter and file incoming mails from newsletters, SNS, work, friends etc. and they all go in specific mailboxes (200+)
I also have some rules that I trigger using MailActOn.
Since with Lion theres now 6 different flags (and that you can rename them) I've included them in the rules actions and set them up to the following categories:
- To Do
- To Do Later
- To File
- News
- Personal
This actually allows me to have these smart mailboxes to appear only when they are flags active.
Now for the first three I want to keep the flags permanently until I'm actully done with them.
But for the "news" and "personal" ones I want to have them "unflag" once I read them.
So to recap, is there a way to systematicall/periodically unflag messages when they are read from specific mailboxes or if they are flagged with a particular flag?
I'd really appreciate if someone would help me out figure out an adequate solution to what I'd like to achieve.
I'm not sure if a kind of a combination of either applescript/workflow/rule would actually make it work...

Here's my scenario:
I have quite many mail.app rules that automatically filter and file incoming mails from newsletters, SNS, work, friends etc. and they all go in specific mailboxes (200+)
I also have some rules that I trigger using MailActOn.
Since with Lion theres now 6 different flags (and that you can rename them) I've included them in the rules actions and set them up to the following categories:
- To Do
- To Do Later
- To File
- News
- Personal
This actually allows me to have these smart mailboxes to appear only when they are flags active.
Now for the first three I want to keep the flags permanently until I'm actully done with them.
But for the "news" and "personal" ones I want to have them "unflag" once I read them.
So to recap, is there a way to systematicall/periodically unflag messages when they are read from specific mailboxes or if they are flagged with a particular flag?
I'd really appreciate if someone would help me out figure out an adequate solution to what I'd like to achieve.
I'm not sure if a kind of a combination of either applescript/workflow/rule would actually make it work...

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

Trigger workflow to HR administrator

Hi All,
I've created a workflow which will trigger when there occurs any change in HR master data,now my requirement is the workflow should be trigger to the HR Administrator P0001-SACHP.i think i have to define a RULE for this.
Thanks in advance
Regards
Hari Sankar

You can create a role for this if you wish and create the ABAP code yourself and then place the Role in the Task.
But it might be easier to just create an "Attribute" in your main Business Object for the HR Administrator (Assuming that you have already created a Subtype of the Business Object, do the following on the Subtype):
1. Create new Attribute
2. Say "Yes" to "Create With ABAP Dictionary Field Proposal"
3. Select Table "PA0001"
4. Select SAHCP
5. Modify name of Attribute and Description (If required, eg. HR_Admin).
6. Change "Release Status" of your new Attribute to "Released".
7. Place cursor on the new Attribute and click on "Program"
If PA0001 has already been implemented in your Business Object, then the underlying ABAP code has been implemented - In your case, I believe that it would have already been implemented or at least inherited, so this is the last step...
Otherwise, you will be prompted if you wish to "Generate Template Automatically"... Select "Yes" and 90% of the ABAP code will be created for you, you can modify it accordingly.
Now, in your Business Object, you have this new attribute (ie. called HR_Admin) that you can place as an "Expression" in your Task to recieve the Work Item.
T

Purchase order release workflow rule

Hi ,
I have made a zcopy of standard workflow(WS20000075) for PO release. My requirement is that there are three level of approvers who have to release the PO. MM consultant says he will assign the approvers for all three levels from SPRO. As per the std workflow there is only one level of approval as far as i have understood .every time if approver rejects the po the mail should go to outlook also , to initiator and the next approver .
standard rule 20000027 is taken care for all three levels of approvals ..what is the binding for rule to workflow?
from workflow side what are the customize things should i follow..i am new to this MM workflow can u please guide me ..
thanks,
sandeep chennoju .

Hi Sandeep
The requirement changed!!!! :-)
Okay...for the email on DEADLINE BREACH
1) You Do not need the fork in the deadline branch
2) Instead, call an Activity Step which calls a method -> Input: WF Initiator (full US + Username), PO Number and the Current Release code
3) In the method coding, call rule 20000027 using FM RH_GET_ACTORS, get the agents (with OTYPE) for the PO and Current Release code
4) Now Fill an internal table (of type TSWHACTOR) with OTYPE and OBJID returned from the above Function Call
5) Append WF Initiator to this table -> OTYPE = US and OBJID = username
6) So you have a table with CURRENT Approvers and the Initiator
7) Pass back this table to task and workflow
8) Now use a mail step, Set Recipient Type as 'G' (org Object) and EXPRESSION = that TABLE passed from above call (type TSWHACTOR)
9) Ensure that the settings are done for SO16 -> Tab Mail Sys Grp -> Send to users home address is selected (in each client – this is not transported, hence maintain in every system once)
10) Ensure that the users have their email ID maintained in User Master (SU01) and the communication Method Set as INT (OR Email is maintained in HR Master Infotype 0105 - if your setup is using that)
11) Ensure Job SWWDHEX is running periodically in the background
12) Ensure Basis Settings and send job are in place to send outbound emails
What will happen when the deadline gets over:
1) SWWDHEX job will pick up the item and the control will come to deadline branch
2) The new step/method will get the agents of Current release code using the FM Call; it will also add WF Initiator to the list
3) The mail step will send to the ORGNIZATIONAL Objects (the Usernames, Positions passed to it in table of type TSWHACTOR)
4) SO16 settings will ensure that the mail is sent to the email address
5) Email address is picked up by the system automatically from User Master or HR Info type 0105 (order is really not known)
6) Basis settings and send job will send the email out of the system
I hope I was able to get your requirements right this time and these will not change :-)
Regards,
Modak

ESS W2 Reprint workflow Rule HR Administrator

Similar Messages

Maybe you are looking for