<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.6000.16735" name=GENERATOR></HEAD>
<BODY><!--ppd1000033-->
<DIV>
<DIV class=jive-message-body><FONT face=Arial><FONT size=2><SPAN
class=239092303-18112008>Hi everyone,</SPAN> <BR><BR>We would like to implement
std workflows in the first phase. <BR><BR>We have implemented HR payroll along
with other modules mm,sd,ps,pm, pp.&fico. <BR><BR>Now, we are struct with
regard user maintenace part in workflow, if we use HR org structure, we are not
able to do testing in development client & quality as othe HR org structure
numbering is different, even in production is it will be different. under these
circumstances, pl advise whether we can use HR org structure or go create with
simple organisation unit and use the same. <BR><BR>Request experts give their
opinion how far it is clear & confident on workflows if we use HR org
structure & let us what are the default Maintenance issues if we use HR org
structure & Simple Organisation structure. <BR><BR>I need experts opinions
enable us to go ahead with our Std Workflows. <BR><BR>Thanx in
advance<BR>Regards<BR>Srihari</FONT></FONT></DIV></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV><BR><BR><P><BR>"The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. SHV Energy Private Limited is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt."</P><P><img style="width: 127px; height: 84px" height=81 src="cid:614488c4-b543-422b-94cc-d8c00215f8e9" width=170 border=0><BR></P></BODY></HTML>