ESS Leave Request Workflow WS20000081

[Bibby, David]

Found the Web Transaction, it's the same as the WF Number WS20000081.
Many Thanks for your help.


-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf
Of Griffiths, Mark
Sent: 04 January 2005 16:05
To: SAP Workflow Users' Group
Subject: RE: ESS Leave Request Workflow WS20000081


The web transaction is already created in the system - you can find it
in SE80 - it may need publishing - speak to your ESS consultant, they
should be able to help you out.

>From Mike's post it looks like there is a new triggering customising
table which may mean that you can use your own copied workflow rather
than changing the original.  Also, double check which workflow to use in
your release: I have a vague recollection that there may be an updated
one, and an updated leave transaction. 

Cheers,

Mark

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Bibby, David
Sent: 04 January 2005 15:14
To: SAP Workflow Users' Group
Subject: RE: ESS Leave Request Workflow WS20000081


Hi Mark,
Thanks for the advice.
Regarding the triggering, do I need to create the web transaction or is
this part of the template, I cannot see anything obvious ?
Regards
David

-----Original Message-----
From: sap-wug-bounces at MIT.EDU [mailto:sap-wug-bounces at MIT.EDU]On Behalf
Of Griffiths, Mark
Sent: 04 January 2005 14:25
To: SAP Workflow Users' Group
Subject: RE: ESS Leave Request Workflow WS20000081


Hi David,

Generally speaking best practice is to make a copy and then change the
copy, then deactivate the old event linkage and activate the new one.

However, the Leave Request workflow (certainly up to 46c) is a bit
different as it is triggered by a Web Transaction in which the template
number is hard-coded, and the workflow started directly (make sure you
make the workflow template a general task to allow this).  In this case
you should take a copy for refernece, and make changes to the original.
In case of support packs etc. you should then copy your changed workflow
for reference in case the workflow is over-written

Cheers,

Mark

SAP UK

-----Original Message-----
From: sap-wug-bounces at MIT.EDU [mailto:sap-wug-bounces at MIT.EDU] On Behalf
Of Bibby, David
Sent: 04 January 2005 13:54
To: SAP Workflow Users' Group
Subject: ESS Leave Request Workflow WS20000081


This maybe a naiive question, so apologies if it is.

I have been asked to implement the ESS Leave Request Workflow WS20000081
of which there will be changes required.

So far, the workflows I have implemented have all been custom workflows.
We do not use any workflows based standard SAP template workflows in our
business.

What is the normal policy (if there is one) on changing SAP Standard
workflow templates ?
i.e. Do people normally copy the workflow template and change the copy,
or do they make changes to the standard workflow template ?

Also there is no triggering event for the ESS Leave Request Workflow
when I look in PFTC.
Does this need to be set up though SWEHR1, 2 or 3 ?

Many Thanks
David


-----------------------------------------------------------------------

This message is confidential. It may also be privileged or
otherwise protected by work product immunity or other legal
rules. If you have received it by mistake please let us know
by reply and then delete it from your system; you should not
copy it or disclose its contents 
to anyone. All messages sent
to and from Linklaters may be monitored to ensure compliance
with internal policies and to protect our business. Emails are
not secure and cannot be guaranteed to be error free as they
can be intercepted, amended, lost or destroyed, or contain
viruses. Anyone who communicates with us by email is taken
to accept these risks.

The contents of any email addressed to our clients are subject
to our usual terms of business; anything which does not relate
to the official business of the firm is neither given nor endorsed by
it.  

The registered address of the UK partnership of Linklaters is One 
Silk Street, London, EC2Y 8HQ. Please refer to 
http://www.linklaters.com/regulation for important information on
the regulatory position of the firm.

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug



---------------------
--------------------------------------------------

This message is confidential. It may also be privileged or
otherwise protected by work product immunity or other legal
rules. If you have received it by mistake please let us know
by reply and then delete it from your system; you should not
copy it or disclose its contents to anyone. All messages sent
to and from Linklaters may be monitored to ensure compliance
with internal policies and to protect our business. Emails are
not secure and cannot be guaranteed to be error free as they
can be intercepted, amended, lost or destroyed, or contain
viruses. Anyone who communicates with us by email is taken
to accept these risks.

The contents of any email addressed to our clients are subject
to our usual terms of business; anything which does not relate
to the official business of the firm is neither given nor endorsed by
it.  

The registered address of the UK partnership of Linklaters is One 
Silk Street, London, EC2Y 8HQ. Please refer to 
http://www.linklaters.com/regulation for important information on
the regulatory position of the firm.

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug



-----------------------------------------------------------------------

This message is confidential. It may also be privileged or
otherwise protected by work product immunity or other legal
rules. If you have received it by mistake please let us know
by reply and then delete it from your system; you should not
copy it or disclose its contents to anyone. All messages sent
to and from Linklaters may be monitored to ensure compliance
with internal policies and to protect our business. Emails are
not secure and cannot be guaranteed to be error free as they
can be intercepted, amended, lost or destroyed, or contain
viruses. Anyone who communicates with us by email is taken
to accept these risks.

The contents of any email addressed to our clients are subject
to our usual terms of business; anything which does not relate
to the official business of the firm is neither given nor endorsed by it.  

The registered address of the UK partnership of Linklaters is O
ne 
Silk Street, London, EC2Y 8HQ. Please refer to 
http://www.linklaters.com/regulation for important information on
the regulatory position of the firm.