workflow maintenance and enhancements

Mon May 3 10:22:37 EDT 2010

Thanks for the replies. Would using a newer version of the workflow for enhancement and keeping the production version for fixes work ? How does versioning affect transports. Can I maintain different transports for different versions ? Will this be better than maintain 2 different templates ? In our environment do not have a separate client to perform fixes.

Regards,

Gayathri

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

Here is how we do it, I figured most organizations on SAP would have something similar ... so much for figuring! 

In ECC, we have a DE (development), QE (quality assurance/testing), PE (production), and FE ( I guess the F is for "fixes") clients. 

The standard transport path is from DE to QE then from QE to PE/FE. 

FE is a redundant environment that is used solely for hot fixes. It is never accessed by end users. It is solely for hot fixes that need to go directly to PE.  Changes to FE are only transported to PE and no other client.  Any changes made to FE requires incorporation into transports from DE or they will be lost. 

If you find this useful and need more detail, I will be happy to provide. 

Berry Martin
IS Professional

Berry.Martin at Milliken.com <mailto:Berry.Martin at Milliken.com> 
864.503.2261 office
864.503.2444 fax
864.923.3529 cell 

From: 

"Keohan, Susan - 1140 - MITLL" <keohan at ll.mit.edu> 

To: 

"SAP Workflow Users' Group" <sap-wug at MIT.EDU> 

Date: 

04/30/2010 11:04 AM 

Subject: 

RE: workflow maintenance and enhancements 

Sent by: 

sap-wug-bounces at MIT.EDU

________________________________

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 J 

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 <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 <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 <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 <http://mailman.mit.edu/mailman/listinfo/sap-wug> 

________________________________

**** Confidentiality and Commercial Terms and Conditions Notice: *****
Privileged/Confidential information may be contained in this message
and is intended only for the use of the addressee. Please advise
immediately if you or your employer do not consent to Internet e-mail
for messages of this kind. If you are not the addressee, or person
responsible for delivering to the person addressed, you may not copy or
deliver this to anyone else. If you receive this message by mistake,
please notify the sender immediately by return e-mail. All commercial
transactions, offers and acceptances are exclusively subject/limited to
and conditioned upon our terms posted at www.milliken.com/terms,
and we object to and reject any of your additional/different terms and
conditions unless we expressly agree to them in a signed writing. 
Thank you.
*********************************************************************** 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20100503/a06cf32e/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 10695 bytes
Desc: image001.jpg
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20100503/a06cf32e/attachment.jpg