<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML dir=ltr><HEAD><TITLE>RE: Workflow Configuration</TITLE>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.3059" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=166365215-01052007><FONT face=Arial
color=#0000ff size=2>Thanks Alon,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=166365215-01052007><FONT face=Arial
color=#0000ff size=2>The HR org objects are only created in Dev (never support)
and we ALE the HR org objects from HR to the ERP system.... keeps them in
synch nicely. :o)</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=166365215-01052007><FONT face=Arial
color=#0000ff size=2>Cheers,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=166365215-01052007><FONT face=Arial
color=#0000ff size=2>Sherie</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=166365215-01052007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=166365215-01052007><FONT face=Arial
color=#0000ff size=2>Sherie Munday</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=166365215-01052007><FONT face=Arial
color=#0000ff size=2>Workflow Developer/Analyst</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=166365215-01052007><FONT face=Arial
color=#0000ff size=2>Air Products & Chemicals, Inc.</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Alon Raskin<BR><B>Sent:</B>
Tuesday, May 01, 2007 11:49 AM<BR><B>To:</B> SAP Workflow Users'
Group<BR><B>Subject:</B> RE: Workflow Configuration<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV id=idOWAReplyText85282 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Just to further add to what
Mike had said, keep in mind number ranges for HR org Objects which may be
created in the two dev systems.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2></FONT> </DIV></DIV>
<DIV id=idSignature27460 dir=ltr>
<DIV><FONT color=#000000>
<DIV dir=ltr align=left>
<DIV dir=ltr align=left>
<DIV dir=ltr align=left><FONT face=Arial size=2>Alon</FONT></DIV>
<DIV dir=ltr align=left></FONT><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu on behalf of Mike
Pokraka<BR><B>Sent:</B> Tue 5/1/2007 10:20<BR><B>To:</B> SAP Workflow Users'
Group<BR><B>Subject:</B> RE: Workflow
Configuration<BR></FONT><BR></DIV></DIV></DIV></DIV></DIV>
<DIV>
<P><FONT size=2>Hi Sherie,<BR><BR>I would disagree here, because *especially*
for scenarios where you have<BR>two dev systems feeding into one it's critical
to have different number<BR>ranges. You may have been fortunate so far but if
you have a team of 7<BR>workflow developers working the same landscape the
numbers can easily get<BR>messy.<BR><BR>My strategy is something like 910 for
ECC, 911 for ECC support, 919 for<BR>ECC Sandpit (hey you may want to do a
manual transport at some point),<BR>920/921/929 for HR, 93n for CRM and so
on.<BR><BR>Just my thoughts...<BR>Cheers,<BR>Mike<BR><BR>On Tue, March 13, 2007
4:55 pm, Munday,Sherie J. wrote:<BR>> PB,<BR>> You really want to number
based upon your release strategy. We use 901 in<BR>> our HR system and
902 in our ERP system so that when we see a workflow<BR>> number we
automatically know in which instance it resides. We keep these<BR>>
same prefixes for both DEV and Prod Support (the only two systems in
which<BR>> we develop). The reason we do this is so that regardless of
which path we<BR>> are currently on the workflow will have the same number
when it reaches<BR>> prod. For example:<BR>><BR>> *<BR>>
In Dev we create workflow #90200037 and move it
through Integ and QA into<BR>> Production.<BR>> *<BR>>
Later our Dev to Prod path is closed for changes
and only used for a new<BR>> Release project. Perhaps we need to make a
quick change to the #90200037<BR>> design by adding a subflow. We would
make our change in ProdSupport. We<BR>> create the subflow in both Dev
and ProdSupport using the same number<BR>> sequence #90200038, and add it to
#90200037. The ProdSupport workflow is<BR>> quickly moved into
production. The Dev workflow is a good representation<BR>> of what is
in production so that any testing or Release changes are kept<BR>> in
synch. Eventually when the Release is moved into production, the
Dev<BR>> workflow will replace the ProdSupport workflow, but the numbers
remain<BR>> the same.<BR>><BR>> Thus whether you want to use the same
prefixes or different ones between<BR>> systems would depend upon your own
company's landscapes and release<BR>> strategy. This just happens to be
what works for us and keeps life<BR>> "simple".<BR>><BR>> Best
Wishes,<BR>> Sherie<BR>><BR>> Sherie Munday<BR>> SAP Workflow
Developer/Analyst<BR>> Air Products & Chemicals, Inc.<BR>><BR>>
________________________________<BR>><BR>> From: sap-wug-bounces@mit.edu
[<A href="mailto:sap-wug-bounces@mit.edu">mailto:sap-wug-bounces@mit.edu</A>] On
Behalf<BR>> Of praveen rajendran<BR>> Sent: Tuesday, March 13, 2007 9:47
AM<BR>> To: SAP Workflow Users' Group<BR>> Subject: Re: Workflow
Configuration<BR>><BR>><BR>> Thanks for the info Ronen...<BR>> but
I've have couple of doubts in this...<BR>> I've maintained the number ranges
like this, in the development system.<BR>> 999 for DEV<BR>> 900 fro
QA<BR>> 910 for PRD<BR>> Is this ok to do this just in Development system
or should i also do this<BR>> in QA and PRD???<BR>><BR>>
Secondly,<BR>> when I use report program RHMOVE30 to create
transport request for my<BR>> Org structure, Is that enough if I transport
Organization Unit in top<BR>> hierarchy and will those Org Units and
positions below automatically<BR>> included into that request or should
I add each Org unit one by one<BR>> into the request???<BR>><BR>>
Regards,<BR>> PB<BR>><BR>><BR>> On 3/8/07, ψεπο τεχρ
<ronenf@paz.co.il> wrote:<BR>><BR>>
Hello,<BR>> For the number prefix: there is no
real need to maintain this in your QA<BR>> & PROD environment since you
probably won't be doing any development in<BR>> those environment. you can
transport the prefix setting from DEV to those<BR>> systems just in order to
get a "green traffic light" in transaction SWU3<BR>> in those
systems.<BR>><BR>> Regarding org units and
positions: you can use report RHMOVE30 to<BR>> transport your org. structure
between systems. the reason you don't get a<BR>> change request prompt each
time you modify your org. plan in dev is<BR>> probably because the 'transport
link' for HR objects is deactivated in<BR>> your DEV system.<BR>><BR>>
Cheers,<BR>>
Ronen<BR>><BR>><BR>>
-----Original Message-----<BR>>
From:
sap-wug-bounces@mit.edu [mailto: sap-wug-bounces@mit.edu<BR>> <<A
href="mailto:sap-wug-bounces@mit.edu">mailto:sap-wug-bounces@mit.edu</A>> ]
On Behalf Of praveen rajendran<BR>>
Sent: Wednesday, March 07, 2007 10:47
PM<BR>>
To: SAP Workflow Users' Group<BR>>
Subject: Workflow Configuration<BR>><BR>><BR>>
Hi,<BR>>
We are implementing workflow
for our company. We did initial<BR>> configuration, Prefix number config and
stuffs. We are using 999 in<BR>> development system, should we use the same
in QA and production system<BR>> also?????<BR>>
We
have created simple organizational structure with various positions<BR>> and
users assigned to the positions. how to transport this Organization<BR>>
structure to QA and PRD systems?? Coz, we don see any transport requests<BR>>
for this.. even it didn't ask for saving in transport request when we<BR>>
created it. After transporting, will those position numbers be same as<BR>>
Position numbers in QA and subsequently PRD??? Because we have directly<BR>>
used these postions as agents in workflow tasks... Are we going in right<BR>>
track??? What can be other issues we might possibly run into???<BR>>
Thanks
for your help...<BR>><BR>>
Regards,<BR>>
PB<BR>><BR>><BR>>
_______________________________________________<BR>>
SAP-WUG mailing list<BR>>
SAP-WUG@mit.edu<BR>>
<A
href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR>><BR>><BR>><BR>><BR>><BR>><BR>>
--<BR>> Thanks and Regards,<BR>> Praveen Rajendran<BR>>
_______________________________________________<BR>> SAP-WUG mailing
list<BR>> SAP-WUG@mit.edu<BR>> <A
href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR>><BR><BR><BR>--<BR>Mike
Pokraka<BR>Senior Consultant<BR>Workflow Connections<BR>Mobile: +44(0)7786
910855<BR><BR>_______________________________________________<BR>SAP-WUG mailing
list<BR>SAP-WUG@mit.edu<BR><A
href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR></FONT></P></DIV></BODY></HTML>