workflow maintenance and enhancements

Tue May 4 09:00:30 EDT 2010

Hi Jocelyn,

Sorry to ask a silly question but what is the "CHARM transport process" ?

Regards
Nat Govender
Toyota South Africa
IT - SAP Workflow Specialist
Internal Ext.   :  32645
Direct Line    :  +27 031 910 2645
Fax               :  086 607 0414
E-mail           :  ngovender4 at toyota.co.za

If you tell the truth, you don't have to remember anything.

             "Dart, Jocelyn"                                               
             <jocelyn.dart at sap                                             
             .com>                                                      To 
             Sent by:                  "SAP Workflow Users' Group"         
             sap-wug-bounces at m         <sap-wug at mit.edu>                   
             it.edu                                                     cc 

                                                                   Subject 
             2010/05/04 01:38          RE: workflow maintenance and        
             AM                        enhancements                        

             Please respond to                                             
               "SAP Workflow                                               
               Users' Group"                                               
             <sap-wug at mit.edu>                                             

Hi Sue,
For something like this we would usually use parallel environments and use
the CHARM transport process to sort it out.
Essentially to control/automate the synchronization process as much as
possible.
This is one of those... "go talk to the basis guys" answers - sorry.
Regards,
Jocelyn

________________________________
From: sap-wug-bounces at mit.edu [sap-wug-bounces at mit.edu] On Behalf Of
Keohan, Susan - 1140 - MITLL [keohan at ll.mit.edu]
Sent: Saturday, 1 May 2010 12:56 AM
To: SAP Workflow Users' Group
Subject: RE: workflow maintenance and enhancements

Hi Sue, Gayathri,

I do understand this dilemma – we go thru it every time we upgrade or apply
major support packs.  We get a ‘prime’ Dev environment in which we do
production support, and then we get the upgrade environment in which we do
enhancements.  It’s a beast.

I was not taking that – the ‘upgrade factor’ – into consideration.  Call it
selective amnesia.

As far as I know copying the WFs and trying to keep both versions in sync
is the only way to do this.  Of course, in my own perfect little world
(imaginary) we would not have to do this kind of thing :)

Thanks for bringing me back to reality on a Friday,
Sue

----
Susan R. Keohan
SAP Workflow Specialist
Enterprise Applications
Information Services Department
MIT Lincoln Laboratory
244 Wood Street, LI-200
Lexington, MA. 02420
781-981-3561
keohan at LL.MIT.EDU

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Sue Doughty
Sent: Friday, April 30, 2010 10:47 AM
To: 'SAP Workflow Users' Group'
Subject: RE: workflow maintenance and enhancements

Hi Sue,

I can understand Gayathri’s issue.

I’m currently working on a six month project that involves changes to the
system done by another group, plus workflow changes to an existing
workflow.  While this six month project is going on we need to have a path
to production to be able to send fixes (if they occur) for the existing
workflow while we are in development on the project.

The only way I knew to do that was to make a copy of the existing workflow
in which I am making the project changes.  If any fixes need to be done
before the project goes to PRD, I’ll have to make changes in both workflows
to keep everything in sync.  It is challenging.

There is no other way to do that, is there?

Regards,
Sue

________________________________
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Keohan, Susan - 1140 - MITLL
Sent: Friday, April 30, 2010 10:18 AM
To: SAP Workflow Users' Group
Subject: RE: workflow maintenance and enhancements

Hi Gayathri,
I would not try to simultaneously fix productive workflows and also do
enhancements – unless you are planning on all of these
corrections/enhancements going to the same place at the same time.
Personally, I would fix the issue with production, transport up, and then
generate a new version of the workflow in your Dev environment and begin
the enhancements.

Having said that, you could, of course, copy the productive workflow to
another workflow template, allowing you to do the fixes in the original
template, and the enhancements in the copied template.  I would hate to
have to coordinate that development effort though.

Just my 2p,
Sue

----
Susan R. Keohan
SAP Workflow Specialist
Enterprise Applications
Information Services Department
MIT Lincoln Laboratory
244 Wood Street, LI-200
Lexington, MA. 02420
781-981-3561
keohan at LL.MIT.EDU

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Gayathri Shivakumar
Sent: Friday, April 30, 2010 8:25 AM
To: sap-wug at mit.edu
Subject: workflow maintenance and enhancements

HI experts,

What is the best way to handle simultaneously fixes to a production
workflow and also work on enhancements to the same workflow ?

Regards,
Gayathri

Yazaki North America, Inc. - Confidentiality & Security Notice

________________________________
This email is intended only for the person or entity to which it is
addressed and may contain confidential, proprietary and/or privileged
material. Any review, distribution, reliance on, or other use of this
information by persons or entities other than the intended recipient is
prohibited. If you receive this message in error, please immediately notify
the sender and delete it and all copies of it from your system.

Visitors are prohibited from taking pictures or video at anytime in YNA or
its affiliated company facilities unless prior authorization is obtained
from facilities management.

Thank you.

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

******************************************************************

This e-mail is a privileged and private communication and may be
read, copied and used only by the intended recipient(s). If you are
not an intended recipient, please inform the sender by return
e-mail with the subject heading "Received in error". Please then
delete the e-mail; destroy any copies of it and do not disclose its
contents to any person or entity. If you are not the intended
recipient, note that any disclosure, copying, distribution or any
action taken or omitted to be taken in reliance on it, is strictly
prohibited and may be unlawful. Neither the sender nor Toyota South
Africa Motors (Pty) Ltd accepts any liability whatsoever as a
result of the further dissemination of this e-mail. 

Toyota South Africa Motors (Pty) Ltd does not guarantee that e-mail
communications are secure or error-free, as information could be
intercepted, corrupted, amended, lost, destroyed, arrive late or
incomplete, or contain viruses. 

******************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20100504/bb8548bb/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20100504/bb8548bb/attachment.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic09758.gif
Type: image/gif
Size: 1255 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20100504/bb8548bb/attachment-0001.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ecblank.gif
Type: image/gif
Size: 45 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20100504/bb8548bb/attachment-0002.gif