Leave Request - WS20000081 - Locking employee not working

GopiMunagala gopi_20us at yahoo.com
Tue Nov 22 08:57:22 EST 2005


Hi David,

Thanks for reply. I don't know what happened this
evening it started working. As mentioned I have
created my own BOR object for find the employee and
lock the employee. I have removed the sub workflow and
added my new BOR object method as one step in main
workflow before we create absences. Now this is
working fine.
Now problem is I have made change directly to SAP
delivered workflow. This created a local transaport. I
can not transport this. I have move the objects to
workbench transport. Any help would be appreciated.

Thanks,
GS

--- "Bibby, David" <david.bibby at linklaters.com> wrote:

> GS,
> Have you checked the binding between the main
> workflow WS20000081 and
> your custom workflow?
> Rgds
> David 
> 
> -----Original Message-----
> From: sap-wug-bounces at mit.edu
> [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of GopiMunagala
> Sent: 22 November 2005 04:00
> To: SAP-WUG at mit.edu
> Subject: Leave Request - WS20000081 - Locking
> employee not working
> 
> Hellow gurus,
> 
> I have implemented ESS employee leave request
> WS20000081. I have
> customized and tested. My workflow is working if
> manager rejects the
> leave. If manager approves employee is not getting
> locked, that's why
> unable to create IT2001. I have infact created my
> own BOR for finding
> employee and locking. Still not working locking
> employee. Any
> help/suggestions would be appreciated.
> 
> Thanks,
> GS
> 
>    
> 
> 
> 
> 
> 	
> 		
> __________________________________
> Yahoo! Mail - PC Magazine Editors' Choice 2005
> http://mail.yahoo.com
> _______________________________________________
> 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
> 


   




		
__________________________________ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com


More information about the SAP-WUG mailing list